The following article provides guidelines for migrating a stand-alone ITMS 8.1 RU7 instance to ITMS 8.5 RU4 using new hardware and a new host name for Notification Server.
NOTE: This guide was written for 8.5 RU4. These guidelines also apply when migrating to newer versions, like ITMS 8.6 release. All of the steps will be the same. Just make sure the newly installed Notification Server / SMP is the same version, or newer, than the old Notification Server.
The descriptions of the old environment and the new environment are as follows:
NOTE: For latest software and Operating systems supported, please visit the online Platform and OS Support Matrix.
|Old environment||New environment|
An Operating System upgrade is needed on the SMP or new hardware is available
Migrating an ITMS 8.1 RU7 environment to ITMS 8.5 RU4 that runs on a new hardware, new SQL Server, and new Windows Server involves the following:
If you don’t have the KMS .zip package from the old ITMS server (and it is impossible to get KMS data), the settings, policies, client tasks, stand-alone replication rules, where custom passwords were used will not work until you will manually re-enter and save them on the new ITMS server.
In case of a domain user usage with password in settings policies, tasks, stand-alone replication rules, etc. this can cause domain account lockout.
In the Symantec Management Console, go to Reports > Notification Server Management > Agent, and open the ITMS Plug-ins status report to identify the required upgrade policies. You can select multiple policies and enable them at once.
KB 257157 "Migrating a stand-alone ITMS 8.5 RU4 to the latest ITMS (8.6 or 8.7) Version using new hardware and a new host name for Notification Server"