Docstoc

Netmail Archive 5.1 Beta - Training… - Messaging Architects

Document Sample
Netmail Archive 5.1 Beta - Training… - Messaging Architects Powered By Docstoc
					NETMAIL ARCHIVE 5.1 - BETA TRAINING

REFERENCE DOCUMENT
TABLE OF CONTENTS

Exchange Online Support ..............................................................................................................................................5

   Supported Features Summary ...................................................................................................................................5

       Exchange Online Mailbox Plans .............................................................................................................................5

       Netmail Archive Feature Support ..........................................................................................................................5

   Netmail Archive With Exchange Online - Operational Overview ..............................................................................6

   Netmail Archive Deployment ....................................................................................................................................7

       Prerequistes ...........................................................................................................................................................7

       Installation Wizard Changes ..................................................................................................................................9

   Outlook Add-in Operation .......................................................................................................................................11

   GroupWIse to Exchange Online Migration ..............................................................................................................13

       Migration Process Summary ................................................................................................................................ 13

       Microsoft Online Services Directory Synchronisation Tool .................................................................................14

       Provisioning Users From GroupWise ...................................................................................................................15

       Address Book Sync & Injection Jobs ....................................................................................................................24

Exalead CloudView ......................................................................................................................................................25

   Exalead Architectural Changes ................................................................................................................................25

   Installation Changes.................................................................................................................................................26

       Server Pre-Requisites...........................................................................................................................................26

       Installation Wizard ...............................................................................................................................................27

       Exalead Services...................................................................................................................................................29

       Exalead Cluster Manager Tool ............................................................................................................................. 29

       maIndexConfig Attribute Setting ......................................................................................................................... 41

   Exalead 4.6 Index Conversion ..................................................................................................................................43

       How Conversion Works .......................................................................................................................................43

       Carrying OUt Conversion .....................................................................................................................................44

NetMail Search Export Function ..................................................................................................................................52
   Export Format ..........................................................................................................................................................52

   Using the Export Wizard ..........................................................................................................................................53

       Initial Selection of Items ......................................................................................................................................53

       Running the Export Wizard ..................................................................................................................................53

       Tracking Export Job Progress ...............................................................................................................................60

       Export Job Completion ........................................................................................................................................63

   Utilizing Exported Data ............................................................................................................................................66

       PDF Exports ..........................................................................................................................................................66

       PST Exports ..........................................................................................................................................................66

       XML Exports .........................................................................................................................................................67

   How the Export Wizard Works ................................................................................................................................68

       Export Process Back-End Summary .....................................................................................................................68

       PDF Export Rendering ..........................................................................................................................................70

   Netmail Search Export Troubleshooting Checklist ..................................................................................................71

Migration Changes.......................................................................................................................................................73

   Migration Changes Summary ..................................................................................................................................73

   Provisioning Wizard Changes...................................................................................................................................73

       Provisioning Wizard – Import User Mapping Workflow ......................................................................................74

       Provisioning Wizard – Standard User Provisioning Workflow .............................................................................81

       Provisioning Wizard - Distribution LIst Workflow................................................................................................98

Netmail Archive 5.1 Beta -Deployment & Upgrade Strategy ....................................................................................107

   New Deployments .................................................................................................................................................107

       Archive Server Installation .................................................................................................................................107

       Remote Provider Install .....................................................................................................................................120

       Index Server Installation ....................................................................................................................................122

   M+Archive to NetMail Archive Upgrades ..............................................................................................................123

   BETA Deployment Strategy ....................................................................................................................................123
      Deploying a New System ................................................................................................................................... 123

      Upgrading an Existing M+Archive System .........................................................................................................123

Unified UI – Netmail WebAdmin (Warp) ................................................................................................................... 127

   Netmail WebAdmin Installation ............................................................................................................................127

   Netmail WebAdmin Operation & Current issues...................................................................................................131

      Logging In ...........................................................................................................................................................131

      Netmail WebAdmin – Operation .......................................................................................................................132

      Current Issues ....................................................................................................................................................134




Author: David Nicoll

Date: December 2011

Version: 1.2 - Beta Refresh
5    Netmail Archive 5.1- Training Reference



    EXCHANGE ONLINE SUPPORT

    This section outlines the new features in Netmail Archive 5.1 for integration with Exchange Online environments,
    as provided within Microsoft’s Office 365 and Live@Edu services.

    More background information on Exchange Online can be found in the Microsoft Service Description for Exchange
    Online, available at, http://tinyurl.com/67vtsku

    That document includes details on prerequisites which the organization using Exchange Online shall need to have
    in place before implementing or moving to Exchange Online.




    SUPPORTED FEATURES SUMMARY


    EXCHANGE ONLINE MAILBOX PLANS

    Each user who accesses the Exchange Online service requires to be assigned to a subscription plan. Exchange
    Online offers three types of plans: Exchange Online Kiosk, Exchange Online (Plan 1), and Exchange Online (Plan 2)
    (more details in the Service Description document mentioned above). Plan 1 and Plan 2 mailboxes include the
    ability to enable the Exchange 2010 personal archive mailbox feature. Plan 2 mailboxes also include the Exchange
    2010 Legal Hold option. Note also that although Kiosk mailboxes do not support direct access via EWS, they do
    support EWS impersonation based access, as used by Netmail Archive. As such, all plan types are supported by
    Netmail Archive.




    NETMAIL ARCHIVE FEATURE SUPPORT

    Netmail Archive 5.1 now includes the capability of deployment in Exchange Online environments as one of the
    supported mail platforms. As with other mail platforms, a dedicated Netmail Archive system is required for the
    Exchange Online environment, and this cannot also archive an on premises Exchange deployment for example.

    The functionality available with Exchange Online systems is restricted by the fact that no modification can be made
    to the back-end Exchange components. As such the following list summarizes the key supported features,

        •   Address Book Synchronization from Exchange Online.
        •   Archiving of Exchange Online mailboxes to on-premises archive stores.
        •   Outlook Add-in based access to archives.
        •   Complete Netmail Archive ILM management and Export capabilities for on-premises archives.
        •   Provisioning Wizard support for migration of GroupWise accounts to Exchange Online.
        •   Migration Agent Injection directly into Exchange Online live mailboxes.
        •   Utility Agent reduce jobs against Exchange Online mailboxes.


    The following features, provided when using on-premises Exchange environments, are not possible or not required
    with Exchange Online systems,
                                                                                         Exchange Online Support       6


     •    OWA based archive access – Since no access is available to the IIS servers providing the OWA access,
          Netmail Archive OWA integration is not possible.
     •    Stubbing support – At the moment stub resolution via the Outlook Add-in is not possible with Exchange
          Online systems, and as such all stubbing features are disabled when deploying against Exchange Online.
     •    Organizational Forms – Therefore no Org Form based installation of the Outlook Add-in is possible.

The following sections explain how Netmail Archive is deployed in an Exchange Online environment and how
specific functionality operates.




NETMAIL ARCHIVE WITH EXCHANGE ONLINE - OPERATIONAL OVERVIEW

A Netmail Archive deployment in an Exchange Online system is a very simple system when compared with one
against an Exchange on-premises system. The only Netmail Archive components which interact with the Exchange
Online system are the Archive Servers - for address book synchronisation, archiving, and deletion (plus injection in
migration scenarios).

No IIS Extensions are required to be installed (although an ewv Virtual Folder can be created on an IIS server to
house the Outlook Add-in config.xml file), and no integration with on-premises AD is required, except in the case of
migration.




Figure 1 - Netmail Archive Server to Exchange Online Connectivity




All communications between Netmail Archive and the Exchange Online system are performed by embedding the
EWS commands within Remote PowerShell scripts via PowerShell API calls. This introduces an additional
prerequisite for the Archive Servers as outlined below.
7    Netmail Archive 5.1- Training Reference



    NETMAIL ARCHIVE DEPLOYMENT

    Deploying Netmail Archive in an existing Exchange Online environment differs from an Exchange on-premises
    deployment in several key ways.


    PREREQUISTES


    REMOTE POWERSHELL

    As stated earlier, each Archive server shall require an additional prerequisite of Remote PowerShell support.

    Using Remote PowerShell, administrators and applications can connect to Exchange Online to perform
    management tasks that are not available or practical in the web management interface of Exchange Online. For
    example, they can use Remote PowerShell to automate repetitive tasks, extract data for custom reports, customize
    policies, and connect Exchange Online to existing infrastructure and processes.

    To use Remote PowerShell, administrators’ computers, and hence Netmail Archive archive servers, must be
    running the Windows Management Framework, which contains Windows PowerShell v2 and WinRM 2.0. These
    components are already installed in computers running Windows 7 or Windows Server 2008 R2. Administrators
    can manually download these components for computers running other operating systems from

             http://support.microsoft.com/kb/968929

    Administrators do not need to install any Exchange Server management or migration tools in order to use Remote
    PowerShell. See the help topic Use Windows PowerShell in Exchange Online for instructions on how to use Remote
    PowerShell.

    Exchange Online uses the same PowerShell commandlets as Exchange Server 2010 Service Pack 1, with certain
    commands and parameters disabled because these features do not apply in the hosted environment. For a list of
    the commandlets available to Exchange Online administrators, see Reference to Available PowerShell Cmdlets.




    EWS IMPERSONATION

    An Exchange Online account with EWS Impersonation rights is still required to facilitate access to all mailboxes. A
    dedicated mailbox is recommended although not absolutely necessary. EWS Impersonation rights can be
    configured via Remote PowerShell access to the Exchange Online system as follows.

    1. Create a dedicated Exchange Online mailbox for Netmail Archive to use,
             e.g. nmarchive@domain.onmicrosoft.com


    2. Run the following powershell commands from a workstation or server with Remote Powershell components (as
    outlined above).

    To connect to Exchange Online first get the admin credentials for session
                                                                                     Exchange Online Support     8



$cred = Get-Credential

This will prompt you for credentials. Enter the username and password for a user allocated to the Organization
Management role in Exchange Online (normally your company administrator account – or any account with admin
rights on the Exchange Online system)

        e.g. username: admin@domain.onmicrosoft.com password: abcd1234

Create a new powershell session to Exchange Online


$s = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri
https://ps.outlook.com/powershell -Credential $cred -Authentication Basic -AllowRedirection

On Vista, Windows 2008, and Windows 7, allow the powershell command to run (certificate) by setting the
policy


Set-ExecutionPolicy remotesigned

Import session commands
$importresults = Import-PSSession $s

The powershell session is now open you can run available commands on Exchange Online.

To display all imported commands that are available to run

Get-Command -Module $importresults | Out-Host -Paging



To set impersonation for the Netmail Archive user account [nmarchive]
New-ManagementRoleAssignment -Name:impersonationAssignmentName1 -Role:ApplicationImpersonation -User:nmarchive
9    Netmail Archive 5.1- Training Reference



    INSTALLATION WIZARD CHANGES

    There are only minor changes to the Netmail Archive installation wizard when installing to an Exchange Online
    environment.


    ARCHIVE SERVER INSTALLATION WIZARD

    The first change is to the Messaging Server dialog box, as shown below.




    Select MS Exchange Online to continue.

    NOTE: Stubbing is not supported with Exchange Online, so future versions of the wizard may be modified to
    disable the Enable Stubbing check box once Exchange Online has been selected.

    When MS Exchange Online has been selected the subsequent Exchange Server Configuration dialog box shall also
    be different, as shown below.
                                                                                          Exchange Online Support      10




The Exchange URL setting shall be auto-populated and greyed out, since PowerShell is used for all connections to
the Exchange Online system.

No Active Directory settings are required since no on premises AD is required for Exchange Online. Instead Netmail
Archive will perform all viewer based authentication via the Exchange Online system.

The Exchange Administrator settings should refer to the appropriate account which you created as a dedicated
account for Netmail Archive use, and granted EWS impersonation rights to, on the Exchange Online system.

NOTE: All Office 365 accounts require that passwords are changed regularly. When you change the password
associated with this dedicated account, you must also update the password in the Netmail Archive configuration
via WebAdmin.




REMOTE PROVIDER INSTALLATION WIZARD

During Remote Provider installation a new option appears in the Exalead and JexconConfiguration dialog for MS
Exch Online. Selecting this option greys out the requirement for Stubbing Agent IP or IIS Extensions server details,
as shown below, since these are not relevant to an Exchange Online deployment.
11    Netmail Archive 5.1- Training Reference




     OUTLOOK ADD-IN OPERATION

     There are two significant factors to consider for Outlook Add-in operation in an Exchange Online environment.


     ADD-IN AUTHENTICATION

     As there is no access to the back-end AD system supporting the Exchange Online system, the Add-in cannot use AD
     account details for authentication. The only ID which can be used is the user’s Exchange Online email address and
     password. Accordingly the prompt for credentials at Add-in first time startup and when detecting password
     changes now asks for the Email Address as opposed to the User ID.
                                                                                           Exchange Online Support       12




NOTE: Netmail Archive deployments to Exchange on-premises systems also now use the email address for
Outlook add-in and Viewer authentication. They also support user ID based authentication, but behind the
scenes the user id is simply used to lookup the email address and authentication is carried out using the email
address.


CONFIG.XML STORAGE

Since there is no access to the IIS servers which provide the Exchange Online OWA client access, it is not possible
to house the Outlook Add-in configuration file, config.xml, on the IISExt server where it exists for an on-premises
Exchange deployment of Netmail Archive.

There are two options for storage of the c onfig.xml in an Exchange Online environment.

    •    Copy config.xml to each workstation – The config.xml can be created and included in the Add-in
         installation directory on workstations where the Outlook Add-in is installed. If using group policy based
         deployment this addition can be made relatively easily. Consideration does need to be given regarding a
         suitable method for modifying all workstation copies of the config.xml should any changes be necessary.
    •    Create an EWV virtual folder on an existing on-premises IIS server or a new dedicated deployment of IIS
         for this purpose. This is a manual process at the moment, as follows.

CONFIGURING STANDALONE IIS SERVER FOR OUTLOOK ADDIN CONFIG.XML STORAGE

Requirements
   • IIS installed on server

    1.   Copy the Config.xml file from the OutlookAddin directory of the installation directory to the IIS server in a
         folder that will be used for the IIS Application (e.g. c:\ewv)
    2.   Modify the Config.xml file with the following parameters:
         Jexcon:
         <Server>IP of AWA Remote Provider</server>
         <port>SSL port for AWA Remote Provider</port>            (Default is 8443)
13    Netmail Archive 5.1- Training Reference



              Remote Provider
              <Server>IP of AWA Remote Provider</Server>
              <Port>AWA Remote Provider Port</Port>                 (Default is 8888)
         3.   Manually create the website in IIS:

     To manually create the website in IIS:

         1.   In IIS manager expand your IIS connections and right click on Default Website>Add Application
         2.   Under the Alias, type in EWV
         3.   Under Physical path, put in the path to the config.xml (e.g. C:\ewv) and click ok.
         4.   Left click on the EWV folder and then open Directory Browsing. On the right hand side, click enable.




     GROUPWISE TO EXCHANGE ONLINE MIGRATION


     MIGRATION PROCESS SUMMARY

     For organisations moving from GroupWise to Exchange Online, Netmail Archive can be used to facilitate migration
     in the same way that it can be used with migrations to on-premises Exchange.

     There are some key differences to the stages involved in such a migration though. The steps involved are as
     follows.

         1.   Two Netmail Archive systems are deployed, one against GroupWise and one against Exchange Online.
         2.   GroupWise mail is archived into xml archives as usual.
         3.   The GroupWise accounts are provisioned into an on-premises AD using a new Exchange Online option in
              the Provisioning Wizard. This step also writes Netmail Archive user objects containing migration attributes
              such as MAID to the eDirectory tree used by the Exchange Online Netmail Archive system.
         4.   The on-premises AD accounts are provisioned to the Exchange Online system by using the Microsoft
              Online Services Directory Synchronization Tool.
         5.   Accounts created in the Microsoft Online Services system by Directory Synchronization need to be
              activated/licensed for Exchange Online.
         6.   The Netmail Archive system deployed against Exchange Online is used to carry out an Address Book Synch
              to load user information. This will merge the user information with the eDirectory user objects created by
              provisioning at step 3.
         7.   Migration jobs are used to inject GroupWise xml archives into Exchange Online mailboxes.

     The key differences from migrations to on-premises Exchange systems are at steps 3 and 4, where the user
     provisioning is done to an intermediate on-premises AD system, and the Directory Synchronization Tool is then
     used to create accounts in the Exchange Online system. The use of the eDirectory user objects to store migration
     attributes rather than the system map file is also a significant change.
                                                                                          Exchange Online Support        14


Step 5 is an important step. It is essential that Online Services accounts created by the DirSync tool are enabled for
Exchange Online before the Address Book Synch is run, to avoid essential migration attributes such as the MAID
being lost, since these are now stored in eDirectory.




Figure 2 - GW to Exchange Online Migration Components




MICROSOFT ONLINE SERVICES DIRECTORY SYNCHRONISATION TOOL

The Microsoft Online Services Directory Synchronisation Tool is normally used where organizations are operating
Exchange Online in conjunction with on-premises Active Directory, to allow synchronization between existing AD
accounts used locally for other services and the accounts created in the cloud for Exchange Online.

NOTE: This also covers scenarios where organizations are using Exchange Online in hybrid mode where some
Exchange accounts are in the cloud and some are in an on-premises Exchange system. Such a hybrid model
would require two Netmail Archive deployments to archive both sets of mailboxes.

In GroupWise to Exchange Online migration scenarios we can make use of this tool to work around the fact that
we cannot provision users directly into the Microsoft Online Services directory.

A video summarizing use of this tool can be found at,

http://www.microsoft.com/en-us/showcase/details.aspx?uuid=cc64351a-26e3-46b5-9d34-02fb1d4bfe9f
15    Netmail Archive 5.1- Training Reference


     The tool can be downloaded at,

     http://www.microsoft.com/download/en/details.aspx?id=5535

     NOTE: Microsoft states that activating directory synchronization should be considered a long-term commitment.
     Currently, you can’t deactivate the Directory Synchronization tool in your Online Services configuration after
     you have activated it. After you have activated directory synchronization, you should only edit synchronized
     objects using on-premises apps.


     DIRECTORY SYNCH PREPARATION AND REQUIREMENTS

     There are a few key points to note about the use of Directory Synchronization

         •    The Directory Synchronization Tool is not yet available as 64-bit and as such must be run on a 32-bit
              version of Windows 2003 or 2008. Updates on the availability of a 64-bit version are provided at,
              http://g.microsoftonline.com/0bd00en-us/599
         •    The server running the Directory Synchronization tool must be in the same windows domain as the AD
              forest that you plan to synchronize, but cannot be a domain controller.
         •    Directory Synchronization only supports synchronising up to 10,000 objects (users and groups).
         •    For AD trees containing up to 50,000 total objects, Directory Synchronization uses Microsoft SQL Express.
              For larger trees a full instance of SQL Server is required.
         •    All Office 365 accounts require that passwords are changed regularly. When you change the password
              associated with the administrator account used by Directory Synchronization, you must run the Microsoft
              Online Services Directory Synchronization Configuration Wizard again and provide the new password.

     For full details on preparing on-premises AD for use with directory synchronization and deploying the tool see,

              http://onlinehelp.microsoft.com/en-us/office365-enterprises/ff652544.aspx


     EXCHANGE ONLINE SINGLE SIGN-ON

     Microsoft recommends that organizations maintaining local on-premise AD should set up single sign-on before
     setting up directory synchronization. Single sign-on enables users to sign in to Exchange Online using their
     corporate credentials.

     Further details are available at,

              http://onlinehelp.microsoft.com/en-us/office365-enterprises/ff652540.aspx




     PROVISIONING USERS FROM GROUPWISE

     As outlined above this is a two-step process

         •    Provisioning from GroupWise to on-premises AD
         •    Provisioning from AD to Exchange Online
                                                                                        Exchange Online Support      16


Each step is detailed in the following sections.


PROVISIONING TO AD

Once the AD tree has been prepared for Directory Synchronization we must provision the users and distribution
lists from GroupWise to AD.

This is done using the Netmail Archive GroupWise to Exchange Migration Tool (Provisioning Wizard). The wizard
contains a new option for provisioning users to AD for Exchange Online, as shown below.




The email address specified should be a valid address for a company administrator on the Exchange Online system,
i.e. an account with admin rights.

The eDirectory details to be entered are for the eDirectory tree which shall be used by the Netmail Archive system
operating against Exchange Online.

NOTE: Currently, if the Provisioning Wizard is run on an archive server then it shall automatically read the
CluserConfig.xml file from the Messaging Architects\Config directory in order to set the eDirectory LDAP
settings, and this screen shall NOT be displayed. This may change in future releases.
17    Netmail Archive 5.1- Training Reference


     If the wizard is run on a workstation you can copy the ClusterConfig.xml from the Exchange Netmail Archive system
     archive server and use the Browse ClusterConfig File button to read it to populate the eDirectory settings.

     Alternatively enter the settings manually.


                     IMPORTANT: If you run the provisioning wizard on an archive server in the GW
                     Netmail Archive system, then it shall read the ClusterConfig from that server and this
                     shall result in user objects being created in the wrong eDirectory tree or container. It
                     shall also cause the wizard to continue as if the Exchange On-premises setting had
                     been chosen.

                     If you wish to run the wizard from an archive server on the GW Netmail Archive
                     system, then you shall need to temporarily rename the ClusterConfig.xml file or the
                     Config folder to stop this file being found and hence allow you to enter settings
                     manually

                     This auto-detect feature may be changed for General Release to avoid this problem
                     scenario.



     The third step of the provisioning Wizard has also changed for Exchange Online scenarios. Only the AD settings are
     required and no connection to read the Exchange System Objects is made as it is with on-premises Exchange
     migration. See below,
                                                                                       Exchange Online Support     18


The remaining screens of the provisioning Wizard are unchanged, although there is no requirement to specify an
Exchange Storage Group in the user default settings when creating users, since all we are doing is creating AD
accounts for synchronisation by the Directory Synchronization tool.




PROVISIONING FROM AD TO EXCHANGE ONLINE

Once the Provisioning Wizard has been run to create the users and groups in AD it is simply a matter of allowing
the Directory Synchronization Tool to synchronise these objects to the Microsoft Online Services directory. The
Directory Synchronization service runs automatic synchronization every three hours. The time taken to complete
synchronization depends on the number of objects being synched from AD.

Synchronization can be triggered immediately rather, than awaiting the periodic synchronization, by running the
Directory Synchronization Configuration Wizard, as follows




Click Next on the opening screen
19    Netmail Archive 5.1- Training Reference




     Enter the email address and password of an admin account on the Exchange Online system then click Next




     Enter credentials for an admin account from the AD tree being synchronised then click Next
                                                                                      Exchange Online Support     20




Ignore the popup regarding Rich Coexistence (unless this is a customer operating a hybrid model of Exchange on-
premise plus Exchange Online in which case the customer should be consulted as to whether they are using Rich
Coexistence). Click Next.
21    Netmail Archive 5.1- Training Reference


     The Wizard shall now configure the Directory Synchronization settings and services on this system to use the
     settings entered. When complete the following window shall display.




     Click Next to move to the following window.
                                                                                        Exchange Online Support     22




Select the option to synchronize now then click Next to start an immediate Synchronization. A popup shall display




This popup provides a link to a help page describing how to verify synchronization has taken place.

The simplest way is to check the Windows Application Event Log for entries from Directory Synchronization stating
that Export has started and completed.




ACTIVATING ACCOUNTS FOR EXCHANGE ONLINE

Once the users and groups have been synchronized to Microsoft Online Services it is then necessary to Activate
these accounts for Exchange Online. This can be done either with the Microsoft Online Services Administration
Portal or via Powershell scripts.
23     Netmail Archive 5.1- Training Reference


     MICROSOFT ONLINE SERVICES ADMINISTRATION CONSOLE

     Using the portal activation can be done individually user by user by opening individual user properties, or by multi-
     select of users and using the Activate Synced Users option, as shown below.




     Figure 3 - Microsoft Online Services Administration Portal


     USING POWERSHELL SCRIPTS TO ACTIVATE USERS

     A powershell script can be run to enable all unactivated users in the Online Services directory for Exchange Online.
     Care should be taken when using this script that it is indeed the case that all users are to be activated. Some
     organisations using Office 365 for example may have some accounts which are not to be licensed for Exchange
     Online.

     A Powershell script, named MAUnlicense.ps1 is available from the Dev team and is executed in one of the
     following ways.

          •    PREREQUISITES

                     o    Make sure you have powershell V2. Download

                     o    Make sure you have the MSOnline module installed on the machine being used. 32bit Download,
                          64bit Download

                     o

     You then have two options, running the script unsigned by bypassing the execution policy or setting the execution
     policy as unrestricted, or, running the script in signed mode.
                                                                                          Exchange Online Support       24


        UNRESTRICTED OR BYPASS EXECUTION POLICY

                 Open PowerShell and run the following command

                          Set-ExecutionPolicy ByPass or Set-ExecutionPolicy Unrestricted

                 Download the script from Dev and run it from powershell

                           *.\MAUnlicense.ps1 you will be prompted for administrator's username, password and
                          locale (US, CA,...)

                          .\MAUnlicense.ps1 -admin someone@onmicrosoft.com -locale US you will be
                          prompted for password

        HOW TO RUN SIGNED SCRIPT

                 Download the certificate from Dev and install it

                          Double click on the certificate and install it in Trusted Root Certification Authority. See
                          attached screenshots

                 Open PowerShell and run the following command

                          Set-ExecutionPolicy RemoteSigned

                 Download the script and run from powershell

                          *.\MAUnlicense.ps1 you will be prompted for administrator's username, password and
                          locale (US, CA,...)

                          .\MAUnlicense.ps1 -admin someone@onmicrosoft.com -locale US you will be
                          prompted for password




ADDRESS BOOK SYNC & INJECTION JOBS

Once accounts are fully provisioned in Exchange Online, an Address Book Synch should be run to load all Exchange
user information into the Netmail Archive eDirectory tree.

Following that, the Migration Agent can be used to create injection jobs to take items from the GW xml archives
into Exchange Online in exactly the same way as with Exchange on-premises deployments.
25    Netmail Archive 5.1- Training Reference



     EXALEAD CLOUDVIEW

     Netmail Archive 5.1 replaces the Exalead 4.6 used in M+Archive 2010, with Exalead 5, also called Exalead
     CloudView. CloudView has significant advantages over Exalead 4.6, the most important being the ability to
     increase the capacity of the indexing system without the need to re-index archive data.

     There are several important changes and new concepts with Exalead CloudView, which this section will summarize.
     These changes also necessitate a conversion of any existing 4.6 indexes in any system being upgraded from
     M+Archive, in order for them to be used in a Netmail Archive 5.1 system. This section outlines the conversion
     process to be followed to complete that task.




     EXALEAD ARCHITECTURAL CHANGES

     Some of the main architectural changes to the indexing system with the introduction of CloudView are,

         •   No more Instances – Exalead CloudView no longer uses the concept of Instances which existed in Exalead
             4.6. Instead the index estate is split into build groups, and the build groups split into slices. These are
             described in more detail below. The biggest advantage of this change is that we are no longer bound by
             the instance count, meaning that we can scale the system easily without reindexing. This also alleviates
             the need to estimate the future instance requirement at deployment time, since we can now deploy a
             relatively small index system and grow it as required.
         •   No Exalead Web Service – The need for the Exalead WebService has disappeared, so all Netmail Archive
             components which communicate with the index system now do so directly to the CloudView service
             ports.
         •   Build Groups – A build group is the closest equivalent to a 4.6 instance. It contains an index plus a logical
             collection of CloudView components containing all the processors and resources necessary to accept and
             analyse documents and to build one or more index slices for that particular index. Build groups are not
             restricted to residing on a single physical server in the way instances were. Instead build groups can be
             distributed across servers by the use of slices. This is what gives us the much improved scalability. In
             Netmail archive there are two core build groups – bg0, for 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 Exalead 4.6 indexes.
         •   Index Slices – An index is organized into one or more slices to facilitate index distribution and load
             balancing. In a single server index system, the number of slices for each build group on that server is set
             to optimize performance based on the number of processor cores in the server. When additional servers
             are added to the index cluster, new slices for each build group are added on those servers to allow the
             build group to extend across all available servers.
         •   Master and Slave(s) structure – With Exalead 4.6 we operated a pseudo-master and slave structure by
             spreading instances across servers but configuring one server to perform amalgamated searches across all
             of these remote_sites. With CloudView the Master and Slave architecture is integral to the Exalead cluster
             architecture. All CloudView 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 so extend the distribution of the index
                                                                                                  Exalead CloudView       26


          system. The Master server is then responsible for the distribution of indexing load across all servers in the
          cluster (including itself) and will endeavour to balance the indexes evenly across the available servers.
     •    Network Ports – CloudView uses many of the same ports as Exalead 4.6, but by default uses port 10000
          as the base port and requires 200 ports from this base port to be available, i.e. 10000-10199. Since we
          recommend dedicated servers for index servers this should not cause problems.




Figure 4 - Example of Build Groups and Slices across servers




INSTALLATION CHANGES

Due to the different architecture of CloudView there are some changes to the pre-requisites, installation wizard,
and the post-installation configuration tools and procedures.


SERVER PRE-REQUISITES

For CloudView there are some new server pre-requisites.

     •    Microsoft .Net 4 Framework – Available at
          http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718
     •    Microsoft Visual C++ 2005 SP1 Redistributable ATL 32-bit AND 64-bit – Available at
          http://www.microsoft.com/download/en/details.aspx?id=14431
     •    Microsoft Visual C++ 2008 SP1 Redistributable ATL 64-bit – Available at
          http://www.microsoft.com/download/en/details.aspx?id=11895
27    Netmail Archive 5.1- Training Reference



     INSTALLATION WIZARD

     There are some minor changes to the Exalead setup wizard to reflect the new architecture.

     The first change is that the Exalead installation no longer updates the maIndexConfig attribute in eDirectory.
     Configuring that attribute is now done solely within Netmail Archive WebAdmin. As such there is no need to
     connect to eDirectory during the Exalead installation, so no corresponding request for LDAP settings during the
     installation wizard.

     The installation paths specified during the setup wizard are also slightly different for CloudView. There are still two
     installation directories; one for the CloudView binaries and one for the indexes. The default path for the binaries
     has changed to a folder named CloudView in the Program Files directory, rather than the Exalead Enterprise folder
     in Program Files (x86) used by Exalead 4.6. There should be no reason to change this default path.




      The default path for the indexes is still in a folder named Indexing but the subdirectory is also now named
     CloudView. The only change that should be necessary to this default path is to change the volume on which the
     Indexing folder is created to the appropriate index store volume.
                                                                                          Exalead CloudView   28




The next change in the setup wizard is to the main Exalead configuration window. The new window is shown
below.
29    Netmail Archive 5.1- Training Reference


     The first server to be installed must be set as the Master, and all subsequent servers installed as Slaves.

     For the Master server install you must specify the IP address of the server being installed to, together with the
     Base and Gateway ports. The default values of 10000 and 10011 should be used unless you have good reason to
     change them. For Slave servers the Master settings must still be specified, but in addition, the IP address of the
     Slave host being installed to is required.




     EXALEAD SERVICES

     Following installation there is only one Exalead CloudView service named,

              Exalead CloudView – cvdefault

     as opposed to the single service per instance and the web service which existed in 4.6. The following screenshot
     shows the services list on an Exalead 4.6 server which has had CloudView installed ready for conversion of indexes.




     NOTE: Do NOT start the CloudView service on a newly installed SLAVE server until you have run the Cluster
     Manager Tool to register the Slave with the Master server and configure slice numbers for the Slave server.




     EXALEAD CLUSTER MANAGER TOOL

     The Exalead Cluster Configuration tool used with Exalead 4.6 in M+Archive systems is no longer required since
     there are no longer any index instances to be configured as Remote Sites.

     That tool has been replaced by the Exalead Cluster Manager Tool, the purpose of which is two-fold,

         •    Used to configure CloudView hosts (both Master and Slave servers) to optimize the number of index slices
              for each build group based on the number of processor cores within the server.
         •    Used to register Slave servers with the Master CloudView server in order to add the Slave server to the
              Exalead cluster and allow the Master to balance indexing operations across all available servers.

     The Exalead Cluster Manager tool is a Messaging Architects custom utility and is found on the index server
     following installation in the following location.
                                                                                                  Exalead CloudView     30


         C:\Program Files\CloudView\Netmail Archive Tools\ExaleadClusterManager.exe

The utility can be run from any location but is most easily run on the Master CloudView server.. In summary the
tool should be used in the following scenarios.

    •    Configuring the CloudView cluster for a new deployment – In this situation you shall use the tool to
         establish a new CloudView cluster, registering all slaves and configuring slice counts for all servers, then
         apply those changes.
    •    Adding a new slave server to an existing CloudView cluster – In this scenario you shall use the tool to
         register one new slave to an existing CloudView cluster and set the slice counts for that new server.

Although the tool is used in a similar way in both scenarios, the following sections provide detailed step by step
instructions for both to avoid any confusion. The key aspects in using the tool are,

     •   All configuration is done via the Master server
     •   Slave servers should be registered and have their slice counts configured before they are installed.



DEPLOYING A NEW CLOUDVIEW CLUSTER

This is the scenario used when carrying out new clean installs of Netmail Archive (See later section for information
on upgrades from M+Archive with Exalead 4.6).

You should already have established the number of Index servers you are going to deploy, using the Exalead sizing
guidelines. The first index server installed is the Master Index server. As soon as you have completed the Master
server CloudView install carry out the following post-installation steps,

    1.   Ensure the Exalead CloudView service is running on the Master server.
    2.   Run the Exalead Cluster Manager executable.
    3.   The following screen shall appear - Enter the IP address and port numbers of the Master server (all
         configuration changes are submitted via the Master server)
31   Netmail Archive 5.1- Training Reference




       4.   Click Connect and you should see, after a few seconds, the list of installed index hosts appear.




            To begin with this list shall only list the Master Index server. We now want to register each of the planned
            Slave servers to add them to this list.

            NOTE: If you are implementing a single Index server environment you can skip this step and go straight
            to step 6. Also note that there is no need to predict future Slave server needs, you need only register
            those Slave servers which you are configuring now as part of the initial deployment.
                                                                                               Exalead CloudView    32


5.   For each Slave server in turn enter the IP address in the New Host IP setting and the Base Port (default
     port is 10000) then click Add Host. You should end up with a list of all Index servers in the Hosts list, as
     follows,




6.   Now that we have registered all our Slave servers we need to configure the slice numbers for the Master
     and each Slave. Select the first Host to configure in the Host list then click Configure
33   Netmail Archive 5.1- Training Reference




       7.   In the resulting window enter the number of processor cores on this host server and, if this is an Exalead
            4.6 server being upgraded, enter the number of 4.6 instances on this server which are going to be
            converted. Click Evaluate and the recommended Slices counts will automatically populate as shown
            above.

       8.   Click OK and a confirmation popup shall display.




            Click Yes to proceed.

       9.   The Cluster Manager Tool shall now make modifications to the Exalead configuration. When configuration
            has completed another popup shall be displayed confirming success.




            Click OK.
                                                                                           Exalead CloudView   34


10. The tool now returns to the main cluster manager screen.




    Repeat steps 6 to 10 to configure slice numbers for each of the other Hosts (i.e. the Slave servers)

11. Once slice numbers have been configured for all hosts, click Apply to commit the changes to the Master
    server.




    A popup confirms configuration application and increments the Exalead configuration version number.
35   Netmail Archive 5.1- Training Reference




       12. Restart the Exalead CloudView service on the Master server.




       13. In the Exalead Web Admin tool you can confirm the slice numbers for build groups match what you just
           configured.




           You can also go to Previously Applied Configurations to confirm the configuration number being used.
                                                                                               Exalead CloudView        36




    14. You can now proceed with installing CloudView to any Slave servers (or starting the CloudView service on
        the Slave servers if you have already installed the software).



ADDING A SLAVE SERVER TO AN EXISTING CLOUDVIEW CLUSTER

It may become necessary to extend the CloudView cluster to provide additional indexing capacity, either soon after
the initial deployment if it is realized that greater scalability is warranted, or at some time after the system has
been running and it is decided that additional capacity is required.

Adding a new Index server is a very simple process. We are simply going to use the Cluster Manager tool to register
the server and configure the slice numbers for it. Following that we install the new slave server and start it up. In
detail the process is.

    1.   Ensure the Exalead CloudView service is running on the Master server.
    2.   Run the Exalead Cluster Manager executable.
    3.   The following screen shall appear - Enter the IP address and port numbers of the Master server (all
         configuration changes are submitted via the Master server)
37   Netmail Archive 5.1- Training Reference




       4.   Click Connect and you should see, after a few seconds, the list of installed index hosts appear.




       5.   Enter the IP address of the new Slave server in the New Host IP setting and the Base Port (default port is
            10000) then click Add Host. You should end up with a list of containing your new slave server(s) as follows,
                                                                                          Exalead CloudView   38




6.   Now that we have registered our Slave server we need to configure the slice numbers for it. Select the
     Host entry for the new Slave in the list,




     then click Configure.
39   Netmail Archive 5.1- Training Reference




       7.   In the resulting window enter the number of processor cores on this host server and click Evaluate. The
            recommended Slices counts will automatically populate as shown above.

       8.   Click OK and a confirmation popup shall display.




            Click Yes to proceed.

       9.   The Cluster Manager Tool shall now make modifications to the Exalead configuration. When configuration
            has completed another popup shall be displayed confirming success.




            Click OK.

       10. The tool now returns to the main cluster manager screen.
                                                                                        Exalead CloudView    40




11. Once slice numbers have been configured for all hosts, click Apply to commit the changes to the Master
    server.




12. A popup confirms configuration application and increments the Exalead configuration version number
13. Restart the Exalead CloudView service on the Master server.
41    Netmail Archive 5.1- Training Reference




         14. In the Exalead Web Admin tool you can confirm the slice numbers for build groups match what you just
             configured.




         15. You can now proceed with installing CloudView to the Slave server (or starting the CloudView service on
             the Slave server if you have already installed the software).




     MAINDEXCONFIG ATTRIBUTE SETTING

     As mentioned previously, the Exalead installation process no longer writes the maIndexConfig attribute to
     eDirectory. Setting this attribute is now a manual process via WebAdmin and should be completed once the
     CloudView servers have been fully installed and configured.

     To configure the index settings in WebAdmin, navigate to the System>Configuration tab and complete the Index
     Servers section as shown in the following screenshots and steps
                                                                                            Exalead CloudView      42




1.   First, ensure that you enter the IP address and port settings for the Master CloudView server into the
     Host, Baseport, and Gateway port settings, as above.
2.   The Document Cap setting will limit the number of documents which are submitted for indexing to this
     server. Once the limit has been reached no more documents shall be pushed to this index server and you
     must ensure other index servers are available for new data.
3.   Now for each Slave server Click the Add button to add it to the Index nodes list by entering the IP address
     in the resulting window and clicking Save. Again note the Document Cap setting for each server added.




4.   You should now have a complete list of all index servers
43    Netmail Archive 5.1- Training Reference




         5.   Click on the main Save button on the Configuration tab to commit these index server settings to the
              maIndexConfig attribute in eDirectory




     EXALEAD 4.6 INDEX CONVERSION

     For organizations upgrading an existing M+Archive system to Netmail Archive, there shall be existing Exalead 4.6
     indexes which must be converted to Exalead CloudView format if they are to be used by the Netmail Archive
     viewers.

     For small M+Archive deployments it may be deemed simpler to dispose of the 4.6 indexes and re-index all the data
     with Netmail Archive, and hence CloudView, but in the majority of cases conversion will be the quickest way to
     maintain access to existing archive data.


     HOW CONVERSION WORKS

     The Cluster manager Tool and a dedicated Messaging Architects conversion tool are used when converting Exalead
     4.6 Indexes to CloudView. Together these tools complete several key tasks,

         •    Configures a new build group on the CloudView system named bg_4_6 to house the converted indexes.
         •    Creates a slice within that build group for each 4.6 instance being converted.
         •    Copies the index files from the 4.6 instance folder to the appropriate slice folder under the CloudView
              directory structure.
         •    Converts the 4.6 index files to CloudView format.

     The end result is a new build group, bg_4_6, with an index slice per 4.6 instance, each of which contains the
     converted indexes from the corresponding instance. These slices for will be created to reside on the same servers
     where the 4.6 instances resided.
                                                                                               Exalead CloudView       44


In order to use these converted indexes you will also need to carry out a corresponding upgrade of the M+Archive
Archive and Remote Provider servers to Netmail Archive, ensuring that the archive repository names are
maintained exactly as they were on the M+Archive system.




CARRYING OUT CONVERSION

The recommended approach to index conversion is to install CloudView 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 system
should have its services running at any time, to avoid port conflicts. The Index server housing Exalead 4.6 Instance
‘0’ would typically become the CloudView Master server. Any additional 4.6 servers will become CloudView Slaves.

Before shutting down Exalead 4.6 to start conversion, you may wish to take a note of the document counts from
each 4.6 instance. These can be compared to the results of the conversion process. Ensure that no updates are
made to the 4.6 instances (data or audit) after you take any counts.

Once CloudView is installed on the Exalead 4.6 servers, the 4.6 services should be shut down when you are ready
to proceed with conversion, and the CloudView service started on the Master. The standard Cluster Manager Tool
process to register slaves and set the CloudView slice configuration should be carried out as described in the
previous section. The only modification to the process is to make provision for the converted instances within the
slice counts.




As shown above this is simply done by indicating the number of Exalead 4.6 instances which exist on each server as
you configure the slice numbers for that host. This will create the bg_4_6 build group and slices to house the
converted indexes.
45    Netmail Archive 5.1- Training Reference


     Once all Slave registrations and slice count configurations have been made, then the Master Exalead CloudView
     service is restarted. There is now one more step to be completed with the Cluster Manager Tool before starting
     conversion.


     INITIALIZE CONVERSION

     Before starting the first index conversions it is first necessary to prepare the CloudView cluster for conversions.
     This is currently achieved via an additional button in the Cluster Manager Tool.

         1.   Start the Cluster Manager Tool and enter the Master index server details then click Connect. You should
              see the list of CloudView hosts appear




         2.   Click the Initialize Conversion button. A popup shall display warning you that any existing converted index
              data shall be deleted
                                                                                                 Exalead CloudView   46


    3.   Acknowledge this popup by clicking Yes to proceed. Behind the scenes the Exalead configuration is now
         readied for index conversion. You shall be returned to the main Cluster Manager Screen. Click Close to
         exit the Cluster Manager Tool.

The CloudView cluster is now ready for index conversions to be carried out. The conversion tool can be found at,

         C:\Program Files\CloudView\Netmail Archive Tools\IndexConversionTool.exe

Conversion is typically carried out on the Master server first, then each of the Slave servers containing 4.6
instances, if any. The process to be carried out on each server is detailed in the following section.


INDEX CONVERSION TOOL EXECUTION

Follow these steps to use the index conversion tool to convert the 4.6 instances on a server.

    1.   After starting the executable the following screen shall be displayed,




         Acknowledge the pre-requisites and click Next.

    2.   A screen shall appear prompting for the appropriate paths to the Exalead 4.6 and CloudView index stores.
         Use the Browse buttons to select the correct folders as shown here (choosing the correct drive for your
         particular system)
47   Netmail Archive 5.1- Training Reference




           In addition complete the Master IP and port accordingly.

           If this is a Slave server you are converting 4.6 instances on, then you shall also need to specify the Slave
           server IP address and a UNC or Drive Mapping based path to the CloudView index data path on the server,
           as shown in this example below,

           NOTE: This connection to the Master index server when converting 4.6 instances on Slave servers is
           crucial, as it allows the centrally managed Document Identifiers Handler table to be updated.

           NOTE: When converting instances residing on the Master server itself there is no need to additionally
           specify the Master index data path as that path will already have been specified in the settings above.
                                                                                          Exalead CloudView   48




     Click Next when all settings have been entered.

3.   A screen shall now display showing the 4.6 instances that have been found on this server at the path
     specified.
49   Netmail Archive 5.1- Training Reference


            Select the instances which are to be converted (normally all instances). The default method is Copy, which
            shall leave the 4.6 instances untouched, but if you are very short of space on the indexing volume you
            may need to change this to the Move method. Move should only ever be used if a confirmed backup of
            the current state of the 4.6 instances exists. Click Next when ready.

       4.   The conversion process shall now begin with the index files being copied from the 4.6 instance to the slice
            directory within the CloudView system.




       5.   As part of this process a command window shall appear when the dictionary is being copied.
                                                                                        Exalead CloudView   50


6.   Once the copy has completed the indexes are converted to CloudView format and then the process is
     repeated for the next 4.6 instance (if any).




7.   Once all instances have been processed an “Index conversion is done” message is displayed,
51   Netmail Archive 5.1- Training Reference


       8.   Click Finish to exit the conversion tool. A popup shall be displayed reminding you to restart the Exalead
            CloudView service.




       9.   Restart the Exalead CloudView service on the Master (and on this server if conversion was taking place on
            a Slave)

       10. Confirm in the Exalead Admin tool that the new build group has been created and slices contain correct
           document numbers for the converted instances.
                                                                                   NetMail Search Export Function      52



NETMAIL SEARCH EXPORT FUNCTION

Exporting of archives has been greatly simplified in Netmail Archive. In M+Archive, Export Agent jobs could be used
to export items that could be defined by a policy to xml files which were indexed by a packaged copy of Exalead; or
to export items to another location; or also to export items to PST file. More granular exports than could be
defined by a policy could be carried out from M+Analytics, but required the use of the Export Agent to then
package these exports up.

The xml exports produced with M+Archive, together with the packaged Exalead indexes could be cumbersome to
use by any third party to whom you needed to provide the exports.

In Netmail Archive this situation has been significantly simplified. The Export Agent now carries out two different
types of jobs,

    •    WebAdmin submitted Export Jobs – These are similar to the old M+Archive export jobs in using a policy to
         define the items for export, but they are restricted to exporting to another location, or exporting to PST.
    •    Netmail Search submitted Export Jobs – Netmail Search (the new branding for M+Analytics) now contains
         a new Export wizard which is used to submit export jobs via HTTP to the Netmail Archive master archive
         node. This job is then executed by the archive server with monitoring available in WebAdmin or Netmail
         Search.

The remainder of this section describes the new Netmail Search Export Wizard submitted export jobs.



EXPORT FORMAT

The format of exports can be any of three possible types,

    •    PDF file – Exported items can be grouped together into one collective PDF file or separated into a single
         PDF files per item. PDF export of attachments requires the addition of suitable conversion software on the
         archive servers. More details on this are provided in the final part of this section of the document, which
         explains how the export wizard works.
    •    PST file – Exports can be made into Microsoft Personal Storage Table (PST) file format. This type of export
         can then be easily read using a Microsoft Outlook client, or any other tool capable of using this Windows
         messaging standard file format. This type of export requires Outlook installed on the Archive servers.
    •    Netmail Archive XML format – Exports can be made to the same XML format as used within Netmail
         Archive. When exporting to this format, the exported items are indexed using dtSearch and packaged
         together with a self-contained version of the NetMail Search utility (referred to as Netmail Search Lite).
         This provides everything the third party needs to view and search the exported items in one simple zip-file
         package.
53    Netmail Archive 5.1- Training Reference



     USING THE EXPORT WIZARD

     The following steps describe the procedure to be followed in order to carry out an export of archived data.


     INITIAL SELECTION OF ITEMS

     The Export function allows you to select the entire contents of one or more search tabs in Netmail Search, or
     specifically selected items within one or more search tabs, as the source data to be exported. Therefore the first
     task is to ensure that the items intended for export are contained within one or more search tabs within a current
     Netmail Search superuser session.

     This can be achieved by opening a previously prepared Case, creating a new Case, or modifying an existing one, to
     define the appropriate scope of items within the search tabs.

     Once the search tabs contain the items required then, if required, you may mark as selected the specific items
     within those search tabs which you wish to export. If you are exporting the entire set of items within the search
     tab(s), then no further selection is required.


     RUNNING THE EXPORT WIZARD

     The Export wizard is started by selecting New Export from the Export menu within the Netmail Search interface,
                                                                                  NetMail Search Export Function       54


The New Export wizard window shall popup displaying step 1 of 6.


NEW EXPORT WIZARD – STEP 1/6




At this step choose whether the export should contain items from all search tabs or only a selected subset of tabs.
Checking the selected tab(s) option results in additional check boxes being displayed for each of the current search
tabs.




Make the required selections then click Next to move to step 2.
55    Netmail Archive 5.1- Training Reference



     NEW EXPORT WIZARD – STEP 2/6

     Now select which items on those tabs are to be exported; all items, or only those items checked as selected




     When you make your choice an appropriate count of the items is shown.




     Click Next to move to the next step.
                                                                                NetMail Search Export Function      56



NEW EXPORT WIZARD – STEP 3/6

It is now necessary to select the desired export type.

NOTE - PST Export requires Outlook to be installed on the Netmail Archive server(s). PDF export of attachments
requires additional software on the Archive servers for processing non-pdf attachments.




Select the required export format and click Next.


NEW EXPORT WIZARD – STEP 4/6

The Export Wizard now provides a choice of additional information which can be included in the export. The choice
of available information is dependent on the format of export chosen, since some options are not required for
some formats.
57    Netmail Archive 5.1- Training Reference


     For PDF based exports the choices are,




     For XML Export choices are limited to,
                                                                               NetMail Search Export Function    58


For PST export choices are limited to




Select the required additional information then click Next for the next step




NEW EXPORT WIZARD – STEP 5/6

The wizard now displays the packaging options for the export. As large exports could amount to several hundred
megabytes, or even gigabytes worth of information, it may be convenient to break down the export into
manageable chunks for simpler storage on portable media for provision to third parties.

The wizard provides several packaging options from which to choose.
59    Netmail Archive 5.1- Training Reference


     Selecting Custom, results in an additional prompt for the custom packaging size.




     Select the appropriate packaging options then click Next to move to the final step.


     NEW EXPORT WIZARD – STEP 6/6

     The final step of the wizard is to provide the export with a name and to state whether a notification email is to be
     sent at completion of the export job. If notification is required, an email address can be specified as the recipient.
     By default this shall be the email address of the superuser of the current NetMail Search session.
                                                                                     NetMail Search Export Function        60


NOTE: If the Netmail Export Search job under the Export Agent in WebAdmin also has an email address set for
notification in the Log Settings, then that address shall also receive the notification email.

It is also possible (since the Beta refresh build 5.1.0.328) to select the option to encrypt the export. For pdf exports
this will result in a password protected pdf file, for xml and pst exports password protected zip files will be
produced.

Clicking Finish will now submit the Export job for execution on the Netmail Search Archive Server(s). In Netmail
Search the Current Export(s) window shall now be displayed to track progress of the current export job, alongside
summary lines for previous exports.




TRACKING EXPORT JOB PROGRESS

Once the New Export wizard steps are completed, the corresponding Export Job can be tracked in the Current
Export(s) window of NetMail Search




This window displays a list of all of the export jobs which have been run or are running for the current superuser
and case.

As the current export job progresses the Current Export(s) window in Netmail Search shall refresh automatically to
update the progress indicator.
61    Netmail Archive 5.1- Training Reference




     Eventually the export job will finish. If you have left Current Export window open this will be indicated by progress
     showing as 100%
                                                                                 NetMail Search Export Function       62


If the Current Export(s) window or Netmail Search session was closed before the job completed, the window can
be re-opened simply by selecting Previous Export from Export menu.

NOTE: If reopening Netmail Search, ensure that you login as the same superuser and load the same discovery
Case that the export was constructed from.




As the Export Job is executed by the archive server(s), it can also be monitored within the Nodes>Monitor option in
WebAdmin, in the same way as any other job.
63    Netmail Archive 5.1- Training Reference



     EXPORT JOB COMPLETION

     Once the job has completed, the Netmail Search Current Export(s) window shall indicate 100% Progress. If the
     option to send an email notification at the end of the export job was selected, then the notification email shall be
     received by the selected recipient upon job completion also (as well as any address specified for notification in
     WebAdmin). This email contains job summary and error reports as well as a prompt to log in to Netmail Search to
     retrieve the export.




     RETRIEVING THE EXPORT

     Once the job has completed the export can be accessed via the Current Export(s) window.




     Clicking the Details button in the Current Export(s) list will display more information concerning the export
     together with a link to access the actual export file.
                                                                                  NetMail Search Export Function   64


For a PDF Export this would look as follows,




For an XML export links to both the zip file package and a search header summary file are available.
65    Netmail Archive 5.1- Training Reference


     For a PST links are provided to the PST file(s) and the search header summary file.




     EXPORT FILE BACK-END STORAGE

     Export files are stored as part of Discovery Case Management device, as defined within the Storage section of
     WebAdmin, under the appropriate superuser and case folder.
                                                                                   NetMail Search Export Function     66



UTILIZING EXPORTED DATA




PDF EXPORTS

Opening PDF exports requires a reader application compatible with Adobe Acrobat PDF format files. The most
common of these is the Adobe Acrobat Reader application. Simply open the PDF files produced by the export in
order to read the data.

The first page of the PDF shall contain the Export header information specifying the options specified via the
Export Wizard.




Thereafter each exported item shall be listed together with the selected additional information for the item –
Audit data, Meta data, and/or attachments.

The standard search tools within your PDF reader application can be used to search the PDF file for any particular
information you wish to find amongst the exported data.




PST EXPORTS

PST Exports can be opened for reading using the Microsoft Outlook client. Simply select the File>Open option from
the Outlook client menus and locate the PST file(s) created by the export. Outlook shall create a folder
representing the PST file and list the sub-folders and exported items within those folders.

Standard Outlook client search functions can be used to search the PST file for any particular information you wish
to find amongst the exported data.
67    Netmail Archive 5.1- Training Reference



     XML EXPORTS

     XML exports take the form of a packaged zip file for provision to the intended recipient of the exported
     information. Alongside the zip file shall be an export header PDF file containing the export options specified as part
     of the export wizard process. The recipient of the export should follow these steps to utilize the exported data.

         1.   Unzip the Export package zip file using a standard file unzipping utility, such as those built in to recent
              versions of the Microsoft Windows operating system.

              The resulting files are comprised of three main folders, Analytics, Case Management, and Data, together
              with a batch file named start.bat.

         2.   Execute the start.bat batch file. Provided your workstation has a suitable version of the Java runtime
              environment installed (jre version 1.6 or later) this will open your browser and load the Netmail Search
              Lite interface.




         3.   Simply select the Export on the left folder to see the exported items in the message list pane, and then
              use the standard features of Netmail Search Lite to search and inspect the data. See the Netmail Search
              Lite user guide for further information.
                                                                                  NetMail Search Export Function      68



HOW THE EXPORT WIZARD WORKS

The preceding sections of this document explain how to utilize the export wizard in Netmail Search to produce
exported data, as well as how to then use the exported data. The purpose of this section is to explain the back-end
mechanics of the export process.

One of the key elements of this process is the new ability within Netmail Archive to trigger M+Open jobs via HTTP
requests as well as via the previous method via eDirectory.

A second key new feature is the replication of the Remote Provider directory to the Case Management Device
(CMD). The first time the Netmail AWA Remote Provider service is started it generates a copy of the Remote
Provider directory into a folder named export_dp on the Case Management Device folder structure. The service
also automatically detects any changes to the files in the Remote Provider folder at subsequent service startup and
replicates these changes to the copy within the Case Management device.

In this way a copy of the Remote Provider files is always available on the CMD to all archive nodes, and it is this
replicated copy which is used by the archive server when executing export jobs submitted from the Netmail Search
wizard.




EXPORT PROCESS BACK-END SUMMARY

The following is a summary of the process followed when a Netmail Search Export is created using the Export
Wizard. It is not intended to show each step in detail but rather to offer an overview of the major steps and
components involved.




    1.   The user completes the Export Wizard in Netmail Search and clicks Finish. This results in the workstation
         submitting an mplus.ediscovery.advanced_export posting to the Data Provider servicing this Netmail
         Search session. This post contains all the required information from the settings entered in the export
         wizard, together with details on the search tabs and items selected for the export.
    2.   The Data Provider writes these settings to a file uniquely named with an exportID (using a timestamp for
         this ID) in a folder named export2 under the relevant case folder on the Case Management Device.
69    Netmail Archive 5.1- Training Reference


         3.   The Data Provider now sends an HTTP job trigger to the M+Open service on the Master Archive server (as
              defined in the xgwxmlv.cfg file with the new maopen.host and maopen.port settings). This trigger
              launches the Export Agent’s Netmail Search Export job. The trigger also contains parameters identifying
              the superuser, case, and exportID.
         4.   The Master Archive server launches a GWOpenProcess as normal to execute the job (note that this job
              will be allocated to an available archive node in the same way as any other job, which may or may not be
              the same master node. This summary assumes the same node for simplicity). The GWOpenProcess for the
              export job copies the replicated Remote Provider directory from the export_dp folder on the case
              management device to a folder named Messaging Architects\exporter on the same archive server running
              the job. (Note: Replicated Remote Provider folders will exist on the case management device for each
              AWA Remote Provider in the Netmail Archive system. The one copied shall be the one matching the
              remote Provider which submitted the export job trigger). The GWOpenProcess now launches a java
              process to run as the Exporter Remote Provider, using the exporter folder just created.
         5.   The Exporter RP creates an export results folder, named <exportid>_results in the case folder on the case
              management device.
         6.   The Exporter RP reads the export file which was created at step 2 in order to determine the export job
              items and settings.
         7.   The Exporter RP submits a search request to Exalead for the first item specified and Exalead returns the
              result.
         8.   The Exporter RP uses the information returned from Exalead to read the item from the archive store. The
              specifics of what now happens with the item, depends on the format of export being executed. For PDF
              exports each item is converted into a pdf file in the Temp directory on the archive server. For XML and
              PST exports the items are written to the export results folder on the case management device. Step 7 and
              8 are repeated for each item to be exported.
         9.   Once all items have been initially processed the Exporter RP now completes the export results. Again this
              step varies depending on the format of the export. For PDF exports the individual pdf’s in the Temp
              directory are written to the export results folder on the case management device, being combined into
              one file if single pdf export was chosen. For XML exports the items are indexed with dtSearch and
              combined in a zip file with a copy of the Netmail Search Lite files from the replicated RP folder on the case
              management device, and the resulting zip file written to the exports results folder. For PST exports the
              items are processed into PST files which are written to the export results folder.

              In addition the Exporter RP creates a file named report.txt in the export results folder summarizing the
              start and end times of the export, whether the job was successful, and the number of items processed.

         10. The java process running the Exporter RP now exits and job control returns to the GWOpenProcess which
             completes the export job by running the notification thread as normal, sending notification emails to any
             address specified in WebAdmin as well as any specified in the Export Wizard.




     Throughout this process, if the Current Export(s) window in Netmail Search is open, it will refresh every ten
     seconds by sending a GetClusterState request to the Master Archive server to get information on the progress of
     the job, as well as checking for the existence of the results.txt summary in the export results folder. This
     information is used to update the status of the job in the Current export(s) window.
                                                                                   NetMail Search Export Function     70



PDF EXPORT RENDERING

As mentioned previously, exporting attachments to pdf requires suitable software on the archive servers to be able
to render certain attachments to pdf format.

By default, only the email bodies, and the .PDF attachments (which don't need conversion), are rendered. For all
other currently supported file types, either Microsoft Office or Open Office are required to be installed to render
the attachments into .PDF. Support for other PDF rendering engines may be added in the future to render non-
word attachments (.txt, .html, etc.) without Office/Open Office, but for now we rely on them.

Therefore in the current version, In order to use the new pdf export with attachments, clients will need to choose
one of these 3 options:


OPTION A

On the remote provider machine, and on EVERY Netmail Archive Node (both worker and master nodes)
1) Install Office 2007
2) Go to http://www.microsoft.com/download/en/details.aspx?id=7
3) Download SaveAsPDFandXPS.exe
4) Run it

Note: you don't need a Full version of office 2007. All you need is Word and/or Excel and/or PowerPoint and/or
Visio.


OPTION B

On the remote provider machine, and on EVERY Netmail Archive Node (both worker and master nodes)
1) Install Office 2010 (save as PDF is now part of the core, so no need for addin)

Note: you don't need a Full version of office 2010 All you need is Word and/or Excel and/or PowerPoint and/or
Visio.


OPTION C

On the remote provider machine, and on EVERY Netmail Archive Node (both worker and master nodes)
1) Install Open Office http://www.openoffice.org/



Option C is clearly the cheapest, but not all word documents are rendered properly by Open Office (symptoms
include missing images, badly formatted paragraph, etc.).

Also, you can install both Office and Open Office and the engine will choose which program to select to render
each file type (useful if an organisation has both Office attachments and Open Office document as well).

The selection of which software is used to convert which type of attachments, and hence also the list of supported
attachment types, is configurable in the following file:
71    Netmail Archive 5.1- Training Reference


              (Program File Directory)\Messaging Architects\RemoteProvider\pdfexport.properties

     This file cannot simply be changed to support new attachment types without there being corresponding software
     to act as the rendering engine, but you can read it to understand how rendering engines are selected when
     attachments are converted to pdf.

     By default there are two "main" engines (which can be increased in future as the system is scalable); the Microsoft
     Office Engine and the OpenOffice Engine. As such Microsoft

     The Office Engine is split in 4 sub-engines; excel, word, visio and powerpoint. The section of the file for each engine
     lists the mime-types of files it can convert to PDF followed by a value, from 1 to 100 which corresponds to the
     quality of the export. This way, if you have both Office 2007 Word and Open Office installed, the system will
     choose Word to render Word document because it is marked with "100" in word versus "75" for open office.

     Here is an example of the configuration, with (...) to indicate that some lines were removed to make it easier to
     paste it in this document.

              OfficeEngine.support.excel=xlsx,100;\
              (...)
              application/ods,75;\
              OfficeEngine.support.visio=vsd,100;\
              (...)
              zz-application/zz-winassoc-vsd,100;\
              OfficeEngine.support.word=docx,100;\
              (...)
              application/odp,75;\
              OfficeEngine.support.powerpoint=ppt,100;\
              (..)
              application/odp,75;\
              OpenOfficeEngine.support=application/vnd.sun.xml.writer,100;\
              (...)
              text/plain,90;\

     The user can change these values to modify the default behaviour, for example if they prefer to choose Open
     Office to render everything except powerpoint files. The user can also refer to this to see the list of attachment
     types that can be rendered as pdf (we cannot, for example, render Autocad document for now as we don't have an
     Autocad to .pdf engine).




     NETMAIL SEARCH EXPORT TROUBLESHOOTING CHECKLIST

     Understanding the process carried out during a Netmail Search export job makes the task of troubleshooting
     problems with such export jobs more understandable.

     The following checklist outlines a checklist which can be followed to help determine which stage of the process
     problems are occurring at.

         1.   Check that the Case Management Device (CMD) has been fully configured to a valid path and with valid
              credentials which allow all archive servers and remote provider servers to access that path. Remote
                                                                                 NetMail Search Export Function      72


        Provider servers need to be able to replicate the remote provider folder to the CMD as well as create case
        folders and export files within those case folders. Archive servers need to be able to read the replicated
        remote provider folder in order to create the exporter folder, read the export file created by the remote
        provider, create the exports results folder, and write data to that results folder.
    2. Check that remote provider folder replication is working by looking for a folder for each Remote Provider
        being created in the export_dp folder of the CMD.
    3. Check that the numerically named export file gets created in the export2 subfolder of the case folder on
        the CMD when you Finish the export wizard in Netmail Search.
    4. Check that the Netmail Search Export job is successfully submitted and started by watching the Nodes
        Monitor screen in WebAdmin. This will also allow you to determine which archive node executes the job.
    5. Check that the exporter folder is created on the Archive node executing the job. Below this folder you
        should see a local copy of the replicated remote provider folder for the relevant remote provider which
        has been copied form the CMD. Note that this directory will already exist if previous export jobs via the
        same remote provider have executed on that archive node. It shall only be updated if updates are
        detected on the replicated folder on the CMD.
    6. Check the logs/jexcon.log file in the exporter folder. This should have an updated timestamp on it and
        show the queries sent to Exalead for the items in the export job. Check the log to confirm that results
        returned are as expected.
    7. Check that the results folder, named <exportid>_results is created in the <case name>\export2 folder.
    8. Check that the export files are created in the results folder.
    9. Check that the report.txt file is created in the results folder and check it for any error messages.
    10. Check the Netmail Search Export job report in the Export Agent in WebAdmin for any additional error
        information, and enable Trace logging on this job to obtain more detail on future jobs.



Following these steps should assist you in identifying at what stage problems are arising. Refer back to the
previous sections to ascertain which components are involved at that stage and troubleshoot the particular action
taking place at that point.
73    Netmail Archive 5.1- Training Reference



     MIGRATION CHANGES

     This section outlines the main changes to the features used for GroupWise to Exchange Migration in Netmail
     Archive 5.1 as compared to M+Archive.

     MIGRATION CHANGES SUMMARY

     The following list summarizes the main changes affecting migration functionality,

         •   Several improvements to performance of GroupWise to Exchange Migration tool (Provisioning Wizard).
         •   Speedy new Provisioning Wizard workflow for environments where users exist in AD already. - Sets MAID
             only and imports a prepared matching list rather than perform matching.
         •   Support for migration from GroupWise to Exchange Online (details in section on Exchange Online).
         •   Support for migration to Exchange 2010 only – Migration to 2003/2007 dropped.
         •   eDirectory used for Migration attributes (MAID, etc) – was introduced in 2010.1.1.

     The following sections provide additional detail on these changes plus other minor amendments.

     PROVISIONING WIZARD CHANGES

     The main changes to the provisioning wizard can be summarized as follows,

         •   User mapping file import – For environments which have users in AD already a simpler, faster workflow is
             provided by importing prepared mappings file, thereby allowing the provisioning wizard to skip matching
             altogether and carry out migration attribute settings only (MAID etc.)
         •   Automated detection of eDirectory Settings – If the provisioning wizard is run on an Archive server it will
             automatically detect the ClusterConfig.xml file in the Messaging Architects\Config folder and read the
             eDirectory LDAP settings from there.
         •   Distribution List provisioning – Distribution List migration can now be handled in a separate provisioning
             wizard workflow which operates with previously provisioned users.
         •   Exchange Online support – The provisioning wizard can provision accounts to AD for onward sync to
             Exchange Online using Microsoft Directory Synchronization.
         •   Exchange 2010 only – Only on-premises Exchange 2010 or Exchange Online are supported as target
             environments. Migration to Exchange 2007 (or 2003) is not supported.
         •   Can disable AD Forest Referral Chasing – If you are working with a simple single domain AD then turning
             off referral chasing speeds up all aspects of the provisioning wizard which read AD.
         •   Set MAID only checkbox on user provisioning – Used as a speedy filter to select only those users
             previously provisioned that need the MAID updated only.
         •   Secure LDAP options – It is now possible to specify the use of a secure LDAP connection both for AD
             connectivity and for the connection to Exchange Archive eDirectory tree.
         •   eDir storage of migration attributes – The provisioning wizard creates ma User objects in the eDirectory
             tree used by the Exchange Netmail Archive system. This replaces some aspects of the system.map file –
             although system.map is still currently required for migration agent jobs. Future versions may do away
             with system.map altogether.

     More detail on these features and other minor changes to the wizard are found below.
                                                                                                    Migration Changes   74



PROVISIONING WIZARD – IMPORT USER MAPPING WORKFLOW

For scenarios where organizations have already provisioned user accounts in AD, going through the standard
provisioning wizard workflow, which includes AD searching and matching, can be a slow process in large AD
environments.

A faster workflow has been added to the provisioning wizard to use in such scenarios. This workflow requires the
following pre-requisites,

    •    GW users already have accounts in AD
    •    Exchange mailboxes have already been created for these AD accounts
    •    A mapping file has been prepared, mapping GW accounts to AD accounts


FORMAT OF USER MAPPING FILE

The user mapping information must be stored in a text file with semicolon separated values (SSV). The provisioning
wizard shall be able to read the file and parse the user mapping information for provisioning.

    •     The file should be a text file with file extension "SSV".
    •     Each line in the file represents a user and contains 10 properties for that user,

               GroupWise display name
               GroupWise first name
               GroupWise last name
               GroupWise user DN
               GroupWise user ID
               GroupWise PO – in PO.Domain format
               GroupWise domain
               GroupWise user type ("1" for user, "2" for distribution list, "3" for resource)
               GroupWise SMTP email
               Exchange AD user DN

The above 10 properties of a user are stored in one line in the file. The properties are separated with semicolons
";" in the line.

Dsiplay Name;FirstName;LastName;GWuserDN;GWID;GWPO.GWDomain;GWDomain;GWType;GWEmail;ADDN

For example,

Gavin Dye;Gavin;Dye;gdye.uk.org;gdye;po2.dom1;dom1;1;gdye@mademo.com;CN= Gavin Dye,CN=Users,DC=ACME,DC=com

When run, this workflow shall simply create, or update, the MAID on the AD\Exchange user objects’ email address
list, as well as create or update the ma user objects in the target eDirectory tree (that used by the Exchange
Netmail Archive System) with the appropriate migration attributes.

The workflow is started by checking the Import user mapping option under User Provisioning in the opening screen
of the wizard, as below.
75    Netmail Archive 5.1- Training Reference




     Clicking Next proceeds to the Exchange and eDirectory configuration screen

     NOTE: If the wizard is run on an Archive server, this screen may not be displayed. See later section on standard
     workflow for user provisioning for an explanation.
                                                                                                 Migration Changes    76


Select your target Exchange system type, enter the eDirectory details for the Exchange and GroupWise Netmail
Archive eDir tree(s), and then click Next to go straight to the AD parameters settings.




Enter the AD details and click Connect to list the AD containers for selection. Select the relevant containers then
click Next.

A screen is now displayed requesting the user mapping file.
77    Netmail Archive 5.1- Training Reference


     Click the Browse User Mapping File button and browse to then open the prepared mapping file.




     The entries from the file are subsequently listed for selection in the wizard. If you do not wish to process all entries
     at this stage use the selection buttons and check boxes to select the users you wish to process.




     Click Next to proceed.
                                                                                    Migration Changes   78


You are now taken straight to the Review and Confirm screen.




Validate the operations about to be taken and click Next to proceed.




Set your reporting options and click Process Users to start processing the users.
79    Netmail Archive 5.1- Training Reference


     The system shall now create/update the MAID on the appropriate AD object for each GW account in turn. Any AD
     users which cannot be found will result in a Failed to Check MAID error, as shown for the third user below,




     At the end of updating the MAID in AD for each account, the wizard shall connect to the target eDirectory tree and
     create/update the corresponding ma user objects.

     NOTE: At the time of writing the current beta build displayed a problem at this stage and did not successfully
     create the user objects in eDir, and generated the “index was outside the bounds of the array” error shown
     above.

     Clicking Next takes you to the closing screen where the System map file can be copied for use with Migration jobs.
Migration Changes   80
81    Netmail Archive 5.1- Training Reference



     PROVISIONING WIZARD – STANDARD USER PROVISIONING WORKFLOW

     Some minor changes have also taken place in the standard user provisioning workflow.




     The layout and options shown on the opening screen have changed to reflect the new procedures for Distribution
     List provisioning and the Import user mapping option (see preceding section for import user mapping workflow,
     and following section for distribution list workflow).




     EXCHANGE AND EDIRECTORY CONFIGURATION

     The Provisioning Wizard presents two options for the target Exchange system, Exchange Online or Exchange On-
     premises. Notice that no version options other than these are now required, since 2007 and 2003 support has
     been removed for migration.

     In addition, since the wizard now creates user objects in the target eDirectory tree (i.e. the one used by Netmail
     Archive in the Exchange environment), LDAP connectivity settings for that tree are required. In order to take
     account of any usermap objects on the GW side we also require LDAP connectivity to the eDir tree being used by
     Netmail Archive on the GW side too.
                                                                                               Migration Changes    82




NOTE: Currently, if the Provisioning Wizard is run on an archive server then it shall automatically read the
ClusterConfig.xml file from the Messaging Architects\Config directory in order to set the first set of eDirectory
LDAP settings.

If the wizard is run on a workstation you can copy the ClusterConfig.xml from the Exchange Netmail Archive system
archive server and use the Browse ClusterConfig File button to read it to populate the first set of eDirectory
settings. Alternatively enter the settings manually.


                IMPORTANT: If you run the provisioning wizard on an archive server in the GW
                Netmail Archive system, then it shall read the ClusterConfig from that server and a
                popup message shall be displayed detecting that this is the GW eDir tree and
                prompting you to browse for the Exchange environment ClusterConfig file.

                If you wish to run the wizard from an archive server on the GW Netmail Archive
                system, then you shall need to browse to a mapped drive on the Exchange Archive
                server or enter settings manually
83    Netmail Archive 5.1- Training Reference



     CONNECT TO THE GROUPWISE SYSTEM




     When using Additional GroupWise User Details, It is no longer necessary to click a button to Retrieve them
     manually at this stage. They shall be retrieved automatically when you click Next.
                                                                                                 Migration Changes      84



ACTIVE DIRECTORY PARAMETERS

The settings required at this stage depend on whether Exchange on-premises or Exchange Online was chosen at
Step 1.

EXCHANGE ON-PREMISES




REFERRAL CHASING

For Exchange On-premises the wizard requires to connect to AD to read the containers to be searched for matches
and in which users are to be provisioned. It also reads the Exchange System Objects from AD.

In an AD Forest, with multiple domains, Exchange System Objects are normally installed into the root domain, and
referral chasing by the wizard is required to traverse the AD forest to find them (or to find other target containers
in large AD forests). This referral chasing can significantly extend the time required to read the information from
AD.

If you are dealing with a simple AD structure where all target containers and the Exchange System Objects exist in
one domain then turning off referral chasing will significantly speed up this step and all subsequent aspects of the
wizard which require reading AD.
85    Netmail Archive 5.1- Training Reference


     SECURE LDAP

     LDAP connectivity to AD is normally unsecured and accessible via port 389, but if LDAP connectivity to AD has been
     tied down to only allow secure LDAP with SSL then a new checkbox on this screen allows AD connectivity to be
     made over secure LDAP on port 636.




     EXCHANGE ONLINE




     For Exchange Online scenarios, only AD settings are required for the on-premises AD tree to which users will be
     provisioned. No Exchange System Objects shall be read since no access to the back-end Exchange system is
     possible.

     The same referral chasing and secure ldap options are available as outlined above for Exchange On-Premises.

     More detail on the Exchange Online path can be found in the Exchange Online section of this document.
                                                                                            Migration Changes    86



SELECT GROUPWISE USERS




Only minor changes have been made to the layout of the GW User selection screen, for the loading and saving of
user lists.
87    Netmail Archive 5.1- Training Reference



     MATCH GROUPWSIE TO ACTIVE DIRECTORY/EXCHANGE USERS

     This step in the normal provisioning workflow is a multi-step stage.




     At the first step click Search to commence the matching search of AD.

     A minor change at this step is that the Search button shall change to stating Loading… whilst the matching search
     executes, as shown in the next screenshot.
                                                                                             Migration Changes      88




Once the search has completed the results shall be displayed as before, with the proposed operation for each user
depending on whether a match was found in AD.
89    Netmail Archive 5.1- Training Reference




     Another change at this step is the addition on the Set MAID Only checkbox. When selected this has the effect of
     filtering the user list to select only those users which have been matched to existing AD users and which are to
     have the MAID checked and created/updated, as shown in the following example.
                                                                                             Migration Changes   90




Once the required users have been matched and selected click Accept Matches as before to proceed.

The screen changes to display the selected items and their proposed actions and settings, as shown below.
91    Netmail Archive 5.1- Training Reference




     Click Next to proceed to setting the AD/Exchange details for any users to be created.




     ACTIVE DIRECTORY /EXCHANGE DETAILS

     The opening screen at this stage lists the users being processed, as shown below. No changes have been made to
     this screen from the M+Archive version.
                                                                                               Migration Changes   92




Click Set Defaults to set the AD/Exchange default settings to be applied to those users being created.
93    Netmail Archive 5.1- Training Reference




     Operation of this screen shall be faster if AD referral chasing was turned off at an earlier stage.

     NOTE: For Exchange Online there is also a minor change in that no Storage group shall need selected, since we
     have no control over the back-end Exchange system. This option shall be disabled for Exchange Online in future.
     For now the Storage button has no effect for Exchange Online.

     Once you have set the defaults accordingly click OK then Set Defaults in the main screen to apply these settings to
     the list of users to be created. The attribute values shall be populated for the users and displayed to allow
     verification and any over-rides to be applied, as shown below.
                                                      Migration Changes   94




Clicking Next moves to the Review and Confirm stage


REVIEW AND CONFIRM




There are no changes to this stage.
95    Netmail Archive 5.1- Training Reference



     PROCESS SELECTED USERS




     Note that the Try Using Secure LDAP checkbox which appeared at this stage in M+Archive has moved to an earlier
     stage in the workflow. No other changes have been made.

     Once Process Users is clicked the wizard shall start executing the proposed actions.
                                                                                                Migration Changes      96




Note the Syncing eDir message at the end of the action list. This is the step which creates the ma user objects with
migration attributes in the target eDirectory tree.


SUMMARY AND REPORTS
97    Netmail Archive 5.1- Training Reference


     No changes have been made to the Summary and Reports screen. It is still necessary to keep a copy of the system
     map file for use with Migration jobs although it is hoped that this requirement shall be phased out in future
     versions to be replaced by usage of the migration attributes on the eDir user objects alone.




     POST PROVISIONING STEPS

     As previously, it is still necessary to apply the appropriate Email Address Policy to newly provisioned mailboxes in
     Exchange, in order to correctly set all Exchange attributes.

     You can still confirm that the MAID value has been written to the Exchange account by checking the email
     addresses in the Exchange Management Console.

     To check that eDirectory ma user objects have been created, use ConsoleOne or an LDAP browser to connect to
     the relevant container in the Netmail Archive Exchange system eDir tree. You should see user objects for the newly
     provisioned users with migration attributes as shown below,
                                                                                               Migration Changes      98


Once you have confirmed these you must now run an Address Book Sync on the Netmail Archive Exchange system
to update these user objects with further AD/Exchange attributes. After the AB Sync the user object shall look as
follows,




Note the additional attributes, such as maInboxFolderID. All of the migration attribute values should remain as
they were prior to AB sync.




PROVISIONING WIZARD - DISTRIBUTION LIST WORKFLOW

There now two separate workflows for provisioning distribution lists to AD and setting their membership.

    •   User Provisioning based workflow – This is the same process as was provided with M+Archive. With this
        option Distribution lists are created/matched in AD as part of the standard user provisioning workflow.
        The only drawback for this method is that it can only add users to distribution lists on the AD side at the
        same time as creating the users in AD. Previously provisioned users will not be added to distribution lists
        with this method.
    •   Distribution List provisioning workflow – A new dedicated workflow for distribution lists only is provided
        from the opening screen of the provisioning wizard. This option can be used to create distribution lists in
99    Netmail Archive 5.1- Training Reference


              AD (or work with previously created/mapped distribution lists) and to add previously provisioned users to
              distribution lists in AD. This method is particularly useful in environments where users’ accounts already
              exist in AD.

     The new dedicated Distribution List workflow is detailed below.


     DEDICATED DISTRIBUTION LIST PROVISIONING

     This workflow assumes that the users you wish to add to the distribution lists on the AD side have already been
     created or matched with the provisioning wizard user provisioning workflow.

     The Distribution List workflow is started by selecting the Provision distribution lists with existing users option on
     the provisioning wizard opening screen, as shown below.




     After clicking Next the standard Exchange and eDirectory Configuration screen is shown to enter the corresponding
     settings.

     Once those are entered the Connect to GroupWise screen is displayed, as below.
                                                                                             Migration Changes     100




Note that the Retrieve Distribution Lists membership and Manage Distribution Lists Mappings options are selected
and greyed out.

IMPORTANT: You MUST select a post office to proceed past this point.

After clicking Next the AD Parameters are requested as normal. Thereafter the next screen shown is the
distribution lists mapping screen, as shown below.
101    Netmail Archive 5.1- Training Reference




      All detected GroupWise distribution lists shall be listed in the left hand pane. If a distribution lists has not been
      created and/or matched in AD previously then the right hand pane shall show greyed out entries of the proposed
      distribution lists that are to be created in AD.

      If you wish to modify any of these proposals, then use the New button to browse the AD tree to select the target
      container for the new distribution list and the Create button to create the proposed mapping.

      Once you are happy with the proposed mappings click Apply to create the distribution list objects in AD.

      If lists were previously mapped and created in AD then the right hand pane shall show the currently mapped object
      in AD in bold text rather than greyed out.

      Once mappings are completed click Next.

      The wizard shall now read the memberships of the GroupWise distribution lists and check this list against
      previously provisioned users in AD. Whilst this process completes the following screen shall display and you should
      await it completing.
                                                                                             Migration Changes   102




Once complete, if any accounts are found in membership lists on GW, but not yet provisioned to AD, they shall
appear in a popup.
103    Netmail Archive 5.1- Training Reference


      Clicking OK on this popup results in the missing users being saved as a user list for use in future runs of the user
      provisioning workflow (if required).




      Clicking OK shall proceed to the Review and Confirm stage.




      The users to be added to the appropriate distribution lists on AD shall now be listed. Click Next to proceed.
                                                                                             Migration Changes       104




Complete any reporting options as normal then click Process Users.

The results screen shall list the actions taken, which should include a note of each group membership processed on
the AD side.
105    Netmail Archive 5.1- Training Reference




      Clicking Next proceeds to the Summary and Reports screen as normal.
Migration Changes   106
107    Netmail Archive 5.1- Training Reference



      NETMAIL ARCHIVE 5.1 BETA -DEPLOYMENT & UPGRADE STRATEGY

      This section outlines the main changes to the installation process for Netmail Archive 5.1 as compared to
      M+Archive installation as well as outlining the installation and upgrade strategy to be followed for deployment of
      Netmail Archive 5.1 during the Beta phase.

      Before carrying out any Beta deployments of Netmail Archive 5.1 please ensure you have the latest build and any
      associated patches from the Dev team.

      NEW DEPLOYMENTS


      ARCHIVE SERVER INSTALLATION

      With regards to new deployments of Netmail Archive, where no pre-existing M+Archive system is being upgraded,
      there is no change to the archive server strategy.

          •    The Netmail Archive cluster is still composed of a Master node and Worker nodes in exactly the same way
               as with M+Archive.
          •    eDirectory is still used in exactly the same way as the configuration repository
          •    Additional components such as the Remote Providers, Stubbing Agents, and IIS Extensions are all
               deployed in the same way as previously.


      POSTGRES INSTALL

      Starting with the Beta Refresh build, 5.1.0.328, a new version of Postgres is now included for use as the logging
      database platform. Postgres version 9.1 replaces version 8.2 as used in earlier versions. This change introduces a
      new Postgres installation process as detailed here.

      The Postgres install is still triggered as part of the Archive Server installation process, if Postgres is not detected as
      being installed already.
                                                        Netmail Archive 5.1 Beta -Deployment & Upgrade Strategy        108


On accepting this prompt you shall also be reminded to install the required ODBC drivers, as these are no longer
included in the main Postgres installation routine. A separate installation utility, named the Posgres Stackbuilder,
will be launched at the end of the main Postgres installer in order to carry out the ODBC driver install.




After acknowledging this reminder a cmd window will open as follows,




This will automatically run the Postgres installer. Prior to the installer screens appearing it shall check for
prerequisites and install the Microsoft Visual C++ 2008 Redistributable automatically if not already installed, as
shown in the following,
109    Netmail Archive 5.1- Training Reference




      Once this has completed the main Postgres install dialogue starts, beginning with a welcome screen.




      Click Next to move to the installation Directory screen.
                                                       Netmail Archive 5.1 Beta -Deployment & Upgrade Strategy       110


The default path should rarely need changed. Clicking Next will result in the Data Directory screen.




Again this path should rarely need changed. Clicking Next will take you to the Password screen. Note that the same
password, as entered here, will now be used for both the Postgres windows service account and the Postgres
superuser account – this differs from Postgres 8.2 where the installation process recommended the use of
different passwords. Using a single password simplifies things especially as this is simply a logging database
platform and security is not a high priority.




Enter and confirm the password required then click Next to display the Port screen.
111    Netmail Archive 5.1- Training Reference




      The default port of 5432 should not require changing. Click Next to obtain the Advanced Options screen.




      This screen allows you to change the default locale for Postgres, from US English to any of the other possible
      values. Once selected click Next to proceed.
                                                      Netmail Archive 5.1 Beta -Deployment & Upgrade Strategy       112




Clicking Next will commence the main Postgres installation which shall be tracked by a progress bar.




Towards the end of the process you shall see the database cluster being installed and activated (as shown above).
Once this is complete the following screen is displayed.
113    Netmail Archive 5.1- Training Reference




      It is very important to leave the checkbox selected to launch the Stack Builder at exit. It is the Stack Builder utility
      which is now used to install the ODBC driver. Clicking Finish will result in the opening Stack Builder window being
      displayed.




      Use the pull down list to select the installation of Postgres you have just made, then click Next to move to the
      component selection screen.
                                                       Netmail Archive 5.1 Beta -Deployment & Upgrade Strategy        114




Expand the Database Drivers category and select the psqlODBC driver in the resulting list. This is the only
additional component required for Netmail Archive use. Once selected click Next to proceed.




Confirm that the ODBC driver is listed in the Selected Packages list. The default download directory should not
require changing. Click Next to proceed with downloading the driver. Note that internet connectivity is required at
this stage in order for the download to succeed.
115    Netmail Archive 5.1- Training Reference




      The Stack Builder utility now downloads the driver before prompting to continue with installation of the driver.




      Click Next to proceed with the installation of the ODBC driver.
                                                        Netmail Archive 5.1 Beta -Deployment & Upgrade Strategy         116


Click Next on the Welcome Screen to obtain the Installation Directory screen.




The default path should rarely require changing. Click Next to proceed.




Click Next to carry out the installation of the ODBC driver. This shall complete relatively quickly before displaying
confirmation of completion.
117    Netmail Archive 5.1- Training Reference




      Clicking Finish returns to the Stack Builder utility completion screen.




      Clicking Finish on here will complete the Postgres installation process and return you to the Archive Server
      installation procedure.

      NOTE: For Worker Node installations only the Postgres ODBC driver is required to be installed. This is achieved by
      downloading the installer for the driver only, and installing this on the worker node, preferably prior to Netmail
      Archive installation. The installation msi file is contained in the zip file,

      http://ftp.postgresql.org/pub/odbc/versions/msi/psqlodbc_09_00_0310.zip
                                                               Netmail Archive 5.1 Beta -Deployment & Upgrade Strategy   118


NOTE: There is a current problem in environments using Master and Worker nodes since the Stack Builder utility
creates an ODBC driver with a different name than the standalone ODBC driver msi utility does. This means that
Master and Worker nodes end up with different driver names and cannot then use the same database connection
string. For now the workaround for this is to uninstall the psqlODBC entry from the Master node from using the
Programs & features applet in the Control Panel, then reinstall the Postgres ODBC driver using the same msi you
used for Worker nodes. This will result in both Master and Worker nodes using the ODBC driver name PostgreSQL
Unicode. You can verify this driver name in the Microsoft Data Sources utility Windows\SysWOW64\odbcad32.exe.
Go to the Drivers tab and verify the name. It will also then be necessary to edit the database connection string in
WebAdmin to match this driver name, for example,

Driver={PostgreSQL Unicode}; Server=192.168.1.124; Port=5432; Database=netmailarchive; Uid=postgres; Pwd=password;

This will then allow all archive servers to be able to connect to the Postgres database, assuming the appropriate
entries have been made in the pg_hba.conf file to allow connections form all servers.

It is hoped that this driver name mismatch shall be addressed in future versions.




CASE MANAGEMENT DEVICE

One change which should be taken into consideration is the increased use of the Case Management Device. As well
as storing discovery cases from M+Analytics, now branded Netmail Search, this storage area is also now used for
the new Netmail Search export functionality. As such it needs to be sized to accommodate a replica of each
Remote Provider folder plus adequate space for exports to be stored and processed.

A new setting in xgwxmlv.cfg allows the AWA Remote Provider service to check the free space on the Case
Management Device at service startup and stop if less than a specified amount is free.




SERVER PREREQUISITES

The only major change to the pre-requisites on the archive server is the requirement for,

     •    Microsoft .Net 4 Framework – Available at
          http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=17718

And any Remote Provider server now requires,

     •    JRE 1.6 or higher – Ensure that you remove any earlier versions of Java and check that java\bin directory is
          added to the path.
119    Netmail Archive 5.1- Training Reference



      INSTALLATION WIZARD CHANGES

      Other than a change in the Postgres installation process, outlined above, there is only one main change to the
      Archive server installation wizard when compared to M+Archive, and this is on the Messaging Server choices, as
      shown here.




      Exchange support is provided for on p-premises Exchange 2007 SP1, 2010, and 2010 SP1, or for Exchange Online,
      and the appropriate version should be chosen at this stage

      NOTE: As a temporary measure during the Beta the Archive server installation wizard does not automatically run
      the createmaster.bat file to create the Netmail Archive objects in eDirectory. This is to avoid confusion in
      upgrade scenarios during the Beta. As such for non-upgrade scenarios it is necessary to run the createmaster.bat
      file manually after the installation wizard has completed and before starting the Netmail Archive services. The
      file can be found at,

              C:\Program Files (x86)\Messaging Architects\WebAdmin\mSetup\createmaster.bat

      This measure shall be rectified for general release and it shall no longer be necessary to run the batch file
      manually.
                                                       Netmail Archive 5.1 Beta -Deployment & Upgrade Strategy        120



REMOTE PROVIDER INSTALL

For the Remote Provider install the Exalead and Jexcon Configuration screen is now as follows,




The new Netmail Search Export functionality requires that the Remote Provider knows the address and port for the
master archive node, in order to submit http job triggers. This setting is then stored in the xgwxmlv.cfg.

In addition, at the conclusion of the Remote Provider install, there is now an option to automate the production of
the keystore for SSL usage. As before you are initially prompted with a reminder to configure certificates.




Acknowledging this shall result in the new prompt.
121    Netmail Archive 5.1- Training Reference


      Clicking Yes will proceed with the automated keystore generation.




      Enter a password to be used for key generation then click Next. The keystore file shall now be generated in the
      Remote Provider folder and the jetty-ssl.xml will be edited to use that file. Confirm that the keystore file has been
      generated as shown below,
                                                       Netmail Archive 5.1 Beta -Deployment & Upgrade Strategy      122




INDEX SERVER INSTALLATION

Index server deployment is simpler with Netmail Archive and is outlined in the specific section regarding Exalead
CloudView in this document.
123    Netmail Archive 5.1- Training Reference



      M+ARCHIVE TO NETMAIL ARCHIVE UPGRADES

      Major upgrade support, i.e. in-place upgrade from previous versions of M+Archive, is not yet complete in Netmail
      Archive. As such during this beta phase a specific upgrade and rollback strategy has been defined (see later
      section). Further documentation on in-place upgrade considerations shall become available as and when the
      capability is released.




      BETA DEPLOYMENT STRATEGY


      DEPLOYING A NEW SYSTEM

      If your beta site does not have an existing M+Archive system then deployment is a straightforward standard
      installation of Netmail Archive. No additional considerations are necessary.




      UPGRADING AN EXISTING M+ARCHIVE SYSTEM

      This section details the approach to be taken when deploying the Beta into an existing M+Archive environment.

      During the Beta phase no in-place upgrade capability form M+Archive to Netmail Archive is possible for the Archive
      servers (or any dedicated Remote Provider servers).

      This approach is designed to facilitate rollback to M+Archive should the need arise, and any other approach may
      make such rollback impossible to achieve, therefore it is highly recommended that this approach be taken.

      NOTE: This strategy is designed for environments using physical servers. For organizations utilizing virtual
      servers for the Archive servers, a simpler approach may be possible by using snapshots of existing environments
      for any possible rollback. This depends on whether a dedicated eDirectory tree is being used for M+Archive. If so
      than snapshots of the M+Archive servers and tree can be used to facilitate rollback. If a tree being shared with
      other production services is being used then this will not be possible and the same strategy outlined below
      should be followed.


      UPGRADE & ROLLBACK STRATEGY

      The Netmail Archive archive servers shall be deployed as a completely new and separate cluster from the
      M+Archive system on different hardware.

      The same eDirectory tree will be used, even though some schema changes are made, and this will not negate the
      ability to rollback.

      Using a separate container in eDirectory for Netmail Archive would necessitate recreating all jobs, policies,
      locations etc. and cause index duplication if re-indexing of data ever took place (due to different device ID’s).
      Instead this approach configures the Netmail Archive system to use the same container as used by M+Archive in
      order to pick up all of the existing configuration.
                                                        Netmail Archive 5.1 Beta -Deployment & Upgrade Strategy          124


For indexing, the same index servers will be used. CloudView and Exalead 4.6 can co-exist on the same machine as
long as only one set of services are running at any time. As such the Indexing server strategy is to install CloudView
on to the existing index servers, and then when ready to cutover, stop the 4.6 system, start CloudView, and
convert the indexes to CloudView.

Rollback involves shutting down all Netmail Archive servers and CloudView services, restoring eDirectory to its pre-
Netmail Archive state via LDIF import of a backup made before rollout, starting M+Archive servers and Exalead 4.6
services, and then running an incremental indexing job to update the 4.6 indexes with any data and/or audits
added during the Netmail Archive operational period.

Details of the steps involved are outlined below.

UPGRADE TO NETMAIL ARCHIVE BETA

The basic strategy to be followed is as follows.

In advance of switchover

    1.   Back up the existing M+Archive eDirectory container using an LDIF export with a trusted LDAP browser.

         NOTE: Some LDAP browsers, and ConsoleOne, can have problems importing some objects in an LDIF file
         even though they were able to export them correctly. The most common problem is constraint
         violations due to the total object context length when doing the import. It is VERY important that you
         have fully tested LDIF export and import of your 2010 archive container before you decide which LDAP
         browser or ConsoleOne version to use for the export at this step. Advance testing of the import
         function can be facilitated by creating a copy of the LDIF export then doing a global replace of the
         Archive2010 container name with a value of the same length, and carrying out a test import of that
         modified LDIF file into a container matching that new name.

    2.   Install Netmail Archive software to new Archive Server(s) – A completely separate Netmail Archive cluster
         should be deployed alongside the existing M+Archive archive servers. This necessitates the use of
         additional server hardware. The same eDirectory tree should be used, and the same eDirectory container
         used by M+Archive should be specified during installation. The install wizard will NOT automatically run
         the createmaster script which would normally create the Netmail Archive objects in this container, and for
         upgrades this should NOT be run manually. The existing Trusted Application should be imported during
         installation.
    3.   Install Exalead CloudView software onto the existing M+Archive Exalead 4.6 Index servers. The CloudView
         software can happily reside on the same server as Exalead 4.6. Do NOT start any CloudView services at
         this stage.


When you are ready for switchover

    4.   Shut down the M+Archive cluster nodes and stop all Exalead 4.6 services.

         NOTE: If any storage on the Archive nodes is being used for archive locations or as the Case
         Management Device you shall need to leave the server running, but ensure that all M+Archive services
         have been shut down and disabled – in case of accidental server restart.
125    Netmail Archive 5.1- Training Reference




          5.   Run the eDirectoryUpgrade tool on the Netmail Archive master archive server to upgrade some eDirectory
               objects with Netmail Archive settings. You will find this tool at,

               C:\Program Files (x86)\Messaging Architects\eDirectoryUpgrade.exe

               The syntax of this command is,

               eDirUpgrade.exe /dn <Archive Container> /u <LDAP user> /p <password> /server <LDAP Server> /port <LDAP port> /ssl <true/false>


               for example:

               eDirUpgrade.exe /dn ou=mplusarchive,o=org /u cn=admin,ou=ou1,o=org /p password /server 10.10.23.55 /port 389 /ssl false


          6.  Start the NetMail Archive services on your new master archive server then log in to WebAdmin.
          7.  Under the System>Configuration tab edit the Index Servers settings to point to the new Exalead 5 index
              server(s) and Save these settings. This should populate the maIndexConfig attribute in the eDirectory with
              the new Exalead 5 connection details.
          8. In the same section in WebAdmin scroll down and edit the logging connection string to match the correct
              string for the Netmail Archive environment, if different. (The old M+Archive connection string shall have
              been read from eDirectory).
          9. Restart Netmail Archive services on the master Archive node.
          10. Run an Address Book Sync to update eDirectory with new attributes.

      You are now ready to convert the indexes – see the earlier section in this document for more detail on these
      steps

          11. Start the CloudView service on the Master index server and use the Cluster Manager Tool to configure the
              Exalead CloudView servers. i.e. register all slave servers then configure slice counts on the servers.
          12. Restart the CloudView service on the Master.
          13. Use the Cluster Manager Tool to Intialize Conversion.
          14. Convert the Exalead 4.6 Indexes on the Master node to CloudView using the Index Conversion Tool.
          15. Restart the CloudView service on the Master.
          16. Convert the Exalead 4.6 indexes on each slave node (if any) restarting the CloudView service on the
              Master after each slave is completed.
          17. Start the CloudView services on each slave and use the Exalead CloudView admin utility to ensure that all
              slices can be seen for the bg_4_6 build group – one for each converted 4.6 instance.
          18. Start all Netmail Archive worker nodes and Remote Providers and check that you can login to Netmail
              Search and access all archives and cases.
          19. Run a test archive job to ensure items are correctly archived and indexed.




      ROLLBACK KTO M+ARCHIVE

      If problems arise and a return to M+Archive is required, then the basic rollback strategy is as follows.
                                                 Netmail Archive 5.1 Beta -Deployment & Upgrade Strategy     126


1.   Shut down the new Netmail Archive cluster by stopping all archive nodes and any dedicated remote
     provider servers.
2.   Shut down the CloudView services on all index servers.
3.   Start the Exalead 4.6 services on all index servers.
4.   Use your trusted ldap browser or version of ConsoleOne to restore the LDIF export of the M+Archive
     container which you made earlier. Ensure that you use the Update/Add setting in your LDAP browser
     when doing so.
5.   Start up the M+Archive cluster servers and services.
6.   Run an Address Book Sync job.
7.   Run an incremental index job to update the 4.6 indexes with any data or audit changes made whilst the
     Netmail Archive system was active.
127    Netmail Archive 5.1- Training Reference



      UNIFIED UI – NETMAIL WEBADMIN (WARP)

      Another significant change in Netmail Archive 5.1 is the integration with the new Netmail WebAdmin unified
      administrative interface which provides a single management tool for Netmail Secure and Netmail Archive.

      At this stage Netmail WebAdmin is simply a front-end portal onto the existing Netmail Archive WebAdmin
      interface, providing Netmail branding plus re-organization of objects to fit the new unified UI model.

      The Netmail WebAdmin service is based upon Warp (as used in M+Guardian for some time). In environments
      housing both Netmail Archive and Netmail Secure it will typically be provisioned on the Netmail Secure systems,
      but in environments containing only Netmail Archive a windows server based version of Warp has been produced
      to allow Netmail WebAdmin to be provisioned on a Netmail Archive server.

      The following sections detail deployment, configuration, and current issues with NetMail WebAdmin in a NetMail
      Archive environment.




      NETMAIL WEBADMIN INSTALLATION

      Within the Netmail Archive distribution you shall find a folder named Warp. Within that folder is the executable to
      launch the Warp setup wizard,

               Warp\warp.exe

      Launch the executable on an Archive server and follow the steps below to install Netmail WebAdmin to that
      server.

          1.   At the Welcome screen click Next.
                                                                       Unified UI – Netmail WebAdmin (Warp)   128


2.   Choose a destination path for the installation (normally the default path) then click Next.




3.   You shall now be prompted to enter port numbers for NetMail WebAdmin to operate on. You can use any
     valid port numbers which you know to be free on this server and communicable to from workstations on
     the organizations network. Make sure you do not use port 89, as Netmail Archive WebAdmin is still
     required to run alongside Netmail WebAdmin and it uses port 89.
     In addition to specifying the ports to be used by Warp you shall also be asked to specify the URL for
     connection to Netmail Archive WebAdmin.
129   Netmail Archive 5.1- Training Reference


             NOTE: There is a current problem with using localhost in the WebAdmin URL setting as shown above,
             since on Windows 2008 systems this resolves to an IPv6 address. For now you should use an explicit IP
             address or hostname in the WebAdmin URL, e.g. http://192.168.1.124:89

        4.   You are now prompted to continue with the installation. Click Next to proceed.




        5.   Once installation has completed a confirmation screen shall appear. Click Finish to exit the install wizard.
                                                                   Unified UI – Netmail WebAdmin (Warp)      130


6.   You should now see a service named Netmail WebAdmin on the server, in addition to the already present
     Netmail Archive WebAdmin. Start this service, if not already started.




7.   You should now be able to obtain the Netmail WebAdmin login screen by opening a browser and going to
     the relevant URL, using the port number you specified during installation.
131    Netmail Archive 5.1- Training Reference



      NETMAIL WEBADMIN OPERATION & CURRENT ISSUES


      LOGGING IN

      Authentication to NetMail WebAdmin uses exactly the same credentials and format as used with Netmail Archive
      WebAdmin, i.e. the fully qualified eDirectory user and password, as shown in the following example.




      If authentication to Netmail WebAdmin fails whilst using the same credentials with Netmail Archive WebAdmin
      works, then validate the URL you entered for connection to Netmail Archive WebAdmin during the setup by
      opening the file,

               C:\Program Files (x86)\messaging Architects\Netmail WebAdmin\etc\warp-config.json

      Search for the term awebadmin to find the relevant setting in the file and validate the URL specified is correct for
      connection to Netmail Archive WebAdmin,

               e.g.     “/awebadmin/”: http://192.168.1.125:89

      If authentication problems still exist, try establishing a logged in Netmail Archive WebAdmin session then at the
      same time try logging in to a Netmail WebAdmin session in a separate browser tab or window.
                                                                          Unified UI – Netmail WebAdmin (Warp)       132



NETMAIL WEBADMIN – OPERATION

Once authenticated successfully you will be presented by the Netmail WebAdmin opening screen,




The example above shows what would be displayed in a Netmail Archive only environment, i.e. no Netmail Secure
system in place. There are some key differences to be aware of when compared to Netmail Archive WebAdmin.


LDAP CONFIGURATION SETTINGS

The LDAP configuration settings for Netmail Archive, normally obtained via the Configure link on the login page of
Netmail Archive WebAdmin, are now available via the Clusters object below the Archive object, as shown below,
133    Netmail Archive 5.1- Training Reference



      SYSTEM CONFIGURATION SETTINGS

      The Configuration settings normally found under the System tab in Netmail Archive WebAdmin are available on
      the specific archive cluster object in Netmail WebAdmin, as below,




      NODES MONITOR SCREEN

      The Monitor screen, used to monitor the progress of running jobs and located under the Nodes object in Netmail
      Archive WebAdmin, is now available via the main Archive object in Netmail WebAdmin.
                                                                       Unified UI – Netmail WebAdmin (Warp)   134



CURRENT ISSUES

At the moment there are some problems with particular aspects of Netmail WebAdmin which in some cases shall
necessitate the continued use of Netmail Archive WebAdmin by administrators.

    •   Job reports are not currently displayed within Netmail WebAdmin
    •   Some settings require a refresh, new browser session, or restart of the Netmail WebAdmin service to
        display, e.g., Nodes list, Node properties, Logging settings on new jobs
    •   Internet Explorer v9 is not currently supported.

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:5
posted:4/4/2013
language:Unknown
pages:134