Notes Migrator | CMT 19.06*
Requirements, Installation and Configuration Guide June 2019
*See page 3 for note about versioning
Binary Tree Documentation
Table of Contents
Section 1. Purpose and Audience ...... 3 Section 2. Requirements ...... 3 2.1 End User Workstation Requirements ...... 3 Operating System ...... 3 Microsoft Outlook ...... 3 Notes ...... 3 Other ...... 4 2.2 Licensing Server Requirements ...... 4 Hardware ...... 4 General Requirements ...... 4 Section 2. Installing SSAM ...... 5 2.1 Downloading SSAM ...... 5 2.2. Installing Software on the Licensing Server ...... 5 2.4. Repairing, or Uninstalling SSAM ...... 9 2.4.1 Repairing SSAM ...... 10 2.4.2 Uninstalling SSAM ...... 12 Section 3. Setting Up the SSAM Application (Database) ...... 14 3.1 Sign the SSAM Database ...... 14 3.2 Configure the Access Control List (ACL) ...... 16 3.3 Add the Domino Address Book and Copy the Database ...... 18 3.3 Enter the License Key ...... 22 3.4 Configure Licensing Notifications ...... 25
Section 4. Configuring Settings in SSAM ...... 27 4.1 Required Settings ...... 27 Domino Tab ...... 27 LDAP Tab ...... 28 PowerShell Credentials Tab ...... 29 PowerShell Execution Policy ...... 29 4.2 End User Migration Settings ...... 30 End User Migration Settings ...... 30 Archive Identification Methods ...... 31 Support Notification ...... 32 4.3 Custom Communications ...... 33
Section 5. Email Repliability ...... 34 5.1 What is a Translation Table? ...... 34 5.2 Configuring the Translation Table ...... 34
Section 6. Message Templates ...... 36 6.1 Creating a New Template...... 36
Appendix A: Installing the Self-Service Archive Migrator Application on End User Workstations ....38 Learn more about Binary Tree ...... 39 Binary Tree Social Media Resources ...... 39 Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 2 Binary Tree Documentation
- Important note about software version numbers - Version 19.06 A new software versioning convention has been implemented to show the year and month of release. The most recent GA version (using the old convention) prior to this release was 1.4.
Section 1. Purpose and Audience The purpose of this document is to provide information on how to install and configure Self-Service Archive Migrator (SSAM) to perform a migration from local Notes mail archives to local PST files or to online archives. This document also includes the software and hardware requirements necessary to perform a typical SSAM installation.
This document assumes the reader has a minimum of one-year experience using a Notes Client and some basic Domino Administration skills, as well as Exchange (or Office 365) and PowerShell for account matching. If Domino/Notes Administration topics mentioned in this document are not understood, please reference the IBM Notes or IBM System Administration documentation.
Section 2. Requirements
2.1 End User Workstation Requirements Operating System
• Windows 8.1
Microsoft Outlook
• Outlook 2010 Professional
• Outlook 2013 Professional
• Outlook/Office365 ProPlus 2016
• Outlook/Office365 ProPlus Click-to-Run 2016
Only 32-bit Outlook clients are supported.
For Outlook 2010 and 2013, Home edition is not supported, only Professional (Pro).
Notes
• Notes 7 or higher (7.0.4 is not supported due to a defect in the Notes code).
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 3 Binary Tree Documentation
Other
• .NET 4.5.2 or higher (usually installed with Windows)
• C++ 2013 runtime 32-bit
The end user workstations all require network HTTP access to the licensing server.
2.2 Licensing Server Requirements Before installing SSAM, check the following requirements to be sure your licensing server is optimally configured.
Hardware
• Hard Disk Drive: 100 MB of free space after the pre-reqs have been installed; SSAM does not require space for logs like Notes Migrator • 2-4 cores, 4GB of RAM (minimum) General Requirements
Notes 8.5 or higher (single-user install)
*It is recommended that Notes Designer be installed on the Licensing Server
IIS with web service components (SMTP and FTP components not needed); for more details, refer to the next section
English version of SQL Server 2012, SQL Server 2012 Express, SQL Server 2016, or SQL Server 2016 Express*; if SQL Server is not detected during installation, the installer will provide the option to install SQL Server 2012 Express
*Internet access is required for the installer to install SQL Server 2012 Express
*Non-English versions of SQL Server are not supported
*Before installing SQL Server Express, complex password requirements must be disabled on the server
*SQL Server 2016 Express is not compatible for installation with Windows Server 2008 or Windows 7
For the installation of SSAM, you will need Microsoft Visual C++ 2013 runtime (both x86 and x64 on the License Control Center) and .NET 4.5.2; if any of the additional packages are not installed, the Installer will automatically install them
You must disable any applications which take over or block the use of port 80 on the License Control Center
Windows PowerShell 2.0 Engine must be enabled on the Control Center to allow PowerShell matching; to enable PowerShell 2.0, navigate to Add Roles and Features Wizard > Features > Windows PowerShell and check Windows PowerShell 2.0 Engine
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 4 Binary Tree Documentation
Section 2. Installing SSAM
2.1 Downloading SSAM Binary Tree maintains the latest release of the SSAM License Server Setup installation package on a secure FTP web site. The address to the FTP site is ftp://cftp.binarytree.com. To download a copy, Binary Tree provides a user name and password. Log on to the web site using the given credentials and download the SSAM License Server Setup.exe to the license server’s Desktop.
2.2. Installing Software on the Licensing Server 1. Open the SSAM License Server Setup executable file to run the SSAM installation wizard. The Notes Migrator | CMT and SSAM Licensing Server | CMT loading screens will first appear and then you should see the following installation wizard screen; click Next:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 5 Binary Tree Documentation
2. Review the License Agreement and Print if desired; if you accept all terms, click Yes:
3. Click Browse to select the location where the SSAM licensing server software will be installed. This installation process also installs the SSAM application (database) in Notes. The application gets installed in the Notes Data Directory:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 6 Binary Tree Documentation
4. Enter the Login ID and Password credentials used in your instance of SQL Server; click Next:
A window will appear showing the progress of installing the SSAM database to the designated server.
5. Click Install to begin the installation of the SSAM licensing server software and the SSAM Notes application:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 7 Binary Tree Documentation
6. Once the installation has finished, the InstallShield Wizard Complete screen will display; click Finish:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 8 Binary Tree Documentation
2.4. Repairing, or Uninstalling SSAM The SSAM software can be modified, repaired, or removed after it has been installed by executing SSAM License Server Setup from the Control Panel.
In the Add or Remove Programs applet, locate the SSAM Licensing Server | CMT icon in the Control Panel and select it. To repair the application, select Repair; if you wish to remove the application, select Remove:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 9 Binary Tree Documentation
2.4.1 Repairing SSAM
1. To repair the currently installed software, select Repair and then click Next:
2. Several Setup Status screens display:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 10 Binary Tree Documentation
3. The Maintenance Complete screen displays when the restore is complete; click Finish:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 11 Binary Tree Documentation
2.4.2 Uninstalling SSAM
1. To remove or uninstall the software, select Remove and then click Next:
2. To remove the SSAM licensing server application, click Yes:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 12 Binary Tree Documentation
3. When the uninstall process is complete, the Uninstall Complete screen displays; click Finish. The SSAM application and licensing server software has been removed.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 13 Binary Tree Documentation
Section 3. Setting Up the SSAM Application (Database) After installing, open the SSAM application (database) in Notes. The Progress Summary screen will display:
3.1 Sign the SSAM Database 1. Click the Sign This Database button; if this step is not completed first, error messages will appear throughout the configuration steps:
2. Click Yes to continue signing:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 14 Binary Tree Documentation
3. On all of the subsequent Execution Security Alert screens, select Start trusting the signer to execute this action and click OK; multiple subsequent alerts may appear:
4. Click OK to confirm the signing:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 15 Binary Tree Documentation
3.2 Configure the Access Control List (ACL) 1. Open the SSAM application in Notes and navigate to Application | Access Control:
2. The Access Control List to: Self Service Archive Migrator window will appear; click the Add button to add the necessary users and groups to the ACL.
3. The Select Names window will appear; select your migration administrator account (it can be an individual or group) and click Add. In the example below, administrator is the user to be added to the ACL; click OK:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 16 Binary Tree Documentation
4. The user has successfully been added to the ACL; be sure that the User type field has been set to Person and Admin has been checked in the Roles box (see screenshot below); click OK:
5. Re-open the Access Control List to Add your SSAM Users Group (or all Domino Users Group) to the ACL. This will allow your Notes users to access the SSAM system. Be sure that the Access field is set to Editor without the Admin Role:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 17 Binary Tree Documentation
3.3 Add the Domino Address Book and Copy the Database In the SSAM Notes application, open Configuration | Settings. Click on the Required Settings tab | Domino tab and follow the steps below:
1. Click the Browse button and select your Domino address Book; this will populate both the Mail Server and Domino Directory fields:
a. In the Choose Application dialog box, browse for your Domino address book and click Open:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 18 Binary Tree Documentation
2. Once the Mail Server and Domino Directory fields are populated, review the Server Mailbox field. The default value is mail.box which you can leave as is or change depending on your environment
3. For User Import View field, leave the default value People; clients with more advanced configurations can change this field if needed
4. Click the Server Db Copy and Mail-In Db Doc button; a series of confirmation boxes will appear:
Your migration ID will require security rights on the Domino server to create databases and templates.
Your migration ID will require ACL rights on the Domino Directory to create a mail-in database entry.
5. In the Does Self Service Archive Migrator 19.06 already exist? dialog box that appears, click No:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 19 Binary Tree Documentation
6. Click Yes in the following window to Create a db copy:
7. In the following Fullname for the mail-in db doc window, rename the database or leave the default value; click OK:
8. The Open the new mail-in doc? window will appear; click Yes to open the new database document and confirm your settings:
9. Click Yes on the Open EMM window:
Going forward, administrators should be sure that all configuration settings are made on the Domino server copy and not their Local workstation.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 20 Binary Tree Documentation
10. Notice the button name changes to Open Mail-In Db Doc; click this button if you want to open the mail-in database copy that was created above:
11. Click Save & Close to exit Settings
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 21 Binary Tree Documentation
3.3 Enter the License Key After purchasing a license key and corresponding number of licenses, follow these steps to apply the license key before continuing with the rest of the configuration:
1. The license key will be emailed to you with instructions on how to apply it. If you need to purchase more licenses, contact [email protected].
2. Open Notes SSAM application and click View License Agreement
3. Review the agreement and click Accept Terms of License Agreement:
4. Next, click Enter License Key:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 22 Binary Tree Documentation
5. On the CMT License dialog box, click Yes:
6. Paste the CMT license key you received via email into the CMT License textbox and click OK:
7. The license should be added successfully; click OK:
8. Click Refresh License Counts:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 23 Binary Tree Documentation
9. The updated license key information will now be displayed on the Progress Summary screen:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 24 Binary Tree Documentation
3.4 Configure Licensing Notifications Two types of license notifications can be configured to send to users:
• Licensing Error Notification – This notification is generated when the number of available SSAM licenses have run out. This indicates that additional SSAM licenses must be purchased (one per migration) to continue migrating
• Licensing Warning Notification – Users will receive this notification when 10% of licenses remain in the license pool. This notification is a helpful reminder that you may need to buy more licenses if more than the remaining licenses will be consumed.
1. Configure the SSAM License Server
2. Use the Send notifications to field to select the contact to which notifications will be sent
3. Configure the subject and message text for each notification type
Click Save and Close when you are finished.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 25 Binary Tree Documentation
Notification Type Description This notification will be sent to end users when all purchased No Available License Notification licenses have run out. More licenses will need to be purchased to perform any additional migrations. This notification will be sent to end users when the specified percentage of licenses remain. If “10” is specified, for example, Low Licenses Warning Notification when only 10% of purchases licenses remain, a notification will be sent to end users warning that the number of licenses is low, but additional migrations can still be performed. End users will receive this notification when the licensing server is unreachable from the end user’s Notes client. The licensing Licensing Server Unavailable Notification server might be unreachable if, for example, a VPN connection the end user is using to connect to the licensing server becomes disconnected.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 26 Binary Tree Documentation
Section 4. Configuring Settings in SSAM Expand Configuration | Settings in the navigation pane:
4.1 Required Settings Domino Tab
1. Enter the name of the Domino Server the SSAM Manager app resides on in the Mail Server field.
2. Enter the file name of the Domino Directory you will use to import users in the Domino Directory field. Click Browse to find and select the Domino server-based NSF. If the NSF has already been copied to the Domino server, a prompt will display when the Browse button is clicked. In the prompt window, click Yes and then browse for the appropriate NSF:
3. Enter the file name of a mail router on the Domino server in the Server Mailbox field.
4. The default Domino Directory view for selecting users to import is the People view. This can be changed if you prefer a different view.
5. Enable this CMT Db for Notifications – The first time you configure this application, you will see a Server Db Copy and Mail-in DB Doc button. Clicking on this will create a copy of this application on the Domino server listed in the Mail Server field, as well as creating a mail-in database document in the Domino Directory. Subsequently, that button with change to a button to open the mail-in database document, as well as an X button that will delete the mail-in database document.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 27 Binary Tree Documentation
Click and hold the icon to reveal helpful tips on how to use a field.
LDAP Tab
If you will be using a translation table to ensure repliability, follow the next steps. Otherwise, go to the Additional tab.
1. Enter the common name of the Active Directory Domain in the Domain field.
2. Enter the LDAP Server name or IP address in the LDAP IP Address or Host Name field.
3. Enter the LDAP port used in your environment in the LDAP Port field.
4. Enter the Active Directory administrator account that has read access (or higher) to the target Domain in the Login ID field.
5. Enter the password associated with the Active Directory administrator account in the Password field.
6. Click on Validate Settings to validate access to Active Directory.
7. Enter the directory base for all LDAP queries in the LDAP Directory Base (Base DN) field.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 28 Binary Tree Documentation
8. Click on Validate Query Settings to verify that you can query LDAP
PowerShell Credentials Tab
Use the PowerShell Credentials settings tab to use PowerShell to match the users against Exchange.
1. Enter the amount of time (in seconds) that PowerShell should delay executing functions in the PowerShell Run Delay field. This allows LDAP operations to replicate in Active Directory prior to cmdlets running. 2. Enter the URL of the remote PowerShell host in the Remote PowerShell URL field. 3. Enter the PowerShell Admin Credentials of the global admin account in the format corresponding to the applicable environment (on-premises Exchange servers or Office 365). In most cases, the PowerShell Admin Credentials should be in SMTP/UPN format, i.e. [email protected]. 4. Enter the MS PowerShell logging path that is used when logging PS1 scripts in the PowerShell Logging Path field. C:/logs is the default path. 5. Enter the reporting path used by the Matching process in the Default Reporting Path for Matching field. C:/Matching/ is the default path.
PowerShell Execution Policy
After filling out the PowerShell Credentials tab, it is a good time to set the administrator’s execution policy in PowerShell. The administrator’s execution policy should be set to “Unrestricted”. To do this, launch PowerShell as an administrator and type the following command at the prompt:
PowerShell Set-ExecutionPolicy Unrestricted
For more information on setting the PowerShell execution policy, see Microsoft’s Set-ExecutionPolicy online documentation (https://docs.microsoft.com/en-us/powershell/module/microsoft.powershell.security/set- executionpolicy?view=powershell-6).
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 29 Binary Tree Documentation
4.2 End User Migration Settings End User Migration Settings
1. If you will be using a translation file generated by SSAM, select Yes in the Include Translation File field. If you will be using an existing translation file that has been delivered by another process to the client workstation, select Use Existing. Please review section 5.2 Configuring the Translation Table, on using a translation file, to determine the correct choice for your environment.
2. For Include All Translations Entries?, select one of the following, to control which address translation entries are included in the translation file:
• All name combinations (default) – this includes all name variations found for the user.
• First Canonical Name - only adds the First Canonical Name found for the user.
Choosing the First Canonical Name option will limit the number of email names returned to the first canonical name listed in the Domino Directory: in other words, the default name for each user. This is faster than the default all name combinations option but may result in issues for users who have changed their name or have aliases in their Person Document relating to other email accounts (i.e., they took over an account that was owned by someone no longer with the company). When in doubt, go with the more thorough default setting!
3. Select how the migration engine is being deployed; either Installed by User or Deployed, i.e. is already installed for end user.
4. Select the destination of the migration; either PST file or Online Archive. If the PST file option is selected, the following additional settings are displayed:
• Attach PST to users profile?: Select Yes to attach migrated PST files to the user’s Outlook profile, matching the primary SMTP address in Exchange automatically. Users should be matched using SSAM if using this option (see Matching Domino Users to Exchange in the user guide).
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 30 Binary Tree Documentation
• SMTP address of profile to find: Select Exchange Primary SMTP or Exchange UPN. Determines which address will be used to find the profile that the PST file will be attached to. Exchange UPN is the default setting.
• Maximum PST File Size: The maximum size allowed for each PST file. During the archive discovery process, the size of the local archives is compared to this value. If the archives exceed the maximum size allowed, the user will be prompted to contact their administrator. Leave this blank if you do not want a size restriction.
• Destination Folder for .pst file(s): Enter the destination location of the PST(s). Windows environment variables, such as %LocalAppData% and %AppData%, can be used when defining the destination folder path.
The end user account logged on to the workstation will need privileges to write data into this directory.
5. Select Yes in the Clean up files copied to User’s machines field, if you would like the files required for migration, including migration logs, to be removed from the workstation after the migration is complete.
6. Select the logging level that will be used. Minimal is recommended unless you are trouble-shooting a problem.
Archive Identification Methods
1. Select Yes in the Identify via Archive Profile field to programmatically search for archive .NSF’s.
2. Select Yes in the Identify via Template Names field to search for local databases that use any of the templates listed in the Templates to Search For field.
3. The Templates to Search For field has been prepopulated with known archive template names. This can be updated as desired. Please note that this may identify local replicas of the server-based mail file.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 31 Binary Tree Documentation
4. Select Yes in the Identify via Database Title field to search by words that commonly appear in the database title, such as the word “archive”. Separate words with a carriage return.
5. Select Yes in the Identify via File Name to search for parts of a file name that are common to archives, such as “a_” or “archive”. Separate parts with a carriage return.
Some of these search methods may identify databases not intended for migration, such as local replicas of the mail file or the archive logs.
6. In File Name Search Criteria, enter part of an archived database file name indicating the database file is archived. Common examples are “a_” or “Archive”.
Support Notification
In the Custom Support Notification field, enter custom text that will instruct end users on how to contact the appropriate support team. This message will appear at the bottom of the Archive Processing forms:
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 32 Binary Tree Documentation
4.3 Custom Communications This section allows you to use placeholder fields to customize the Message templates. You may add additional placeholder fields as needed.
The Doc Link Placeholder is used to provide the end user a doc link for easy access to their configuration document in this application. The doc link is needed for starting the migration process (see Place Holder Fields in the user guide for additional information on message templates).
Additional placeholder fields can be added to the body of a message template and are mapped to fields in the person document. Placeholder fields are mapped to person document fields using the Replacement Field column in the Custom Communications tab (shown in the screenshot below).
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 33 Binary Tree Documentation
Section 5. Email Repliability
5.1 What is a Translation Table? To accurately transmit emails between Domino and Exchange, a Translation Table is used to translate the email headers and map contact address attributes of a person existing in Domino to their corresponding identity in Exchange/Office365.
The Translation Table contact address attributes are as follows:
1) Name 2) Email address 3) Short name 4) Canonical name 5) Hierarchical name 6) X500
In order for addresses in migrated messages to resolve and have Exchange formatting (instead of Notes formatting), the Address Translation table is used during the migration to update the address fields (To, CC, BCC). While this is standard practice when performing production mail migrations, it is optional when migrating archives to PST files. Consider the following when determining if you should use one for your archive migrations: 7) Will your users be replying and forwarding email from the PST files often? 8) The Address Translation table can be very large, depending on the size of your environment. This file will need to be copied to each end-user workstation during the migration process, so each workstation must have the disk capacity to house the translation file. 9) The size of the translation file may increase the time it takes to perform the migration.
5.2 Configuring the Translation Table If you will be using an Address Translation table, open the Add Names to Translation Table view under Configuration | Email Repliability.
1. Click on Add Names to Translation Table and Select Add All Names to Translation Table.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 34 Binary Tree Documentation
2. When complete, click on Match selected entries and select Match all entries using LDAP (recommended). If matching entries to Office 365, use the Match selected entries user PowerShell option.
3. Go to the Save Translation Entries view and click Save Translation Table.
Make sure the administrator’s execution policy is set in PowerShell. For more information, see PowerShell Execution Policy.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 35 Binary Tree Documentation
Section 6. Message Templates Message Templates are customizable email messages used to communicate with your end users. There are three pre-configured templates:
• 1 Week Notice
• Validation Check
• Archive Migration
The 1 Week Notice has general user instructions for the end users. The Validation Check template is used to send an end user-driven workstation validation check to ensure that individual workstations meet the requirements to perform the migration. The Archive Migration template is designed to be used to initiate the migration. You may also create additional templates as desired.
You must customize the existing templates with the appropriate information for your migration.
6.1 Creating a New Template
1. From the Message Template view, click New Template.
2. Enter a name for the template (visible to the migration administrators only).
3. The From field should contain the name of the sender of this email. We suggest that it be descriptive and meaningful to your user community.
4. Enter a descriptive subject for this email in the Subject field.
5. Choose the Template Type for this email. The Email Only type are notifications that do not require confirmations or action by the end user.
6. Choose the Delivery Method for this email. Notifications can be inserted directly into the user’s Domino mail file or routed as a mail message to the user. The three dropdown menu options are described below:
• Default routes the email via the Domino server.
• Insert into Domino Mailbox opens the user’s mailbox and copies the message into the user’s inbox.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 36 Binary Tree Documentation
• Route as mail to user routes the email via the Domino server. Route as mail to user performs the same function as Default (above).
7. Check the User Action Required box if migration for the user cannot proceed until they respond to this User Notification message.
8. Type the body of the message in the Body field.
9. Place Holder Fields – When a message template is in Edit mode, you will see a button at the top of the form called Insert Place Holder Field. Clicking the button will display the preconfigured placeholder fields. You can add these placeholder fields as needed in the body of the message. Additional placeholder fields may be created in the Custom Communications Settings.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 37 Binary Tree Documentation
Appendix A: Installing the Self-Service Archive Migrator Application on End User Workstations The Self-Service Archive Migrator application is typically deployed using email communication. If a desktop policy prevents detaching files to the Program directory, the SSAM application can be deployed using a software deployment system. The process below will cover the standard steps for remotely installing the Self-Service Archive Migrator application using a GPO (Group Policy Object). The customer’s process for deploying software using a GPO or a third-party product may be different and is not covered by Binary Tree Support
Refer to the End User Workstation Requirements to verify all workstations meet the requirements for the SSAM application installation.
To install the SSAM application with a GPO:
1. Right-click on the Notes Archive Migrator MSI, point to Share with, and click on specific people.
2. Add a security group. The "authenticated users" group already includes all computers and is a good group to use. The group you add must have the shared Read permission and NTFS permission.
3. Click Share.
4. Click Done.
5. From the Start menu, point to Administrative Tools and click on Group Policy Management.
6. Right-click on the domain or OU you will be migrating and click on Create a GPO in this domain and link it here.
7. In the New GPO dialog box, enter a Name for the GPO and click OK.
8. Click on the new GPO and click OK.
9. Right-click on the GPO and select Edit.
10. Open Computer Configuration > Policies > Software Settings and right-click on Software Installation and then point to New and click on Package.
11. In the File Name field, enter the UNC path to the MSI file and click Open.
12. Select the Self-Service Archive Migrator and click Open.
13. In the Deploy Software window, select the Assigned deployment method and click OK.
The device must be rebooted for the applied group policy to complete the installation.
To verify the GPO:
1. Log on to a workstation within the scope of the GPO using administrator credentials.
2. From a command prompt on the workstation, run gpresult -r
3. The Computer Settings section will display the applied group policy.
A newly applied group policy will not immediately be displayed. The Computer Settings section displays the applied group policy
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 38 Binary Tree Documentation
Learn more about Binary Tree For more information on Binary Tree, visit us at www.binarytree.com/company/about-binary-tree.
Binary Tree Social Media Resources
© Copyright 2019, Binary Tree, Inc. All rights reserved.
The Binary Tree logo and the tagline “Powering Enterprise Transformations” are registered trademarks, and any references to Binary Tree’s products and services are trademarks, of Binary Tree, Inc. All other trademarks are the trademarks or registered trademarks of their respective rights holders.
Self-Service Archive Migrator | CMT 19.06 Requirements, Installation and Configuration Guide 39