サポートと今すぐチャット
サポートとのチャット

Migrator for Notes 20.14.2 - Requirements

Outlook Client Requirements

  • Supported versions:

    • Outlook 2016 (32-bit), Outlook Professional Plus 2013 SP1 which is part of Microsoft Office Professional Plus 2013 SP1 (32-bit only) (most recent version of Microsoft Outlook, via Windows Update, is required). Office 365 ProPlus and Click-to-Run 2016 and 2019 versions are also supported.

Note: This must be the 32-bit version of Outlook Professional. Home, Workgroup or any other specialized version is not supported on any migration workstation.

  • All reminders are shut-off (click Tools -> Options -> Other -> Reminder Options)

  • Auto-archiving is disabled (click Tools -> Options -> Other -> Auto Archive)

  • Programmatic warnings disabled (click Tools –> Trust Center –> Programmatic Access –> Never warn me about suspicious activity (not recommended))

  • Cache mode must not be enabled because the migration data will not be written directly to the server store

  • Outlook should be updated to the current patch levels, at the time of this product release

 


For Office 365 migrations the Outlook client should be activated for best performance.


In testing, there have been performance loss for throughput between Outlook 2016 or Outlook 2019 and Outlook 2013 with 2013 showing better performance.

Notes Requirements

Notes is also known as Lotus Notes, IBM Notes, and HCL Notes.

  • Supported versions:

    • Notes version 12 is supported for Windows 10, Windows Server 2016 and Windows Server 2019

    • Notes version 11 is supported for Windows 10, Windows Server 2012, Windows Server 2016 and Windows Server 2019

    • Notes version 10 is supported for Windows 10, Windows Server 2012, Windows Server 2016 and Windows Server 2019

    • Notes version 9.0.1 FP10 is supported for Windows 10, Windows Server 2012, Windows Server 2016 and Windows Server 2019

    • Notes version 8.5.3 Fix Pack 6 is supported for Windows Server 2012

    • Notes must be installed as a single user installation (multi-user installations are not supported)

    • Notes Designer must be installed for Notes links to migrate properly

    • The Notes Designer client must be installed in the migration workstation for doc links to migrate properly

*Notes 7.0.4 is NOT supported

*If you are using Notes 8.5.3, Fix Pack 6 is required due to a product defect that could impact data fidelity

*If you are using Notes 9.0.1, Fix Pack 10 is required due to a product defect that could impact data fidelity

  • Ensure that you enable the Notes ID security for the option “Do not prompt for password from other Notes-based programs (Reduces security)”

  • Ensure that you turn off Notes mail reminders in the Notes client preferences mail section

  • Ensure that you enable TCP/IP as the only port in the Notes client install preferences

  • On each migration workstation, Server Connection documents may be required to provide access to some of the Notes/Domino servers; if connection documents are required, it is the customer’s responsibility to provide the appropriate Destination server address

  • A standard HCL Domino mail template is required to be applied to the .nsf email databases for migration; mail templates from R6.5 to R12 are supported; R8.5 to R12 mail templates are recommended

 


HCL Notes Fix Packs are provided by the product vendor (HCL) as patches to address issues found within the Notes client and by extension the Notes Application Programming Interface (API) that are used by the migration system to access and process Notes mail file data. The Migrator for Notes product is verified and tested at the time of release with the Fix Packs specified for standard Notes mail, calendar, contact and task data.

If issues are encountered with accessing or processing specific data within the Notes/Domino environment a newer Fix Pack from HCL may be required. In these cases, the items addressed by a Fix Pack should be verified with HCL support to confirm the details of any fixes and HCL recommendations should be followed. The data migration should be validated in the Notes/Domino environment if any changes are made to Notes Fix Pack versions.

General Requirements

  • For the Migration Control Center only:

    • 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 (for upgrades only), SQL Server 2012 Express (for upgrades only), SQL Server 2016, SQL Server 2016 Express, or SQL Server 2019*; if SQL Server is not detected during installation, the installer will provide the option to install SQL Server 2016 Express

*Internet access is required for the installer to install SQL Server 2016 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 2012 R2

*TLS 1.0 should be enabled on the controller for the installation process to access the SQL server and create the database

  • For the installation of Migrator for Notes, you will need Microsoft Visual C++ 2019 runtime (both x86 and x64 on Migration Control Center) and .NET 4.8; 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 Migration 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

  • For the Migration Workstations:

    • For the installation of Migrator for Notes, you will need Microsoft Visual C++ 2019 runtime (only x86 on Workstations) and .NET 4.8

The installer will not install these items and they will need to be installed separately

  • For both Migration Control Center and Migration Workstations:

    • To use the import users with Excel feature or export users to Excel feature, Microsoft Excel must be installed and properly registered with the operating system; typically, this is only needed on the Migration Control Center, or where the import is going to be performed from

    • Do not have restrictions in your Group Policies or workstation policies that prevent the automatic creation of MAPI profiles or .pst files on the migration workstations

    • Ensure that any personal firewalls and the Windows firewall are OFF and disabled as a service

    • Ensure that Antivirus software is disabled, specifically, the real time scanning protection; otherwise, migration throughput will be reduced and other issues can occur such as crashes in stressful states of migration workload. If it cannot be disabled, please exclude the following directories from scanning:

      • C:\windows\temp and (%TEMP% if different)

      • C:\Program Files (x86)\Binary Tree\CMT for Exchange

      • C:\Exported PSTs (or the directory specified by the user for storing PSTs)

      • C:\windows\temp and (%TEMP% if different)

      • C:\Program Files (x86)\Binary Tree\CMT for Exchange (Migration Worker)

      • C:\Program Files\Binary Tree\CMT for Exchange (Migration Controller)

      • C:\Exported PSTs (or the directory specified by the user for storing PSTs)

      • %LocalAppData%\Binary Tree (eg C:\Users\Administrator\AppData\Local\Binary Tree)

    • Ensure that WSUS, Intel LanDesk, and other such programs are excluded from running on the migration workstations. These programs can halt migrations as their screens pop up to run tasks, as well as unscheduled re-boots caused by these processes can interrupt migrations.

    • Ensure that User Account Control (UAC) is disabled to allow Migrator for Notes to communicate with other applications and temporary folders

    • The Windows workstation login account should be a Local Administrator

    • Ensure that you turn off Automatic Windows updates

 

 


Windows Updates can be processed on migration machines but these should be completed in a planned method without migrations in progress

IIS and ASP.NET in Windows

  • For the Migration Control Center only:

    • .NET Framework 4.7 or 4.8

    • Base version (v10.0) within Windows Server 2019

    • Base version (v10.0) within Windows Server 2016

    • Base version (v8.5) within Windows Server 2012 R2

    • IIS Server installed with the default website, settings and default locations including:

  • Default Weblog Path: C:\WINDOWS\system32\LogFiles

  • ISAPI Objects Enabled (filters must be disabled)

  • Unlimited web site connections

  • No bandwidth throttling

  • Home directory: C:\inetpub\wwwroot

  • Directory Security: SSL Disabled

  • ASP

  • ASP.NET version 4.0

  • .NET 4.5.2 or higher

  • To avoid installation issues, IIS 6 Management Compatibility components should be installed and enabled if using Windows Server 2012 R2

In Windows Server 2012 R2, enable IIS 6 Management Compatibility and all sub-options under Management Tools in Web Server (IIS) server role

  • For both Migration Control Center and Migration Workstations:

    • The machines must be logged into the destination Exchange Domain if migrating to an on-premise Exchange environment (does not apply to MS365 migrations)

      • You cannot have restrictions on any workstation policy that can prevent the automatic creation of MAPI profiles or .pst files

      • All workstation names must be excluded from group policies that restrict local account privileges; It is recommended that all workstation names be excluded from Group Policy Objects (GPOs)

    • All migration workstations must be able to talk with each other over Port 80

    • XML calls must make connections between the Migration Control Center and All Migration Workstations using Anonymous Access

関連ドキュメント

The document was helpful.

評価を選択

I easily found the information I needed.

評価を選択