Summary
The current IS server is on a Windows 2000 server and as the ServerProtect administrator, you want to move it to a Windows 2003 server.
The Normal Servers (NS) are in a mix of Windows 2000 and 2003 servers and you want to know how this will affect the ability of the IS to deploy new installations of the Normal Servers to both Windows 2000 and 2003 servers.
Details
The IS can be moved from a Windows 2000 server to a Windows 2003 server. Also, it can deploy to all the NS in both server versions.
Before setting up a new Information Store, when using remote install, note that this process does not require the NS on the IS to be the source server. The source server should be a similar server to the destination server.
For example: Exchange/Exchange, File/File, Print/Print, so that exclusions can be automatically propagated.
To set up the new Information Store:
- Install an NS using remote install.
- After the NS has been installed, use the SPNT management console to move the IS to the new NS.
Important: Before moving the IS, export the ServerProtect registry using the registry editor. Go to HKLM\SOFTWARE\TrendMicro\ServerProtect\CurrentVersion.
The important registry hives under CurrentVersion are InformationServer and Task. The first hive holds the Normal Server tree, which the management console uses, while the second hive holds the list or tasks that each NS executes.
If the process of moving the IS fails, use the exported registry file to restore the list of NS on the old or new IS.
The important registry hives under CurrentVersion are InformationServer and Task. The first hive holds the Normal Server tree, which the management console uses, while the second hive holds the list or tasks that each NS executes.
If the process of moving the IS fails, use the exported registry file to restore the list of NS on the old or new IS.
