Upgrading to ITMS 7.1 SP2 - Best Practices

Article:TECH177513  |  Created: 2011-12-21  |  Updated: 2013-01-28  |  Article URL http://www.symantec.com/docs/TECH177513
Article Type
Technical Solution


Subject

Issue



This document outlines the best practices to upgrade to ITMS 7.1 SP2.

Click here for an overview video of this process.

NOTE: If you are looking to upgrade to ITMS 7.1 SP2 - MP1, click here.


Solution



Pre upgrade steps

Ensure you are logged onto the server as the Application Identity user account.  You can verify the Application Identity user account in the console under Settings > All Settings and then navigating to Settings > Notification Server > Notification Server Settings.

  1. If applications on your client machines rely on DCOM, see www.symantec.com/docs/Tech109673 for important information about uninstalling and upgrading pcAnywhere 7.1 SP1
  2. Perform a Backup of the ITMS server and the Symantec CMDB database
  3. Make note of Configuration Settings (Task Server Settings / Agent Communication Settings / Policy Refresh Settings / Membership Update Settings)
  4. Ensure that IT Management Suite component versions match the Symantec Management Platform version.
  5. Be aware that Deployment Solution's automation environment is not compatible with HTTPS. Imaging and other tasks fail if HTTPS is configured for Notification Server.
  6. Disable hierarchy/replication (if applicable). See HOWTO21657 for instructions.
  7. Run the report "current replication activity" (reports/notification server management/server/replication/) and verify this report is blank. If this report returns results you must wait until all replications jobs have been completed before performing the upgrade.
  8. Remove NSE files from the “Bad” folders  if they exist. Event Queues are located under "C:\ProgramData\Symantec\SMP\EventQueue\" :
    1. EvtInbox\bad
    2. EvtQFast\bad
    3. EvtQLarge\bad
    4. EvtQPriority\bad
    5. EvtQSlow\bad
    6. EvtQueue\bad
  9. Verify Symantec logs for existing errors or warnings (if found take note and try to resolve any errors/warnings before the upgrade).
  10. If you are upgrading from 7.1 or 7.1 SP1 to 7.1 SP2 then run the scheduled task "NS.packagerefresh" and resolve any warnings or errors that occur, before running the 7.1 SP2 upgrade.
  11. Launch SIM by right-clicking and then selecting “run as administrator”.
  12. Upgrade via the View and Install Update option.

Note: If you are using SIM 7.1.194 and or earlier, use Install new products option.

You must upgrade all installed products to 7.1 SP2, most easily accomplished by selecting the currently installed suite(s). See HOWTO60852“Upgrading solutions to the same version as the Symantec Management Platform (SMP)”

Post upgrade steps

  1. Compare Configuration Settings as noted in step 2 above
  2. Re-enable hierarchy/replication (if applicable) only after all servers in the hierarchy have been upgraded to the same product version
  3. Verify Symantec logs for errors/warnings
  4. Perform a database defragment of the Symantec CMDB Database (see HOWTO8589)

Question:

What are the ramifications if the install was run from the “View and Install Updates" and what are the recommendations if the SMP was updated to SP2 from the “View and Install Updates" menu?

Answer:

A Customer can get into an unverified scenario.  For example a customer just upgraded Inventory Solution but didn't upgrade Software Management Solution. Symantec has not tested this version mismatch. The best way to remedy this situation is to install the 7.1 SP2 Suite(s) through "Install New Products" which will ensure all installed products are updated to the same version. 

 In the case of Activity Center UI, without doing a suite upgrade you may not always get the latest version of Activity Center which can lead to a reduced UI functionality. 

We are working with Dev to change SIM to only show hotfixes in the "View and Install Updates" section.
 





Article URL http://www.symantec.com/docs/TECH177513


Terms of use for this information are found in Legal Notices