ITMS 7.1x installation, upgrade, and migration prerequisites

Article:HOWTO77026  |  Created: 2012-05-18  |  Updated: 2012-10-08  |  Article URL http://www.symantec.com/docs/HOWTO77026
Article Type
How To


Environment

Subject


ITMS 7.1x installation, upgrade, and migration prerequisites

Complete the tasks in the following checklists in preparation for your ITMS installation, upgrade, or migration.

An installation is defined as a new installation of one or more of the following:

  • IT Management Suite

  • Client Management Suite

  • Server Management Suite

  • Asset Management Suite

  • Any of the components that are parts of these suites.

For more information on ITMS installation, see the Symantec™ Management Platform 7.1 SP2 Installation Guide at www.symantec.com/docs/DOC4798

An upgrade is defined as an upgrade to an existing installation of any of the components or suites that are mentioned above.

For more information on upgrades, see the Symantec™ Management Platform 7.1 SP2 Installation Guide at www.symantec.com/docs/DOC4798

A migration is defined as a move to a new database, from Symantec Management Platform 6.x or 7.0.

For more information on migrating from 6.x to 7.1 SP2, go to www.symantec.com/docs/DOC4742.

For more information on migrating from 7.0 to 7.1 SP2, go to www.symantec.com/docs/DOC4743.

Table: Installation checklist

Item

Task

Description

Notes or KB article

1

Ensure sufficient space on OS Drive (C:\ )

Additional space that is needed on the OS Drive:

  • Stand-alone Notification Server: 1GB

  • Child Notification Server: 9GB

  • Parent Notification Server: 1GB + the product of 2 MB per agent on all child Notification Servers

You can install Symantec Management Platform (SMP) on an alternate drive.

However, some SMP operations write files to the OS Drive's ProgramData folder (typically C:\ProgramData\Symantec\SMP).

These files include:

  • Logs (capped at 400MB by default)

  • Data that is posted by Agents to be processed (capped at 500MB by default)

  • Data that is posted by another Notification Server for replication (not capped)

2

Ensure that ITMS component versions match the Symantec Management Platform version.

The components that you install or upgrade must be the same version as the Symantec Management Platform (SMP).

For example, if you install Patch Management on Symantec Management Platform , ensure that it is the same version as the SMP.

www.symantec.com/docs/HOWTO60852

3

Configure IIS compatibility.

IIS must be configured with the roles and features that are required for installation.

The knowledge base articles show the command lines that can be run with ServerManagerCMS.exe or PowerShell to set the required options.

www.symantec.com/docs/HOWTO75140

www.symantec.com/docs/HOWTO75141

4

Check network ports.

Basic server-agent communication uses standard web ports: 80 or 443.

Other features and functionality can use other ports. The knowledge base article maps all functionality to the network ports that need to be open.

www.symantec.com/docs/DOC1892

5

Check ITMS credential and security best practices.

ITMS uses a variety of credentials. The knowledge base article contains helpful tips; for example, the Symantec App Identity should be a service account. It also offers best practices for improving the security of the database.

www.symantec.com/docs/HOWTO75157

6

Be aware of Deployment Solution incompatibility with HTTPS.

Deployment Solution's automation environment is not compatible with HTTPS. Imaging and other tasks fail if HTTPS is configured for Notification Server.

www.symantec.com/docs/TECH127620

7

Be aware of your site distribution needs.

Task, package, and deployment site services are all site server roles. These site services can be deployed in multiple combinations to meet endpoint demands.

A remote site may only need a package server. A task server may be needed only at the datacenter. However, a deployment site server requires that the task service and package services be installed on the same computer.

Your topology and your use of solutions determines if you should combine site services onto a single computer or use dedicated computers.

www.symantec.com/docs/DOC4827

8

Be aware of requirements for installing solutions in a Notification Server hierarchy.

In a hierarchy, all solutions that are to be installed on Child Notification Servers also need to be installed on Parent Notification Servers.

CMDB and Asset Solutions (installed by the ITMS Suite) can only be installed on the Parent Notification Server.

Do not install the ITMS Suite or these two solutions on Child Notification Servers.

N/A

9

Review logs before installing new ITMS components.

Review Notification Server logs for errors or warnings that may cause instability with the product.

If you find errors or warnings, take note of them and try to resolve them.

This step assumes that you have one of the Altiris Suites installed and want to install additional components.

Table: Upgrade checklist

Item

Task

Description

Notes or KB article

1

Perform a database and server backup

Perform a backup of the ITMS server and the CMDB database.

 

2

Make note of configuration settings.

In the console, navigate to Task Server Settings > Agent Communication Settings > Policy Refresh Settings > Membership Update Settings.

 

3

Disable hierarchy replication (if applicable).

Refer to the knowledge base articles on the right on "Disabling hierarchy replication" and Upgrading Notification Servers in a hierarchy."

www.symantec.com/docs/HOWTO44016

www.symantec.com/docs/HOWTO21657

4

Run the report "current replication activity"

In the Symantec Management Console, navigate to Reports > Notification Server Management > Server > Replication.

Verify that this report is blank. If the report returns any results, you must wait until all replications jobs have been completed before performing the upgrade.

 

5

Review NSE queues

On the Symantec Management Platform server, remove any Notification Server Event (NSE) files from the following "\bad" folders:

  • EvtInbox\bad

  • EvtQFast\bad

  • EvtQPriority\bad

  • EvtQLarge\bad

  • EvtQSlow\bad

  • EvtQueue\bad

www.symantec.com/docs/TECH177513

5

Ensure that ITMS component versions match the Symantec Management Platform version.

The components that you install or upgrade must be the same version as the Symantec Management Platform (SMP).

Or, if you upgrade your SMP from 7.1 SP1 to SP2, you must upgrade your ITMS components to the same version as the SMP.

www.symantec.com/docs/HOWTO60852

6

Be aware of Deployment Solution incompatibility with HTTPS.

Deployment Solution's automation environment is not compatible with HTTPS. Imaging and other tasks fail if HTTPS is configured for Notification Server.

www.symantec.com/docs/TECH127620

7

Review logs before installing new ITMS components.

Review Notification Server logs for errors or warnings that may cause instability with the product.

If you find errors or warnings, take note of them and try to resolve them.

 

8

(7.1x to 7.1 SP2 only)

Run "NS.packagerefresh" task.

If you upgrade from 7.1 or 7.1 SP1 to 7.1 SP2, run the scheduled task "NS.packagerefresh".

Resolve any warnings or errors that occur, before running the 7.1 SP2 upgrade.

 

9

Ensure that all critical tasks are completed.

During an upgrade, all services are stopped and any outstanding tasks may fail, report up incorrectly, or be terminated.

www.symantec.com/docs/HOWTO54534

10

Be aware of agent plug-in status.

You need to be aware of all of your agent plugins: Which are enabled? Which ones are you upgrading? What are their dependencies?

All plugin policies are disabled during upgrade, so you need to turn them on.

Any plugins that are not upgraded may cause conflicts with newer software. It is best practice to upgrade all components at the same time to ensure full compatibility.

 

Table: Migration checklist

Item

Task

Description

1

Perform a database and server backup

Perform a backup of the ITMS server and the CMDB database.

2

Review logs before installing new solutions.

Review Notification Server logs for errors or warnings that may cause instability with the product.

If you find errors or warnings, take note of them and try to resolve them.

3

Ensure product parity.

In IT Management Suite 7.1, some products are replaced or absorbed by other products, or have a new product name. When you install IT Management Suite, you must install at least the same equivalent products that you installed on the 6.x or 7.0 Notification Server.

4

Ensure that 7.1x and 6.x/7.0 servers have unique names and IP addresses.

Symantec recommends that you give the 7.1 server a name and an IP address that is different from the name and IP address of the 6.x or 7.0 server.

5

Be aware of "mixed-mode" limitation

Symantec Management Platform 7.1 does not support mixed mode. A Symantec Management Platform 6.x server or 7.0 server cannot communicate with a Symantec Management Platform 7.1 server.

5

Migration from 6.x only:

Ensure that you are on the latest version of Notification Server 6.x.

Before you migrate from Notification Server 6.x to Symantec Management Platform 7.1, you must have Notification Server 6.0 R13 and the latest solutions installed. If you do not have the latest version of Notification Server 6.x, upgrade to the latest version first.

You must also upgrade your 6.x solutions and the agents on your managed computers. For example, if you have Notification Server 6.0 R11 installed, you must upgrade to 6.0 R13 before you migrate to Symantec Management Platform 7.1.

6

Migration from 6.x only:

Create a new database.

When you install the Symantec Management Platform 7.1 products, you must create a new database. You cannot run Symantec Management Platform 7.1 against the 6.x database.

Schema changes were made to the database to increase the speed and to unify the structure of the database.

7

Migration from v7.0 only

Use same SQL collation.

Whenyou restore the CMDB, use the same collation that was used for Symantec Management Platform 7.1. You can restore the database to the same instance of the SQL Server that 7.0 uses, and use a new database name.

You can also restore the database to another instance of SQL Server using the previously used database name. You restore the database so that you can connect to it with Symantec Installation Manager during the installation.When you connect to the database, all of its data is migrated.

8

Migration from v7.0 only

Use same SIM installation path on 7.0 and 7.1x server.

When you install Symantec Installation Manager on the 7.1 server, you need to use the same installation path that you used on the 7.0 server.

If you change the installation path, you cannot upgrade the Symantec Management Agent and the agent plug-ins.


Legacy ID



v74766012_v75328471


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


Terms of use for this information are found in Legal Notices