Migrating Notification Server data to Windows Server 2012 R2
ITMS Installation and Upgrade
Use the following steps to migrate Notification Server data from Windows Server 2008 R2 to Windows Server 2012 R2:
Table: Steps to perform on the Windows Server 2012 computer
Assign the Windows Server 2008 R2 computer name and IP address to the Windows Server 2012 R2 computer
After shutting down the Windows Server 2008 R2 computer, assign the same server name and IP address to the Windows Server 2012 R2 computer. This step ensures that all the client computers connect to the new server using the server name and IP address.
Restore CMDB data on the Windows Server 2012 R2 computer
You can use SQL Server Management Studio to restore the database. When you restore the database, use the same collation that was used on the Symantec Management Platform 7.5 server.
If you host Microsoft SQL Server on-box, install it on the Symantec Management Platform 7.5 SP1 server and copy the backed-up database to the SMP 7.5 SP1 server and restore it.
If you host Microsoft SQL Server off-box, you can use the same SQL Server or set up a new SQL Server.
View and manage the agent
registration status to verify
The Agent Registration Status report lets you view and manage
all registration requests and completed registrations from
Symantec Management Agents. In this report, you can check if the site servers and client computers have successfully established communication with Notification Server.
Use the following steps on Windows Server 2012 R2 computer to restore your previous CMDB data:
Open Microsoft SQL Management Studio.
In the left pane, on the right-click menu of the Databases folder, click Restore Database.
In the Restore Database dialog box, click From device.
Click the ellipsis option that is associated with the From device option that lets you select the database.
In the Specify Backup dialog box, click Add.
In the Locate Backup File dialog box, select the CMDB that you backed up on the Symantec Management Platform 7.5 server, and click OK.
In the Specify Backup dialog box, click OK.
In the Restore Database dialog box, in To database, enter a name for the database, select the database in the Select the backup sets to restore section, and click OK.
After the database is restored, click OK in the dialog box that appears.
Importing the data from the migration wizard data store file
Do one of the following to start the migration wizard in the import mode:
Install the migration wizard on the Symantec Management Platform 7.5 SP1 server with Symantec Installation Manager. By default, the migration wizard starts after it is installed.
Run the migration wizard EXE manually.
When you install the optional migration wizard components, the migration wizard EXE is installed. The EXE for the migration wizard is NSUpgradeWizard.exe, and by default it is in the C:\Program Files\Altiris\Upgrade directory.
If the Welcome page appears, click Next.
On the Export / Import Task Selection page, select the data store file you created when you exported the 7.5 data, and click Next.
On the Password Protection page, if a password was used when the data was exported, enter that password.
On the Importer Configuration page, select the data to import, and click Next.
The options on the Importer Configuration page are as follows:
Lets you select the products whose data you want to migrate. Data is imported only for the products that are checked.
Displays the importers for the product that you select in the Products section. Data is imported only for the importers that are checked in the Enabled column.
Displays a dialog box that lets you filter the data that an importer migrates as follows:
You can uncheck any item that you do not want to migrate.
The Details option lets you display the Filter Details dialog box.
You can sometimes change a value on the Filter Details dialog box. For example, when you import a locally stored package file, you can sometimes change the drive to which it is migrated.
On the Product Readiness Check page, review the messages, and click Next.
This page displays each product that has data that is not included in the import. To view an explanation of why the data is not included, click in the Message column.
On the Task Summary page, verify the migration tasks the wizard is about to perform, and click Next.
When the message that the data import has completed successfully appears, click OK.
If the data is not imported successfully, a message with instructions appears.
(Optional) To display each action's sub-actions, check Show Details.
Viewing and managing the agent registration status
After restoring CMDB, importing the data store file, and manually copying the data for few solutions to the Windows Server 2012 R2 computer, use the following steps to view and manage the agent registration status on the Windows Server 2012 computer:
In the Symantec Management Console, on the Reports menu, click All Reports.
In the left pane, under Reports, expand Notification Server Management > Registration, and then click Agent Registration Status.
(Optional) On the Agent Registration Status page, use the right-click menu options to modify the status of the agent. Note that depending on the status of the agent, the right-click options vary.
You can allow the agents that are in the Pending, Blocked, or Revoked state.
If you allow a blocked agent, the trust is granted next time when the agent sends a registration request to Notification Server.
You can block the agents that are in the Pending or Revoked state.
If you block a revoked computer, its functional status does not change. However, changing the status lets you differentiate the revoked computers that should never again connect to Notification Server from the revoked computers that may still require your attention.
Note that computers with the Blocked status are removed from the list after a predefined period of time if no new registration requests were sent from the same computer during this time. The default period is three months, but you can change it on the Purging Maintenance page.
You can revoke the registration of the agents that you have previously allowed. For example, you can revoke the registration for the client computer that is reported missing or stolen. After you revoke the agent, it stops receiving policies from Notification Server. Also, a revoked computer cannot be used as a site server.
During the revocation of internal agent trust, the agent encryption key registration gets marked as revoked on Notification Server. Revoked agents do not receive policies and do not run tasks. Also, the revoked agent clears locally stored policies to minimize its activity. After the revocation, Symantec Management Agent is forced to reinitiate the registration process.
The agent receives information about its revoked status next time when it tries to access secured data. Notification Server does not notify the agent about the revocation event when it occurs.
Note that the revoked agent remains in the Revoked state even if the agent registration policy allows it. You must manually manage the revoked computers, if you want to change their state.