Netmail Archive 5.2 Installation Guide for Microsoft Exchange

Transcription

1 Netmail Archive 5.2 Installation Guide for Microsoft Exchange

2 Netmail Archive Installation Guide for Microsoft Exchange Netmail Archive is an enterprise-class electronic messaging solution that helps organizations address their current and future challenges of archiving, retention, regulatory compliance, and fast retrieval of messages. Netmail Archive integrates seamlessly and transparently into your corporate system, improves server performance, lowers storage costs, and offers you the tools to individually or globally search archived messages in aid of legal discovery, regulatory compliance, or organizational policy enforcement. Netmail Archive adds value to your messaging collaboration system by providing secure, centralized archiving and retrieval of information. These services are controlled by policies that allow organizations to define their rules for information retention centrally. The Netmail Archive solution addresses an organization s long-term archiving requirements by managing and maintaining a platform-independent external XML data repository featuring storage management, access management, and full Information Lifecycle Management (ILM) capabilities to classify, manage, retain, migrate, and dispose of records ensuring maximum uptime and enhanced performance for your system. Table of Contents Introducing Netmail Archive About Microsoft Exchange Netmail Archive Deployment Scenarios Netmail Archive Feature Overview Component Overview Overall Installation Sequence Documentation List Netmail Archive Master Node System Requirements Pre-Installation Tasks for an Exchange Deployment Installing the Netmail Archive Master Node in an Exchange Environment Post-Installation Tasks for Exchange Indexing Node(s) Server Requirements Pre-Installation Tasks Installing the Index Server Start the Index Service Run the Cluster Manager Tool Configure Archive Server to Index Server Communications Index Conversion Using the Index Server Administration Console Netmail Archive Worker Node(s) Installing Worker Node(s) in an Exchange Environment Post-Installation Tasks for Worker Nodes Set Up End-User Archive Access with the Outlook Client Install Netmail IIS Extensions Install the Netmail Archive Outlook Add-In Run the Outlook Add-In on End-User Workstations Using the Netmail Archive Outlook Add-In for the First Time Install the Remote Provider(s) for Netmail Search, the Outlook Add-In, and OWA Installing the Remote Provider(s) Remote Provider Post-Installation Tasks Configuring Netmail Search Appendix A - Rebuilding the PostgreSQL Database Appendix B - Preserving Data & System Integrity of Netmail Archive Appendix C - Netmail Archive and Anti-virus Software 2 Copyright 2013, Messaging Architects. Updated: 10/05/2013

3 Introducing Netmail Archive In this section: About Microsoft Exchange Netmail Archive Deployment Scenarios Netmail Archive Feature Overview Component Overview Overall Installation Sequence Documentation List About Microsoft Exchange Microsoft Exchange is a messaging and collaboration system that supports , calendaring, task management, and contact management. Netmail Archive adds value to your Exchange system by providing secure, centralized archiving and retrieval of information. In an Exchange environment, the Netmail Archive system is responsible for extracting information from Exchange, indexing XML content thus created, exporting content from the archive repository, and running grooming and deletion jobs on the archive repository. The Netmail Archive system is also capable of converting the contents of PST files into XML format. PST files are used to store native copies of messages, calendar events, and other items within Microsoft software (such as Outlook), freeing up storage space on the users mail server. It may be beneficial to perform PST Import when first deploying Netmail Archive so that all archives, including native Exchange archives, are consolidated in the central repository. To attain 100% retention of from your Exchange system, the Exchange journaling feature can be used. It is important to understand the difference between journaling and archiving. Journaling is the ability to record all communications; archiving refers to reducing the strain of storing data by backing it up, removing it from its native environment, and storing it elsewhere. In Netmail Archive, you can archive the Exchange Journal Account to attain 100% retention. By archiving this account, you can be sure that all data has been archived, even if individual account data has been deleted within the Exchange system. Microsoft Exchange offers message-only journaling and envelope journaling. Message-only journaling captures all messages from users on a specific mailbox database and sends the message copy to a specified journaling mailbox. Envelope journaling is different from message-only journaling in that it allows you to archive P1 message headers (envelope headers). This includes information about the recipients, including BCC recipients and recipients from distribution groups. Due to the limitations of message-only journaling, you should enable envelope journaling to attain 100% retention with Netmail Archive. Note: Messaging Architects recommends that you use Exchange envelope journaling as a useful tool in your overall retention strategy. Netmail Archive Deployment Scenarios Integrating seamlessly and transparently into the system, Netmail Archive frees up server space, improves server performance, and ensures fast retrieval of archived and attachments. Netmail Archive allows administrators to enforce flexible policies without breaching privacy and freedom of information rights, and at the same time, to tackle an exponentially growing volume of electronic data by easily integrating with a number of third-party storage systems. The number of servers required for your Netmail Archive deployment will vary depending on a number of factors, such as: Number of users Quantity of new daily messages to process Average size of attachments to process Records retention policy (size of archive indexes) Frequency of Archival access Archiving frequency (every day or every second day) Information Lifecycle Management jobs Messaging Servers Netmail Archive supports the following messaging servers: GroupWise 3 Copyright 2013, Messaging Architects. Updated: 10/05/2013

4 In a GroupWise environment, the Netmail Archive system is responsible for extracting information from GroupWise, indexing XML content, exporting content from the data repository to various output formats, and running grooming and deletion jobs on the archive repository. The Netmail Archive server requires a Windows 2003 Server or a Windows 2008 Server. A single Netmail Archive server should be able to effectively archive more than 500,000 items in less than 24 hours. Note: Netmail Archive integrates with GroupWise via SOAP API or Object API. Stubbing functionality requires SOAP API integration. Exchange In an Exchange environment, the Netmail Archive server is responsible for extracting information from Exchange, indexing XML content, exporting content from the data repository, and running grooming and deletion jobs on the archive repository. The Netmail Archive server requires a Windows 2003 Server or a Windows 2008 Server. A single Netmail Archive server should be able to effectively archive more than 500,000 items in less than 24 hours. Note: Netmail Archive integrates with both Exchange 2007 and Exchange 2010 via EWS. Mixed GroupWise and Exchange Environment With Netmail Archive, you can also use a mixed messaging and collaboration system if you are currently running both GroupWise and Exchange in your environment or if you are planning a migration from your current server to an alternate server in the near future. Multiple Node Deployment and Clustering To provide organizations with a robust solution that is scalable and fault tolerant, Netmail Archive supports clustering and load-balancing to enable multiple servers to work together. Netmail Archive is configured to automatically detect any additional nodes and cluster together for maximum performance and uptime. Within a cluster, the Master node will automatically detect the current load of any of the Worker nodes in the cluster and distribute the workload between the nodes accordingly to better utilize system resources. The following figure illustrates how Netmail Archive functions in a multiple node deployment scenario: Through the Netmail Archive Administration Console, archiving jobs are defined and stored in edirectory. The Master node scans edirectory and executes jobs based on their schedules. When executing a job, the Master node allocates work across the available nodes in the cluster. The nodes query the messaging servers for data. Data is then sent to the nodes from the messaging server for processing through Netmail Archive. After processing, Netmail Archive converts the data to XML format and writes the data to the storage system. The nodes also signal the Index Server to read the data and index the contents. 4 Copyright 2013, Messaging Architects. Updated: 10/05/2013

5 Netmail Archive can help you respond to ediscovery requests quickly and cost-effectively and significantly reduce your risk and liability. The Netmail Archive solution helps organizations proactively gather, restore, search, organize, and deliver and other records for litigation discovery and regulatory investigations. Netmail Archive s high performance archiving capabilities quickly archive and index selected electronic records that are easily transferred to a choice of media for storage. With Netmail Archive s sophisticated new indexing and powerful search tools, archived and other electronic records can be located and accessed instantly from any web browser where approved users can search, review, view, and organize these electronic assets as required. Pre-planning is an important step to consider when planning your Index Server deployment. The number of Index Servers required for your Netmail Archive deployment will vary depending on a number of factors. For example, as the volume of increases, you should take into consideration the number of messages you expect to index. Also, performance is proportional to the number of spindles available to the Index Server. A basic Index Server should have four disks or more to store the index. A single Netmail Archive Index Server should be able to index between 50 and 75 million documents. For more information on installing the Index Server, see Installing the Index Server. Netmail Archive Feature Overview Netmail Archive provides a set of tools which enable the user to proactively address three key concerns: policy-based retention/deletion, full Information Lifecycle Management, and long-term data accessibility and portability. Policy-Based Retention Presently, regulated industries require the retention of documents and records, including . Best practices suggest that enforcing a corporate policy by extracting information and retaining it according to relevant business drivers is the best approach to tackling regulatory compliance. Moreover, a corporate-wide retention policy ensures reliable protection of corporate records and preparedness for legal discovery. It also increases employee productivity by reducing the time spent managing individual mailboxes. Netmail Archive supports enhanced SEC 17.4 compliancy for storage of data on WORM media through integration with storage solutions, such as NetApp storage systems from Network Appliance, Inc., the Hitachi Content Archive Platform (HCAP), and hardware-agnostic Netmail Store storage software. Messages can be tagged by Netmail Archive with retention dates that deny the capabilities of modifying or deleting these messages until after the retention date has been reached. Netmail Archive addresses regulatory compliance through a robust feature set and capabilities that offer: The option of pre-defined policies for automated archiving of single or multiple accounts following industry regulations. Transparent implementation of corporate electronic data retention policies. The option of 100% retention of all account information, including user deleted s. Real-time auditing to meet even the most stringent regulatory obligations. A set of tools for search and discovery of messages and attachments. Flexible storage options supporting any Windows CIFS-conformant storage solution, including magnetic, optical disks, Storage Area Network (SAN), Network Attached Storage (NAS), and Content Addressed Storage (CAS). Full Information Lifecycle Management Netmail Archive provides administrators with a complete Information Lifecycle Management solution to deploy and manage more effective retention and archiving policies to reduce current storage requirements and database sizes. It provides organizations with the ability to improve their collaboration system performance and reliability, as well as reduce their storage costs and recovery times in the event of system failure. By deploying Information Lifecycle Management policies, organizations can more effectively manage their archive store(s) through grooming and deletion. Long-Term Data Accessibility and Portability More and more, is becoming a source of legal documentation and this affects how industries approach long-term electronic data management. Organizations mandated to recover for legal discovery can no longer rely on backup tapes and personal archives. Netmail Archive stores corporate archives in a way that offers their easy and quick retrieval. The wide range of search functions for auditing and record retrieval enables you to perform search and discovery of content and records with granular control that greatly facilitates the process of legal discovery. Netmail Archive lowers the cost of system administration and the time required to recover messages. This feature ensures total compliance with SEC regulations in that it stores information to Read-only media. In other words, files are exported in a non-modifiable and undeletable state until a specified retention date is reached. Message discovery options include: Global search of single or multiple mailboxes Standard content, subject, date, and address searches Attachment search Refined searches Enhanced Proximity, Wordlist, and Approximate Spelling searches Audit trail searches 5 Copyright 2013, Messaging Architects. Updated: 10/05/2013

6 All searches are performed on archives containing mail messages, appointments, tasks, notes, and attachments. Electronic messages are exported to a platform-independent repository to ensure portability and ease of discovery in system-independent XML format. Netmail Archive offers Single Instance Storage (SIS), which enables the storage of a single copy of any archived message attachment. In a non-sis archiving environment, every archived message attachment is stored, even if the attachments are identical. SIS reduces storage costs by storing only a single copy of identical attachments. In Netmail Archive, SIS is implemented at the application level, so organizations benefit from this feature regardless of their storage integration. Component Overview Netmail Archive is modular and consists of several components that can be implemented depending on your needs. Netmail Administration Console The Netmail Administration Console includes the main administrative interface of Netmail Archive. It is a flexible and intuitive web-based application that allows administrators to configure Netmail Archive, create policies, and run jobs. Upon login, administrators can access system information, view and configure Master and Worker nodes, and view, modify and/or create policies and jobs through the various available job agents. Policy Engine The Policy Engine is the back-end component that creates, organizes, and manages policies within Netmail Archive. The Policy Engine facilitates the implementation of corporate-wide retention, storage, and compliance management by using pre-defined policies. With the policy engine, you can create archiving policies that truly meet your organization s needs. Policies contain specific criteria which are then applied to various Job Agents in the Netmail Administration Console. Polices may be as simple or as complex as your business needs dictate, and because Netmail Archive gives you flexible control over the organization s policies, you can always amend existing policies or create new ones as your business needs change. With the Policy Engine, system administrators can: Create policies for automated archiving and exporting of single or multiple accounts dependent on industry regulations. Schedule archiving and/or storage tasks to run automatically at regular intervals. Send notifications upon completion of the policy-driven archiving, exporting, indexing, and information lifecycle management processes. Create a task process to securely copy and convert messages and attachments from existing mailboxes and archives into ASCII form based on the XML format. Archive Agent The Archive Agent is the main component of Netmail Archive. With the Archive Agent, administrators can create archiving jobs to move any information held in your system s message store, such as messages, calendar information, and any attachments, to an external repository in XML format. The Archive Agent provides more granular archiving to XML by allowing enhanced criteria searching including advanced date selection and message property options. With the Archive Agent, you can: Deploy and enforce corporate-wide retention, storage, and compliance management policies by using pre-defined archiving tasks. Implement policies for automated archiving of single or multiple accounts according to industry regulations. Schedule archiving tasks that are executed automatically at regular intervals. Perform tasks with the option of including personal address books. Send notifications automatically upon completion of the archiving process. Gather and convert messages stored in PST files into XML format for archiving. Export Agent The Export Agent gives organizations the ability to create specific jobs to export (or copy) the contents of their XML repositories for various purposes (e.g., the provision of selected information to an external auditor. With the Export Agent, you can: Execute jobs, in conjunction with Netmail Search, to export selected items from their archive to PST, PDF, or Searchable XML format, ready for provision to any third party. Execute jobs to export archived content from one XML repository to another, for storage management or retention policy purposes. Send notifications automatically upon completion of the export job. Group Agent The Group Agent allows you to schedule a series of jobs to run consecutively. The Group Agent helps you make intelligent scheduling decisions by allowing you to configure consecutive jobs to run automatically, removing the need for constant administrator intervention. 6 Copyright 2013, Messaging Architects. Updated: 10/05/2013

7 Information Lifecycle Management (ILM) Agent The ILM Agent provides organizations with the ability to deploy full information lifecycle management policies to address their long-term records retention and records management needs. Using pre-defined ILM policies, organizations can better manage their XML repositories. With the ILM Agent, you can: Apply file grooming policies to automatically move selected data to an alternate storage location, such as a network-attached storage (NAS) device, to maximize storage performance while minimizing costs. Enforce ILM policies to expire messages that have reached the retention period defined by the policy. Send notifications upon completion of ILM processes. Index Agent The Index Agent allows organizations to create separate Index Jobs for your XML repositories rather than having the indexing completed by the archiving job. This can be used to improve archiving performance, as well as process more concurrent users. With the Index Agent, you can create: Scheduled tasks to specify the type of indexing you wish to perform, such as incremental indexing. Tasks to recreate indexes, or convert existing indexes in XML format and re-index. Relationships between indexing tasks and specific archiving jobs. Notifications upon completion of indexing tasks. Migration Agent The Migration Agent can be used by organizations to facilitate migration from a GroupWise system to an Exchange platform. In conjunction with the Archive Agent and the GroupWise to Exchange Provisioning Utility, the Migration Agent assures constant accessibility of data to ensure a seamless migration between systems. With the Migration Agent, you can: Create tasks to migrate data from the original system to the Exchange system. Create and customize tasks to migrate data into the live Exchange system or into the Exchange archive location. Create tasks to recover items archived from Exchange and inject them back into the live Exchange system. Strip attachments before they even enter the Exchange system. Attachment Stripping Agent The Attachment Stripping Agent allows you to strip attachments from messages in Exchange and store a single copy of each stripped attachment in Netmail Store. Stripped attachments are replaced by links that point to the attachments in Netmail Store. With the Attachments Stripping Agent, you can: Create tasks to strip attachments from messages in either the Exchange Primary Mailbox or Archive Mailbox, or both. Set an expiration date for stripped attachments, after which they are deleted and can no longer be viewed. Create tasks to re-attach attachments in their original format to their respective messages. Utility Agent The Utility Agent allows you to perform various maintenance tasks on the mail system, including folder management and mailbox reduction, and on the XML store. With the Utility Agent, you can: Deploy enterprise-wide management policies to create user folder structures in the corporate system mailboxes. Assist in implementing your retention policy by performing tasks to delete messages from your Exchange system or from PST files based on specified criteria. Delete attachments in the XML SIS store that no longer need to be saved. Apply tools to convert legacy GWArchive data into a format that is readable by the current version of Netmail Archive. Send notifications upon completion of maintenance tasks. Create tasks to import PST files and relocate them to a specified destination folder in preparation for archiving their contents. Netmail Search Netmail Search is an advanced ediscovery tool that allows administrators to intelligently view and manage their archived data through advanced search features and guided navigation. The tool s search functions include the ability to search for both message and attachment attributes. Advanced search features allow for word list usage, exact phrase matching, forbidden term searching, approximate spelling matching, and more. Administrators may also build their own search queries, meaning they are never limited to default search criteria. Guided navigation lets users filter search results for easy viewing and auditing, and commenting and tagging features let administrators note the relevance of specific data. 7 Copyright 2013, Messaging Architects. Updated: 10/05/2013

8 Netmail Search employs a case management organizational system. Upon logging into Netmail Search, administrators are greeted with a Case Management Dashboard that lets them create and manage multiple cases. Through this case management system, administrators can respond to any and all ediscovery requests simultaneously and are spared the headache of sifting through all archived data each time an ediscovery request is made. Advanced search options and guided navigation, plus the logic of case management, are delivered to administrators in an easy-to-use, intuitive web-based interface. GroupWise to Exchange Provisioning Utility The GroupWise to Exchange Provisioning Utility is a standalone tool that is designed to help organizations migrate from a GroupWise platform to Exchange 2010 On-premise or Online. The Provisioning Utility migrates user accounts and distribution lists. The migration of the actual data ( , calendar items, etc.) is handled by Netmail Archive. Indexing Server The Indexing Server is the component that makes ediscovery possible. This highly advanced piece of technology acts, within the platform, as the creator of the index of all messages and attachments archived by the system. It is also responsible for processing the search queries (which are applied against that same index) whenever users seek specific content from the archive. This dual functionality is accessed through jobs in the Netmail Administration Console for the indexing part, and through the web-based search interface Netmail Search. In Netmail Search, guided navigation and query creation allow administrators to search and sort search results by date, size, or relevance, as well as to refine results by excluding irrelevant locations, dates, files, or authors. Outlook Add-In The Netmail Archive Outlook Add-In provides seamless end-user access to archived items through the Outlook client, both via stubs and by providing direct access to the full archive mailbox using an embedded Netmail Search interface. OWA ISAPI Extensions The Netmail Archive OWA ISAPI Extensions are installed to your Exchange OWA CAS servers and provide seamless end-user access to archived items through the Outlook Web App (OWA) client interface, both via stubs and by providing direct access to the full archive mailbox using an embedded Netmail Search interface. Remote Provider The Remote Provider is a little-known and barely visible component of the Netmail Archive solution, but an important one when it comes to user access to the archived items. This component receives the requests for information (queries) from Netmail Search, the Outlook Add-In, or the OWA ISAPI extensions, and passes them on to the Index Server for processing. It then re-packages the results for presentation by the appropriate client. When a user selects a specific archived item (message or attachment or audit file) to display in Netmail Search, or via the Outlook Add-In or OWA archive interfaces, it is also the Remote Provider that fetches the data from the archive and presents it in the appropriate client. Overall Installation Sequence For a typical deployment of the Netmail Archive solution, a number of components need to be installed and/or configured to ensure effective and proper functionality of the archiving system. The following is an outline of the overall installation procedure for the entire Netmail Archive system: Verify that the system requirements are met on all servers and/or VMs Install and configure the Netmail Archive Master node Install and configure the Indexing node(s) Install the Worker node(s) (if applicable) Install and configure the Remote Provider(s) for Netmail Search, Outlook Add-In, and Outlook Web App access Documentation List The Netmail Archive Installation Guide and the Netmail Archive Administration Guide combine to explain how to install and configure the Netmail Archive Server and Web components, as well as various helpful administrative utilities. After installing and configuring Netmail Archive with the help of this guide, refer to the Netmail Archive Administration Guide to learn how to easily use the Netmail Administration Console to create retention and archiving policies and schedule archiving jobs. Below is a brief description of the components of Netmail Archive and the documentation available for each. The documentation listed below can be found in the Messaging Architects Documentation folder in the Netmail Archive package. Component Description Available Documentation 8 Copyright 2013, Messaging Architects. Updated: 10/05/2013

9 Netmail Administration Console Policies Archive Agent Migration Agent Export Agent Group Agent ILM Agent Index Agent Attachment Stripping Agent Utility Agent Netmail Search for ediscovery Netmail Search for End Users A web-based administrative interface that allows for configuration and management of policies and jobs, as well as configuration and monitoring of the Netmail Archive system. Criteria filters used by jobs to determine which items they will act upon. Allows administrators to create archiving jobs to move any information held in your system s message store to an external XML repository. Allows administrators to migrate their GroupWise data to Exchange or to perform an Exchange Recovery. Gives organizations the ability to create specific policies to export the contents of their XML repositories to external media of various sizes. Allows administrators to schedule a series of jobs to run consecutively. Allows organizations to deploy full information lifecycle management policies to address their long-term records retention and records management needs. Allows organizations to create separate Index Job for their XML repositories rather than having the indexing completed by the archiving job. Allows administrators to strip message attachments and replace them with HTTP links to the original copies in Netmail Store. Allows administrators to perform various maintenance tasks on the Exchange message store or the XML repositories. A powerful web-based ediscovery tool that offers several advanced search capabilities to allow administrators to find and manage relevant information quickly and efficiently. A powerful web-based ediscovery tool that offers several advanced search capabilities to allow end users to easily search and manage their personal archives. Netmail Archive Installation Guide and Netmai l Archive Administration Guide Netmail Archive Administration Guide Netmail Archive Administration Guide Netmail Archive Administration Guide Netmail Archive Administration Guide Netmail Archive Administration Guide Netmail Archive Administration Guide Netmail Archive Administration Guide Netmail Archive Administration Guide Netmail Archive Administration Guide Netmail Search User Guide for ediscovery Netmail Search User Guide & Netmail Search User Guide for External Reviewers Indexing Server Remote Provider Creates the index of all messages and attachments archived by the system and processes users search queries. Receives information requests from Netmail Search, sends them to the Index Server for processing, and prepares the results for viewing in Netmail Search. Netmail Archive Installation Guide Netmail Archive Installation Guide 9 Copyright 2013, Messaging Architects. Updated: 10/05/2013

10 Netmail Archive Master Node A successful installation of Netmail Archive requires the step-by-step completion of the following steps. Once all the procedures outlined below have been carried out in the appropriate order, you will be able to implement policy-based retention within your organization. Installing Netmail Archive System Requirements Meet Hardware and Software Requirements Verify the Secondary Logon Service is Running on the Server Install Outlook Client (for exporting to PST format) Pre-installation Tasks Configure User Accounts and Rights Configure Exchange Impersonation (EWS) Verify.NET Framework 4.0 is Installed edirectory Access Install Java Runtime Environment bit (on the Archive node) Choose your SQL-Based Logging Database Netmail Archive Installation Deploy Netmail Archive Start Netmail Archive Services Post-installation Tasks Launch the Administrative Console and Log In Update the Address Book Cache Verify Netmail Archive Licensing Configure Web Browser for Index Server Communications System Requirements For a successful installation of Netmail Archive and optimum expected performance of the solution, ensure that your servers or VMs have been built according to the minimum recommended system requirements. For the most up-to-date system information and requirements, please refer to System Requirements for Netmail Archive or contact Messaging Architects. Furthermore, ensure that the following miscellaneous prerequisites are met before proceeding with the pre-installation tasks: Miscellaneous Prerequisites Anti-Virus Software Management Software Windows Firewall Turn OFF all AV Software until the Netmail Archive software is installed and validated Do not install any management software, including Manufacturer monitoring or Backup software Turn OFF firewall 10 Copyright 2013, Messaging Architects. Updated: 10/05/2013

11 User Access Control DEP Settings Windows Policies Turn off UAC Turn on for Essential Windows Services only Do NOT apply policies Pre-Installation Tasks for an Exchange Deployment The following list of requirements must be met before installing Netmail Archive in an Exchange environment. User Accounts and Rights In order to provide Netmail Archive with the required levels of access to your Active Directory (AD) and Exchange System, it is necessary to create dedicated service accounts in Active Directory and Exchange for Netmail Archive use. During the installation of Netmail Archive, these accounts are referred to as the Active Directory Administrator and the Exchange Administrator accounts, but they do not require full administrative rights. Once installed, Netmail Archive refers to these accounts as the AD User and EX User accounts. These two roles can be fulfilled by a single AD account with a mailbox as explained below. In terms of required rights, the only AD rights required by the service account are read rights to objects in the AD forest, which allow this account to be used for LDAP lookups against AD. These rights are the default for a standard user account in AD. For Exchange, Netmail Archive makes use of Exchange Web Services (EWS) to access mailboxes for archiving and other purposes. In addition, Netmail Archive requires an actual mailbox in Exchange in order to compile and send notification s. The simplest way of providing all of the required levels of access is to create a single AD service account, perhaps named nmarchive for identification purposes, create an Exchange mailbox for this account, and grant the required EWS permissions to it, as detailed in the next section. In addition to AD and Exchange access, Netmail Archive needs to run various Windows services on the Netmail Archive servers. Some of these services are required to run as an account which has both local administrative rights on the server where the services are running and file system rights to locations being used for archive storage. This is most easily achieved by adding the dedicated service account created for AD and Exchange access, as outlined above, to the local Administrator groups of the Netmail Archive server(s). Some organizational policies may restrict the use of a single domain account in this way. In such cases, you will have to create a dedicated service account plus other accounts dedicated as local administrators that will be used for running services. A single domain account, however, should suffice in the majority of cases. Configuring Exchange Impersonation (EWS) EWS (Exchange Web Services) is used by Netmail Archive to access both Exchange 2007 and 2010 and requires Exchange Impersonation to be configured. Exchange Impersonation enables Netmail Archive to use the dedicated service account you created for it to impersonate any other Exchange account in order to access mailboxes for archiving and other purposes. Configuring Impersonation on Exchange 2010 To configure the dedicated service account you created for Netmail Archive with Impersonation rights, complete the following steps on an Exchange CAS server: Note: The following standard Exchange 2010 prerequisites are required to carry out the configuration of Exchange Impersonation: - You must be logged in with Administrative credentials for the CAS server. - You must have Domain Administrator credentials, or other credentials with the permission to create and assign Exchange roles and scopes. - Remote PowerShell must be installed on the computer from which you will run the commands. 1. Open the Exchange Management Shell. 2. Run the New-ManagementRoleAssignment cmdlet to add impersonation permission to the specified user. The following example shows how to configure Exchange Impersonation to enable a service account named nmarchive in a domain called mydom to impersonate all other users in an organization. New-ManagementRoleAssignment -Name:NMArchiveImpersonation Role:ApplicationImpersonation User mydom\nmarchive" 11 Copyright 2013, Messaging Architects. Updated: 10/05/2013

12 Note: The Name attribute in this command is used purely as a label for this role within the Exchange role based access control (RBAC) roles list. Any string can be used. For more information about Exchange Server 2010, visit Configuring Impersonation on Exchange 2007 For Exchange 2007, the process is more complicated. First, we need to use the ms-exch-epi-impersonation permission to give the service account the ability to submit an impersonation call through each Client Access Server. To apply this to the service account against all your CAS servers, use the following Exchange Management Shell command: Get-ExchangeServer where {$_.IsClientAccessServer -eq $TRUE} ForEach-Object {Add-ADPermission -Identity $_.distinguishedname -User (Get-User -Identity nmarchive select-object).identity -extendedright ms-exch-epi-impersonation} where nmarchive is the name of the service account used for Netmail Archive. Now we must also use the ms-exch-epi-may-impersonate permission to grant the service account access to specific mailboxes or to all mailboxes in a mailbox database. To apply this for the service account against all current mailbox databases use the following Exchange Management Shell command: Get-MailboxDatabase ForEach-Object {Add-ADPermission -Identity $_.DistinguishedName -User nmarchive -ExtendedRight ms-exch-epi-may-impersonate} Note: In Exchange 2007, the dedicated service account cannot be a member of any Exchange administrative group, as the ms-exch-epi-impersonation permission is explicitly denied to those groups. For Exchange 2007, the requirement to add permissions for specific CAS servers and user mailboxes means that if new message databases or CAS servers are added to the Exchange infrastructure, these Impersonation rights will need to be update d for the new components. For more information about configuring Exchange Impersonation for Exchange Server 2007, visit 5%28EXCHG.80%29.aspx..NET Framework Verify that Microsoft.NET Framework version 4.0 is installed. To verify that Microsoft.NET Framework is installed, navigate to the Control Panel and launch the Add and Remove Programs function. In the list of currently installed programs, look for Microsoft.NET Framework 4.0. If Microsoft.NET Framework version 4.0 is not installed, the program is available for download from edirectory Access Netmail Archive is a distributed system involving several servers. As such, a mechanism is needed to store its configuration information while allowing access from all servers. In addition, the Archive Servers of a Netmail Archive system operate in a cluster, where one server can take over from another in the case of a failure. As such, a configuration store that can also be distributed to allow for such failure scenarios is needed. To achieve this, Netmail Archive makes use of the freely available edirectory directory services system form Novell. Netmail Archive can either store its configuration in any existing edirectory tree in the organization, or a new dedicated edirectory tree can be deployed on the Netmail Archive servers themselves. Note: Future versions of Netmail Archive may support the use of other directory services, such as OpenLDAP, but for now, edirectory is a requirement. Messaging Architects recommends the use of Novell edirectory 8.8 SP7 for Windows or higher. Full instructions on installing a dedicated edirectory tree to the Netmail Archive servers can be obtained from ocumentation/edir88/. The current edirectory download for Windows is available at Initially, edirectory access is used during installation for extending the edirectory schema and creating the Netmail Archive configuration objects. Once operational, Netmail Archive requires edirectory access only for storing and reading its configuration. As such, Messaging Architects recommends the creation of a dedicated Netmail Archive edirectory user account. For during the installation period, this account will need full administrative rights to the edirectory tree (in order to extend the schema and create the initial objects). Thereafter, however, the account will only require administrative rights granted to the container where the Netmail Archive objects are stored. These account requirements are most easily achieved by creating an edirectory user (perhaps named "NMArchive") within a container created in edirectory specifically for storing the Netmail Archive configuration objects (again perhaps named "NMArchive"). Install Java Runtime Environment bit 12 Copyright 2013, Messaging Architects. Updated: 10/05/2013

13 Verify that Java Runtime Environment bit is installed on your Archive server. Disable automatic updates. JDK bit is required for your Index Server. If you are using GroupWise WebAccess (for instance, in a mixed GroupWise/Exchange environment) you should install JRE bit on your GroupWise WebAccess Server. Note: Java Runtime Environment 6.0 is sometimes referred to as Java Runtime Environment 1.6. At the time of publication, Java Runtime Environment 6.0 was available for download at the following link: ads/index.html. Install SQL-Based Database During the Netmail Archive installation process, you will be prompted to install PostgreSQL to use as the logging database. However, if you do no t want to use the PostgreSQL database, make sure that the database you are using is fully installed and accessible from the Netmail Archive server(s). If you are using a database other than PostgreSQL, Oracle, MySQL, MSSQL (2005/Express), or MSSQL (2000/MSDE), the database must contain a valid connection string, which you will be prompted to enter during the Netmail Archive installation process. Note: PostgreSQL is the recommended database for Netmail Archive. For more information on logging databases, see Netmail Archive Logging Database. Installing the Netmail Archive Master Node in an Exchange Environment Installation sequence for Netmail Archive 5.2 Locate and run the setup.exe file located in the Netmail Archive directory of the Netmail Archive distribution. The Netmail Archive Setup Program will install the Netmail Archive Master node. The installation program will guide you through the installation process. Follow the onscreen instructions to install Netmail Archive in an Exchange environment. Important: Netmail Archive does not support installing the Netmail Archive software from a Microsoft Windows mapped drive. Instead, you should copy the Netmail Archive installation files to the server on which you will be installing Netmail Archive. On the Netmail Archive Welcome screen, click Next to proceed. On the License Agreement screen, carefully review the software license agreement, and then click I accept the terms of the license agreement to accept the License Agreement. Click Next to continue. 13 Copyright 2013, Messaging Architects. Updated: 10/05/2013

14 On the Choose Destination Location screen, install Netmail Archive in the default destination folder, or browse to the location where you want to install Netmail Archive. Click Next to continue. The Cluster Configuration screen allows you to choose whether you are installing a Master or Worker archive node. Where workloads require, Netmail Archive can be configured to run a cluster of archive nodes. The first server installed should always be chosen as a Master node and all subsequent archive nodes installed as Worker nodes. Within a cluster, the Master node will automatically distribute the workload across the available archive nodes to better utilize system resources. For smaller environments intending to use only one archive node, the Master role must be chosen. 14 Copyright 2013, Messaging Architects. Updated: 10/05/2013

15 1. On the Cluster Configuration screen, select the Install Master Node option, since you are installing the first archive node of the cluster, or you are installing only a single archive node. Note: For more information about installing Worker nodes, see Netmail Archive Worker Node(s). 2. Under Master Configuration, enter the IP Address of the computer where you are installing Netmail Archive. Note: If your server has multiple IP addresses (e.g., in the case where you are using iscsi NICS as well as LAN NICS), then ensure that you enter the correct IP Address for Netmail Archive communication (e.g., the LAN IP address). 3. The Port field specifies the port number that will be used for Netmail Archive cluster communications by this node. By default, the port number of the Master node is It should not have to be changed, as Netmail Archive should be installed on a dedicated server. However, you can change the default port number based on which ports are currently in use and your network security requirements. Whichever port you choose, be sure to verify that there are no firewalls or filters on the port that would impede communications. 4. Click Next to continue. If you do not have an SQL database installed on your system, the PostgreSQL Installation dialog box appears, prompting you to install PostgreSQL as your logging database. If you want to use PostgreSQL as your logging database, click Yes to proceed with the PostgreSQL installation. Otherwise, click No to continue with the Netmail Archive installation (which continues with the Messaging Server screen). Note: If you choose not to install PostgreSQL, you can opt to manually install a different supported database. After clicking Yes, you are reminded to include the ODBC drivers as part of the PostgreSQL installation. Click OK to acknowledge the reminder and continue with the PostgreSQL installation. 15 Copyright 2013, Messaging Architects. Updated: 10/05/2013

16 Installing PostgreSQL Prior to the launch of the PostgreSQL installation, a command window opens (as shown below). This command window must be kept open for the duration of the PostgreSQL installation. The installer will also automatically install the Microsoft Visual C Redistributable if it is not found already installed on the server. On the PostgreSQL Welcome screen, click Next to proceed with the installation. Important: Note that the Netmail Archive Installation Wizard window remains open while you install PostgreSQL. A separate PostgreSQL Installation Wizard opens over the window of the Netmail Archive Installation Wizard. Do not exit the Netmail Archive Installation Wizard. Once the PostgreSQL installation is complete, you will be able to seamlessly continue with the installation of Netmail Archive. Note: If, during the installation of PostgreSQL, the creation of the Postgres database fails, refer to Appendix A - Rebuilding the PostgreSQL Database for information on how to manually rebuild your Postgres database. 16 Copyright 2013, Messaging Architects. Updated: 10/05/2013

17 On the Installation Directory screen, use the default location or specify the location in which you want to install PostgreSQL. Click Next to continue. On the Data Directory screen, use the default location or specify the location in which you want to store your data, and then click Next to continue. 17 Copyright 2013, Messaging Architects. Updated: 10/05/2013

18 On the Password screen, enter and confirm the password for the PostgreSQL database super user and service account. If a service account already exists, enter the corresponding password for the account. If a service account does not exist, a new one will be created when you click Ne xt. Click Next to continue. On the Port screen, enter the number of the port on which the PostgreSQL system should listen for connections. It is recommended to use the default value of 5432 unless you have good reason to change it. Click Next to continue. 18 Copyright 2013, Messaging Architects. Updated: 10/05/2013

19 On the Advanced Options screen, select the locale to be used by the new database cluster, and click Next. On the Ready to Install screen, click Next to install PostgreSQL. 19 Copyright 2013, Messaging Architects. Updated: 10/05/2013

20 On the Completing the PostgreSQL Setup Wizard screen, you are asked if you want to launch Stack Builder upon closing the Setup wizard. Keep this option selected, as it is used to install the PostgreSQL ODBC driver, and click Finish. Note: If, during the installation of PostgreSQL, the creation of the Postgres database failed, refer to Appendix A - Rebuilding the PostgreSQL Database for information on how to manually rebuild your Postgres database. On the Stack Builder Welcome screen, use the dropdown list to select the version of Postgres you have just installed, and click Next to continue. 20 Copyright 2013, Messaging Architects. Updated: 10/05/2013

21 The next screen allows you to select the applications you want to install. Select Categories > Database Drivers, and then select the psqlodbc driver. Click Next to continue. On the next screen, review your application selection, and choose a directory to which you want to download your selected application, if required. Click Next to download the installation file. 21 Copyright 2013, Messaging Architects. Updated: 10/05/2013

22 Once the installation file has been successfully downloaded, the application can be installed. Click Next to begin the installation. The Setup psqlodbc screen appears. Click Next to continue. 22 Copyright 2013, Messaging Architects. Updated: 10/05/2013

23 On the Installation Directory screen, specify the location in which you want to install psqlodbc. The default path should match your PostgreSQL installation path and does not need to be changed. On the Ready to Install screen, click Next to begin the installation of psqlodbc. 23 Copyright 2013, Messaging Architects. Updated: 10/05/2013

24 On the Completed the psqlodbc Setup Wizard screen, click Finish to exit the wizard. On the Stack Builder Installation Completed screen, click Finish to exit the wizard. 24 Copyright 2013, Messaging Architects. Updated: 10/05/2013

25 PostgreSQL and Stack Builder have now been installed on your system, and you are ready to continue with the Netmail Archive installation. The Messaging Server screen allows you to select which type of messaging server you are using with your Netmail Archive system. 1. Under MS Exchange, select which version of Exchange you are using: MS Exchange 2007 SP1 MS Exchange 2010 MS Exchange 2010 SP1 MS Exchange Online 2. Select Enable stubbing if you would like to use Netmail Archive s stubbing functionality. Note: Stubbing is not supported with Exchange Online. Important: In an Exchange environment, stubbing will only function with Outlook 2003 SP3, Outlook 2007 SP1, and Outlook Copyright 2013, Messaging Architects. Updated: 10/05/2013

26 3. Click Next to continue. The Exchange Server Configuration screen allows you to specify Exchange Access Information. The screen will appear slightly different depending on whether you are installing Exchange 2007 or Exchange On-premise/Online. For Exchange 2007: 1. Under Exchange URL, enter an EWS connectivity URL to a local Exchange CAS server using the syntax illustrated in the example. 2. Under Active Directory Server IP, enter the address and port number of a local Active Directory domain controller. 3. Under Active Directory Administrator Name, enter the account and password combination for the Active Directory service account which you set up for Netmail Archive use. 4. Under Exchange Administrator account name, enter the account and password combination for the Exchange service mailbox which you set up for Netmail Archive use and to which you granted EWS permissions (typically the same Active Directory service account). Important: For Exchange 2007, the names of both the Active Directory Administrator Name and the Exchange Administrato r account name need to be entered in domain\user format. 5. Under Administrator Account, enter the address for the Exchange service mailbox to be used by Netmail Archive. 6. Click Next to continue. For Exchange 2010 On-premise or Online: 1. Under Exchange PowerShell URL, enter a PowerShell URL to connect to your local Exchange CAS server or Exchange Online system using the syntax illustrated in the example field. 2. The Active Directory Server IP, Port, Active Directory Administrator Name, and Password fields are greyed out, since an on-premise Active Directory is not required for Exchange Netmail Archive will perform all viewer-based authentication through PowerShell. 3. Under Exchange Administrator SMTP address, enter the UPN (User Principal Name) for the Exchange system administrator, and enter the corresponding Password for that user. 4. Under Administrator Account, enter the address of the Exchange system administrator. The Exchange administrator settings should refer to the Exchange service account that you created as the dedicated account for Netmail Archive and to which EWS impersonation rights on the Exchange 2010 system were granted. 26 Copyright 2013, Messaging Architects. Updated: 10/05/2013

27 Note: All Exchange Online accounts require that passwords are changed regularly. When you change the password associated with this dedicated account, you must also update the password in Netmail Administration Console. 5. Click Next to continue. The LDAP Server Connectivity Parameters screen lets you configure how Netmail Archive will access edirectory via the LDAP server in order to create and store its configuration objects. 1. Under LDAP Server IP Address, enter the IP Address of a local edirectory LDAP server. 2. Select SSL if you require a secure (SSL) connection between Netmail Archive and the edirectory tree. If you choose for SSL to be enabled, the default Port Number is 636. If you choose for SSL to be disabled, the default Port Number is 389. However, if your LDAP server is configured to listen on a different port, you can change the default port number. 3. Under Administrator Common Name, specify the edirectory account name with administrator rights to the tree using the syntax illustrated in the example. 4. Under Administrator Password, specify the password used to access the account. 27 Copyright 2013, Messaging Architects. Updated: 10/05/2013

28 Note: You will use this Administrator Name and Password combination to later log in to the Netmail Administration Console. If you are following the suggested best practices, this will be the dedicated edirectory account you set up earlier. 5. Under edirectory Configuration Container, specify the path to the container where you want to create and store the Netmail Archive objects in edirectory using the syntax illustrated in the example. 6. Select Perform Validation if you want the installation program to validate the information provided. 7. Click Next to continue. The Service Logon Information screen allows you to specify which account you want to use to start Netmail Archive Services. In order to start Netmail Archive services, the specified account must have local Administrator privileges on the server. 1. On the Service Logon Information screen, enter the user account you want to use to start Netmail Archive services. User accounts must be specified using the following syntax: DOMAIN\username. Click Browse to browse to the location. 2. Under Password, enter the password used to access the account. 3. Click Next to continue. Tip: If there is no domain controller to authenticate against, you must authenticate locally using the following syntax:.\username The Logging Database Configuration and Notification Setting screen allows you to select a database and specify where Netmail Archive will store logging information. 28 Copyright 2013, Messaging Architects. Updated: 10/05/2013

29 1. If you have installed PostgreSQL, the default logging Database is PostgreSQL. However, if you do not want to use this database, select which database you want to use from the available options: MySQL MSSQL (2005/Express) MSSQL (2000/MSDE) Other Important: If you are using the PostgreSQL database, the information you enter on the Logging Database Configuration and Notification Setting screen should match the information that you entered during the installation of PostgreSQL. For instance, your user name should be postgres and your password should match what was entered during the installation of PostgreSQL. For more information about installing the PostgreSQL database, see Installing PostgreSQL. 2. Under Server name, enter the IP address or host name of your database server (this server, if you installed PostgreSQL). 3. Under Database name, ensure the name netmailarchive is entered. 4. Under User name, ensure the name postgres is entered if you are using PostgreSQL, or enter a valid database user account for connecting to your other database system. 5. Under Password, enter the database user s password (as entered earlier, if you are using PostgreSQL). 6. Once those settings are entered, click Apply to update the ODBC Connection String in the textbox below. If you are using a non-postgresql database, you may need to verify that the connection string is correct and customize it if necessary 7. Under Notification address, enter an address where you want logging notifications to be sent. 8. Select Perform Validation if you want the installation program to validate the information provided. 9. Click Next to continue. Tip: To avoid the PostgreSQL service account password expiring, it is recommended that you adjust the postgres Windows user account configuration in the Microsoft Management Console to disable password expiration. The Enter Values screen is pre-populated with the Netmail Archive WebAdmin URL and the port numbers on which the Netmail Unified UI will operate. This information does not need to be changed. Click Next to continue. 29 Copyright 2013, Messaging Architects. Updated: 10/05/2013

30 Note: There is a known problem with using localhost in the WebAdmin URL setting as shown in the figure above. On Windows 2008 systems, this resolves to an IPv6 address. As such, if you do need to change the URL, you should use an explicit IP address or hostname in the WebAdmin URL field (e.g., On the Ready to Install screen, click Install to begin the installation. The installation wizard will now copy the required files to your server and create the Netmail Archive configuration objects in edirectory. Command windows will open as the edirectory schema is being extended and as the edirectory objects are being created. On the Wizard Complete screen, click Finish to exit the Netmail Archive installation installation wizard. 30 Copyright 2013, Messaging Architects. Updated: 10/05/2013

31 Note: Because Windows sometimes keeps certain components locked, you may be prompted to restart the server at the end of the installation sequence. If no other components are to be installed on the node, you can proceed with the restart. Otherwise, it may be more efficient to wait until all installation tasks have been performed before restarting the machine. Post-Installation Tasks for Exchange After installing Netmail Archive in an Exchange environment, you must complete the following steps before creating, applying, and deploying archive policies. Netmail Archive Licensing Before you can begin using Netmail Archive, you must have a valid Netmail Archive license file. You will need to manually add the license file to the appropriate directory. If you installed Netmail Archive in its default installation location, place the license file in the C:\Program Files\Messagin g Architects directory on the Master node. Otherwise, place the license file in the directory in which you installed Netmail Archive. Note: You should also copy the license file to the same folder on any Worker nodes that you will subsequently install, as some of these may take over the Master role in the case of a server failure. To activate the license, you must restart several services from the Windows Start Menu. For more information, see Start Netmail Archive Services. 31 Copyright 2013, Messaging Architects. Updated: 10/05/2013

32 Important: If you do not restart the services, Netmail Archive will add the MALicense Checker Trigger to its list of tasks, but may not process the license right away. If you want to verify that your license has been updated, log in to the Netmail Administration Console using the procedure detailed below, and expand the left-hand folder view to select the Archive > Clusters > <Cluster Name> > Agents > Archive object, as shown in the figure below. A license count for the Archive Agent should now appear on the License tab. This license count should match the license count in your file. Important: The MALic.xml file has a digital signature applied to it, so if you attempt to edit the file, the license will be invalid. Note: If you are upgrading to Netmail Archive 5.1 from a previous version of Netmail Archive (formerly M+Archive) and are planning a migration from a GroupWise system to an Exchange system, please contact Messaging Architects for an updated license file. How to Count Licenses Licensing in Netmail Archive controls the maximum number of accounts against which the various Agents can run jobs. Licence usage by a Netmail Archive agent is defined as the number of accounts currently allocated to jobs for that agent. When this count is being calculated, it is important to keep two aspects in mind: Any single mail account will be counted only once for the usage figure of an agent, even if the mail account is currently allocated to multiple jobs for that agent. Any distribution lists/groups being used in job user lists will be expanded to the current membership, and the individual mailboxes will be counted as if listed themselves. Note that the current membership as known by Netmail Archive will be based on the membership at the time of the last Address Book Sync execution. Any agent for which the current usage count exceeds the licensed count will not execute any jobs until the license infringement has been rectified. Note the following important points: The Netmail Archive license count does not need to match the number of accounts in the mail system, since it only applies to the accounts allocated to Netmail Archive jobs. The Netmail Archive administrator is at liberty to decide which accounts are to be processed and may not need to archive all mail system accounts. Licenses are not applied to archived data. That is, if an account has been archived and deactivated and no future ILM jobs are required to run on that account's archived data, then a license is not required for that account, as it will not be allocated to any jobs. 32 Copyright 2013, Messaging Architects. Updated: 10/05/2013

33 For systems with large user turnovers, it is likely that the ILM and Index Agent license counts will need to be higher, as these agents act on archived mail accounts, not live mail system accounts. With specific storage systems such as Netmail Store, where a specified data retention period is part of the storage system properties, there is no need to run an ILM Deletion Job on the data at the end of the retention period. The deletion job is performed automatically by the storage system. There are no license limitations on ediscovery operations against archived data. You can perform ediscovery on any archived data without requiring a license. Start Netmail Archive Services After completing the Netmail Archive installation, you must start Netmail Archive Services. During the installation program, a shortcut was created for you in the Windows Start menu. To use the shortcut, choose Start > All Programs > Netmail Archive > Start Netmail Archive Services. To start these services manually: 1. Choose Control Panel > Administrative Tools > Services from the Windows Start menu. 2. Double-click Services to open the Services dialog box. 3. Locate and right-click the Netmail Open service in the list of Services, and select Start. 4. Locate and right-click the Netmail Administration Console service in the list of Services, and select Start. Tip: When Netmail Open is subsequently started or stopped after this first post-install startup, it will auto-start or auto-stop both the Netmail Administration Console and ThreadPool services. For the first startup, however, Netmail Administration Console nee ds to be started manually. Note: Before starting Netmail Archive Services, ensure that the account which services are using has the log on as a service permission enabled in Windows. Verify Administrator Rights After installing Netmail Archive in an Exchange environment, you can test the archiving function by archiving the Administrator account. If you are successful in archiving the Administrator account, Netmail Archive has been installed properly. If you are unable to archive the accounts of other users, verify that the Administrator account has been granted sufficient access to the mailboxes. For detailed instructions on performing an Archive Job, refer to the Netmail Archive Administration Guide. For more information about modifying administrator rights or configuring Exchange impersonation, refer to Pre-Installation Tasks for an Exchange Deployment. Launch the Administration Console and Log In The Netmail Administration Console is a web-based application that allows administrators to configure Netmail Archive, create policies, and run jobs. To launch the Netmail Administration Console, open a standard web browser and enter the IP address of the server where you installed Netmail Archive, followed by the port number specified during the Unified UI installation (e.g., The console can be accessed from any workstation with access to the IP address and port number. On the Netmail Administration Console login screen, enter your and, and click. The username and password User Name Password Login requested are those of an edirectory user with full rights to the container holding the Netmail Archive configuration objects. By default, this is the dedicated edirectory user that you created before installation. The username is entered in the following format: username.container.org (e.g., nmarchive.archive.myorg). 33 Copyright 2013, Messaging Architects. Updated: 10/05/2013

34 Note: For more information about logging in to the Netmail Archive Administration Console, refer to the Netmail Archive Administration Guide. Confirm Connectivity to Exchange and AD In ongoing normal operation, the Address Book Sync job is executed automatically by Netmail Archive in order to read Exchange mailbox information into the Netmail Archive system. This allows GroupWise accounts to be allocated to archive jobs, for example. You can run this job manually now in order to confirm connectivity to AD and Exchange system. In the Netmail Administration Console, select the Archive > Clusters > <Cluster Name> object in the tree. By default, the Configuration tab is displayed. Click the Address Book Sync tab to specify your Address Book cache settings. To execute the address book sync job and confirm that it has connected correctly to Exchange and AD: 1. Under Address Book Cache, click Run Now to start the address book sync job immediately. 2. Choose the Archive object in the tree menu on the left-hand side of the Netmail Administration Console, and then click the Monitor tab. The M onitor tab tracks the jobs currently being processed. Expand the entry for the cluster node and a SyncAB Trigger should appear in the Running Job ID column. You can monitor the status of the job and the elapsed time of the job. 3. When the job has completed, GroupWise user and Post Office information should have been read into Netmail Archive. To confirm that CAS information has been read, navigate to the Archive > Clusters > <Cluster Name> object in the tree, and select the P.O. tab. Note: For more information about updating your address book cache, refer to the Netmail Archive Administration Guide. Configure Web Browser for Index Server Communications The Netmail Archive system uses HTTP communication between archive servers and index servers. To avoid degraded performance, it is preferable that your Master and Worker archive servers do not use proxy settings to communicate with the Index Server s web service. Windows proxy configuration is carried out via Internet Explorer. 34 Copyright 2013, Messaging Architects. Updated: 10/05/2013

35 To add a proxy exclusion via Internet Explorer: 1. Navigate to Tools > Internet Options on the top toolbar of the Internet Explorer screen. 2. Select the Connections tab. 3. Select LAN settings. 4. Select Use a proxy server for your LAN. 5. Click Advanced. 6. In the dialog box that appears, enter the requested proxy IP addresses and port information. 7. In the Exceptions section, under Do not use proxy server for addresses beginning with, enter the IP address of your Index Server s IP address. 8. Click OK to close the Proxy Settings dialog box. 9. Click OK to close the LAN Settings dialog box. 10. Click OK to close the Internet Options dialog box. Now that you have successfully installed the Netmail Archive Master node, policy-based retention is now possible. However, to perform ediscovery and lifecycle management, you will need to install additional components, namely the Index Server and Remote Provider. The installation of these two components is covered in subsequent chapters. 35 Copyright 2013, Messaging Architects. Updated: 10/05/2013

36 Indexing Node(s) After installing the Netmail Archive Master node, you are ready to deploy your first Index Server, which is responsible for indexing and search functionality. Netmail Archive s Index Server provides organizations with the means for the archive viewer interfaces, including Netmail Search, to access and search the archived data. Through a web-based administration console, the Index Server also offers search engine monitoring, system information, and administration. Installing Your Index Server System Requirements Meet Hardware and Software Requirements Verify.NET Framework 4.0 is installed Install three versions of Microsoft Visual C++ Redistributable Pre-Installation Tasks Install the Index Server Start the Index Service Run the Cluster Manager Tool Index Conversion Server Requirements The Index Server must be installed on a separate server than the Netmail Archive Master Node (archive server). Messaging Architects requires that you install the Index Server on a 64-bit operating system in a production environment. Installing the Index Server on a 32-bit operating system may degrade performance. Windows 2008 R2 Enterprise Edition 64-bit is the current recommendation, however, you can check here for the latest requirements. Pre-Installation Tasks In order to ensure a successful deployment of your Index Server, there are certain things you must do to prepare your system before installing the Index Server..NET Framework Verify that Microsoft.NET Framework version 4.0 is installed and enabled. To verify that Microsoft.NET Framework is installed, navigate to the Control Panel and launch the Add and Remove Programs function. In the list of currently installed programs, look for Microsoft.NET Framework 4.0. If Microsoft.NET Framework version 4.0 is not installed, the program is available for download from Note: If using Windows Server 2008 R2, you can verify that Microsoft.NET Framework is installed through the Server Manager. To do so, click Start > Administrative Tools > Server Manager. In the Server Manager interface, click Features, and verify that.net Framework 4.0 is listed in the right-hand pane. Install Microsoft Visual C SP1 Redistributable Package (x64) Verify that the following three versions of Microsoft Visual C++ are installed on the server or servers on which you will be installing the Index Server: Microsoft Visual C SP1 Redistributable ATL 32-bit AND 64-bit These versions can be downloaded here: Microsoft Visual C SP1 Redistributable ATL 64-bit. 36 Copyright 2013, Messaging Architects. Updated: 10/05/2013

37 This version can be downloaded here: Installing the Index Server Copy the Netmail Indexing files from the Netmail Archive distribution to the server on which you are installing your Index Server, and then run the setup.exe file. The installation wizard will guide you through the installation process. Important: The Index Server must be installed on a 64-bit operating system in a production environment. Only a 64-bit setup.exe file is provided for installation. On the Welcome screen, click Next to continue. On the Netmail Indexing Path screen, install the Index Server in the default destination folder, or browse to the location where you want to install the Index Server. Click Next to continue. The Netmail Indexing Data Path screen requires you to indicate the path where your indexes will be stored. It is recommended that you keep the default Netmail Indexing/Cloudview folder name, but you must ensure that you change the drive to your chosen index storage volume. Once you have done this, click Next to continue. 37 Copyright 2013, Messaging Architects. Updated: 10/05/2013

38 On the Select Node Type and enter your Exalead server screen, specify if you are installing a Master or Slave Index server. 1. Select Master if you are installing the Master Index server, or select Slave if you are installing a Slave Index server. Note: The first index server to be installed must be set as the Master server. Any subsequent servers installed must be set as Sl ave servers. 2. If you are installing the Master Index server, specify the IP address of the server where the Master Index server is being installed, as well as the Base Port and Gateway Port. Unless unavailable, use the default Base port and the default Gateway port If you are installing a Slave Index server, specify the existing Master Index server settings as well as the IP address of the Slave host being installed. Click Next to continue. On the Ready to Install the Program screen, click Install to begin the installation. 38 Copyright 2013, Messaging Architects. Updated: 10/05/2013

39 The installation phase can take several minutes to complete. Towards the end of the installation process, a command window opens, followed by a message that reminds you to run the Cluster Manager to complete the installation process. Click OK. On the Wizard Completed screen, click Finish to exit the installation wizard. Start the Index Service After completing the installation of the Index Server, you must start the Index Service. To start the Index Service: 39 Copyright 2013, Messaging Architects. Updated: 10/05/2013

40 1. Choose Control Panel > Administrative Tools > Services from the Windows Start menu. 2. Double-click Services to open the Services dialog box. 3. Locate the Netmail Indexing (CloudView) service in the list of Services, and click Start. Important: Do not start the Index Service on a newly installed Slave server until you have run the Cluster Manager tool to register the Slave with the Master server and configured slice numbers for the Slaver server. Run the Cluster Manager Tool The Cluster Manager tool can be run from any location, but it is most easily run on the Master Index server. The ExaleadClusterManager.exe file can be found in C:\Program Files\Netmail Indexing\Netmail Archive Tools. The Cluster Manager tool has two uses: 1. In the case of a new deployment, the tool is used to establish a new Index Server cluster, register all Slave servers and configure slice counts for all the servers, and apply the settings. To deploy a new Index Server cluster, see Deploying a New Index Server Cluster. 2. In the case of an existing Index Server cluster, the tool is used to register a new Slave server to the Index Server cluster and to set the slice count for that new server. To add a Slave server to an existing Index Server cluster, see Adding a Slave Server to an Existing Index Server Cluster. Note: Generally, when using the Cluster Manager tool, all configuration should be done through the Master server, and Slave servers should be registered and have their slice counts configured before they are installed. A few definitions: Build Group: A logical component containing an index and a logical collection of Index Server components containing all the processors and resources needed to accept and analyze documents and to build the index. In Netmail archive there are two core build groups: bg0 f or the archive items, and bgaudits for the audit files. In addition, for systems being upgraded from M+Archive, a third build group named bg_4_6 is used to handle converted indexes from the previous version of the Index Server. Index Slices: A segmentation of the index to facilitate index distribution and load balancing. Within a server, a build group is split into slices to optimize performance based on the number of processor cores in the server. Indexes are also sliced to allow for distribution across servers. Deploying a New Index Server Cluster 40 Copyright 2013, Messaging Architects. Updated: 10/05/2013

41 A new Index Server cluster is deployed when a new installation of Netmail Archive is carried out. All Index Server deployments have a single Master server. As the need arises for additional capacity, Slave servers are added to the cluster and registered with the Master server. These Slave servers are configured with additional slices for each build group and thus extend the distribution of the index system. The Master server is then responsible distributing the indexing load across all servers in the cluster (including itself) and will aim to balance the indexes evenly across the available servers. Note: Prior to deploying a new Index Server cluster, you should establish the number of Index Servers you are going to deploy. This can be done by following the Index Server sizing guidelines. To configure your new Index Server cluster, follow these steps: 1. Locate and double-click the ExaleadClusterManager.exe file. The Exalead Cluster Manager dialog box opens. 2. Enter the IP address, Base port and Gateway port numbers of the Master server. 3. Click Connect. After a few seconds, a list of installed index hosts appears under Hosts. Initially, this list will only contain the Master server. You need to register each of the planned Slave servers in order to add them to this list. Note: If you are implementing a single Index Server, you can skip this registration process and proceed directly to step Copyright 2013, Messaging Architects. Updated: 10/05/2013

42 4. Under Slave, enter the New Host IP address and Base Port number (the default port number is 10000) of a new Slave server you want to register, and then click Add Host. Repeat this process for all of your Slave servers. Each time you add a new Slave server, it will be added to the list of Index Servers under Hosts. Note: There is no need to predict future Slave server needs; you need only register those Slave servers that you are configuring now as part of the initial deployment. 5. Once you have registered all of your Slave servers, you need to configure the slice numbers for the Master server and each Slave server. To do so, under Hosts, select the first server in the list, and then click Configure. 42 Copyright 2013, Messaging Architects. Updated: 10/05/2013

43 6. The Slices Configuration dialog box opens. Under Host Parameters, enter the number of processor cores on this host server, and click Eval uate. The two text fields under Slicesconfiguration are then automatically populated with the recommended slice counts. Note that for the server on which you are running the Cluster Manager tool, the number of processor cores is automatically detected. 7. Click OK. A message confirming the slice numbers that will be applied appears. Click Yes to proceed. The Cluster Manager tool then makes the appropriate configuration changes to the Index Server. 43 Copyright 2013, Messaging Architects. Updated: 10/05/2013

44 8. Once the configuration is complete, click OK to dismiss the message confirming that the configuration was a success. 9. Repeat steps 5 through 8 to configure the slice numbers for each of the other hosts (i.e., Slave servers). 10. Once the slice numbers have been configured for all hosts, click Apply to commit the changes to the Master server. A message confirming that the configuration was a success appears. The message also displays the new Index Server configuration version number. Click OK to dismiss the message. 11. It is also necessary to install some updates to the Netmail Indexing administrative interface to allow the Index Servers to be managed from the Netmail Administration Console. To perform this install, click Install/Upgrade in the Cluster Manager window. 12. A popup informing you that the Indexing service needs to stop appears. Click Yes to continue. 13. When the install is complete, another popup appears to inform you of this and that the Indexing service has been restarted. Click OK to return to the Cluster Manager window, and then click Close to exit the Cluster Manager tool. 44 Copyright 2013, Messaging Architects. Updated: 10/05/2013

45 Adding a Slave Server to an Existing Index Server Cluster It may become necessary to extend the Index Server cluster to provide additional indexing capacity. Adding a new Index server is a very simple process. The Cluster Manager tool is used to register the server and to configure the slice numbers for it. The new Slave server is then installed and started up. To add a Slave server to an existing cluster, follow these steps: 1. Locate and double-click the ExaleadClusterManager.exe file. The Exalead Cluster Manager dialog box opens. 2. Enter the IP address, Base port and Gateway port numbers of the Master server. 3. Click Connect. After a few seconds, a list of installed index hosts appears under Hosts. 45 Copyright 2013, Messaging Architects. Updated: 10/05/2013

46 4. Under Slave, enter the New Host IP address and Base Port number (the default port number is 10000) of a new Slave server you want to register, and then click Add Host. Your new Slave server appears in the list of Index Servers under Hosts. 5. Once you have registered your Slave server, you need to configure the slice numbers for it. To do so, under Hosts, select the new Slave server in the list, and then click Configure. 46 Copyright 2013, Messaging Architects. Updated: 10/05/2013

47 6. The Slices Configuration dialog box opens. Under Host Parameters, enter the number of processor cores on this host server, and click Eval uate. The two text fields under Slicesconfiguration are then automatically populated with the recommended slice counts. 7. Click OK. A message confirming the slice numbers that will be applied appears. Click Yes to proceed. The Cluster Manager tool then makes the appropriate configuration changes to the Slave server. 47 Copyright 2013, Messaging Architects. Updated: 10/05/2013

48 8. Once the configuration is complete, click OK to dismiss the message confirming that the configuration was a success. 9. Once the slice numbers have been configured, click Apply to commit the changes to the Master server. A message confirming that the configuration was a success appears. The message also displays the new Index Server configuration version number. Click OK to dismiss the message, and then click Close to exit the Cluster Manager. 10. Restart the Index Service on the Master server. Important: Don't forget to add the new Slave server to the Archive > Clusters > <Cluster Name> > Configuration tab in the Netmail Administration Console. Configure Archive Server to Index Server Communications Once your Index server(s) are installed, you now need to configure Netmail Archive to enable communications between the Archive node(s) and the Index server(s). Netmail Administration Console Settings Open your web browser, and log in to the Netmail Administration Console. Navigate to the Archive > Clusters > Cluster > <Cluster Name> obje ct and to the Configuration tab, as shown in the figure below. 48 Copyright 2013, Messaging Architects. Updated: 10/05/2013

49 Under the Index Servers header, complete the following: 1. Under Host, enter the IP address of your Master Index server. 2. Under Base port, enter the base port you specified during installation of your Master Index server. By default, the port number is Under Gateway port, enter the gateway port of your Master Index server that you specified during installation. By default, the port number is Under Document Cap, specify the maximum number of documents the Master Index server should index before it is considered at full capacity. The default value of 50 million documents should be used unless you have been advised otherwise by Messaging Architects. As Index servers near their caps, additional index capacity can be easily obtained by adding additional Slave Index servers. 5. Under Index nodes, use the Add button to register details of any Slave Index servers which you have already installed. If at any point in the future you add a Slave Index server, you must return to the Netmail Archive Administration Console to register the new Slave. 6. Click Save at the bottom of the screen to save the modified configuration. Proxy Exception Settings on Archive Servers The Netmail Archive system uses HTTP communication between archive servers and index servers. To avoid degraded performance, it is preferable that your Master and Worker archive nodes do not use proxy settings to communicate with the Index Server(s). Rather, they should communicate directly to the Index Server(s). As such, you must add proxy exceptions for each of the Index Server IP addresses to the Internet settings on your Master and Worker archive nodes. Note: This process is only required if you currently have a proxy configured on your archive nodes. Windows proxy configuration is carried out via Internet Explorer. To add a proxy exclusion in Internet Explorer: 1. In the top toolbar of the Internet Explorer screen, navigate to Tools > Internet Options. 2. In the Internet Select the Connections tab. 3. Select LAN settings. 4. In the LAN Settings dialog box that appears, select Use a proxy server for your LAN. 49 Copyright 2013, Messaging Architects. Updated: 10/05/2013

50 5. Click Advanced. 6. In the Proxy Settings dialog box that appears, enter the requested proxy IP addresses and port information. 7. In the Exceptions section, under Do not use proxy server for addresses beginning with, enter the IP address of your Index Server(s). 8. Click OK to close the Proxy Settings dialog box. 9. Click OK to close the LAN Settings dialog box. 10. Click OK to close the Internet Options dialog box. Index Conversion For organizations upgrading an existing M+Archive system to Netmail Archive, there will be existing indexes from the previous version of the Index Server (Exalead 4.6). These indexes must be converted to the new Index Server (Exalead CloudView) format if they are to be used by the Netmail Archive viewers. The Cluster Manager tool and a dedicated Messaging Architects conversion tool are used when converting Exalead 4.6 indexes to CloudView indexes. Together, these tools complete several key tasks: Creation of a slice within the bg0 build group for each 4.6 instance being converted Copying of the index files from the 4.6 instance folder to the appropriate slice folder under the CloudView directory structure Conversion of the 4.6 index files to CloudView format The end result is the default build group, bg0, with one slice per 4.6 instance, each of which contains the converted indexes from the corresponding instance. In order to use these converted indexes, you will also need to carry out a corresponding upgrade of the Archive and Remote Provider software to Netmail 5.x version, and ensuring that the archive repository names are exactly the same as those on the M+Archive system. Preparing for the Conversion The recommended approach to index conversion is to install CloudView (the indexing version included in Netmail Archive) on top of each existing Exalead 4.6 server. The software installs to different directories by default and can co-exist quite happily, although only one index system should have its services running at any time to avoid port conflicts. Tip: The Index Server housing Exalead 4.6 instance 0 typically becomes the CloudView Master server in an upgrade scenario. Any additional 4.6 servers become CloudView Slave servers. Before shutting down 4.6 to start the conversion, take note of the counts from each 4.6 instance. These can be compared to the results of the conversion process. Ensure that no updates are mad e to the 4.6 instances (data or audit) after you note the counts. Once CloudView is installed on the Exalead 4.6 servers, complete the following preparatory steps: 1. Stop the Exalead 4.6 Services on all Index servers. 2. Start the Netmail Indexing Service on the Master Index server. 3. Run through the process of registering Slave servers and configuring slice numbers with the Cluster Manager tool, as described in Adding a Slave Server to an Existing Index Server Cluster. Ensure that you configure slice numbers for the Master Index server as well. When you are configuring the slice numbers, be sure to adjust the numbers to include the converted instances as part of the slice count. To do so, in the Slices Configuration dialog box, next to Number of 4.6 Instances to be Added to the Host, indicate the number of Exalead 4.6 instances that exist on each server for the host in question. Do this for each individual host. This will create the slices that will house the converted indexes. 50 Copyright 2013, Messaging Architects. Updated: 10/05/2013

51 4.Once all Slave servers have been registered and slice counts configured, restart the Master Netmail Indexing Service. Running the Index Conversion Tool Now that you have prepared the Index Server for conversion, the index conversion can be carried out using Messaging Architects Index Conversion tool. To run the tool, double-click the IndexConversionTool.exe file located in C:\Program Files\Netmail Indexing\Netmail Archive Tools. 1. On the Prerequisites screen, verify and confirm that you meet all the requirements for index conversion. Click Next to continue. 2. On the Specify the locations screen, complete the following: Use the Browse buttons to select the appropriate paths to the Exalead 4.6 and CloudView index stores. Specify the Master Server IP address and Base port number. Ignore Use Slave Server option as this has been deprecated after Netmail Copyright 2013, Messaging Architects. Updated: 10/05/2013

52 3. The Select Index Instances to Convert screen lists the Exalead 4.6 instances that have been found on the server at the specified path. Select the instances that you want to convert (normally all instances are selected). They will be processed sequentially. The default processing method is Copy, which leaves the 4.6 instances untouched. If, however, you have a limited amount of space on the indexing volume, you may need to change this to the Move method. Important: Move should only be used if a confirmed backup of the current state of the 4.6 instances exists. When ready, click Next to continue. A warning window appears, indicating this is the first run of the conversion tool and that any previously converted index data residing on this server will be deleted. Click Yes to continue. 52 Copyright 2013, Messaging Architects. Updated: 10/05/2013

53 The conversion process now begins. The Index Conversion Tool dialog box appears, indicating that conversion is being initialized. Once the conversion process has been initialized, the first Exalead 4.6 instance is checked prior to being converted. The Index Conversion Tool dialog box displays this in the Conversion Log field. Once checking is complete, the index data files for this first instance are copied from the 4.6 instance to the slice directory within the CloudView system, as indicated in the Conversion Log. Once the copying is complete, the files are then converted into Netmail Archive index format. 53 Copyright 2013, Messaging Architects. Updated: 10/05/2013

54 Towards the end of this process, a command window opens as the index dictionaries are being generated. Once conversion is complete, it is indicated in the Conversion Log. If you are converting multiple 4.6 instances, the process is now repeated for the next instance. 54 Copyright 2013, Messaging Architects. Updated: 10/05/2013

55 4. When all instances have been processed, an Index conversion is done message is displayed in the Conversion Log, and a popup reminding you to restart the Netmail Indexing service is displayed. Click OK to dismiss the popup, and then click Finish to exit the Index Conversion tool. Restart the Netmail Indexing service on the server. Using the Index Server Administration Console The Index Server component of Netmail Archive is designed to simplify information search and retrieval for organizations of all sizes. The Index Server requires minimal additional administration. However, if you need to log in to the Index Server s Administration Console to fine-tune or troubleshoot the Index Server, you can access the console by opening a standard web browser and entering the IP address of the server where you installed the Index Server, followed by the search port of For example, The interface can be accessed from any workstation with access to this IP address and port number. Use the administrator credentials (user name and password) you specified during installation of the Index Server. 55 Copyright 2013, Messaging Architects. Updated: 10/05/2013

56 Netmail Archive Worker Node(s) After you have installed the Netmail Archive Master archive node and Index Server, you can install additional Worker archive nodes. In this section: Installing Worker Node(s) in an Exchange Environment Post-Installation Tasks for Worker Nodes Installing Worker Node(s) in an Exchange Environment Installation sequence for Netmail Archive 5.2 Run the Netmail Archive Installation Wizard Copy the Netmail Archive distribution files to your proposed Worker node server, and then locate and run the setup.exe file located in the Netmail Archive directory of the distribution. The installation program will guide you through the installation process. Follow the onscreen instructions to install Netmail Archive Worker node(s) in an Exchange environment. On the Netmail Archive Welcome screen, click Next to proceed. On the License Agreement screen, carefully review the software license agreement, and then click I accept the terms of the license agreement to accept the License Agreement. Click Next to continue. 56 Copyright 2013, Messaging Architects. Updated: 10/05/2013

57 On the Choose Destination Location screen, install Netmail Archive in the default destination folder, or browse to the location where you want to install Netmail Archive. Click Next to continue. Important: Netmail Archive does not support installing the Netmail Archive software from a USB key. Instead, you should copy the Netmail Archive installation files to the server on which you will be installing Netmail Archive. The Cluster Configuration screen is displayed. 57 Copyright 2013, Messaging Architects. Updated: 10/05/2013

58 1. On the Cluster Configuration screen, select the Install Worker Node option. Installing Netmail Archive on a second server will increase the scalability and processing power of your Netmail Archive system. Note: The first Archive server installed within a deployment should be the Master node. If additional Archive servers are required, these will be installed subsequently as Worker nodes. For more information on installing the Master node, see Installing the Netmail Archive Master Node in an Exchange Environment. 2. Under Master Configuration, enter the IP Address of the computer where you installed the Netmail Archive Master node. Note: If your server has multiple IP addresses (e.g., in the case where you are using iscsi NICS as well as LAN NICS, then ensure that you enter the correct IP address for Netmail Archive communication (i.e., the LAN IP address). Under Port, enter the port number of the Master node. Use the default port number 8585 (or the port number you used to install the Master node, if you opted not to use the default port). 3. Under Worker Configuration, enter the IP Address of the computer where you are installing the Netmail Archive Worker node. Note: If your server has multiple IP addresses (e.g., in the case where you are using iscsi NICS as well as LAN NICS, then ensure that you enter the correct IP address for Netmail Archive communication (i.e., the LAN IP address). The Port field specifies the port number that this node will use for Netmail Archive cluster communications. By default, the port number is It should be unnecessary to change this, as Netmail Archive should be installed on a dedicated server. However, you can change the default port number based on which ports are currently in use and your network security requirements. 4. Click Next to continue. The Service Logon Information screen allows you to specify which account you want to use to start Netmail Archive Services. In order to start Netmail Archive services, the specified account must have local Administrator privileges on the server. 58 Copyright 2013, Messaging Architects. Updated: 10/05/2013

59 1. On the Service Logon Information screen, enter the user account you want to use to start Netmail Archive services. User accounts must be specified using the following syntax: DOMAIN\username. Click Browse to browse to the location. Tip: To avoid any problems creating files on the server, the account used should ideally be part of the Local Administrators group on the server. Also, it may be necessary to grant this user file rights to GroupWise Native Archive locations if you plan on importing Native Archives, or to Export locations if you are going to export data to file system paths. Furthermore, it is typically recommended that all Archive and Index servers be in the same Windows Domain, and that a dedicated domain account for Netmail Archive is created for use with this service account. 2. Under Password, enter the password used to access the account. 3. Click Next to continue. Tip: If there is no domain controller to authenticate against, you must authenticate locally using the following syntax:.\username. The Enter Values screen is pre-populated with the Netmail Archive WebAdmin URL and the port numbers on which the Netmail Unified UI will operate. This information does not need to be changed. Click Next to continue. 59 Copyright 2013, Messaging Architects. Updated: 10/05/2013

60 On the Ready to Install screen, click Install to begin the installation. Once the installation is complete, the Wizard Complete screen appears. Click Finish to exit the installation wizard. Install PostgreSQL on the Worker Node Once the installation of the Worker node is complete, you need to install the PostgreSQL ODBC driver on the Worker node to allow it to connect to the logging database you installed on the Master node. To do so, locate and run the edb_psqlodbc.exe file located in C:\Program files (x86)\me ssaging Architects\PGInstall. The Setup psqlodbc screen appears. Click Next to continue. 60 Copyright 2013, Messaging Architects. Updated: 10/05/2013

61 On the Installation Directory screen, specify the location in which you want to install psqlodbc. Typically, the default path is used. On the Ready to Install screen, click Next to begin the installation of psqlodbc. 61 Copyright 2013, Messaging Architects. Updated: 10/05/2013

62 On the Completed the psqlodbc Setup Wizard screen, click Finish to exit the wizard. The PostgreSQL ODBC driver has now been installed on your system. Post-Installation Tasks for Worker Nodes Once you have installed your Worker node, you must complete a few more steps before you can start using Netmail Archive to create and apply archive policies. Start Netmail Archive Services After completing the Netmail Archive installation, you must start Netmail Archive Services. During the installation program, a shortcut was created for you in the Windows Start menu. To use the shortcut, choose Start > All Programs > Netmail Archive > Start Netmail Archive Services. To start these services manually: 1. Choose Control Panel > Administrative Tools > Services from the Windows Start menu. 2. Double-click Services to open the Services dialog box. 62 Copyright 2013, Messaging Architects. Updated: 10/05/2013

63 3. Locate the Netmail Open service in the list of Services, and click Start. Configure PostgreSQL on the Master node If you are using the default option of PostgreSQL for your Netmail Archive logging database, then you must configure PostgreSQL on the Master node to ensure that Worker nodes can connect correctly to the postgres database. By default, the PostgreSQL database is configured to listen on all Master node IP addresses where the Master node was installed. You should confirm this is still the case by checking the postgresql.conf file on the master node. To modify the PostgreSQL configuration file: 1. Locate the postgres configuration file postgresql.conf. By default, this file is located in C:\Program Files (x86)\postgresql\9.1\data on you Master node. 2. Open the file for editing in Notepad, and navigate to the Connection Settings section. 3. Make sure that postgres is configured to listen on all interfaces. To do so, ensure that the listen_address line is not commented out with a # symbol at the beginning of the line and that the address is set to * : listen_address = * Note: If you installed Netmail Archive as a Worker node and are using a database other than PostgreSQL, you should ensure that database information can be properly exchanged between your Master and Worker nodes. Additionally, the PostgreSQL database needs to be configured to allow connections from the Worker nodes. This is configured in the pg_hba.conf file in the same folder on the Master node. To modify the pg_hba.conf file: 1. Open the file for editing in Notepad. 2. Towards the end of the file, add additional IPv4 connection lines for the Master node and each Worker node IP address. For example:: # TYPE DATABASE USER ADDRESS METHOD # IPv4 local connections: host all all /32 md5 host all all /32 md5 host all all /32 md5 Note: Rather than adding a line for each individual Worker node for which you want to allow connections, you may choose to add a single line that allows authenticated ODBC connection from any IP address. This is done by adding a line having the following format: host all all /0 md5 63 Copyright 2013, Messaging Architects. Updated: 10/05/2013

64 Set Up End-User Archive Access with the Outlook Client After successfully installing Netmail Archive in your Exchange environment, you have the option of setting up end-user archive access and stubbing resolution in the Outlook and Outlook Web App (OWA) clients. To do so, you need to perform several steps in order for these features to function properly: Install the Netmail IIS Extensions to your OWA CAS Install the Netmail Archive Outlook Add-In Run the Outlook Add-In on End-User Workstations Install Netmail IIS Extensions The Netmail IIS Extensions need to be installed in order for stubbing and archive access to function properly for OWA. These extensions need to be installed on every Exchange Client Access Server (CAS) that is providing OWA in your environment (by default, this includes all CAS servers). To begin the installation of the Netmail IIS Extensions, locate and run the Netmail IISInstaller.exe file in the installation package provided to you by Messaging Architects on your CAS server. This file should be located in the IIS directory. Important: This installation must be done on the CAS Server where IIS is running for OWA provision. On the Welcome screen, click Next to begin the installation. On the Selection screen, select which of the following features you would like to install: Netmail OWA Stubbing Resolution ISAPI filter: This feature allows for stubs to be resolved in Outlook Web App or Outlook Web Access. Netmail AWA IIS Server Extension: This feature creates a link in Outlook Web App or Outlook Web Access that gives users direct access to Netmail Search. Netmail Archive Outlook Addin server side components: This feature copies the installation files for the Outlook Add-in to the CAS server in preparation for deploying it to workstations. Netmail AWA Web Site: This feature copies the necessary web pages and templates for the Netmail Search interface via OWA. Note: Messaging Architects recommends that you install all components to your CAS servers. Click Next after making your selections. 64 Copyright 2013, Messaging Architects. Updated: 10/05/2013

65 On the Microsoft Exchange version screen, select the Exchange Server version you are using. Click Next to continue. On the Netmail Archive components screen, enter the following information: 1. Under Server, enter the IP address of your Remote Provider Server. The Remote Provider is the component of Netmail Archive that enables Netmail Archive components to connect to the Index Server, allowing you to easily retrieve archived data that has been indexed by Netmail Archive. See Install the Remote Provider(s) for Netmail Search, the Outlook Add-In, and OWA for more information. 2. Under Jexcon Port, enter the secure port number of your Remote Provider Server. Use the default port number of 8443, or enter a different port number if the Remote Provider has been amended to use an alternate port. 3. Under Remote Provider Port, enter the unsecured port number of your Remote Provider Server. Use the default port number of 8888, or enter a different port number if the Remote Provider has been amended to use an alternate port. Click Next to continue. 65 Copyright 2013, Messaging Architects. Updated: 10/05/2013

66 On the Configure Server Parameters screen, enter the following information: 1. Under Active Directory, enter the server name or IP address of a local Active Directory DC server, the LDAP port number for that server, and the Active Directory user name and password of your AD service account created for Netmail Archive use. The user name must be entered using the following syntax: DOMAIN\username. 2. Under Exchange/IIS, complete the following: Enter the server name or IP address of your Exchange Server and the EWS port number. Select SSL if you require a secure (SSL) connection between Netmail Archive and Exchange. If you choose for SSL to be enabled, the default Port is 443. If you choose for SSL to be disabled, the default Port is 80. Note: If you are using an Exchange 2010 Server, you do not need to specify the server name or IP address, port number, or SSL connection requirement. These fields will be greyed out. Enter the server name or IP address of the CAS/IIS Server to which you are installing and the secured IIS port number (default is 443). You should also enter the IIS web site name of the site being used to house the Exchange virtual directory and OWA application. Typically, this is the Default Web Site on your CAS server. If you have a secondary web site also configured for OWA, this too can be specified. Enter the Exchange user name and password for the dedicated mailbox you configured for Netmail Archive (typically, this is the same account as the AD user specified above). The user name must be entered using the following syntax: DOMAIN\username. Note: Note that IIS 6 cannot read web site names. As such, if you are using IIS 6, the IIS Website field will be greyed out. If you are using IIS 7, you will not have this issue. If you are using Windows 2000 or 2003, you will have IIS 6, and if you are using Windows 2008, you will have IIS 7. Click Next to continue. 66 Copyright 2013, Messaging Architects. Updated: 10/05/2013

67 On the Ready to Install screen, click Install to begin the installation. On the Wizard Completed screen, click Finish to complete the Netmail IIS Extensions installation program. 67 Copyright 2013, Messaging Architects. Updated: 10/05/2013

68 It is now necessary to reset your IIS server on the CAS server in order to load the installed extensions. This is most easily done by running the iis reset command at a command prompt. You may want to do so in off hours if this CAS server is currently in use by users. Install the Netmail Archive Outlook Add-In The Netmail Archive Outlook Add-In provides seamless end-user access to archived items through the Outlook client, both via stubs and by providing direct access to the full archive mailbox using an embedded Netmail Search interface. There are four possible ways of installing the Outlook Add-In to an end user s workstation: Interactive (manual) installation Command line based silent installation Group policy based installation Organizational Forms based installation, using notification messages or stubs These methods are discussed in detail in the coming sections. Prerequisite Components Before installing the Netmail Archive Outlook Add-In, you must ensure that certain prerequisite components are installed on the workstations. Earlier versions of Netmail Archive attempted to automatically install these components as part of the Outlook Add-In installation, but because of their varying rights requirements, these components must now be installed separately, before the Add-In can be installed. The installation files for the prerequisite components can be found when you install the Netmail IIS Extensions onto your Exchange client access server(s) as part of your Netmail Archive deployment. By default, the files are located in the C:\IISExt\WebContent folder. The prerequisite installation files are as follows: vstor.exe: This is the Microsoft Visual Studio 2005 Tools for Office Second Edition (VSTO 2005 SE) redistributable package which installs the Visual Studio Tools for Office runtime. This component needs to be installed for ALL USERS of the workstation. Also, since this installation requires writing to the registry (HKLM reg. keys) as well as Program Files sub-folders, it must be run with Local Administrator rights (i.e., the installation needs to RUN AS a user account which is directly or indirectly assigned to the Local Administrators Group of the workstation). Note: For workstations using Outlook bit, which is only applicable to 64-bit operating systems, the VSTO bit version of the VSTO prerequisite must be used. The provided vstor.exe wrapper should detect the 64-bit environment and install this version. This is not required on 64-bit operating systems running 32-bit versions of Outlook. In such a scenario, the 32-bit version of VSTO is still used. If an organization uses standard desktop builds, this component could also be incorporated as part of each workstation s and/or desktop's image to avoid future individual installations. O2003PIA.msi & O2007PIA.msi: These are the Office 2003 and Office 2007 Primary Interop Assemblies (PIA) redistributables. These are Microsoft Windows Installer packages that contain the Primary Interop Assemblies for Office 2003 and 2007 products and are a pre-requisite for the Netmail Archive Outlook Add-In in Outlook 2003 and 2007 environments, respectively. 68 Copyright 2013, Messaging Architects. Updated: 10/05/2013

69 Note: Outlook 2010 has the Primary Interop Assemblies built in and does not require a redistributable. Again this component could be incorporated into any desktop image used for standard builds..net 4 Client Profile: For Outlook bit running on 64-bit operation systems, the.net 4 Client Profile from Microsoft must also be installed as a prerequisite. Important: RPs must be SSL (keystore) enabled to support the Add-In. Interactive Installation of the Netmail Archive Add-In The interactive installation is the simplest method to use when carrying out a small number of installations. Use the C:\IISExt\WebContent\Netmail ArchiveOutlookAddin.exe file ( MPLUSArchive64Setup.exe for Outlook bit) to install the Netmail Archive Outlook Add-In. This file can be found in the same directory as the prerequisite installation files ( C:\IISExt\WebContent). To carry out an interactive installation, follow these steps: 1. Log in to the workstation as the user who will be using the Add-In (the Add-In installs to the Windows Current User, and files and registry settings are installed to the user profile to provide support for roaming profiles). 2. Map a drive to the IISExt\WebContent folder on the Exchange CAS server or copy the NetmailArchiveOutlookAddin.exe file to a local drive on the workstation. 3. Run the Netmail ArchiveOutlookAddin.exe file to install the Add-In. Follow the instructions of the wizard: On the Welcome screen, click Next to continue. On the Parameters screen, enter the URL to the EWV directory on your Exchange Client Access Server containing the Netmail Archive IIS Extensions. 69 Copyright 2013, Messaging Architects. Updated: 10/05/2013

70 On the Ready to Install screen, click Install to begin the installation. On the Wizard Complete screen, click Finish to exit. 70 Copyright 2013, Messaging Architects. Updated: 10/05/2013

71 Command Line Based Silent Installation When there are many workstations on which the Add-In must be installed, it is more convenient to use an installation method that does not involve user intervention, therefore allowing for automation through login scripts or other automation methods. The command line installation method is essentially the same as that of the interactive installation, except that the needed parameter (the URL for the EWV web site) is provided as a parameter. The installation therefore proceeds in a silent manner, as follows: 1. Log in to the workstation as the user who will be using the Add-In (the Add-In installs to the Windows Current User, and files and registry settings are written to their profile). 2. Map a drive to the IISExt\WebContent folder on the Exchange CAS server or copy the NetmailArchiveOutlookAddin.exe and setup.iss files to a local drive on the workstation (use the MPLUSArchive64Setup.exe file in an Outlook bit environment). 3. Execute the following command line with the exact arguments described: Netmail ArchiveOutlookAddIn.exe -s /v"configurl=<http address>" where, -s is for silent install, and the CONFIGURL provides the IP address of the reference EWV web site folder to be used by the Add-In (Example for a 32-bit version of Outlook: Netmail ArchiveOutlookAddIn.exe -s /v"configurl= "). Group Policy Based Installation The Outlook Add-In installation can be performed through a Group Policy in Active Directory. The Group Policy Object (GPO) will require a software distribution location that can be accessed by all workstations that will have this MSI deployed. Preferably, this location is a mapped drive. To perform this type of installation, you need to create or edit an existing GPO through the Group Policy Management Console. To do so, follow these steps: 1. Open the Group Policy Management console. 2. Expand Forest > Domains, and create a new Group Policy. Note that the GPO will be assigned to users, not to computers. 71 Copyright 2013, Messaging Architects. Updated: 10/05/2013

72 3. Right-click the new GPO, and select Edit. This GPO will be applied under User Configuration > Policies > Software Settings > Software installation. 4. In the Group Policy Management Editor, right-click Software installation, select New >Package, and select the Netmail ArchiveOutlookAddin.MSI file for a 32-bit deployment or the MPLUSArchive64Setup.MSI for a 64-bit deployment. 5. In the Deploy Software dialog box, select the Assigned software deployment method, and click OK. 6. Once the policy has been created, right-click the policy, and choose Properties. The NetmailArchiveOutlookAddIn Properties dialog box opens. 7. Select the Deployment tab. Ensure that the deployment type is set to Assigned, the Install this application at logon deployment option is selected, and the Basic installation user interface option is selected. 8. Click OK. You can now assign this GPO to users requiring the Outlook Add-In. 72 Copyright 2013, Messaging Architects. Updated: 10/05/2013

73 Organizational Forms Based Installation Another method of installing the Netmail Archive Outlook Add-In is via the Netmail Archive Organizational Forms. This method is triggered by opening an notification message sent by a Netmail Archive Archive Job, or by opening a stubbed item that was created by Netmail Archive in the user s mailbox. The goal is to synchronize the provisioning of the Outlook Add-In with the users as you start to archive their mail. As mentioned, this deployment method uses the Netmail Archive Organizational Forms. It also requires that an additional MIME type be configured within IIS. The use of Organizational Forms requires the existence of a Public Folders database and an Organizational Forms library in your Exchange system. These exist by default for Exchange 2007, but not for Exchange Note: The Netmail Archive Organizational Forms are required only if stubbing will be implemented or if you want to use this installation method for the Outlook Add-In. The procedure for this deployment method for the Outlook Add-In is as follows: Validate or Create an Public Folder database Validate or Create an Organizational Forms library Install the Netmail Archive Organizational forms Install the Add-In via a stub or notification message Validate or Create a Public Folder Database for Exchange 2010 For Exchange 2007, a public folder database exists by default, but by default the public folder database is not created when you deploy Exchange Therefore, you first have to confirm whether a Public Folder database already exists within the Exchange system. If it does, then you can jump to the next stage of this process. To check if a Public Folder database already exists, open the Exchange Management Console and select the Organization Configuration > Mailbox option in the tree menu. If a public folder database exists it will be shown on the Database Management tab, as shown in the following figure. 73 Copyright 2013, Messaging Architects. Updated: 10/05/2013

74 If no Public Folder database exists, select New Public Folder Database from the Action panel on the right-hand side. The New Public Folder Database wizard opens. On the Introduction screen, enter a name for the database and the Exchange server on which it should reside, and then click Next. 74 Copyright 2013, Messaging Architects. Updated: 10/05/2013

75 On the Set Paths screen, the default paths for the database should suffice, unless you have reason to change them. Click Next to continue. The wizard confirms the actions about to be taken. Click New to proceed. 75 Copyright 2013, Messaging Architects. Updated: 10/05/2013

76 The Completion screen summarizes the creation of the database. Click Finish to exit the wizard. You should now see the new Public Folder Database displayed in the Mailbox configuration screen in the Exchange Management Console. 76 Copyright 2013, Messaging Architects. Updated: 10/05/2013

77 Validate or Create an Organizational Forms Library Now that you have confirmed the existence of a Public Folder database, you now need to validate the existence of or create an Organizational Forms Library on the Exchange Server. An Organizational Forms Library is a special type of public folder that is listed only under the NON_IPM_SUBTREE systems folder of your Public Folder database. You can have only one Organizational Forms Library for each language in an organization. Netmail Archive makes use of this library to store the Netmail Archive organizational forms. In Exchange 2007 and 2010, an Organizational Forms Library may or may not exist, depending on the system. The first step is to validate if it does exist. If this library already exists, proceed with deploying MA forms in the library. Otherwise, follow the steps below to create an Organizational Forms Library in Exchange 2007, or see To create an Organizational Forms Library in Exchange 2010 for the Exchange 2010 procedure. To check if an Organizational Forms Library exists for Exchange 2007 or 2010, navigate to the Toolbox in the Exchange Management Console and start the Public Folder Management Console. 77 Copyright 2013, Messaging Architects. Updated: 10/05/2013

78 Navigate to System Public Folders\EFORMS REGISTRY. If no entry exists below this, then you have no Organizational Forms Library and must create one. If an entry exists under EFORMS REGISTRY, then this is your library, and you should now install the Netmail Archive Organizational Forms. 78 Copyright 2013, Messaging Architects. Updated: 10/05/2013

79 To create an Organizational Forms Library in Exchange 2007: First, you need to create a new public folder using the Exchange Management Shell or Console. Using the Exchange Management Shell: 1. Click Start, point to All Programs, click Microsoft Exchange Server 2007, and then click Exchange Management Shell. 2. Run the following command at the Exchange Management Shell prompt: New-PublicFolder -Path "\NON_IPM_SUBTREE\EFORMS REGISTRY" -Name "Organizational Forms Library" You can use the Exchange Management Shell on any version of Exchange 2007 to create a folder. However, in Exchange 2007 SP1, you can also create the library using the Exchange Management Console. Using the Exchange Management Console: 1. Go to Toolbox in Exchange Management Console. 2. Double-click Public Folder Management Console. 3. In the left pane, click System Public Folders. 4. If no EFORMS REGISTRY folder exists already, in the Action pane, click New Public Folder. Type EFORMS REGISTRY as the folder name, and then click NEW. After the folder is created, click Finish to exit the wizard. 5. In the left pane, expand System Public Folders, and select the EFORMS REGISTRY entry. In the Action pane, click New Public Folder. Type Organizational Forms Library as the folder name, and then click NEW. After the folder is created, click Finish to exit the wizard. Next, you need to add the PR_EFORMS_LOCALE_ID. Use an account that belongs to the Exchange Administrators Group to log on to a client computer that is running Microsoft Office Outlook 2003 or a later version of Microsoft Outlook. 1. Start the Microsoft Exchange Server MAPI Editor ( Mfcmapi.exe) from the MFCMAPI folder. To obtain the MAPI Editor, visit the following Microsoft web site: 2. Create a MAPI profile if it is necessary. 3. On the Session menu, click Logon and Display Store Table. 4. On the MDB menu, click Open Public Folder Store, and then click OK. 5. Expand Public Root, expand NON_IPM_SUBTREE, and then expand EFORMS REGISTRY. 6. Click the public folder that you created previously. For example, click Organizational FormsLibrary. 7. On the Property Pane menu, click Modify Extra Properties. 8. Click Add, and then click Select Property Tag. 9. Click PR_EFORMS_LOCALE_ID in the list, and then click OK. 10. Click OK two times. A red mark is displayed next to the newly created PR_EFORMS_LOCALE_ID property. 11. Double-click PR_EFORMS_LOCALE_ID. 12. In the Unsigned Decimal box, type the desired locale ID, and then click OK. For example, type 1033 for English, type 1040 for Italian, or type a different ID for a different locale. To determine the locale ID for other locales, visit the following Microsoft web site: msdn2.microsoft.com/en-us/li brary/aa aspx" class="external-link" rel="nofollow"> msdn2.microsoft.com/en-us/library/aa aspx. 13. Exit MAPI Editor. Your Exchange 2007 system is now ready for installation of Netmail Archive Organizational Forms. To create an Organizational Forms Library in Exchange 2010: First, you need to create a new public folder using the Exchange Management Shell or Console. Using the Exchange Management Shell: 1. Click Start, point to All Programs, click Microsoft Exchange Server 2010, and then click Exchange Management Shell. 2. Run the following command at the Exchange Management Shell prompt: 79 Copyright 2013, Messaging Architects. Updated: 10/05/2013

80 New-PublicFolder -Path "\NON_IPM_SUBTREE\EFORMS REGISTRY" -Name "Organizational Forms Library" Using the Exchange Management Console: 1. Click Toolbox in the tree of the Exchange Management Console. 2. Double-click Public Folder Management Console. 3. In the action pane, click Open Tool. 4. In the public folder tree of the Public Folder Management Console, expand System PublicFolders, and then click EFORMS REGISTRY. 5. In the actions pane, click New Public Folder. 6. On the Introduction page, complete the following fields: Name: Use this box to type the name of the new public folder, for example, Organizational Forms Library. Path: Use this read-only box to verify the path to the public folder. The path should read: \Non_IPM_SUBTREE\EFORMS REGISTRY. 7. On the Completion page, review the following, and then click Finish to close the wizard: A status of Completed indicates that the wizard completed the task successfully. A status of Failed indicates that the task wasn't completed. If the task fails, review the summary for an explanation, and then click Back t o make any configuration changes. Next, you need to add the PR_URL_NAME property to the library. To perform this procedure, the ExFolders tool ( ExFolders.exe ) must exist in the <Exchange Installation Path>\V14\Bin directory. You can download the tool from one of the following locations: If you are running Exchange 2010 Service Pack 1 (SP1), download the tool here: 1-ExFolders-e6bfd405. If you are running the release to manufacturing (RTM) version of Exchange 2010, download the tool here: com/exchange-2010-rtm-exfolders-c76c3649. After the download, be sure to copy the ExFolders.exe file to the <Exchange Installation Path>\V14\Bin directory. 1. Navigate to the <Exchange Installation Path>\V14\Bin directory, and then double-click ExFolders.exe. Note: You must run the ExFolders tool from an Exchange 2010 server. 2. In the ExFolders management console, navigate to File > Connect. 3. In Connect, click Public Folders. 4. Next to the Global Catalog box, click Select, and then select a global catalog server you want to use. 5. Next to the Database(s) box, click Select, select the public folder database you want to use, and then click OK. A public folder hierarchy will appear in the ExFolders console tree. 6. Expand System Folders, expand EFORMS REGISTRY, right-click the public folder you created for the organizational forms library, and then click Property Editor. 7. On the Property menu, click Add Property To View. 8. In Add Property To View, type 0x E, and then click OK. 9. Sort the Name column to find the PR_URL_NAME property you just added. 10. Right-click PR_URL_NAME, and then click Edit Value. 11. In the Value box, type /NON_IPM_SUBTREE/EFORMS REGISTRY, and then click OK. 12. Close the ExFolders tool. Next, you need to add the PR_EFORMS_LOCALE_ID Property. 80 Copyright 2013, Messaging Architects. Updated: 10/05/2013

81 1. Start the Microsoft Exchange Server MAPI Editor ( Mfcmapi.exe) from the MFCMAPI folder. Note: To perform this procedure, you must use the Microsoft Exchange Server MAPI Editor (MFCMAPI) tool on a computer that is running the 64-bit version of Microsoft Outlook To download MFCMAPI, visit the following Microsoft web site: microsoft.com/download/en/details.aspx?displaylang=en&id= Create a MAPI profile if it is necessary. 3. On the MDB menu, click Open Public Folder Store, and then click OK. The Public Folder Management Console appears. 4. In the console tree, expand Public Root, expand NON_IPM_SUBTREE, expand EFORMSREGISTRY, and then click the public folder that you created previously. For example, click Organizational Forms Library. 5. In the result pane, in the Property Name(s) column, click the PR_URL_NAME property. 6. On the Property Pane menu, click Modify Extra Properties. 7. In Extra Properties, click Add. 8. In Property Tag Editor, click Select Property Tag. 9. In Property Selector, click PR_EFORMS_LOCALE_ID, and then click OK. 10. Click OK to close Property Tag Editor, and then click OK to close Extra Properties. 11. To verify that the property was added, in the Public Folder Management Console, locate the newly created PR_EFORMS_LOCALE_ID prope rty in the Property Name(s) column. A red exclamation point (!) is displayed as its icon. 12. Double-click PR_EFORMS_LOCALE_ID to open Property Editor. 13. In the Unsigned Decimal box, type the desired locale ID, and then click OK. For example, type 1033 for English, 1040 for Italian, and so on. To determine the locale ID for other locales, visit the following Microsoft web site: Exit MAPI Editor. Install the Netmail Archive Organizational Forms Now that you have validated or created a Public Folder database and Organizational Forms Library, you are now ready to install the Netmail Archive Organizational Forms. On a workstation or server with Outlook 2003 or higher installed, copy the necessary files to any temporary directory on the workstation: MAExchangeSetup.vbs MessagingArchitectsAppt.oft MessagingArchitectsMail.oft MessagingArchitectsTask.oft These files can be found in the IISExt\WebContent directory on the CAS server on which you installed the Netmail Archive IIS Extensions. While logged in as a user with permissions to the Public Folders database, run the MAExchangeSetup.vbs file. The following prompt should appear: Note: You may also be prompted for a mail profile and password and should ensure you are using a mail profile for a user with adequate permissions to the Public Folder database (typically, a member of the Exchange Administrators group). Enter the valid URL to the Netmail Archive EWV virtual directory on your CAS server IIS server, and then click OK. The forms are now be loaded into the Public Folder you created earlier and the following confirmation window should appear: 81 Copyright 2013, Messaging Architects. Updated: 10/05/2013

82 Click OK to finish. You can confirm that the organizational forms are installed by opening Outlook and selecting File > Options > Advanced > Custom Forms. Click Manage Forms, and you should see the following: This screen can also be used to validate the installed form versions when carrying out upgrades of the organizational forms. Important: You need to run the MAExchangeSetup.vbs file every time Netmail Archive is updated or upgraded. IIS MIME Type Requirement As the final step to accommodate the Outlook Add-In installation method using Organizational Forms, it is necessary to add an additional MIME type to your IIS Server configuration on your Exchange Client Access server. This will allow for the use of the setup.iss file. You can do this at the command line of your IIS Server by using the following command: %SystemRoot%\windows\system32\inetsrv\appcmd set config /section:staticcontent /+[fileextension='.iss',mimetype='text/plain'] Alternatively, you can use the MIME Types icon in the Features View of the IIS Manager by adding the file extension.iss with a MIME type of text/ 82 Copyright 2013, Messaging Architects. Updated: 10/05/2013

83 plain. Using the Organizational Forms to install the Add-In Once the Organizational Forms are installed and the.iss file type added to the MIME types, installation of the Outlook Add-In by this method is triggered by the opening of a notification message or a stub in the user s Outlook Client. The first step in this method therefore, is to create one of these in the user s mailbox. If you want to send a notification message to trigger the install, the following steps must be followed: 1. Run an Archive job against the mailboxes to which you want to install the Add-In to. Ensure you select the Send an Outlook AddIn Install Notification option in the Criteria tab of the Archive job in WebAdmin. 2. Once the job is complete, an notification should appear in the end user s inbox. By double-clicking the message, the end user will trigger the installation of the Add-In. If you are using stubbing in your environment and want to use a stub to trigger the Add-In installation, you need to run either an Archive job with stubbing enabled or a post-archiving Stubbing job against the user mailboxes for which you want to install the Add-In. Run the Outlook Add-In on End-User Workstations If you are using a stub or notification message to trigger the Add-In installation, when an end user opens the item in their Outlook Client, they will 83 Copyright 2013, Messaging Architects. Updated: 10/05/2013

84 be prompted to download and install the Netmail Archive Outlook Add-In. The end user should click Yes to download and install the Add-In. Once the installation of the Add-In is complete, the user must restart Outlook. After end users follow these simple steps, the Outlook Add-In should be fully installed. Using the Netmail Archive Outlook Add-In for the First Time Regardless of which method was used to install the Netmail Archive Outlook Add-In, the first time an end user tries to access their archives for the first time after the installation of the Add-In, they are prompted for their password. Once their password has been entered, it is validated and cached in the registry, so users do not have to re-submit their password each time they want to access their archives. To access Netmail Search though Outlook, users need to click the Add-Ins tab and then select Netmail Archive from the dropdown. Netmail Search is then displayed directly in their Outlook client. To return to their inbox and view their mail, users simply have to click on the Inbox folder. It is also possible for stubs to be resolved in the Outlook Client. A small stubbing icon will differentiate stubbed items from non-stubbed items in the Outlook Client. The following figure shows the stubbing icon: 84 Copyright 2013, Messaging Architects. Updated: 10/05/2013

85 85 Copyright 2013, Messaging Architects. Updated: 10/05/2013

86 Install the Remote Provider(s) for Netmail Search, the Outlook Add-In, and OWA In order to gain access to archived items through the Netmail Archive archive viewer interfaces, you need to install the Remote Provider. The Remote Provider is a client access proxy between the client plug-ins and the archive data and indexing engine. All client access calls and authentication validation related to archive access are handled by the Remote Provider. Through the installation of the Remote Provider, users will be able to use the Netmail Search standalone viewer, as well as gain access to the Netmail Search interface directly through Outlook or Outlook Web App. In addition, if you have chosen to use stubbing in your environment, the Remote Provider is instrumental in the stub resolution process for Outlook and Outlook Web App. Note: Outlook Web App is the 2010 version of Outlook Web Access. If you are currently using Outlook Web Access, you still need to install the Remote Provider in order for users to be able to open Netmail Search directly in Outlook Web Access. Installing the Remote Provider(s) In small and medium sized systems, the Remote Provider component is typically installed onto one or more of the archive nodes. In larger systems, where the user load on the Remote Provider justifies it, dedicated Remote Provider servers may be used. To install the Remote Provider on your chosen system, navigate to the RemoteProvider folder, and run the RemoteProvider.exe file. The installation program will guide you through the installation process. Follow the onscreen instructions to install the Remote Provider. On the Re mote Provider Welcome screen, click Next to proceed. On the Choose Destination Location screen, install the Remote Provider in the default location, or browse to the location where you would like to install the Remote Provider. Click Next to continue. 86 Copyright 2013, Messaging Architects. Updated: 10/05/2013

87 On the M+Open and Jexcon Configuration screen, enter the requested information for configuration. 1. Under Netmail Open Configuration, complete the following: Under Netmail Archive Master IP, enter the IP address of the Master Archive server. This will be used by Netmail Search when carrying out export jobs. Under Netmail Archive Master port, enter the port number used by the Master Archive server for Netmail Archive cluster communications. The default number is 8585 unless you modified it during installation. 2. Select MS Exchange or MS Exch Online as the messaging server you are using with your Netmail Archive system, and enter the IP address of the first CAS server where you have installed the Netmail Archive IIS extensions under IIS Extension Server IP. You will configure your other CAS server addresses later. Note: If you select MS Exch Online, the IIS Extension Server IP field will be auto-populated and greyed out. 3. Click Next to continue. The Remote Provider LDAP Connectivity Parameters screen lets you configure how the Remote Provider will access the edirectory server using LDAP. 87 Copyright 2013, Messaging Architects. Updated: 10/05/2013

88 Note: When completing the fields on this screen, enter the same information you entered when configuring Netmail Archive s access to the edirectory server using LDAP. 1. Under LDAP Server IP Address, enter the IP address of the edirectory LDAP Server. 2. Select SSL if you require a secure (SSL) connection between Netmail Archive and the edirectory tree. If you enable SSL, the default Port Number is 636. If you do not enable SSL, the default Port Number is 389. However, if you LDAP server is configured to listen on a different port, you can change the default port number. 3. Under Administrator Common Name, specify the account name with administrator rights to the edirectory section where the Netmail Archive configuration objects were stored. This is the account that was created as part of the prerequisites prior to installation. See edirectory Access. 4. Under Administrator Password, specify the password used to access the account. 5. Under edirectory Configuration Container, specify the path to the container where you created the Netmail Archive objects in edirectory using the syntax illustrated in the example. The User container field is not used for Exchange. 6. Select Perform validation if you want the installation program to validate the information provided. 7. Click Next to continue. On the Remote Provider Configuration screen, you can configure the Remote Provider. 88 Copyright 2013, Messaging Architects. Updated: 10/05/2013

89 1. Under Netmail Search/AWA Remote Provider, Install Netmail Search/AWA Remote Provider is selected by default. The Netmail AWA Remote Provider allows Netmail Search to be accessed through a standalone Web browser, Outlook Web App, or Outlook (through the Add-In). The Netmail AWA Remote Provider is also needed to carry out stub resolution for Outlook and Outlook Web App. 2. Under AWA Port, enter the TCP/IP port number that the Remote Provider will listen on for requests. By default, this port number is 8888 and should not require changing. 3. Under SMTP Server IP, enter the IP address of your Exchange SMTP Server. Important: The Netmail Search interface allows users to forward items out of the archive store to designated recipients. It uses the SMTP server specified here as an SMTP relay for sending these forwarded mails. When specifying the SMTP Relay Server IP, ensure that your mail server is configured to allow relaying from the IP address of this Remote Provider server. 4. Click Next to continue. The Logon Information screen allows you to specify which Windows account you want to use to start Remote Provider services. In order to start Netmail Archive services, you must have local Administrator privileges on the server. Enter the password for the account. Click Next to continue. On the Ready to Install screen, click Install to begin the installation. 89 Copyright 2013, Messaging Architects. Updated: 10/05/2013

90 On the Wizard Complete screen, click Finish to complete the installation. Restart the server if necessary. After you have clicked Finish in the Remote Provider installation wizard, you are prompted as to whether you would like to create the keystore necessary for SSL communications. Even if you do not plan to use SSL for Remote Provider communications, it is good practice to complete these steps. On the first popup that refers you to the Netmail Archive Installation Guide for instructions on configuring certificates, click OK. On the Question popup, click Yes to proceed with keystore generation. 90 Copyright 2013, Messaging Architects. Updated: 10/05/2013

91 On the Creating a Keystore screen, enter a password to be used for this process. Note that any random password will suffice, and this password does not need to be recorded. Click Next to proceed with keystore generation. A command window briefly appears while this is being carried out. Once the command window closes, the process is complete. Remote Provider Post-Installation Tasks After completing the Remote Provider installation program, there are several post-installation tasks for you to complete in order for Netmail Search to function properly. Registering Additional CAS Servers Once you have finished installing the Remote Provider, you can register any additional CAS servers where you have installed the Netmail Archive IIS Extensions. This is done by adding the address of those servers to the Trusted IP list of the Remote Provider. 1. On the Remote Provider server use Notepad or Wordpad to open the jexcon.ml file located in C:\Program Files (x86)\messaging Architects\RemoteProvider. 2. Search for the XML tag <trustedips> and enter the list of IP addresses of your CAS servers between this tag and the </trustedips> tag. For example: <trustedips> , , </trustedips> Starting the Remote Provider Service After installing the Remote Provider or making any changes to the Remote Provider configuration files, you must (re)start the Windows service 91 Copyright 2013, Messaging Architects. Updated: 10/05/2013

92 which was created. 1. To start the service manually, choose Control Panel > Administrative Tools > Services from the Windows Start menu. 2. Double-click Services to open the Services dialog box. 3. Locate the Netmail AWA Remote Provider service in the list of services. Start, or Stop and restart, the service as appropriate. Configuring the Remote Provider on a Server with Multiple IP Addresses The Remote Provider listens on port 8888 for communications from the viewers. When the server running the Remote Provider is configured with two or more network interfaces and has two different IP addresses on different subnets (such as NAT), you need to specify on which address the Remote Provider should listen. 1. On the Remote Provider server, open the xgwxmlv.cfg file located in C:/Program Files/Messaging Architects/Remote Provider. 2. Locate the line in the file which contains: nat.host= 3. Edit the line to include the IP address on which the Remote Provider should listen. Example: nat.host= Save the changes made to the xgwxmlv.cfg file, and then restart the Netmail AWA Remote Provider service. Configuring Netmail Search It is possible to modify some of the default settings in Netmail Search in order to change behavior of the Netmail Search interface. Depending on your compliance needs and wants, you can enable the End-User Delete option. You can also change Netmail Search audit tags, or add or modify dropdown lists. If you plan to use Netmail Search's exporting functionality, read the tips below to avoid running into any problems. Enable End-User Delete End-User Delete gives administrators the ability to allow ALL users, without any exceptions, to delete their archived items via the Netmail Search interface. As such, End-User Delete should be used with caution. With this feature, items are permanently deleted from the archive, but the audit files are kept for ediscovery purposes. To enable End-User Delete, follow these steps: 1. Browse to the Remote Provider folder C:\Program Files(x86)\Messaging Architects\RemoteProvider, and open the xgwxmlv.cfg file. 2. Locate the following line in the file: Message.deletable=false. 3. Edit the line so that it states the following: Message.deletable=true. When this line is set to true, users can delete items from their archives through Netmail Search. 4. After modifying and saving the file, restart the Netmail Remote Provider service. Warning: Messaging Architects generally does not advise enterprises to enable End-User Delete, because with this feature, enterprises no longer have control over their records. Before enabling this feature, please consult your legal counsel. Once this feature is enabled, a Delete button will appear in users Netmail Search interface. Customize Netmail Search 92 Copyright 2013, Messaging Architects. Updated: 10/05/2013