ITMS 7 6 Installation and Upgrade Guide English

Symantec IT Management
Suite 7.6 powered by Altiris

technology Installation and
Upgrade Guide
Symantec IT Management Suite 7.6 powered by

Altiris technology Installation and Upgrade Guide
Legal Notice
Copyright 2015 Symantec Corporation. All rights reserved.
Symantec, the Symantec Logo, the Checkmark Logo, Altiris, and any Altiris or Symantec
trademarks or registered trademarks of Symantec Corporation or its affiliates in the U.S. and
other countries. Other names may be trademarks of their respective owners.
This Symantec product may contain third party software for which Symantec is required to
provide attribution to the third party (Third Party Programs). Some of the Third Party Programs
are available under open source or free software licenses. The License Agreement
accompanying the Software does not alter any rights or obligations you may have under those
open source or free software licenses. Please see the Third Party Notice document for this
Symantec product that may be available at
http://www.symantec.com/about/profile/policies/eulas/, the Third Party Legal Notice Appendix
to this Documentation or TPIP ReadMe File accompanying this Symantec product for more
information on the Third Party Programs.
The product described in this document is distributed under licenses restricting its use, copying,
distribution, and decompilation/reverse engineering. No part of this document may be
reproduced in any form by any means without prior written authorization of Symantec
Corporation and its licensors, if any.
THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED
CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED
WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR
NON-INFRINGEMENT, ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH
DISCLAIMERS ARE HELD TO BE LEGALLY INVALID. SYMANTEC CORPORATION SHALL
NOT BE LIABLE FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES IN CONNECTION
WITH THE FURNISHING, PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE
INFORMATION CONTAINED IN THIS DOCUMENTATION IS SUBJECT TO CHANGE
WITHOUT NOTICE.
The Licensed Software and Documentation are deemed to be commercial computer software
as defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19
"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, et seq.
"Commercial Computer Software and Commercial Computer Software Documentation," as
applicable, and any successor regulations, whether delivered by Symantec as on premises
or hosted services. Any use, modification, reproduction release, performance, display or
disclosure of the Licensed Software and Documentation by the U.S. Government shall be
solely in accordance with the terms of this Agreement.
Symantec Corporation
350 Ellis Street
Mountain View, CA 94043
http://www.symantec.com
Technical Support
Symantec Technical Support maintains support centers globally. Technical Supports
primary role is to respond to specific queries about product features and functionality.
The Technical Support group also creates content for our online Knowledge Base.
The Technical Support group works collaboratively with the other functional areas
within Symantec to answer your questions in a timely fashion. For example, the
Technical Support group works with Product Engineering and Symantec Security
Response to provide alerting services and virus definition updates.
Symantecs support offerings include the following:
A range of support options that give you the flexibility to select the right amount
of service for any size organization
Telephone and/or Web-based support that provides rapid response and

up-to-the-minute information
Upgrade assurance that delivers software upgrades
Global support purchased on a regional business hours or 24 hours a day, 7

days a week basis
Premium service offerings that include Account Management Services
For information about Symantecs support offerings, you can visit our website at
the following URL:
www.symantec.com/business/support/
All support services will be delivered in accordance with your support agreement
and the then-current enterprise technical support policy.
Contacting Technical Support

Customers with a current support agreement may access Technical Support
information at the following URL:
Before contacting Technical Support, make sure you have satisfied the system
requirements that are listed in your product documentation. Also, you should be at
the computer on which the problem occurred, in case it is necessary to replicate
the problem.
When you contact Technical Support, please have the following information
available:
Product release level
Hardware information
Available memory, disk space, and NIC information
Operating system
Version and patch level
Network topology
Router, gateway, and IP address information
Problem description:
Error messages and log files
Troubleshooting that was performed before contacting Symantec
Recent software configuration changes and network changes
Licensing and registration

If your Symantec product requires registration or a license key, access our technical
support Web page at the following URL:
Customer service
Customer service information is available at the following URL:
Customer Service is available to assist with non-technical questions, such as the
following types of issues:
Questions regarding product licensing or serialization
Product registration updates, such as address or name changes
General product information (features, language availability, local dealers)
Latest information about product updates and upgrades
Information about upgrade assurance and support contracts
Information about the Symantec Buying Programs
Advice about Symantec's technical support options
Nontechnical presales questions
Issues that are related to CD-ROMs, DVDs, or manuals
Support agreement resources

If you want to contact Symantec regarding an existing support agreement, please
contact the support agreement administration team for your region as follows:
Asia-Pacific and Japan
customercare_apj@symantec.com
Europe, Middle-East, and Africa
semea@symantec.com
North America and Latin America
supportsolutions@symantec.com
Contents
Technical Support ............................................................................................... 4

Chapter 1
Introducing IT Management Suite installation ............. 10

About IT Management Suite ...........................................................
About installing the IT Management Suite .........................................
About developing an installation plan ..........................................
About the Symantec Installation Manager ..........................................
What's new in Symantec Installation Manager ..............................
Best practices for installing the IT Management Suite ..........................
Where to get more information ........................................................
Chapter 2
Installing the IT Management Suite solutions .............. 24

Prerequisites for installing IT Management Suite .................................
SQL Server recommendations and third-party software
requirements ...................................................................
IIS role services installed by the Symantec Installation
Manager .........................................................................
The Symantec IT Management Suite Platform Support Matrix ...............
Introduction ...........................................................................
Symantec Management Platform ...............................................
Client Management Suite .........................................................
Server Management Suite ........................................................
Deployment Solution ...............................................................
Language Support ..................................................................
Installing the IT Management Suite ..................................................
Installing the Symantec Installation Manager ................................
Installing Symantec Management Platform and IT Management
Suite .............................................................................
Chapter 3
10
11
16
17
18
19
21
24
29
31
33
33
34
50
60
72
85
85
88
91
Performing the post-installation tasks ......................... 104

About performing post-installation tasks ..........................................
Launching the Symantec Installation Manager ..................................
Adding a product listing file ...........................................................
Updating the product listing file ......................................................
105
106
107
109
Contents
Installing critical product listing updates ...........................................

Applying licenses to a product .......................................................
Installing language packs, documentation, or the migration
wizard ................................................................................
Installing hot fixes .......................................................................
Configuring Notification Server to use HTTPS after ITMS installation
is completed ........................................................................
Creating or importing an SSL certificate .....................................
Creating an HTTPS binding ....................................................
Verifying the HTTPS binding ...................................................
Configuring a package server to publish HTTPS package
codebases ....................................................................
Configuring Cloud-enabled Management Site Server Settings
policy ...........................................................................
Configuring sites and site servers to serve Cloud-enabled
agents ..........................................................................
Viewing an SSL certificate ............................................................
Backing up Notification Server cryptographic keys .............................
Restoring the cryptographic keys ...................................................
Reconfiguring an installed product .................................................
Repairing the installation of an installed solution ................................
Creating and installing an installation package for offline
installation ...........................................................................
Updating an installation package for offline installation .......................
Creating a support package ..........................................................
Delaying an update of the Symantec Installation Manager ...................
Uninstalling or repairing the optional components ..............................
Uninstalling the IT Management Suite solutions ................................
Viewing the Symantec Installation Manager logs ...............................
Disabling the creation of verbose Symantec Installation Manager
logs ...................................................................................
Chapter 4
110
111
113
115
117
120
123
124
125
126
128
131
131
133
133
134
135
139
141
142
144
145
147
148
Upgrading to IT Management Suite ............................... 150

About upgrade paths of IT Management Suite 7.6 .............................
Best practices for upgrading to IT Management Suite 7.6 ....................
Upgrading to IT Management Suite 7.6 ...........................................
Upgrading to Notification Server 7.6 ...............................................
Upgrade checklist for IT Management Suite 7.6 ..........................
Performing upgrade to Notification Server 7.6 .............................
Performing post-upgrade tasks ................................................
About setting up Cloud-enabled Management after upgrade or
migration .......................................................................
150
153
154
155
156
161
164
166
Contents
Upgrading Symantec Management Agent ........................................

About agent registration after an upgrade ..................................
Viewing the Legacy Agent Registration Requests report ...............
Upgrading site servers .................................................................
Chapter 5
166
167
168
168
Migrating Notification Server data from Windows

Server 2008 R2 to Windows Server 2012
R2 .................................................................................... 171
Migrating Notification Server data from Windows Server 2008 R2 to
Windows Server 2012 R2 ....................................................... 171
Backing up Notification Server data from Windows Server 2008
R2 ..................................................................................... 173
Migrating Notification Server data to Windows Server 2012 R2 ............ 177
Chapter 6
Migrating to IT Management Suite 7.6 ......................... 184

About migrating to IT Management Suite 7.6 .................................... 184
Readiness checklist for IT Management Suite migration ..................... 185
Post-migration checklist for IT Management Suite migration ................ 188
Chapter 7
Troubleshooting information .......................................... 191

Troubleshooting installation issues ................................................. 191
Troubleshooting upgrade issues .................................................... 194
Appendix A
Reference topics ................................................................ 198

Solutions of IT Management Suite .................................................
About Cloud-enabled Management ................................................
Symantec Installation Manager shortcut keys ...................................
IT Management solutions and their dependent solutions .....................
198
203
205
205
Glossary ............................................................................................................. 213

Index ................................................................................................................... 221
Chapter
Introducing IT Management
Suite installation
This chapter includes the following topics:
About IT Management Suite
About installing the IT Management Suite
About the Symantec Installation Manager
Best practices for installing the IT Management Suite
Where to get more information
About IT Management Suite

IT Management Suite (ITMS) combines client and server configuration management
with IT asset and service management. It promotes effective service delivery and
helps reduce the cost and complexity of managing corporate IT assets. These
assets may include desktops, laptops, thin clients, and servers in heterogeneous
environments running Windows, Linux, UNIX, or Mac operating systems. You can
manage all of the features of the suite through a central console on a common
platform: the Symantec Management Platform. This common platform integrates
management functions to accelerate automation for better service, value, and IT
efficiency.
IT Management Suite comprises of the following management capabilities:
Server management
The server management incorporates a variety of wizards and other features
that let you automate configuration, stage tasks, and create policies to manage
your servers. The server management capabilities support Windows, UNIX, and
Introducing IT Management Suite installation

Linux operating systems. In addition, the same management disciplines are

applied to both physical systems and virtual systems, including both Microsoft
Hyper-V and VMware.
Client management
The client management helps you discover the resources in your network, and
lets you check their state. The reporting tools help you identify problems and
take immediate action to fix them. The client management capabilities support
Windows, Linux, UNIX, and Mac operating systems.
IT asset management
IT asset management builds upon solid inventory foundations for configuration
management. It helps you accurately value both your discoverable and
non-discoverable assets, and tracks your assets and your asset-related
information. You can manage contracts, software license compliance, and
procurement processes as well as the configuration items that are associated
with your assets.

An installation is when you install the IT Management Suite (ITMS) 7.6 solutions
and Symantec Management Platform (SMP) on a computer for the first time. You
do not have any previous versions of these installations on the computer.
This topic consists of the following information:
Suites and solutions to be installed
Types of installation of the IT Management Suite 7.6
IT Management Suite 7.6 installation scenarios
Suites and solutions to be installed

You can install the entire ITMS, or the SMP, individual suites, and solutions in
different combinations on a computer as per your requirement.
During installation of the entire ITMS, the SMP, individual suites and solutions, and
any other additional component get installed on the computer. After the ITMS
installation on a computer, that computer can be assigned as a Notification Server.
A Notification Server is the management server computer in your ITMS environment.
Notification Server installs and manages the Symantec Management Agent, passes
data to and from the CMDB, interacts with the Symantec Management Platform
and other components, and displays information through the Symantec Management
Console.
11

You can perform fresh installation of any of the following suites or their individual
solutions using the Symantec Installation Manager (SIM):
IT Management Suite
Client Management Suite
Server Management Suite
Asset Management Suite
To see the complete list of suites and solutions that are available for installation,
See Solutions of IT Management Suite on page 198.
Note: Symantec recommends that you install and test the latest version of ITMS in
a test environment before you install it in a production environment.
Types of installation of the IT Management Suite 7.6

On a computer, you can perform the following types of installations of the ITMS
solutions using the Symantec Installation Manager:
12

Table 1-1
Types of installation of the IT Management Suite
Type of installation
Description
First-time installation
A fresh installation is when you install the IT Management

Suite solutions and Symantec Management Platform on
a computer for the first time. You do not have any previous
versions of these installations on the computer.
The configuration of SQL server and the associated
hardware influences overall performance of the ITMS
solutions and SMP in your environment. Based on the
installation of the SQL Server, the installation can be any
of the following types:
On-box installation
An on-box installation is when you install the SQL
Server locally on the Notification Server computer.
Installing the SQL database locally does not result in
maximum performance, but it can deliver acceptable
performance.
Off-box installation
An off-box installation is when you install the SQL
Server on a separate server from the Notification Server
computer. In such case, the SQL Server performs much
better, because the SQL Server offloads the work of
data processing and frees resources for Notification
Server processing.
See Installing the IT Management Suite on page 85.

On-box upgrade from 7.1 SP2 MP1.1 or 7.5 SP1 HF5
An on-box upgrade is when you upgrade from ITMS 7.1

SP2 MP1.1 or ITMS 7.5 SP1 HF5 to the latest version of
ITMS using same hardware, server operating system, or
database.
See About upgrade paths of IT Management Suite 7.6
on page 150.
Off-box upgrade from 7.1 SP2 MP1.1 or 7.5 SP1 HF5
An off-box upgrade is when you upgrade from ITMS 7.1

SP2 MP1.1 or ITMS 7.5 SP1 HF5 to the latest version of
ITMS using the different hardware, server operating
system, and database.
See About upgrade paths of IT Management Suite 7.6
on page 150.
13

Table 1-1
Types of installation of the IT Management Suite (continued)

Description
Off-box migration from SMP 7.0 or from Notification Server An off-box migration is when you install the latest version
6.x
of the IT Management Suite solutions on a new computer,
and then migrate the data from the earlier ITMS solutions
to the latest version of the application. You can migrate
Notification Server 6.x or 7.0 data to either Notification
Server 7.1 SP2 MP1.1 or Notification Server 7.5. After
migrating the data, you must upgrade to Notification Server
7.6. The way you migrate the data and which data is
migrated depends on whether you use Notification Server
6.x or Symantec Management Platform 7.0.
If your current Notification Server is installed on a 64-bit
server, you can install the latest version of the ITMS
solutions on that computer. However, before you install
the Windows 2008 R2 or Windows 2012 R2 operating
system, you must complete all of the required migration
steps. Because the risk is high that a few of these migration
steps might not complete successfully, Symantec
discourages the reuse of the current server.
For more information about migration to ITMS, see any of
the following documents:
Offline installation
Altiris IT Management Suite from Symantec Migration

Guide version 7.0 to 7.5.
Altiris IT Management Suite from Symantec Migration
Guide version 6.x to 7.5.
An offline installation installs the IT Management Suite

solutions on a computer that does not have an Internet
connection. An offline installation can be a first-time
installation or a migration. To perform an offline installation,
you must first create an installation package.
To create the installation package, you use the Symantec
Installation Manager on a computer that has an Internet
connection. You then copy and run the installation package
on the computer that does not have an Internet connection.
See Creating and installing an installation package for
offline installation on page 135.
14

Table 1-1
Types of installation of the IT Management Suite (continued)
Description
Hot fix installation
Hot fixes for shipping IT Management Suite solutions are

released periodically to address security or other
high-priority fixes.
The current ITMS or SMP hot fixes are available through
the SIM and are applied to the existing installed solutions.
The hot fix count starts after the last time you downloaded
or updated the product listing file. All other hot fixes are
rolled out by the Symantec Support team.
See Installing hot fixes on page 115.
Critical update installation
Occasionally, Symantec releases critical updates to your

currently-installed product listing file. The critical update
of the product listing file forces you to resolve the critical
update on the computer.
See Installing critical product listing updates on page 110.
IT Management Suite 7.6 installation scenarios

You can install the ITMS solutions in any of the following methods:
Install ITMS 7.6 in an online mode

If Internet connection is established on a computer, you download and install
the Symantec Installation Manager installer file. The Symantec Installation
Manager is packaged with a default product listing file symantec_v2.pl.xml.zip.
The product listing file displays a list of products that you can install. You select
the suites or solutions for first-time installation using the default product listing
file. On confirmation, the .msi files of individual solutions get downloaded and
the installation process and configuration process is initiated.
See Installing the Symantec Installation Manager on page 88.
See Installing Symantec Management Platform and IT Management Suite
on page 91.
Install ITMS 7.6 in an offline mode

To install ITMS 7.6 on the computers that do not have an Internet connection,
you must create an installation package. You create an installation package
using a computer that has ITMS 7.6 previously installed on it and has Internet
connectivity. You then download or copy the entire installation package on a
computer that does not have an Internet connection, and then execute the
installation in an offline mode using the Symantec Installation Manager.
See Creating and installing an installation package for offline installation
on page 135.
15

About developing an installation plan

You use the Symantec Installation Manager to install the IT Management Suite
solutions. Before you install and run the Symantec Installation Manager, you must
develop an installation plan.
As you develop an installation plan, you must answer the following questions:
What type of installation must you perform?

You must determine if the installation is a first-time installation, an on-box
upgrade, or a migration from a previous version of the product. For either a
first-time installation or a migration, you must also determine whether the
computer can have an Internet connection. Although the overall process for
each of these types of installations is very similar, the type of installation affects
how you install the product.
See Solutions of IT Management Suite on page 198.
For more information, see the IT Management Suite 7.6 Planning for
Implementation Guide at http://www.symantec.com/docs/DOC8038
How many computers do you plan to manage with the IT Management Suite
solutions?
You configure the installation differently depending on the size of your
environment. For example, in a large environment you would not install SQL
Server on the same computer where you install the IT Management Suite
solutions.
Does the computer meet the system requirements?

During the installation process, Symantec Installation Manager performs a
readiness check to determine if the computer is ready for the installation.
However, this check only verifies that the computer meets the minimum
requirements. Before you begin the installation, you must make sure that the
computer meets the system requirements that are appropriate for your
environment.
See The Symantec IT Management Suite Platform Support Matrix on page 33.
See SQL Server recommendations and third-party software requirements
on page 29.
Is the installation for a production environment or for evaluation purposes?

If you are an evaluator, you can quickly install and begin testing the products.
Symantec recommends that you install the products in a test environment before
you install them in a production environment. Use the test environment to
evaluate and validate the functionalities of the latest version of the IT
16

Management Suite solutions. Throughout the process, keep the test server
available to test, troubleshoot, and validate hot fixes and updates.

The Symantec Installation Manager is used to install the Symantec Management
Platform and IT Management Suite solutions. The Symantec Installation Manager
uses an installation wizard that walks you through the installation process. During
the installation process, the Symantec Installation Manager verifies hardware and
software prerequisites and lets you install additional components such as Microsoft
.NET. The installation wizard also helps you perform the initial configuration of
Notification Server and the database.
Use the Symantec Installation Manager to perform any of the following tasks:
Install new products
Upgrade products to more recent versions
Install hot fixes
Install optional components
Back up Notification Server cryptographic keys for disaster recovery
Apply purchased licenses
Create an installation package to install the products on a computer that does

not have an Internet connection
Create a support package that you can send to Symantec support
Repair or uninstall installed products
Reconfigure a product that did not configure successfully during installation
Access the Symantec Notification Server Migration Wizard to migrate data from
Notification Server 6.x or Symantec Management Platform 7.0
View Symantec Installation Manager logs
For more information about Symantec Installation Manager, see the Symantec
Installation Manager Getting Started Guide at the following URL:
http://www.symantec.com/docs/DOC6717
17

What's new in Symantec Installation Manager

The latest release of Symantec Installation Manager (SIM) introduces the following
new features:
Table 1-2
List of new features in the Symantec Installation Manager
Feature
Description
Integration of KMS restore

utility with SIM
The KMS restore utility is deployed using the Symantec Installation Manager. This
utility lets you restore the backed-up cryptographic keys.
You can use this utility on a computer on which Symantec Management Platform is
installed.
Following is the location of the KMS restore utility:
<Install_Dir>\Program Files\Altiris\Symantec Installation
Manager\KMSRestoreUtility\KMS_Utility
Integration of IT Analytics
configuration through SIM
You can now configure the IT Analytics Server configuration using SIM.
You can configure the Report server and the Analysis server name and the database
connection using SIM.
The configuration pages are displayed when IT Analytics 7.6 is selected for installation,
or during upgrade, if an older version of IT Analytics is not already configured through
the Symantec Management Console.
If you decide not to configure the Report server and the Analysis server using SIM,
you can configure the servers through the IT Analytics page from the Symantec
Management Console.
Installation readiness checks

for upgrade to 7.6.
To support upgrade to 7.6, Symantec Installation Manager checks for the following:
Supported upgrade path

The supported upgrade paths are 7.1 SP2 MP1.1 (includes the SMP build version
7.1.8401) and ITMS 7.5 SP1 HF5 (build version 7.5.3300). Install Readiness Check
blocks the upgrade process if non-supported upgrade path is selected to upgrade
to 7.6
Supported database version
If you select 7.1 SP2 MP1.1, or 7.5 SP1 HF5 database in the Use existing
database option in the Database Configuration page of SIM installation wizard,
then SIM continues with the upgrade process. SIM restricts usage of all other
database versions, and blocks the upgrade process.
18

List of new features in the Symantec Installation Manager

(continued)
Table 1-2
Feature
Description
New install readiness checks

are added and upgraded
Following new install readiness checks are added:
Other enhancements
ASP.NET 4.5.1
SQL 2014
WCF 4.5.1
Java 8
Migration Wizard IRC
Following enhancements are introduced:
New progress bar is introduced during SIM installation.
Refresh option is added on the Licensing page.
Unsupported database version

From this release onwards, SQL 2005 is not supported. To upgrade to ITMS 7.6,
you must first upgrade SQL to one of the following supported versions:
SQL 2008
SQL 2008 R2
SQL 2012
SQL 2014
For more information, refer to the following article:

http://www.symantec.com/docs/HOWTO109671

Following are the best practices for installing the IT Management Suite (ITMS) 7.6
solutions on a computer:
Install the latest version of Java before installation so that the Software Library
and other Package settings work directly after install.
See Table 2-3 on page 30.
Enable the plug-in rollouts for Inventory and Software Management directly after
the installation. Alternatively, you can plan to roll out the plug-ins after the
installation.
Ensure that you have the user logged in as the application identity when you
install any ITMS solution.
The application identity of Notification Server is the account under which
Notification Server runs. You specify the appropriate user name and password
when you install Notification Server, and you only need to update it when
19

necessary. For example, if your organization has a password change policy,

the CMDB access credentials may be forced to change. The application identity
no longer has permission to log on to the SQL Server.
To verify that the user account is an application identity account:
In the Symantec Management Console, in the Settings menu, click All

Settings.
In the left pane, under Settings folder, expand Notification Server, and
then click Notification Server Settings.
On the Notification Server Settings page, in the Processing tab, ensure

that the user account is an application identity account in the Application
identity area.
In a hierarchy, all solutions that are to be installed on child Notification Servers

must be installed on the parent Notification Server.
Note: A few solutions or architectural components must be installed only on the
parent Notification Server. For example, CMDB and Asset Management Solutions
that gets installed as part of IT Management Suite installation. Do not install the
CMDB and Asset Management Solutions on child Notification Servers.
Specify HTTPS communication only or both HTTP and HTTPS communications

to access the Symantec Management Platform and to communicate with the
client computers. You must perform this task when you have logged on to the
Notification Server computer as an administrator.
HTTP is unsecured and is subject to man-in-the-middle and eavesdropping
attacks, which can let attackers gain access to website accounts and sensitive
information. HTTPS is designed to withstand such attacks and is considered
secure against such attacks. HTTPS mode of communication creates a secured
channel for a communication that is more reliable and improves communication
with client computers. To set up cloud-enabled management, you must configure
the Notification Server computer to use only HTTPS communication.
See About Cloud-enabled Management on page 203.
You can specify HTTPS communication on the Notification Server computer
using any of the following methods:
Specify to use HTTPS communication when you install the IT Management

Suite solutions.
During the IT Management Suite installation on a computer, you can select
to use HTTPS communication using the Symantec Installation Manager.
You can select the HTTPS communication while specifying Notification
20

Server settings on the Notification Server Configuration page in the

installation wizard of the Symantec Installation Manager.
See To configure Notification Server settings and SQL database settings
on page 95.
Set up HTTPS communication after the installation of IT Management Suite

solutions is completed.
After the ITMS solutions installation is completed and the Notification Server
computer is set up, you can create an SSL certificate and import the
newly-created SSL certificate. You must then configure the Notification Server
computer to use the newly-created SSL certificate to set up HTTPS
communication.
See Configuring Notification Server to use HTTPS after ITMS installation
is completed on page 117.
Before you start a fresh installation of ITMS solutions or an upgrade to ITMS

7.6, you must check the SSL configuration for the SMP website. If the Require
SSL option is selected for the SMP website in the IIS Manager, ensure that the
Client Certificates: Require option is not selected.
After the Symantec Management Platform (SMP) website is configured to
Require SSL option with Client Certificates: Require option in the Internet
Information Services (IIS) Manager, the configuration does not start and the
installation process or the upgrade process fails. Additionally, a forbidden (403)
error is displayed and an associated warning is reported in the Altiris Log Viewer.
Before you start installing ITMS 7.6, ensure that you use same database collation
on all the servers that might participate in Notification Server hierarchy.
Hierarchy is not supported on the servers that have different database collation
on parent Notification Server and child Notification Server.

Use the following documentation resources to learn about and use this product.
Table 1-3
Documentation resources
Document
Description
Location
Release Notes
Information about new

features and important
issues.
The Supported Products A-Z page, which is available at the following

URL:
http://www.symantec.com/business/support/index?page=products
Open your product's support page, and then under Common Topics,
click Release Notes.
21

Table 1-3
Documentation resources (continued)
Document
Description
Location
User Guide
Information about how to

use this product,
including detailed
technical information and

instructions for
performing common
tasks.
The Documentation Library, which is available in the Symantec

Management Console on the Help menu.
The Supported Products A-Z page, which is available at the
following URL:
http://www.symantec.com/business/support/index?page=products
Open your product's support page, and then under Common Topics,
click Documentation.
Help
Information about how to

use this product,
including detailed
technical information and
instructions for
performing common
tasks.
The Documentation Library, which is available in the Symantec

Click the page and then press the F1 key.
Help is available at the

solution level and at the
suite level.
Use the Context command, which is available in the Symantec

Context-sensitive help is available for most screens in the Symantec

Management Console.
You can open context-sensitive help in the following ways:
This information is
available in HTML help
format.
In addition to the product documentation, you can use the following resources to
learn about Symantec products.
Table 1-4
Resource
Description
SymWISE
Articles, incidents, and
Support
issues about Symantec
Knowledgebase products.
Symantec product information resources

Location
http://www.symantec.com/business/theme.jsp?themeid=support-knowledgebase
Cloud Symantec All available IT

http://help.symantec.com/Welcome?locale=EN_US&context=itms7.6
Help Center
Management Suite and
solution guides are
accessible from this
Symantec Help Center
that is launched on cloud.
22

Table 1-4
Symantec product information resources (continued)
Resource
Description
Location
Symantec
Connect
An online resource that

contains forums, articles,
blogs, downloads,
events, videos, groups,
and ideas for users of
Symantec products.
http://www.symantec.com/connect/endpoint-management/forums/
endpoint-management-documentation
Here is the list of links to various groups on Connect:
Deployment and Imaging

http://www.symantec.com/connect/groups/deployment-and-imaging
Discovery and Inventory
http://www.symantec.com/connect/groups/discovery-and-inventory
ITMS Administrator
http://www.symantec.com/connect/groups/itms-administrator
Mac Management
http://www.symantec.com/connect/groups/mac-management
Monitor Solution and Server Health
http://www.symantec.com/connect/groups/monitor-solution-and-server-health
Patch Management
http://www.symantec.com/connect/groups/patch-management
Reporting
http://www.symantec.com/connect/groups/reporting
ServiceDesk and Workflow
http://www.symantec.com/connect/workflow-servicedesk
Software Management
http://www.symantec.com/connect/groups/software-management
Server Management
http://www.symantec.com/connect/groups/server-management
Workspace Virtualization and Streaming
http://www.symantec.com/connect/groups/
workspace-virtualization-and-streaming
23
Chapter
Installing the IT
Management Suite
solutions
Prerequisites for installing IT Management Suite
The Symantec IT Management Suite Platform Support Matrix
Installing the IT Management Suite

Before you begin installation, ensure that the computer on which you plan to install
IT Management Suite (ITMS) meets the minimum requirements.
The minimum requirements for installing IT Management Suite on a computer are
as follows:
Installing the IT Management Suite solutions

Installation checklist
Table 2-1
Item
Checklist item
Description
Space availability on OS Ensure that sufficient space is available on the computer's OS drive:
drive (C:\ drive).
C:\ drive.
The additional space that is required on the OS drive is as follows:
Hard disk drive of 80 GB capacity is required on a physical computer or

a virtual computer for installing the ITMS solutions on that computer.
12.5 GB of free space is required for first-time installation of the ITMS
solutions and the Symantec Management Platform (SMP).
The ITMS and SMP folders and data would consume around 7 GB of
space, the ITMS log files would consume around 1 GB of space,
Symantec Management Platform environment with SQL installed locally
would consume around 2.5 GB of space, and in hierarchy setups the
replication data would consume around 2 GB of space.
1 GB of space is required for standalone Notification Server.
9 GB of space is required for child Notification Server.
1 GB + 2 MB per solution on all child Notification Servers of space is

required for parent Notification Server.
You can install the Symantec Management Platform (SMP) on an alternate

drive of the computer.
However, a few SMP operations write files to the OS drives hidden folder
ProgramData, typically the C:\ProgramData\Symantec\SMP folder.
By default, the data that gets written to the OS drives hidden ProgramData
folder is as follows:
Log files that Notification Server generates

The log files contain the data that Notification Server generates. By
default, up to 2000 MB of data can be stored, and up to 200 log files can
be stored.
Data that another Notification Server generates for replication
No limit is set for the size of data that another Notification Server
generates for replication in a hierarchy.
System settings such as Configure the computer name and add the computer to the Active Directory
the computer name, and before installing the IT Management Suite. Ensure that the account that you
the domain name.
use for ITMS installation has local administrator's rights on the computer.
Additionally, ensure that the computer name does not include underscores.
25

Installation checklist (continued)
Table 2-1
Item
Checklist item
Description
Minimum software
requirements.
Ensure that the computer on which you plan to install the IT Management
Suite is configured with the following software:
Windows Server
SQL Server
Because ITMS functionality creates a heavy workload on the SQL Server,
Symantec recommends that you install Microsoft SQL Server on a more
powerful computer which is not affected by any other activities of the
ITMS processes.
Note: During install readiness check, Symantec Installation Manager

checks whether SQL Server is installed on the computer. If no database
is found on the computer, then Symantec recommends that you install
SQL Server, and then continue with the ITMS installation using Symantec
Installation Manager.
.NET Framework 4.5.1
Note: Sometimes it is required to restart the computer after installing the

.NET Framework 4.5.1.
Internet Explorer
See Console/Browser on page 39.

See The Symantec IT Management Suite Platform Support Matrix
on page 33.
on page 29.
4
SQL Server database.
Install SQL Server on the computer where you plan to install the IT
Management Suite or on a different computer.
The latest version of the IT Management Suite requires SQL Server to be
installed either on the same computer or on a different computer. The version
of SQL Server that you need depends on the number of endpoints that you
manage.
on page 29.
26

Table 2-1
Item
Checklist item
Description
Server roles and role

services.
On the computer where you plan to install IT Management Suite, you must
install the following server roles and server role services:
Application server
Web server (IIS)
File Services
.NET Framework 4.5.1
Windows Process Activation Service
Message Queuing Activation
WCF (Windows Communication Foundation) Activation
Note: If the required role services are not previously installed, you are
prompted to install the roles during the Install Readiness Check in the
Symantec Installation Manager installation wizard.
6
Third-party software.
Install the additional third-party software that the IT Management Suite

solutions require. For example, Ajax, Microsoft Silverlight, and Java JRE.
on page 29.
Additional network ports Verify and configure the additional network ports for executing specific
to be configured for
communication tasks in your environment.
performing different
Notification Server and endpoints communicate with each other using the
communication tasks.
standard web ports. By default, the standard web ports, such as port 80 for
HTTP communication, and port 443 for HTTPS communication are configured
on the computers.
Apart from the standard web ports that are configured on computers, you
may also need to configure additional network ports to perform specific
communication tasks. For example, the following tasks require configuration
of additional network ports on the computer:
Enabling the hierarchy and replication on the Notification Server computer.
Downloading packages from Notification Server or package server on

the client computer.
Downloading the agent for UNIX, Linux, or Mac operating systems from
Notification Server on the client computer.
The following knowledge base article provides information about all the
additional communication tasks and their associated network ports that you
can configure in your ITMS 7.6 environment:
27

Table 2-1
Item
Checklist item
Description
Additional user
credentials to be
configured for
performing different
tasks.
Verify and configure the ITMS user credentials and security best practices
for executing different tasks in your environment.
Apart from the standard ITMS user credentials that are configured on the
computers, you must configure additional user credentials for performing
different tasks. Configuration of the additional user credentials is mandatory
and is a part of the configuration tasks. For example, you must additionally
configure the following user credentials to perform the associated tasks:
Database Access Credential to access and modify the database.
App Identity Credential to execute the Symantec Management Console

and several other ITMS processes.
Additionally, the Symantec administrator role must be assigned to the local

administrator user account on the computer where you installed the ITMS
solutions. You are required to execute this step so that you can perform
additional tasks in your ITMS environment, such as, upgrading to the latest
version of ITMS solutions.
The following knowledge base article provides information about various
user accounts and their roles and privileges for performing specific tasks in
your ITMS environment:
www.symantec.com/docs/HOWTO75157
9
Site distribution
requirements.
Identify your site distribution requirements and plan the site server
requirements.
The topology and usage of solutions in your environment lets you determine
whether to combine site services onto a single computer or use dedicated
computers.
Task service, package service, and deployment site service are all site server
roles. These site services can be deployed in multiple combinations to meet
the endpoint requirements in your environment.
For example, a remote site may only need a package server. A task server
may be needed only at the datacenter.
28

Table 2-1
Item
Checklist item
Description
10
Requirements for
installing solutions in a
hierarchy.
Identify the requirements for installing solutions in a Notification Server

hierarchy.
In a hierarchy, all solutions that are to be installed on child Notification Servers
must be installed on the parent Notification Server.
Note: A few solutions or architectural components must be installed only

on the parent Notification Server. For example, CMDB and Asset
Management Solutions that gets installed as part of IT Management Suite
installation.
Do not install the CMDB and Asset Management Solutions on child
Notification Servers.
11
Check for pending

restarts and restart the
computer, if required.
Check whether there are any pending restarts on the computer from other
installations or updates and restart the computer if required before
proceeding.
The Symantec Installation Manager checks for any pending restart tasks
when you launch the Symantec Installation Manager and during the install
readiness check. You must restart Notification Server if Symantec Installation
Manager detects any pending reboots before installing or upgrading any
solution.
SQL Server recommendations and third-party software requirements

The IT Management Suite 7.6 requires SQL Server either installed on-box or off-box.
The version of SQL Server that you need depends on the number of endpoints that
you manage.
29

IT Management Suite 7.6 SQL Server recommendations
Table 2-2
Proof of Concept
100-1,000
endpoints
1,000 to 5,000
endpoints
Microsoft SQL Server

Express 2008 SP2 or
higher, 2012, and
2014.

2008 SP2 or higher,
or 2012 Standard or
Enterprise.

2008 SP2 or higher, or
2012 Standard or
Enterprise.
5,000-10,000
endpoints
10,000-20,000
endpoints
Microsoft SQL Server Microsoft SQL Server

2008 SP2 or higher, 2008 SP2 or higher,
or 2012 Standard or or 2012 Enterprise.
Enterprise.
Symantec
Although you can
Although you can host Symantec
recommends that you
host SQL Server on SQL Server on box,
recommends that you host SQL server off
box, Symantec
Symantec recommends host SQL server off
box.
recommends that you that you host SQL
box.
host SQL Server off Server off box.
box.
The IT Management Suite 7.6 solutions also require the following additional
third-party software:
Table 2-3
IT Management Suite 7.6 required third-party software
Software
Purpose
Adobe Flash Player 10 or 11
The Adobe Flash Player plug-in for Internet Explorer is required for the
Resource Association Diagram in the Asset Management Suite.
Adobe Reader
Adobe Reader is required to open the documentation that is available in PDF

format for ITMS solutions.
AJAX 1.0
Ajax is used to enable asynchronous calls to allow for a dynamic user

interface. For example, loading menus on demand and rendering on the fly.
Ajax is fundamental to many of the user interface control behaviors menus,
grids, trees, lists, component art controls, etc.
Microsoft Access 2010 OLEDB driver
Data Connector requires this driver to be able to communicate with Access

(.mdb) and Excel (.xls) files. Install the 64-bit version of the driver.
Microsoft Report Viewer 2008

Redistributable Package or later
The Microsoft Report Viewer 2008 Redistributable Package or later includes

controls for viewing reports designed using Microsoft reporting technology.
Microsoft Network Monitor 3.4
Microsoft Network Monitor 3.4 is a protocol analyzer. It allows you to capture

network traffic and view and analyze it.
Microsoft .NET 4.5.1 (for Notification

Server)
Symantec Management Platform depends on the Microsoft .NET framework.
Microsoft .NET 4.5.1 (for ITMS)
ITMS depends on the Microsoft .NET 4.5.1 framework.
30

Table 2-3
IT Management Suite 7.6 required third-party software (continued)
Software
Purpose
Web Browser
Microsoft Internet Explorer is the browser that supports Symantec

Management Console.
See Console/Browser on page 39.
Microsoft Silverlight 5
Silverlight is required for the First Time Setup page in the Symantec
Management Console.
Server Manager roles and role services Application Server role and IIS 6 Management Compatibility, ASP, and web
server role services.
Note: If the required IIS Role Services are not installed, you are prompted
to install them on the Install Readiness Check page.
See IIS role services installed by the Symantec Installation Manager
on page 31.
Sun Java Runtime 32-bit version 8
Java JRE is required for LiveState and Altiris Package Conversion. Java
JRE is also required on any computer that remotely accesses the Symantec
Management Console when the Software Library is used as the package
source.
You must have the latest 32-bit Java version installed on the computer to
carry out all Deployment Solution tasks.
IIS role services installed by the Symantec Installation Manager

Before you begin installing the IT Management Suite, you must install the Web
server (IIS) role on the computer. If the required IIS role services are not installed,
you are prompted to install them on the Install Readiness Check page from the
Symantec Installation Manager. When you confirm the installation, the Symantec
Installation Manager can automatically install and configure these IIS role services
on the server.
Note: Apart from the IIS role services that are installed with the Web server, you
may also require to install a few additional IIS role services. These roles services
are required to install the IT Management Suite. The Symantec Installation Manager
identifies such IIS roles services and prompts you to install them automatically
through the Install Readiness Check page of the Symantec Installation Manager
installation wizard.
31

Following are the IIS role services that are installed when you configure the IIS role
on the computer:
Application Server
Web Server (IIS) Support
Windows Process Activation Service Support
HTTP Activation
Web Server (IIS)
Web Server
Common HTTP Features
Static Content
Default Document
Directory Browsing
HTTP Errors
HTTP Redirection
Application Development
ASP.NET
.NET Extensibility
ASP
ISAPI Extensions
ISAPI Filters
Health and Diagnostics
HTTP Logging
Logging Tools
Request Monitor
Tracing
Security
Basic Authentication
Windows Authentication
Digest Authentication
Client Certificate Mapping Authentication
32

IIS Client Certificate Mapping Authentication
URL Authorization
Request Filtering
IP and Domain Restrictions
Performance
Static Content Compression
Dynamic Content Compression
Management Tools
IIS Management Console
IIS Management Scripts and Tools
Management Service
IIS 6 Management Compatibility
IIS 6 Metabase Compatibility
IIS 6 WMI Compatibility
IIS 6 Scripting Tools
IIS 6 Management Console
The Symantec IT Management Suite Platform Support

Matrix
This section outlines which platforms are supported for the installation of Symantec
Management Platform, the Client Management Suite, and the Server Management
Suite components. The section also contains the Symantec IT Management Suite
language support matrices for the core platform and the management agent.
Introduction
The Symantec IT Management Suite Platform Support Matrix (PSM) has been
created to provide current and future planned platform support information to
interested parties. It is organized to display supportability information based on the
Symantec IT Management Suite (ITMS) components as well as by ITMS release.
Many OS and database platforms include multiple versions that are based on the
same platform kernel. An example would be Windows Vista where there is Home
Basic, Home Premium, Business, and Ultimate. QA testing resources are limited;
33

therefore, we have only included a platform in the PSM if that platform has actually
been tested. This does not necessarily prevent a derivative platform from being
used by a customer, however, it should be understood that if an untested derivative
platform were used, support would not be provided.1
Any forward-looking indication of plans for products is preliminary. All future release
dates are tentative and are subject to change. Any future release of the product or
planned modifications to product capability, functionality or feature is subject to
ongoing evaluation by Symantec, and should not be relied upon in making
purchasing decisions
As changes occur, an updated version of this document will be made available.
Note: The PSM includes supportability matrices for the Symantec solutions currently
included in Client Management Suite (CMS), Server Management Suite (SMS) or
IT Management Suite (ITMS). For additional Symantec solution support information,
please refer to the solution release notes published with each solution.
1Requests
to formally support currently untested platforms will be treated as an

enhancement request and will be considered in the context of the numbers of
customers who could benefit from support weighted against the amount of QA and
Engineering effort required to provide that support
Symantec Management Platform

The following section contains the Microsoft platform support matrices for the
Symantec Management Platform. This section outlines which platforms are
supported for the installation of Symantec Management Platform components. For
information about supported agent platforms, please refer to the Symantec Client
Management Suite, and Server Management Suite sections provided later in this
document.
Notification Server and Workflow Server

Table 2-4
Microsoft Server SMP 6.x
operating
systems
Notification Server and Workflow Server

SMP 7.0 SP5 SMP 7.1 SP2 SMP 7.5
MP1.1
SMP 7.5 SP1 SMP 7.6
Supported
Not
Supported
Windows Server 2003

Windows Server
2003 SP2 x86
Supported2
Not
Supported
Not
Supported
Not
Supported
34

Table 2-4
operating
systems
Notification Server and Workflow Server (continued)

MP1.1
SMP 7.5 SP1 SMP 7.6
Windows Server
2003 R2 x86
Supported2
Supported
Not
Supported
Not
Supported
Not
Supported
Not
Supported
Windows Server
2003 R2 SP2 x86
Not
Supported2
Supported
Not
Supported
Not
Supported
Not
Supported
Not
Supported
Windows Server 2008

Windows Server
2008 R21
Not
Supported
Not
Supported
Supported
Supported
Supported
Supported
Windows Server
2008 R2 SP11
Not
Supported
Not
Supported
Supported
Supported
Supported
Supported
Windows Server 2012

Windows Server
2012
Not
Supported
Not
Supported
Not
Supported
Not
Supported
Not
Supported
Not
Supported
Windows Server
2012 R2
Not
Supported
Not
Supported
Not
Supported
Not
Supported
Supported3
Supported3
The Symantec Management Platform version 7.1 supports Windows Server 2008
R2 (64-bit only) Enterprise, Standard, and Datacenter editions. Core Edition is not
a supported platform.
2Due
to incompatibilities between Windows Server 2003 and the Windows ADK for
WinPE 4.0, Deployment Solution 6.9 SP6 does not support Windows Server 2003
for running the Deployment Server except in the cases of remote PXE servers and
remote SQL servers. For more information, refer to the following article:
3The
Symantec Management Platform version 7.5 SP1 and 7.6 support Windows
Server 2012 R2 (64-bit only) Standard and Datacenter editions. Core Edition is not
a supported platform.
Note: Workflow Server includes the Workflow Server and Process Manager
Components. The support matrix for the Workflow Designer is included in the
Designer and Tools section below
35

Table 2-5
Notification Server on a virtual host
Virtual host
version
SMP 6.x

MP1.1
SMP 7.5 SP1 SMP 7.6
VMware ESX 3.5
Supported
Supported
Supported
Not supported Supported
Supported
VMware ESX 4.0
Supported
Supported
Supported
Supported
Supported
Supported
VMware ESX 5.0
Not supported Not supported Supported
Supported
Supported
Supported
VMware ESX 5.1
Not supported Not supported Not supported Supported
Supported
Supported
VMware ESXi 5.5
Not supported Not supported Not supported Not supported Supported
Supported
Windows Hyper-V
Server 2008 R21
Supported
Supported
Supported
Windows Hyper-V
Server 2012
Supported
Supported
Windows Hyper-V
Server 2012 R2
Supported
It should be noted that core Hyper-V Server 2008 requires that UAC be set to a
lower level (1 down from the max security level) to allow the Symantec Management
Agent to work.
2VMware
ESXi 5.5 supports Network Discovery, Deployment Solution, Inventory

Solution, and Virtual Machine Management. Please refer to the following article:
Note: For more details about hosting the Notification Server computer on a virtual
host, please reference the knowledge base article titled Installing the Symantec
Management Platform on VMware:

Table 2-6
Microsoft SQL
Server Version
SMP 6.x
Microsoft SQL Server 2005

MP1.1
SMP 7.5 SP1 SMP 7.6
36

Table 2-6
Microsoft SQL Server (continued)
Microsoft SQL
Server Version
SMP 6.x

MP1.1
SMP 7.5 SP1 SMP 7.6
Microsoft SQL
Server 2005 SP2
R5
Supported
Supported
End of life
End of life
End of life
Microsoft SQL
Server 2005 SP3
R10
Supported
Supported
End of life
End of life
End of life
Microsoft SQL
Server 2005 SP4
R13
Supported
Supported
End of life

Microsoft SQL
Server 2008
R13
Supported
Supported
End of life
End of life
End of life
Microsoft SQL
Server 2008 SP1
Supported
End of life
End of life
End of life
Microsoft SQL
Server 2008 SP2
Supported
Supported
Supported
Microsoft SQL
Server 2008 SP3
Supported
Supported
Supported
Microsoft SQL
Server 2008 R2*
Supported
Supported
Supported
Microsoft SQL
Server 2008 R2
SP1
Supported
Supported
Supported
Microsoft SQL
Server 2008 R2
SP2
Supported
Supported
Supported
Microsoft SQL
Server 2012
Supported
Supported
Microsoft SQL
Server 2012 SP1
Supported
Supported

Microsoft SQL
Server 2014
Not supported Not supported Not supported Not supported Not supported Supported
37

SQL 2008 R2 support includes support for cumulative rollup 4.
Note: The Notification Server computer installation is tested with Microsoft SQL
Express, Standard, and Enterprise versions x86 and 64-bit. Using a 64-bit OS in
combination with an x64 version of SQL Server is highly recommended for dedicated
SQL servers that have more than 4GB of physical memory to take advantage of
the memory addressing capabilities of 64-bit hardware. For additional information,
please refer to the following article:
Microsoft SQL Server Collations

Microsoft SQL Server Collations
Table 2-7
Microsoft SQL Server SMP 6.x
Collations

MP1.1
SMP 7.5 SP1 SMP 7.6
Latin1_General_BIN
Supported
Supported
Supported
Supported
Supported
Supported
Latin1_General_BIN2
Supported
Supported
Supported
Supported
Supported
Supported
Latin1_General_CI_AI
Supported
Supported
Supported
Supported
Supported
Supported
Latin1_General_CI_AS
Supported
Supported
Supported
Supported
Supported
Supported
Latin1_General_CS_AI
Supported
Supported
Supported
Supported
Supported
Supported
Latin1_General_CS_AS
Supported
Supported
Supported
Supported
Supported
Supported
Latin1_General_CP1_CI_AS Supported
Supported
Supported
Supported
Supported
Supported
Microsoft IIS
Table 2-8
Microsoft IIS
IIS Version
SMP 6.x

MP1.1
Microsoft IIS 6
Supported
Supported
Not supported Not supported Not supported Not supported
Microsoft IIS 7.5

(IIS 6 compatibility)
Microsoft IIS 7.5
Native
SMP 7.5 SP1 SMP 7.6
Supported
Supported
Supported
Not supported Not supported Not supported Not supported Not supported Not supported
38

Microsoft IIS (continued)
Table 2-8
IIS Version
SMP 6.x

MP1.1
SMP 7.5 SP1 SMP 7.6
Microsoft IIS 8.5

Native (IIS 6
compatibilty)
Supported
Microsoft .NET
Microsoft .NET
Table 2-9
.NET Version
SMP 6.x

MP1.1
Microsoft .NET
Framework 1.1
Supported
Not supported Not supported Not supported Not supported Not supported
Microsoft .NET
Framework 3.5
Microsoft .NET
Framework 3.5
SP1
Supported
Microsoft .NET
Framework 4.0
Microsoft .NET
Framework 4.5.1
Supported
SMP 7.5 SP1 SMP 7.6
Supported
Not supported
Console/Browser
Table 2-10
Browser Version SMP 6.x
Console/Browser

MP1.1
SMP 7.5 SP1 SMP 7.6
Microsoft Internet Explorer

Microsoft Internet
Explorer 6 SP1
Supported
Microsoft Internet
Explorer 7
Supported
Supported
Supported
Supported
Supported
Supported
39

Table 2-10
Browser Version SMP 6.x
Console/Browser (continued)

MP1.1
SMP 7.5 SP1 SMP 7.6
Microsoft Internet
Explorer 8 1
Supported
Supported
Supported
Supported
Microsoft Internet
Explorer 91
Supported
Supported
Supported
Microsoft Internet
Explorer 101
Not supported Not supported Not supported Limited

support
Supported
Supported
Microsoft Internet
Explorer 111
Supported
Note: Current referenced browser support is for the 32-bit version of Internet
Explorer.
1
Browser will automatically switch to compatibility mode when required.
Workflow Designer
The Workflow Designer and Tools are the client tools used to design, publish, and
debug processes. The following matrix defines the Microsoft platforms that the
Designer and Tools are supported on.
Table 2-11
Microsoft
Windows
operating
systems
Designer and Tools
Workflow
Workflow
Workflow
Workflow
Workflow
Workflow
Designer 6.x Designer 7.0 Designer 7.1 Designer 7.5 Designer 7.5 Designer 7.6
SP5
SP2 MP1.1
SP1
Windows XP
Windows XP SP2
x86/x64
Supported
Supported
Supported
End of life
End of life
End of life
Windows XP SP3
x86/x64
Supported
Supported
Supported
Supported
Supported
End of life
Supported
Supported
Windows Vista
Windows Vista
x86/x64
40

Table 2-11
Designer and Tools (continued)
Microsoft
Windows
operating
systems
Workflow
Workflow
Workflow
Workflow
Workflow
Workflow
SP5
SP2 MP1.1
SP1
Windows Vista
SP1 x86/x64
Supported
Supported
Supported
End of life
End of life
End of life
Windows Vista
SP2 x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Windows 7
x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Windows 7 SP1
x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Windows 8
x86/x64
Supported
Windows 8.1
x86/x64
Supported
Windows 8.1
Update 1 x86/x64

(from SMP
7.5 SP1 HF2
onwards)
Supported
Windows 8.1
Update 2 x86/x64
Windows 7
Windows 8
Windows Server 2003

Windows Server
2003 R2 x86/x64
Supported
Supported
Windows Server
2003 R2 SP2
x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows Server 2008

Windows Server
Supported
2008 SP2 x86/x64
Supported
41

Table 2-11
Designer and Tools (continued)
Microsoft
Windows
operating
systems
Workflow
Workflow
Workflow
Workflow
Workflow
Workflow
SP5
SP2 MP1.1
SP1
Windows Server
2008 x86/x64
Supported
Supported
Supported
Supported
Supported
Windows Server
2008 R2 SP1
Supported
Supported
Supported
Windows Server
2008 R2 SP21
Supported
Windows Server 2012

Windows Server
2012
Supported
Windows Server
2012 R2
Supported
Microsoft has not yet announced a release date for Windows Server 2008 R2
SP2, so no support has been added for these versions.
Site server
Any server that has either the Package Service or the Task Service installed on it
is called a "Site Server. The site server support matrix below indicates full support
for Package and Task Services on the specified platform unless otherwise indicated.
These services will also run on any supported Notification Server OS platform.
Table 2-12
Site server
operating
systems
Site server OS support matrix
SMP 6.x

MP1.1
SMP 7.5 SP1 SMP 7.6
Windows Server
2000 SP4
Supported
Windows 2000
Professional SP4
Supported
Windows 2000
Windows XP
42

Table 2-12
Site server OS support matrix (continued)
Site server
operating
systems
SMP 6.x

MP1.1
SMP 7.5 SP1 SMP 7.6
Windows XP SP2
x86/x641
Supported
Supported
Supported
Supported x64
Supported x64
Support for
package
server only
Windows XP SP3
x86/x641
Supported
Supported
Supported
Supported
Supported
Support for
package
server only
Windows Vista
Windows Vista
x86/x6411
Not supported Support for

package
server only
Windows Vista
SP1 x86/x641

package
server only
Support for
package
server only
End of life
End of life
End of life
Windows Vista
SP2 x86/x641
R13
Supported
Supported
Supported
Supported
Supported
Windows 7
x86/x641
R13
Supported
Supported
Supported
Supported
Supported
Windows 7 SP1
x86/x641
R13
Supported
Supported
Supported
Windows 8
Supported
Windows 8.1
Supported
Windows 8.1
Update 1

(from SMP
7.5 SP1 HF2
onwards)
Supported
Windows 8.1
Update 2
Windows 7
Windows 8
Windows Server 2003
43

Table 2-12
Site server
operating
systems
SMP 6.x

MP1.1
SMP 7.5 SP1 SMP 7.6
Windows Server
2003 SP2 x86
R5
Supported
Supported
Supported4
Supported4
Support for
package
server only
Windows Server
2003 SP2 x641
R9
Supported
Supported
Supported4
Supported4
Support for
package
server only
Windows Server
2003 R2 x86/x641
Supported
Supported
Not supported Not

supported4
Not
supported4
Support for
package
server only
Windows Server
2003 R2 SP2
x86/x641
Supported
Supported4
Supported4
Support for
package
server only
Supported
Supported
Supported
Supported
Supported
Windows Server
R13
2008 SP2 x86/x641
Supported
Supported
Supported
Supported
Supported
Windows Server
2008 R2
R13
Supported
Supported
Supported
Supported
Supported
Windows Server
2008 R2 Core
Windows Server
2008 R2 SP1
R13
Windows Server 2008

Windows Server
2008 x86/x641
R8
Supported
Supported
Supported
Windows Server
2012
Supported
Windows Server
2012 R2
Supported
Windows Server 2012
Red Hat Enterprise Linux 4
44

Table 2-12
Site server
operating
systems
SMP 6.x

MP1.1
SMP 7.5 SP1 SMP 7.6
Red Hat Enterprise Support for

Linux 4 WS
package
x86/x64
server only2

package
server only2
End of life
Not supported Not supported

Linux 4 ES x86/x64 package
server only2

package
server only2
End of life
Not supported Not supported

Linux 4 AS x86/x64 package
server only2

package
server only2
End of life
End of life
End of life
Red Hat Enterprise Not supported Not supported Support for

Linux 5.1 Server
package
x86/x64
server only
Support for
package
server only
Support for
package
server only
Not supported

Linux 5.2 Server
package
x86/x64
server only
Support for
package
server only
Support for
package
server only
Not supported

Linux 5.3 Server
package
x86/x64
server only
Support for
package
server only
Support for
package
server only
Not supported

Linux 5.4 Server
package
x86/x64
server only
Support for
package
server only
Support for
package
server only
Not supported

Linux 5.5 Server
package
x86/x64
server only
Support for
package
server only
Support for
package
server only
Not supported

Linux 5.6 Server
package
x86/x64
server only
Support for
package
server only
Support for
package
server only
Not supported
Red Hat Enterprise Not supported Not supported Not supported Support for
Linux 5.7 Server
package
x86/x64
server only
Support for
package
server only
Not supported
45

Table 2-12
Site server
operating
systems
SMP 6.x

MP1.1
SMP 7.5 SP1 SMP 7.6
Linux 5.8 Server
package
x86/x64
server only
Support for
package
server only
Not supported
Linux 5.9 Server
package
x86/x64
server only
Support for
package
server only
Not supported
Linux 5.10 Server
package
x86/x64
server only
Support for
package
server only
Support for
package
server only
Red Hat Enterprise Not supported Not supported Not supported Not supported Limited
Linux 5.11 Server
support for
x86/x64
package
server only
(from SMP
7.5 SP1 HF5
onwards))
Limited
support for
package
server only

Red Hat Enterprise Not supported Not supported Supported
Linux 6.0 x86/x64
Support for
package
server only
Support for
package
server only
Support for
package
server only

Linux Server 6.0
x86/x64
Support for
package
server only
Support for
package
server only
Support for
package
server only

Linux 6.1 Server
x86/x64
Support for
package
server only
Support for
package
server only
Support for
package
server only
Linux 6.2 Server
package
x86/x64
server only
Support for
package
server only
Support for
package
server only
Linux 6.3 Server
package
x86/x64
server only
Support for
package
server only
Support for
package
server only
46

Table 2-12
Site server
operating
systems
SMP 6.x

MP1.1
Linux 6.4 Server
package
x86/x64
server only
SMP 7.5 SP1 SMP 7.6
Support for
package
server only
Support for
package
server only
Red Hat Enterprise Not supported Not supported Not supported Not supported Supported for Support for
Linux 6.5 Server
package
package
x86/x64
server only
server only
(from SMP
7.5 SP1 HF2
onwards)
Red Hat Enterprise Not supported Not supported Not supported Not supported Limited
Linux 6.6 Server
support for
x86/x64
package
server only
(from SMP
7.5 SP1 HF5
onwards)5
Limited
support for
package
server only

Red Hat Enterprise Not supported Not supported Not supported Not supported Not supported Support for
Linux 7 Server
package
x86/x64
server only
Novell SUSE Enterprise Server
Novell SUSE Linux Support for
Enterprise Server package
9 x86/x64
server only
Novell SUSE Linux Support for

Enterprise Server package
10 x86/x64
server only

package
server only
Support for
package
server only
Support for
package
server only
Support for
package
server only
Novell SUSE Linux Not supported Not supported Support for

Enterprise Server
package
11 x86/x64
server only
Support for
package
server only
Support for
package
server only
Support for
package
server only
Novell SUSE Linux Not supported Not supported Not supported Support for
Enterprise Server
package
11 SP1 x86/x64
server only
Support for
package
server only
Support for
package
server only
47

Table 2-12
Site server
operating
systems
SMP 6.x

MP1.1
Novell SUSE Linux Not supported Not supported Not supported Support for
Enterprise Server
package
11 SP2 x86/x64
server only
SMP 7.5 SP1 SMP 7.6
Support for
package
server only
Support for
package
server only
Novell SUSE Linux Not supported Not supported Not supported Not supported Supported for Support for
Enterprise Server
package
package
11 SP3 x86/x64
server only
server only
(from SMP
7.5 SP1 HF2
onwards)
Novell SUSE Linux Not supported Not supported Not supported Not supported Limited
Enterprise Server
support for
12 x86/x64
package
server only
(from SMP
7.5 SP1 HF5
onwards)6
Not supported
Sun Solaris
Sun Solaris 7
SPARC
Support for
package
server only
Sun Solaris 8
SPARC
Support for
package
server only
Sun Solaris 9
SPARC
Support for
package
server only
Sun Solaris 10
x86/x64/SPARC
Support for
package
server only
Sun Solaris 11
x86/x64/SPARC
Support for
package
server only
IBM AIX
48

Table 2-12
Site server
operating
systems
SMP 6.x

MP1.1
SMP 7.5 SP1 SMP 7.6
IBM AIX 5.1 PPC
Support for
package
server only
IBM AIX 5.2 PPC
Support for
package
server only
IBM AIX 5.3 PPC
Support for
package
server only
Hewlett-Packard HP-UX
Hewlett-Packard
HP-UX 11
PA-RISC/IA-64
Support for
package
server only
Hewlett-Packard
HP-UX 11i
PA-RISC/IA-64
Support for
package
server only
It should be noted that core 6.x agents running on x64 platforms currently only
support running in WOW64 (32-bit emulation mode). This limits the core agent to
seeing only those files and registry entries in the 32-bit environment. Starting with
Notification Server 7.1, the Symantec Management Agent adds native 64-bit support.
2
The Package Service supports Red Hat Enterprise Linux 4 WS x86/x64, and
Novell SUSE Linux Enterprise Desktop version 10 and 11 when Apache web server
has been installed. Apache web server is not installed by default on these operating
systems.
4 Windows Server 2003 is supported for Network Boot Services, that is, Deployment
Solution PXE server. However, imaging is limited to saving or deploying the image
using UNC. HTTP imaging requires IIS 7, which is not supported by Windows Server
2003.
5
You can see the RHEL 6.6 Early Support Statement at

6
You can see the Novell SUSE Linux Enterprise Server 12 x86/x64 Early Support
Statement at http://www.symantec.com/docs/DOC8122
49

Cloud-enabled Management
Cloud-enabled Management (CEM) that is introduced in the IT Management Suite
7.5 lets you manage client computers over the Internet using an Internet gateway
that is located in the demilitarized zone (DMZ). CEM is supported on Microsoft
Windows computers and Mac OS X computers. CEM lets you manage the client
computers even if the client computers are outside of the corporate environment
and cannot access the management servers directly. The CEM managed client
computers do not need to use a VPN connection to your organization's network.
The following table contains information about operating system (OS) support for
the Internet gateway server:
Table 2-13
operating
systems
Internet gateway

MP1.1
SMP 7.5 SP1 SMP 7.6
Windows Server
2008 R2 SP1 x64
Supported
Supported
Windows Server
2008 R2 SP2 x64
Windows Server
2012 R2 x64
Microsoft has not yet announced a release date for Windows Server 2008 R2
SP2, so no support has been added for SMP 7.5 SP1.
Note: Internet gateway requires .NET 4.5 SP1 as well as 64-bit OS platform.
Client Management Suite

The following section includes operating system support for the solutions used in
Client Management Suite (CMS).
The Client Management Suite includes full support for the following solutions unless
otherwise indicated:
Deployment Solution6
Inventory Solution
Inventory for Network Devices
50

Network Discovery
Patch Management Solution,
Real-Time System Manager
Software Management Solution
51
Client OS Support Matrix

Table 2-14
Agent on
Client
operating
systems
6.x
7.0 SP5
Supported
Windows XP
Professional
SP2 x86
Client OS Support Matrix

7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Not
Not
Supported3 supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
Supported
Supported
End of life
End of life
End of life
End of life
End of life
Windows XP
Professional
SP2 x641
R9
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows XP
Professional
SP3 x86
R8
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support 2
Limited
support 2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Windows 2000
Windows
2000
Professional
SP4
Windows XP
Windows XP R8
Tablet PC
Edition 20052
Windows XP Embedded
Windows XP
Embedded
SP3
Not
supported

Table 2-14
52
Client OS Support Matrix (continued)
Agent on
Client
operating
systems
6.x
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Windows
Embedded
Standard
Not
supported
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Windows
Embedded
Point of
Service 1.0
Not
supported
Limited
support2
Limited
support2
End of life
End of life
End of life
End of life
End of life
Windows
Embedded
Point of
Service 1.1
SP3
Not
supported
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Windows
Embedded
POSReady
2009
Not
supported
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Limited
support2
Windows
Vista
x86/x641
Supported
Supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Windows
Vista SP1
x86/x641
R8
Supported
Supported
End of life
End of life
End of life
End of life
End of life
Windows
Vista SP2
x86/x641
R10
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows 7
x86/x641
R13
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows 7
x86/x64 SP1
R13
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows Vista
Windows 7

Table 2-14
53
Agent on
Client
operating
systems
6.x
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Windows 7
XP Mode
Not
supported
Not
supported
Limited
support
Limited
support
Limited
support
Limited
support
Limited
support
Limited
support
Windows Embedded 7 2
Windows
Embedded
Standard 7
x86/x64
Not
supported
Not
supported
Not
supported
Not
Not
Not
Not
Not
supported 2 supported 2 supported 2 supported 2 supported 2
Windows
Embedded
Standard 7
x86/x64 SP1
Not
supported
Not
supported
Not
supported
Not
Not
Supported16 Supported16 Supported16
,2
,2
supported 2 supported 2 , 2
Windows
Not
Embedded
supported
POSReady 7
Not
supported
Not
supported
Not
Not
Not
Not
Not
supported 2 supported 2 supported 2 supported 2 supported 2
Windows 8
Windows 8
Not
supported
Not
supported
Limited
support 12
Supported15 Supported15 Supported15 Supported15 Supported15
Windows 8.1
Not
supported
Not
supported
Not
supported
Limited
support 15
Supported15 Supported15 Supported15 Supported15
Windows 8.1
Update 1
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported Supported15
(from 7.5
SP1 HF2
onwards)15,
18
Windows 8.1
Update 2
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported Supported15
(from 7.5
SP1 HF5
onwards)15,
21
Apple Mac OS X5

Table 2-14
54
Agent on
Client
operating
systems
6.x
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Apple Mac
OS X (10.2)
PPC
Limited
support14
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Apple Mac
OS X (10.3)
PPC
Limited
support14
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Apple Mac
OS X (10.4)
Universal
Limited
support14
Limited
support14
Limited
support14
End of life
End of life
End of life
End of life
End of life
Apple Mac
OS X (10.5)
Universal
Limited
support14
Limited
support14
Limited
support14
End of life
End of life
End of life
End of life
End of life
Apple Mac
OS X (10.6)
Limited
Limited
support8, 14 support14
Limited
support14
Limited
support
Limited
support
Limited
support
Limited
support
End of life
Apple Mac
OS X (10.7)
Not
supported
Not
supported
Limited
Limited
support 7, 14 support
Limited
support
Limited
support
Limited
support
End of life
Apple OS X
(10.8)9
Not
supported
Not
supported
Limited
support 14
Limited
support
Limited
support
Limited
support
Limited
support
Limited
support 14
Apple OS X
(10.9)
Not
supported
Not
supported
Not
supported
Not
supported
Limited
support 14
Limited
support 14
Limited
support 14
Limited
support 14
Apple OS X
(10.10)
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Limited
support 14
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported

Red Hat
Enterprise
Linux 3 WS
x86/x64
Limited
support 4

Table 2-14
55
Agent on
Client
operating
systems
6.x
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Red Hat
Enterprise
Linux 4 WS
x86/x64
Limited
support4
Limited
support4
Limited
support4
End of life
End of life
End of life
End of life
End of life

Red Hat
Enterprise
Linux 5
x86/x64
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Not
supported
Red Hat
Enterprise
Linux 5.1
x86/x64
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Not
supported
Red Hat
Enterprise
Linux 5.2
x86/x64
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Not
supported
Red Hat
Enterprise
Linux 5.3
x86/x64
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Not
supported
Red Hat
Enterprise
Linux 5.4
x86/x64
Not
supported
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Not
supported
Red Hat
Enterprise
Linux 5.5
x86/x64
Not
supported
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Not
supported
Red Hat
Enterprise
Linux 5.6
x86/x64
Not
supported
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Not
supported

Table 2-14
56
Agent on
Client
operating
systems
6.x
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Red Hat
Enterprise
Linux 5.7
x86/x64
Not
supported
Not
supported
Not
supported
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Not
supported
Red Hat
Enterprise
Linux 5.8
x86/x64
Not
supported
Not
supported
Not
supported
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Not
supported
Red Hat
Enterprise
Linux 5.9
x86/x64
Not
supported
Not
supported
Not
supported
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Not
supported
Red Hat
Enterprise
Linux 5.10
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
17,4
Supported
17,4
Supported
17,4
Red Hat
Enterprise
Linux 5.11
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
17,4
Not
supported

Red Hat
Enterprise
Linux 6.0
x86/x64
Not
supported
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Red Hat
Enterprise
Linux 6.1
x86/x64
Not
supported
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Red Hat
Enterprise
Linux 6.2
x86/x64
Not
supported
Not
supported
Not
supported
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4

Table 2-14
57
Agent on
Client
operating
systems
6.x
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Red Hat
Enterprise
Linux 6.3
x86/x64
Not
supported
Not
supported
Not
supported
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Red Hat
Enterprise
Linux 6.4
x86/x64
Not
supported
Not
supported
Not
supported
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Red Hat
Enterprise
Linux 6.5
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Limited
Limited
Support
Support
19
(from 7.5
SP1 HF2
onwards) 4,
4,
19
Red Hat
Enterprise
Linux 6.6
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Limited
support
(from 7.5
SP1 HF5
onwards) 4
Not
supported
Novell SUSE Linux Enterprise Desktop4

Novell SUSE Limited
Linux
support4
Enterprise
Desktop 10
x86/x64
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Novell SUSE Not

Linux
supported
Enterprise
Desktop 11
x86/x64
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Novell SUSE Not

Linux
supported
Enterprise
Desktop 11
SP1 x86/x64
Not
supported
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4

Table 2-14
Agent on
Client
operating
systems
6.x
58
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Novell SUSE Not

Linux
supported
Enterprise
Desktop 11
SP2 x86/x64
Not
supported
Not
supported
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Limited
support 4
Novell SUSE Not

Linux
supported
Enterprise
Desktop 11
SP3 x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
(from 7.5
SP1 HF2
onwards)4,
Supported
Novell SUSE Not

Linux
supported
Enterprise
Desktop 12
x86/x64
Not
supported
4, 20
20
Not
supported
Not
supported
Not
supported
Not
supported
Limited
support
(from 7.5
SP1 HF5
onwards)
Not
supported
1 Note that core 6.x agents running on Windows x64 platforms currently only support
running in WOW64 (32-bit emulation mode). This limits the core agent to seeing
only those files and registry entries in the 32-bit environment. Starting with
Notification Server 7.1, the Symantec Management Agent adds native 64-bit support.
2
Windows Embedded capabilities are limited.
For Windows 7 Embedded (CMS 7.1 or later), see the following article:
http://www.symantec.com/docs/TECH190554
For Windows XP Embedded (CMS 7.0 or later), see the following article:
3
Microsoft ended support for Windows 2000 on July 13, 2010, hence support for
Windows 2000 agents has been removed in the 7.0 SP5 release. Base agent
functionality using a 7.0 SP4 agent in a 7.0 environment provides limited functionality
for the agent computers as they are upgraded.
4
The Linux agent does not support PC Transplant, Application Management,

Software Virtualization Client Functionality, the WiseScript scripting tool, Software
Portal, Application Metering, or the ability to evaluate software detection rules that
are not .rpm packages.

The Mac OS X agent does not support PC Transplant, Application Management,

Software Virtualization Client Functionality, the WiseScript scripting tool, or
Application Metering.
6 For additional support information for Deployment 6.9, please refer to the following
article:
7
In 7.1 SP1, Mac OS X 10.7 is only available through a special point fix. posted
on September 19, 2011. Please see the following article:
8
In NS 6.x, Mac OS X 10.6 support is limited to the Symantec Management Agent

and basic inventory; none of the solutions support it. Basic inventory and Symantec
Management Agent support is available through a special point-fix. Please see the
following article:
9
Apple has ceased referring to its OS as Mac OS X and now only uses OS X
as the name of the operating system
10
Software detection rules support for OS X is added in 7.5.
12
Microsoft Windows 8 support has known limitations listed in this article:
14
This version of the OS X agent does not support detection rules.
15pcAnywhere
Solution is not supported on all versions of Microsoft Windows 8

operating system. Please refer to the following articles:
16Symantec
Endpoint Protection Integration Component (SEPIC), pcAnywhere

solution, and Deployment Solution are not supported for Windows Embedded
Standard 7 SP1 client computers. Please refer to following article:
17Symantec

solution are not supported for Red Hat Enterprise Linux 5.10 client computers.
Please refer to the following article:
18
For additional support information for Windows 8.1 Update 1, please refer to the
following article:
59

19
For additional support information for RHEL 6.5, please refer to the following
article:
20
For additional support information for SLES 11 SP3, please refer to the following
article:
21
For additional support information for Windows 8.1 Update 2, please refer to the
following article:
Server Management Suite

The following section includes operating system (OS) support for the solutions used
with Server Management Suite (SMS).
The Server Management Suite includes full support for the following solutions unless
otherwise indicated:
Deployment Solution10
Inventory for Network Devices
Inventory Solution
Network Discovery
Patch Management Solution
Real-Time System Manager
Monitor Solution for Servers
Virtual Machine Management
60

61
Server OS Support Matrix

Table 2-15
Agent on
Server
operating
systems
6.x
7.0 SP5
Server OS Support Matrix

7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Not
Not
supported2 supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Windows Server 2000

Windows
Server 2000
SP4
Supported
Windows Server 2003

Windows
Server 2003
SP2 x86
R5
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2003
SP2 x641
R9
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2003
R2 x86/x641
Supported
Supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Windows
Server 2003
R2 SP2
x86/x641
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Not
Small
supported
Business
Server (SBS)
2003 R2
x86/x641
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows Server 2008

Windows
Server 2008
x86/x641
R8

Table 2-15
Agent on
Server
operating
systems
6.x
62
Server OS Support Matrix (continued)
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Windows
R13
Server 2008
SP2 x86/x641
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
Core
x86/x641
R13
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
R2
R13
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
R2 Core3
R13
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
R2 SP1
R13
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
R2 SP2
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
Supported
Supported
Windows Server 2012

Windows
Server 2012
Not
supported
Not
supported
Not
supported
Limited
support
Supported
Windows
Server 2012
R2
Not
supported
Not
supported
Not
supported
Not
supported
Windows
Hyper-V
Server 2008
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported

Table 2-15
Agent on
Server
operating
systems
6.x
Windows
Not
Small
supported
Business
Server (SBS)
2008
63
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Apple Mac OS X Server

Apple Mac
OS X Server
(10.2) PPC
Limited
support4
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Apple Mac
OS X Server
(10.3) PPC
Limited
support4
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Apple Mac
OS X Server
(10.4)
Universal
Limited
support4
Limited
support4
Limited
support4
End of life
End of life
End of life
End of life
End of life
Apple Mac
OS X Server
(10.5)
Universal
Limited
support4
Limited
support4
Limited
support4
End of life
End of life
End of life
End of life
End of life
Apple Mac
OS X Server
(10.6)
Limited
support12
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
End of life
Apple Mac
OS X Server
(10.7)
Not
supported
Not
supported
Limited
support11
Limited
support4
Limited
support4
Limited
support4
Limited
support4
End of life
Apple OS X
Server
(10.8)15
Not
supported
Not
supported
Limited
support4
Limited
support4,14
Limited
support4,14
Limited
support4,14
Limited
support4,14
Limited
support4,14
Apple OS X
Not
Server (10.9) supported
Not
supported
Not
supported
Not
supported
Supported
Supported
Supported
Supported

Table 2-15
64
Agent on
Server
operating
systems
6.x
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Apple OS X
Server
(10.10)
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported

Red Hat
Enterprise
Linux 3 ES
x86/x64
Limited
support5
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Enterprise
Linux 3 AS
x86/x64
Limited
support5
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported

Red Hat
Enterprise
Linux 4 ES
x86/x64
Limited
support5
Limited
support5
Limited
support5
End of life
End of life
End of life
End of life
End of life
Red Hat
Enterprise
Linux 4 AS
x86/x64
Limited
support5
Limited
support5
Limited
support5
End of life
End of life
End of life
End of life
End of life

Red Hat
Enterprise
Linux 5
Server
x86/x64
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported
Red Hat
Enterprise
Linux 5.1
Server
x86/x64
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported

Table 2-15
65
Agent on
Server
operating
systems
6.x
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Red Hat
Enterprise
Linux 5.2
Server
x86/x64
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported
Red Hat
Enterprise
Linux 5.3
Server
x86/x64
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported
Red Hat
Enterprise
Linux 5.4
Server
x86/x64
Not
supported
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported
Red Hat
Enterprise
Linux 5.5
Server
x86/x64
Not
supported
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported
Red Hat
Enterprise
Linux 5.6
Server
x86/x64
Not
supported
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported
Red Hat
Enterprise
Linux 5.7
Server
x86/x64
Not
supported
Not
supported
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported
Red Hat
Enterprise
Linux 5.8
Server
x86/x64
Not
supported
Not
supported
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported

Table 2-15
66
Agent on
Server
operating
systems
6.x
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Red Hat
Enterprise
Linux 5.9
Server
x86/x64
Not
supported
Not
supported
Not
supported
Limited
Limited
Limited
Limited
Not
support5, 17 support5, 17 support5, 17 support5, 17 supported
Red Hat
Enterprise
Linux 5.10
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
Supported
20
20
Red Hat
Enterprise
Linux 5.11
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
20
Not
supported
Red Hat
Enterprise
Linux 6
Server
x86/x64
Not
supported
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported
Red Hat
Enterprise
Linux 6.1
Server
x86/x64
Not
supported
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported
Red Hat
Enterprise
Linux 6.2
Server
x86/x64
Not
supported
Not
supported
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported
Red Hat
Enterprise
Linux 6.3
Server
x86/x64
Not
supported
Not
supported
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not
supported
Supported
Not supported

Table 2-15
67
Agent on
Server
operating
systems
6.x
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Red Hat
Enterprise
Linux 6.4
Server
x86/x64
Not
supported
Not
supported
Not
supported
Limited
Limited
Limited
Limited
Not
support5, 17 support5, 17 support5, 17 support5, 17 supported
Red Hat
Enterprise
Linux 6.5
Server
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Enterprise
Linux 6.6
Server
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Novell SUSE Limited

Linux
support5
Enterprise
Server 8 x86
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Novell SUSE Limited

Linux
support5
Enterprise
Server 9
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Novell SUSE Limited

Linux
support5
Enterprise
Server 10
x86/x64
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Novell SUSE Not

Linux
supported
Enterprise
Server 11
x86/x64
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Not supported

Table 2-15
Agent on
Server
operating
systems
6.x
68
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Novell SUSE Not

Linux
supported
Enterprise
Server 11
SP2 x86/x64
Not
supported
Not
supported
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Limited
support5
Novell SUSE Not

Linux
supported
Enterprise
Server 12
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
VMware vSphere / ESX / ESXi

VMware ESX Limited
/ ESXi 3.0.1 support6
Limited
support6
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
VMware ESX Limited

Limited
support6
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
VMware ESX Limited

Limited
support6
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
VMware ESX Limited

/ ESXi 3.5
support6
Limited
support6
Limited
support6
Not
Not
Not
Not
Not
supported6 supported6 supported6 supported6 supported6
VMware
vSphere /
ESX / ESXi
4.0
(Agentless)
Not
supported
Not
supported
Limited
support8
Limited
support8
Limited
support8
Limited
support8
Limited
support8
Limited
support8
VMware
vSphere /
ESX / ESXi
4.1
(Agentless)
Not
supported
Not
supported
Limited
support8
Limited
support8
Limited
support8
Limited
support8
Limited
support8
Limited
support8

Table 2-15
69
Agent on
Server
operating
systems
6.x
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
VMware
vSphere /
ESX / ESXi
5.0
(Agentless)
Not
supported
Not
supported
Limited
support8
Limited
support8
Limited
support8
Limited
support8
Limited
support8
Limited
support8
VMware
vSphere /
ESX / ESXi
5.1
(Agentless)
Not
supported
Not
supported
Limited
support8
Limited
support8
Limited
support8
Limited
support8
Limited
support8
Limited
support8
VMware ESXi Not

5.5(Agentless) supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported8, Supported8, Supported8,

19
19
19
Sun Solaris 7 Limited

SPARC
support7
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported

SPARC
support7
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported

SPARC
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Sun Solaris
10 x86/x64
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Sun Solaris
10 SPARC
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Sun Solaris
11 x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
Sun Solaris
11 SPARC
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
Sun Solaris
Zones
Not
supported
Not
supported
Limited
support7,13
Limited
Limited
Limited
Limited
Limited
support7, 13 support7, 13 support7, 13 support7, 13 support7, 13
Sun Solaris
Hewlett-Packard HP-UX

Table 2-15
Agent on
Server
operating
systems
6.x
70
7.0 SP5
7.1 SP2
MP1.1
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Hewlett-Packard Limited
HP-UX 11.11 support7
(11i)
PA-RISC9
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Not
supported
Hewlett-Packard Limited
HP-UX 11.23 support7
(11i v2)
PA-RISC/IA-649
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Not
supported
Hewlett-Packard Not
HP-UX 11.31 supported
(11i v3)
PA-RISC/IA-649
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
IBM AIX 4.3.3 Limited

support7
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
IBM AIX 5.1

PPC
Limited
support7
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
IBM AIX 5.2

PPC
Limited
support7
Limited
support7
Limited
support7
End of life
End of life
End of life
End of life
End of life
IBM AIX 5.3

PPC
Limited
support7
Limited
support7
Limited
support7
End of life
End of life
End of life
End of life
End of life
IBM AIX 6.1

PPC
Not
supported
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
IBM AIX 7.1

Standard
Not
supported
Not
supported
Not
supported
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
IBM LPAR-s
Not
supported
Not
supported
Limited
support7,13
Limited
support7
Limited
support7
Limited
support7
Limited
support7
Limited
support7
IBM AIX
1 It should be noted that core 6.x agents running on Windows x64 platforms currently
only support running in WOW64 (32-bit emulation mode). This limits the core agent
to seeing only those files and registry entries in the 32-bit environment. Starting

with Notification Server 7.1, the Symantec Management Agent adds native 64-bit
support.
2
Microsoft ended support for Windows 2000 on July 13, 2010, hence support for
Windows 2000 agents has been removed in the 7.0 SP5 release. Base agent
functionality using a 7.0 SP4 agent in a 7.0 environment will provide limited
functionality for the agent computers as they are upgraded.
3
Monitor Packs for Servers support only agentless monitoring of Windows Server
2008 R2 Core Edition servers.
4 The Mac OS X agent does not support PC Transplant, Monitor Solution, Application
Management, Software Virtualization Client Functionality, the WiseScript scripting

tool, or Application Metering.
5
The Linux agent does not support PC Transplant, Application Management,

Software Virtualization Client Functionality, Software Portal, the WiseScript scripting
tool, or Application Metering.
6
VMware ESX and ESXi 3.x supports Inventory for Network Devices, Network
discovery at a hardware level, and Monitor Solution only.
7
The UNIX agent does not support PC Transplant, Application Management,

Software Virtualization Client Functionality, Software Portal, the WiseScript scripting
tool, Application Metering, or Patch Management.
8
VMware ESX and ESXi 4 supports Inventory for Network Devices, and Network
Discovery only. Starting with the Symantec Management Platform 7.1, ESX and
ESXi 4.x servers will be managed as agentless.
9 IA-64 support on NS 6.x is provided by running PA-RISC binaries under the HP-UX
Aries translation engine which is included as a core component of HP-UX. IA-64

support with the 7.x version is provided natively.
10 For additional support information for Deployment 6.9, please refer to the following
article:
11
In 7.1 SP1, Mac OS X 10.7 is only available through a special point fix posted
on September 19, 2011. Please refer to the following
article:http://www.symantec.com/docs/HOWTO58968
12
In NS 6.x Mac OS X 10.6 support is limited to Altiris Agent and basic inventory,
while none of the solutions support it. Basic inventory and AA support is available
through a special point-fix. Please refer to the following article:
71

72
13
Only basic Zones and LPARs support provided. We do not gather any additional
inventory about the environment like guest-host mapping and we do not support
running in child zones.
14
Software detection rules support for OS X is added in 7.5.
15
Starting with version 10.8, Apple no longer refers to their OS as Mac OS X, but
only as OS X.
17
Inventory, Software Management and Patch only.
18pcAnywhere
Solution is not supported on Windows Server 2012 R2 operating

system. Please refer to following article: http://www.symantec.com/docs/DOC6855
19VMware
ESXi 5.5 supports Network Discovery, Deployment Solution, Inventory

Solution, and Virtual Machine Management. Please refer to following article:
20Symantec

solution are not supported for Red Hat Enterprise Linux 5.10 client computers.
Please refer to the following article:
Deployment Solution
This section includes the operating system (OS) support matrix for the Imaging and
the Scripted OS installation (SOI) through the Deployment Solution.
Table 2-16
Imaging
Support
Imaging OS Support Matrix
6.9 SP5
MR3
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Windows XP
Professional
SP2 x86/x64
Not
supported
Supported
Not
supported
End of life
End of life
End of life
End of life
End of life
Windows XP
Professional
SP3 x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Not
Vista x86/x64 supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Windows XP
Windows Vista

Table 2-16
73
Imaging OS Support Matrix (continued)
Imaging
Support
6.9 SP5
MR3
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Windows
Vista SP1
x86/x64
Not
supported
Supported
Not
supported
End of life
End of life
End of life
End of life
End of life
Windows
Vista SP2
x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows 7
x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows 7
SP1 x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows 8
Limited
support5
Limited
support 5
Supported
Supported
Supported
Supported
Supported
Supported
Windows 8.1
Not
supported
Not
supported
Not
supported
Limited
support8
Windows 8.1
Update 1
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
(from 7.5
SP1 HF2
onwards)
Supported
Apple Mac
OS X (10.4)
Universal
Limited
support6
Not
supported
Limited
support6
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Apple Mac
OS X (10.5)
Universal
Limited
support6
Not
supported
Limited
support6
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Apple Mac
OS X (10.6)
Limited
support6
Not
supported
Limited
support6
Supported
Supported
Supported
Supported
Supported
Apple Mac
OS X (10.7)
Not
supported
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Windows 7
Windows 8
Apple OS X

Table 2-16
74
Imaging
Support
6.9 SP5
MR3
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Apple OS X
(10.8)
Not
supported
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Apple OS X
(10.9)
Not
supported
Not
supported
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Apple OS X
(10.10)
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
Windows Server 2003

Windows
Server 2003
SP2 x86
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2003
SP2 x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2003
SP2 x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows Server 2008

Windows
Server 2008
x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
SP2 x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Supported
Server 2008
Core x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
R2
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
R2 Core
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported

Table 2-16
75
Imaging
Support
6.9 SP5
MR3
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Windows
Server 2008
R2 SP1
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
R2 SP2
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
Limited
support5
Supported
Supported
Supported
Supported
Supported
Supported
Not
supported
Not
supported
Windows Server 2012

Windows
Server 2012
Limited
support5
Windows
Server 2012
R2
Not
Not
supported5 supported

Red Hat
Enterprise
Linux 4 ES
x86
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 4 AS
x86
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported

Red Hat
Enterprise
Linux 5
Server x86
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.1
Server x86
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.2
Server x86
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported

Table 2-16
76
Imaging
Support
6.9 SP5
MR3
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Red Hat
Enterprise
Linux 5.3
Server x86
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.4
Server x86
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.5
Server x86
Supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.6
Server x86
Supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.7
Server x86
Supported
Not
supported
Supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Enterprise
Linux 5.8
Server x86
Supported
Not
supported
Supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Enterprise
Linux 5.9
Server x86
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Not
Enterprise
supported
Linux 6.0 x86
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Not
Enterprise
supported
Linux 6.1 x86
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Supported

Table 2-16
Imaging
Support
6.9 SP5
MR3
77
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF5
7.5 SP1
7.6
Red Hat
Not
Enterprise
supported
Linux 6.2 x86
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Not
Enterprise
supported
Linux 6.3 x86
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Not
Enterprise
supported
Linux 6.4 x86
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Enterprise
Linux 6.5
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Limited
support
(from 7.5
SP1 HF2
onwards) 4
Limited
support
Red Hat
Enterprise
Linux 6.6
x86/x64
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Limited
support
Novell SUSE Linux Enterprise Server

Novell SUSE Supported
Linux
Enterprise
Server 9 x86
Not
supported
Supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported

Linux
Enterprise
Server 10 x86
Supported
Supported
Supported
Supported
Supported
Supported
Supported

Linux
Enterprise
Server 11 x86
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Novell SUSE Not

Linux
supported
Enterprise
Server 12 x86
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported

78
Deployment Solution 7 is built on the Symantec Management Platform, which is

a departure from DS 6.9a standalone Windows application.
2
For additional information on Deployment Solution 6.9 (including system

requirements), please refer to the following article:
4
Unless otherwise noted, this applies to Server, Client and Workstation versions
of the OS.
5
Limited support introduced in these versions. See the following links:
http://www.symantec.com/docs/DOC6284 and
6
DS 6.9 requires Mac OS X Server for Mac imaging.
7 pcAnywhere Solution is not supported on Windows 8.1 and Windows Server 2012
R2 operating systems. Please refer to the following article:

Table 2-17
Scripted OS 6.9 SP5
Install
MR3
Support
Scripted OS Install Support Matrix
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF6
7.5 SP1
7.6
Windows XP
Windows XP
Professional
SP2 x86/x64
Supported
Supported
Supported
End of Life
End of Life
End of Life
End of Life
End of Life
Windows XP
Professional
SP3 x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
End of Life
Windows
Supported
Vista x86/x64
Not
supported
Supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Windows
Vista SP1
x86/x64
Supported
Supported
Supported
End of life
End of life
End of life
End of life
End of life
Windows
Vista SP2
x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows Vista

Table 2-17
Scripted OS 6.9 SP5
Install
MR3
Support
79
Scripted OS Install Support Matrix (continued)
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF6
7.5 SP1
7.6
Windows 7
Windows 7
x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows 7
SP1 x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows 8
Not
supported
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Windows 8.1
Not
supported
Not
supported
Not
supported
Limited
support8
Windows 8.1
Update 1
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Apple Mac
OS X (10.6)
Limited
support5
Not
supported
Limited
support5
Apple Mac
OS X (10.7)
Not
supported
Not
supported
Not
supported
Apple OS X
(10.8)
Not
supported
Not
supported
Not
supported
Apple OS X
(10.9)
Not
supported
Not
supported
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Apple OS X
(10.10)
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows 8
Not
supported
Supported
(from 7.5
SP1 HF2
onwards)
Supported
Apple OS X
Windows Server 2003

Windows
Server 2003
SP2 x86
Supported

Table 2-17
80
Scripted OS 6.9 SP5

Install
MR3
Support
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF6
7.5 SP1
7.6
Windows
Server 2003
SP2 x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2003
R2 SP2
x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows Server 2008

Windows
Server 2008
x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
SP2 x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Supported
Server 2008
Core x86/x64
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
R2
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
R2 Core
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
R2 SP1
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Windows
Server 2008
R2 SP2
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Supported
Limited
support2
Supported
Supported
Supported
Supported
Supported
Supported
Windows Server 2012

Windows
Server 2012
Limited
support1

Table 2-17
81
Scripted OS 6.9 SP5

Install
MR3
Support
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
Windows
Server 2012
R2
Not
supported
Not
supported
Not
supported
Not
supported
7.5 HF6
7.5 SP1
7.6

Red Hat
Enterprise
Linux 4 ES
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 4 AS
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported

Red Hat
Enterprise
Linux 5
Server
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.1
Server
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.2
Server
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.3
Server
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.4
Server
Supported
Supported
Supported
Supported
Supported
Supported
Supported
Supported

Table 2-17
82
Scripted OS 6.9 SP5

Install
MR3
Support
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF6
7.5 SP1
7.6
Red Hat
Enterprise
Linux 5.5
Server
Supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.6
Server
Supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 5.7
Server
Supported
Not
supported
Supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Enterprise
Linux 5.8
Server
Supported
Not
supported
Supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Enterprise
Linux 5.9
Server
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Enterprise
Linux 5.10
Server
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported

Red Hat
Enterprise
Linux 6.0
Not
supported
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 6.1
Not
supported
Not
supported
Not
supported
Supported
Supported
Supported
Supported
Supported
Red Hat
Enterprise
Linux 6.2
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported

Table 2-17
83
Scripted OS 6.9 SP5

Install
MR3
Support
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF6
7.5 SP1
7.6
Red Hat
Enterprise
Linux 6.3
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Enterprise
Linux 6.4
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Enterprise
Linux 6.5
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Red Hat
Enterprise
Linux 6.6
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Novell SUSE Linux Enterprise Server

Linux
Enterprise
Server 9
Not
supported
Supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported

Linux
Enterprise
Server 10
Supported
Supported
Supported
Supported
Supported
Supported
Supported

Linux
Enterprise
Server 11
Not
supported
Supported
Supported
Supported
Supported
Supported
Supported
Novell SUSE Not

Linux
supported
Enterprise
Server 12
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
Limited
support4
Not
supported
Not
supported
Not
supported
Not
supported
Not
supported
VMware ESX/ESXi
VMware ESX Limited
3.5
support4

Table 2-17
Scripted OS 6.9 SP5

Install
MR3
Support
7.1 SP2
MP1.1
6.9 SP6
7.5
7.5 HF3
7.5 HF6
7.5 SP1
7.6
VMware
Limited
ESX/ESXi 4.x support4
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
VMware ESXi Not

5.1
supported
Not
supported
Not
supported
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited
support4
Limited support was introduced for DS 6.9 SP5 MR3. See the following KB for
more information:
2
Limited support was introduced for DS 7.1 SP2 MP1.1. See the following KB for
more information:
4
This is limited to provisioning of the VMware host OS only and is not referring to
SOI of the guest OSs.
5
DS 6.9 requires Mac OS X Server for Mac imaging.
In DS 7.5, Scripted OS Installs are referred to as NetInstall.
7pcAnywhere Solution is not supported on Windows 8.1 and Windows Server 2012
R2 operating systems. Please refer to following article:

Deployment Solution 6.8 and 6.9 Platform Support Matrix

The following table lists the platform support matrix for the listed versions of
Deployment Solution:
Table 2-18
Release
Link to the article
6.9 SP6
DOC7340
6.9 SP5
HOWTO48932
6.9 SP4
DOC2079
6.9 SP3
DOC1846
6.9 SP2
HOWTO9454
84

Table 2-18
(continued)
Release
Link to the article
6.9 SP1
HOWTO9454
6.9
HOWTO9454
6.8 SP2
HOWTO4931
6.8 SP1
HOWTO4931
6.8
HOWTO4931
Language Support
The following section contains the Symantec IT Management Suite language support
matrices for the core platform and the management agent.
Core Localization indicates the Console and Help files have been localized in the
referenced languages. It also indicates the supported language for the operating
system where the Notification Server computer installs.
Agent Localization indicates the Agent and Agent Help have been localized in the
referenced languages.

The Symantec Installation Manager lets you install the IT Management Suite
solutions, and the Symantec Management Platform on a computer. The Symantec
Installation Manager manages the entire installation process that includes licensing,
installation, configuration, data migration, and updates.
A fresh installation is when you install the IT Management Suite solutions and
Symantec Management Platform on a computer for the first time, and you do not
have any previous versions of these installations on the computer.
Note: Symantec recommends that you install and test the latest version of IT
Management Suite in a test environment before you install it in a production
environment.
The following end-to-end use case guides you to complete the installation of
Symantec Installation Manager, Symantec Management Platform 7.6, IT
Management Suite 7.6, and the solutions. You must first complete the installation
prerequisites and then install the Symantec Installation Manager on the computer.
After the Symantec Installation Manager is installed, you must then install the latest
85

version of the IT Management Suite from the Symantec Installation Manager by

launching the installation wizard.
After the IT Management Suite 7.6 installation is completed, you can then perform
any of the following tasks:
Perform additional post-installation and configuration tasks.

See About performing post-installation tasks on page 105.
Perform migration of Notification Server 6.x or Notification Server 7.0 to the

latest version of Notification Server.
See About migrating to IT Management Suite 7.6 on page 184.
You must perform the following steps to install the latest version of IT Management
Suite 7.6 on a computer:
Table 2-19
Installing the latest version of IT Management Suite 7.6 on a

computer
Step
Action
Description
Step 1
Meet the installation prerequisites. Ensure that your computer meets the prerequisites to install the
IT Management Suite 7.6 solutions.
See Prerequisites for installing IT Management Suite on page 24.
Step 2
Meet the recommended system

requirements.
When you install IT Management Suite 7.6 solutions, the Symantec

Installation Manager checks for the minimum system requirements.
If the minimum system requirements are not met, the installation
does not proceed.
However, the minimum system requirements may not be sufficient
for your environment. Before you install the IT Management Suite
solutions, you must determine what the recommended system
requirements are for your environment and configure the computer
accordingly. The recommended system requirements primarily
depend on the number of managed endpoints.
See The Symantec IT Management Suite Platform Support Matrix
on page 33.
86

Table 2-19

computer (continued)
Step
Action
Description
Step 3
Download and install the Symantec Download and install the Symantec Installation Manager from
Symantec downloads website.
If you have an Internet connection that is established on the
computer, you can download and install the
SymantecInstallationManagerSetup.exe file from the
www.symantec.com/products/downloads website. After the
download completes, you must install the Symantec Installation
Manager installer file.
You install the Symantec Installation Manager on the computer
where you plan to install the Symantec Management Platform 7.6
and IT Management Suite 7.6 solutions.
For an offline installation, you first install the Symantec Installation
Manager and then use the application to create an installation
package. You then use the installation package to install the IT
Management Suite 7.6 and the solutions on a computer that is not
connected to the Internet.
See Creating and installing an installation package for offline
installation on page 135.
Step 4
Install Symantec Management

Platform 7.6 and IT Management
Suite 7.6 solutions using the
Symantec Installation Manager.
Launch the Symantec Installation Manager and start the installation

wizard to install the IT Management Suite 7.6 solutions. During
the installation process, you perform the following installation tasks:
Configure the initial installation settings.
Check installation readiness.
Configure Notification Server installation settings.
Configure the SQL database installation settings.
Back up Notification Server cryptographic keys for disaster

recovery.
Apply the product licenses during initial installation.
See Installing Symantec Management Platform and IT

Management Suite on page 91.
87

Table 2-19

computer (continued)
Step
Action
Description
Step 5
Launch the Symantec

Management Console.
After the installation is complete, launch the Symantec

Management Console to perform additional post-installation tasks
or migration tasks on the computer.
On the Installation Complete page, select the Launch Symantec
Management Console check box to launch the Symantec
Management Console on the computer. The Internet Information
Services (IIS) Manager redirects the console request to the
appropriate link with https://<IP address>/altiris/. You
can manually launch the Web console either from the Start menu
of the computer. Alternatively, you can manually launch the Web
console if you know the IP address of the Notification Server
computer. For example: https://<IP
address>/altiris/console.
The Welcome page of the Symantec Management Console is
displayed, which contains links to the major first-time setup
configuration steps:
Discover computers.
Roll out the agent.
Gather inventory.
Schedule patch management.
Installing the Symantec Installation Manager

The Symantec Installation Manager lets you install the Symantec Management
Platform and IT Management Suite (ITMS) solutions. The Symantec Installation
Manager manages the entire installation process that includes installation,
configuration, licensing, data migration, and updates.
Except for offline installations, you install Symantec Installation Manager on the
computer where you plan to install the IT Management Suite solutions.
Note: The Symantec Installation Manager is a standalone application whose release
version is separate from the IT Management Suite, which is a suite of solutions.
For example, the Symantec Installation Manager of release version 7.5 SP1 can
be used to install IT Management Suite of release version 7.1 SP2 MP1.
If you migrate from Symantec Management Platform 7.0, use the same installation
path for Symantec Installation Manager that you used for IT Management Suite 7.0
88

installation. For example, if the installation path is C:\Program Files that was
used for ITMS 7.0 installation, then use C:\Program Files for ITMS 7.5 installation.
If the installation path is D:\Program Files for ITMS 7.0 installation, then use
D:\Program Files for ITMS 7.6 installation.
For more information about Symantec Installation Manager, see the Symantec
Installation Manager Getting Started Guide at the following URL:
To install Symantec Installation Manager
Download and run the Symantec Installation Manager installer file.
If Internet connection is established on the server, you can download the

Symantec Installation Manager installer file along with the product suite
from the following IT Management Suite Software Download page:
www.symantec.com/business/products/downloads
In the Search by Product Category pane on the left, click Infrastructure

Operations.
From the list of products that are available for download, click Download
beside the IT Management Suite product entry.
On the Symantec Terms and Conditions page, click I AGREE.
On the Communication Options page, specify your communication

preferences and then click Submit.
On the Software Dowload page, click Download Now to download the

Symantec Installation Manager.
On the About the Download Manager dialog box that is displayed, click
Click to download your file now.
Browse and save the installer file at the required location on the computer.
You can view the download status in the Symantec Download Manager
window.
You can also go to https://fileconnect.symantec.com and then enter the

associated serial number to download the product.
After the Symantec Installation Manager installer file is downloaded, you must
execute the SymantecInstallationManagerSetup.exe file to install the
Symantec Installation Manager on the computer.
89

You can copy and execute the SymantecInstallationManagerSetup.exe file

from an installation package. You can use this method in case there is no
Internet connectivity.
If Microsoft SQL Server is not installed on the computer, in the dialog box that
is displayed, a URL is provided to download and install Microsoft SQL Server
Express edition.
Note: You can install SQL Server on another computer (off-box installation) or
on this computer (on-box installation) before or after SIM installation.
If Microsoft Windows Installer 4.5 is not installed, click Accept to accept the
license agreement and begin the installation.
This task is applicable for Microsoft Windows Server 2003 computers only.
After you click Accept, a Software Update Installation Wizard appears and
walks you through the installation of Windows Installer 4.5. After you install
Windows Installer, you may have to restart your computer.
Microsoft Windows Installer 4.5 is a prerequisite for the installation of Symantec
If Microsoft .NET Framework 4.5.1 is not installed, the Symantec Installation

Manager Setup displays dialog box to read the license agreement for .NET
Framework 4.5.1. click Accept. The Symantec Installation Manager Setup
automatically installs .NET Framework 4.5.1 (x86 and x64). After you install
.NET Framework, Symantec recommends that you restart the computer.
In the Welcome dialog box, click Next.
In the License Agreement dialog box, check I accept the terms in the license
agreement, and click Next.
In the Destination Folder dialog box, click Begin install to install the files in
the default location.
To install the files in a different location, click Browse, and specify a different
location.
In the dialog box that appears, click Install.

By default, the Launch Symantec Installation Manager option is selected on
this page. This option opens the Symantec Installation Manager to the Install
New Products page.
90

Installing Symantec Management Platform and IT Management Suite

Launch and use the Symantec Installation Manager to install Symantec Management
Platform and IT Management Suite solutions.
Note: Symantec recommends that you install and test IT Management Suite in a
test environment before you install it in a production environment.
The following procedure addresses how you must launch the installation wizard
from Symantec Installation Manager and select the Symantec Management Platform
and IT Management Suite solutions to be installed. You must then configure the
required settings for setting up the IT Management Suite on a computer.
After the installation is completed, the Symantec Management Console launches
on the computer where you installed the IT Management Suite solutions. The
Welcome page of the Symantec Management Console is displayed, which contains
links to the major first-time setup configuration steps. Additionally, you can perform
the post-installation tasks or run the migration wizard to migrate Notification Server
6.x/7.0 to the Notification Server 7.6.
The installation of IT Management Suite solutions using the Symantec Installation
Manager includes the following steps:
1.
Configuring initial settings and checking the installation readiness

See To configure initial installation settings and check the installation readiness
on page 92.
2.
Configuring Notification Server settings and SQL database settings

See To configure Notification Server settings and SQL database settings
on page 95.
3.
Configuring IT Analytics settings

See To configure IT Analytics settings on page 101.
4.
Reviewing and starting the installation, backing up Notification Server

cryptographic keys, and applying licenses to solutions
See To review and start the installation, back up Notification Server
cryptographic keys, and apply licenses to solutions on page 102.
91

To configure initial installation settings and check the installation readiness
Start the Symantec Installation Manager on the computer.

After you complete the installation of Symantec Installation Manager on the
computer, the application automatically launches. To launch the application
manually, click Start > All Programs > Symantec > Symantec Installation
Manager > Symantec Installation Manager.
(Optional) If required, change the product listing file.

The product listing file is a platform-neutral XML file that the Symantec
Installation Manager uses to install the IT Management Suite solutions. The
Symantec Installation Manager is packaged with a default product listing file
symantec_v2.pl.xml.zip. You use the default product listing file for first-time
installation of IT Management Suite solutions. The product listing file displays
a list of products that you can install. The latest product listing file is stored at
http://www.solutionsam.com/solutions/pl/symantec_v2.pl.xml.zip website.
You may be required to change the product listing file manually in any of the
following situations:
When you install the ITMS solutions on a computer without Internet

connectivity.
In such case, you download the latest product listing file from
http://www.solutionsam.com/solutions/pl/symantec_v2.pl.xml.zip and copy
the file to the computer that has no Internet connectivity.
When you purchase a product that has its own product listing file.
For example, the third-party products that have their own product listing
files.
You can also update the product listing file after the installation is completed,
to get the list of updated product versions. On detecting an updated product
listing file, the Symantec Installation Manager prompts you to update the file.
See Updating the product listing file on page 109.
On the Installed Products page that is displayed after you launch the Symantec
Installation Manager, select the Participate in the Symantec Product
Improvement Program check box to allow Symantec to collect information
about the success or failure of installation and upgrade processes, and the
usage information about the telemetry solution anonymously
For more information on the Symantec Product Improvement Program, see
www.symantec.com/docs/HOWTO77301.
92

On the Install New Products page, select the IT Management Suite solutions
to install and then click Next.
Note: Click the Show all available versions check box to see all the versions
of ITMS solutions that are available for installation or upgrade. You can then
select the solution that you want to install from the list of available solutions.
(Optional) On the Optional Installations page, select the optional components

for installation and then click Next.
You can also install the optional components, such as documentation, language
packs, or the migration wizard after the IT Management Suite installation is
completed.
See Installing language packs, documentation, or the migration wizard
on page 113.
When migrating to the latest version of IT Management Suite, ensure that you
install the migration wizard by selecting the Migration Wizard optional
component.
On the Install Location page, select the drive on which you want to install the
IT Management Suite solutions, and then click Next.
These products can be installed on a drive different from where Symantec
Installation Manager is installed.
On the End User License Agreement page, verify that the correct solutions
are selected for installation, select the I accept the terms in the license
agreements check box, and then click Next.
If you need to change the product selection, click Back twice.
On the Contact Information page, enter the requested information, and then
click Next.
After you configure the initial installation settings, the Symantec Installation
Manager checks for installation readiness.
On the Install Readiness Check page, verify that the installation prerequisites
are met.
By default, the installation readiness check begins automatically. On the Install
Readiness Check page, the Symantec Installation Manager checks whether
the computer meets the minimum requirements for the installation. If any system
requirement is not found, the Symantec Installation Manager prompts you to
confirm the installation of the required role services automatically.
93

In a few cases, the Symantec Installation Manager provides information and

download link for the missing software. In addition, you must ensure that your
system scales to meet your organization's infrastructure requirements. See
The Symantec IT Management Suite Platform Support Matrix on page 33.
The Install Readiness Check checks for the following information:
Whether the server meets the minimum hardware specifications.
Whether the server meets the minimum software requirements.
Whether the server is currently in a hierarchy. Certain solutions can only

be installed in certain locations within the hierarchy.
The Symantec Installation Manager determines the location within the
hierarchy and blocks the installation or upgrades of products where
necessary. It also validates whether replication is enabled. Replication
cannot be enabled during an upgrade.
Whether the server configuration is compatible with the latest version of IT

Management Suite. For example, Symantec Installation Manager checks
whether IIS is configured correctly or, in an upgrade scenario, whether the
server is in a hierarchy.
Whether a restart needs to take place. There may have been a recent
installation that required a restart, but the restart was postponed.
Whether any bad Notification Server Events (NSEs) are present. SIM
automatically scans for and clears bad NSEs and logs any action taken.
Whether the collation of the database server matches the collation of the
database.
The Install Readiness Check page also provides the recommended

requirements for the installation.
For more information about checking the installation readiness of a computer,
see the following video in Symantec Connect:
Checking Installation Readiness for IT Management Suite
The following symbols denote each installation requirement:
Icon
Description
The requirement and any recommendations are met.
The requirement is met and you can continue with the installation,
but there are a few recommendations to consider.
94

Icon
Description
The requirement is not met. You cannot continue with the installation
until you meet the requirement.
The requirement is met, and there is additional useful information
that you can read.
Note: In a few cases, you are prompted to install ADOMD.NET from the
Microsoft Downloads website. Ensure that version ADOMD.NET 9.0 file,
SQL_Server2005_ADOMD_x64.msi file is compatible with Microsoft SQL Server
2008/2012/2014. Download and execute the ADOMD.NET file to install
ADOMD.NET.
10 On the Install Readiness Check page, click Check install readiness again
to check the installation readiness once again after you have installed the
minimum requirements.
11 On the Install Readiness Check page, after the installation readiness check
confirms that the minimum requirements are met, click Next.
To configure Notification Server settings and SQL database settings
On the Notification Server Configuration page, specify the following

information:
Option
Description
User name
Provide the user name to access Notification Server.

Include the domain name or use .\username or
computername/username. The user name must be a
Windows user with local administrator rights to the
Notification Server computer.
Password
Provide a password for the account.
95

Option
Description
Website
Specify the website for Notification Server. You can

leave the default site or establish your own.
After you configure a website, the Refresh option lets
you see the website in the drop-down list.
After you configure a website, a Service Unavailable
message may occur when you click Next, if one or more
of the following conditions is true:
The Network Service account does not have Local

Activation permissions to the Internet Information
Services Admin service.
The ASP.NET worker process account on
Notification Server does not have the correct file
permissions.
Microsoft Windows SharePoint Services 3.0 is
installed on the same website as Notification Server.
For more information about how to resolve these same

issues for a different product, see the following Microsoft
knowledge base article:
http://support.microsoft.com/kb/930461
Fully Qualified Domain
Name
Enter the Fully Qualified Domain Name. The Fully

Qualified Domain Name must resolve to the same
computer where Notification Server is installed.
96

Option
Description
Certificate
Select either of the following options for specifying the

SSL certificate:
Create self-signed
Select this option to create a self-signed SSL
certificate on a computer and use the newly-created
certificate to set up an HTTPS communication on
that computer. When you click Next on this page, a
dialog box appears that informs you that Symantec
Installation Manager automatically creates a
self-signed certificate.
Import
Select this option to import an already-created SSL
certificate and then set up an HTTPS communication
on the computer. While importing an SSL certificate,
the file must be of .pfx extension, must be
password protected. Additionally, the SSL certificate
must be a trusted certificate. To enable trust, install
this certificate in the Trusted Root Certification
Authorities store.
<Certificate available on this computer>
Select this option to browse and specify an SSL
certificate from the existing certificates that are
available on the Notification Server computer. The
available certificates are populated in the certificate
control and you can browse and select the certificate
you want to. When you select this option, a Select
Certificate list appears that displays the certificates
that already exist on the computer. Select the
certificate you want to use from the list.
You can click the Certificate Requirements link to see

the minimum requirements for the certificates that the
IT Management Suite supports.
97

Option
Description
Require HTTPS to access

the Management Platform
Select the Require HTTPS to access the Management

Platform check box to use HTTPS communication to
access the Symantec Management Console. If you
check this option, the default SSL port 443 is enabled
and port 80 access is disabled.
During the installation of the IT Management Suite
(ITMS) on a computer, by default the HTTPS
communication gets configured on that computer. As
an administrator, you can specify HTTPS communication
only or both HTTP and HTTPS communications to
access the Symantec Management Platform and to
communicate with the client computers
HTTP is unsecured and is subject to man-in-the-middle
and eavesdropping attacks, which can let attackers gain
access to website accounts and sensitive information.
HTTPS is designed to withstand such attacks and is
considered secure against such attacks.
By default, the Notification Server computer is
configured with HTTPS to communicate with the client
computers. HTTPS mode of communication creates a
secured channel for a communication that is more
reliable and improves communication with client
computers.
Note: You must configure Notification Server to use

HTTPS communication only if you want to set up
Cloud-enabled Management.
See About Cloud-enabled Management on page 203.
For more information on how to set up Cloud-enabled
management, see the IT Management Suite 7.5
Administration Guide.
For more information on how to set up Cloud-enabled
management, see the IT Management Suite 7.5 SP1
Administration Guide.
See Configuring Notification Server to use HTTPS after
ITMS installation is completed on page 117.
For more information about setting up HTTPS
communication in your ITMS environment, see the How
to run ITMS 7.5 on HTTPS feature card.
98

Option
Description
SSL Port
Select the port for the HTTPS communication that you

set up.
The default SSL port for HTTPS communication is 443.
If the SSL port is not configured for the selected website,
then the Symantec Installation Manager sets the SSL
port to 443. If the port 443 is already configured for a
few other website or service, then the Symantec
Installation Manager prompts you to reconfigure the
SSL port for the selected website.
Configure my email
information now
(Optional) Lets you configure how Notification Server

events are emailed. You must enter the DNS name or
IP address of your SMTP server. If the server requires
authentication, you must enter a valid user name and
password. The Send Test Email option lets you verify
that Notification Server sends the email to the correct
address.
You can also configure the email in the Symantec
Management Console after you install the product.
The Notification Server Configuration page lets you configure Notification

Server credentials and the website settings and email settings.
For more information about configuring Notification Server settings on a
computer, see the following video in Symantec Connect:
Configuring Notification Server settings through SIM - Part 1
On being prompted to set the application pool for the selected website to
Classic .NET AppPool, click OK.
On the Notification Server Configuration page, click Next.
99

On the Database Configuration page, specify the following information:

Option
Description
SQL Server name
Enter the name of the server that runs Microsoft SQL

Server. You can install the Configuration Management
Database to a specific SQL Server instance by entering the
server name and SQL instance. For example, <SQL
Server name>\<SQL instance>. For the logon, you
can use Windows authentication or SQL Server
authentication.
The Browse for SQL on the Network button starts a
search for a database. If you do not click this button, the
Symantec Installation Manager does not search for
databases (either local or on the network.) If you installed
a SQL Express database through Symantec Installation
Manager, this database automatically populates the SQL
Server name field.
Use Windows
authentication or Use
SQL Server login
Specify whether to use SQL Admin credentials or Windows

credentials to log in to the SQL Server.
Database name
Specify to create a new SQL database or use an existing

SQL database.
The Create new option lets you create a new SQL database
whose default name is Symantec_CMDB. You can change
this name to one that better fits your environment.
The Use existing option lets you reinstall the Symantec
Management Platform products on a different computer
and access the existing database. When you migrate from
Symantec Management Platform 7.0, it also lets you access
a restored 7.0 database. If you used SQL credentials, the
Refresh option lets you view an existing database.
If you use an existing database that is restored from a
backup, the SQL collation for server collation and database
collation must be similar. If there is any discrepancy, the
Symantec Installation Manager displays a validation error
message on the Database Configuration page.
For more information, see topics on restoring the
Configuration Management Database in the Altiris IT
Management Suite from Symantec Migration Guide version
7.0 to 7.5.
100

Option
Description
Database timeout
Specify the number of seconds before the database times

out. You can increase this value if you generate reports
with large amounts of data.
For more information about configuring SQL database settings on a computer,

see the following video in Symantec Connect:
Configuring database while installing NS
For more information on how to set up and configure the SQL database
environment, see the IT Management Suite 7.6 Planning for Implementation
Guide at the following URL:
Note: When migrating from IT Management Suite 7.0, connect to the restored
7.0 SQL database.
On the Database Configuration page, click Next.
To configure IT Analytics settings
On the Analysis Server configuration page, enter the Analysis server name
and verify the connection to the server.
Select an existing database or create a new database for Analysis server.
Click Next.
In the Reporting Server Configuring page, specify the Report server virtual
directory URL.
For example, http://servername/ReportServer$InstanceName/
Create a Report folder or use an existing Report folder.
Specify the Authentication type for the Report Server. You can either use
the Windows integration authentication or Stored credentials.
(Optional) Select if you want to localize the report parameters.
Click Next
101

To review and start the installation, back up Notification Server cryptographic keys,
and apply licenses to solutions
On the Review Installation Details page, click Begin install to start the
installation immediately.
(Optional) After the installation is completed, on the Back up Notification

Server Cryptographic Keys page, browse and select the location where you
want the key backups to be stored, specify the password to encrypt the
individual cryptographic keys, and then click Next.
The option to back up Notification Server cryptographic keys is displayed only
after the installation is completed. You can take a backup of Notification Server
cryptographic keys after the installation is completed. To take a backup after
the installation is completed, click Close on the Back up Notification Server
Cryptographic Keys page.
See Backing up Notification Server cryptographic keys on page 131.
(Optional) On the Product Licensing page, click Install Licenses, select the
product license file, and then click Next.
You can install the product licenses after the installation is completed. To
specify the product licenses after the installation is completed, click Close on
the Product Licensing page.
See Applying licenses to a product on page 111.
On the Installation Complete page, select either one or all of the following
options, and then click Finish.
Select the Run Notification Server Migration Wizard check box to run
the migration wizard. A dialog box appears that displays the instructions
for migrating Notification Server 6.x or Symantec Management Platform
7.0 data.
If you have installed the migration wizard, the Run Notification Server
Migration Wizard check box is selected by default on the Installation
Complete page.
To proceed with 6.x migration, see the chapter Migrating from Notification
Server 6.x in the Altiris IT Management Suite from Symantec Migration
To proceed with 7.0 migration, see the chapter Migrating from Symantec
Management Platform 7.0 in the Altiris IT Management Suite from Symantec
Migration Guide version 7.0 to 7.5.
Select the Launch Symantec Management Console check box to launch

the Symantec Management Console on the Notification Server computer.
102

The Internet Information Services (IIS) Manager redirects the console

request to the appropriate link with https://<IP address>/altiris/. You
can manually launch the Web console either from the Start menu of the
computer. Alternatively, you can manually launch the Web console if you
know the IP address of the Notification Server computer. For example:
https://<IP address>/altiris/console.
103
Chapter
Performing the
post-installation tasks
About performing post-installation tasks
Launching the Symantec Installation Manager
Adding a product listing file
Updating the product listing file
Installing critical product listing updates
Applying licenses to a product
Installing language packs, documentation, or the migration wizard
Installing hot fixes
Configuring Notification Server to use HTTPS after ITMS installation is completed
Viewing an SSL certificate
Backing up Notification Server cryptographic keys
Restoring the cryptographic keys
Reconfiguring an installed product
Repairing the installation of an installed solution
Creating and installing an installation package for offline installation
Updating an installation package for offline installation
Performing the post-installation tasks

Creating a support package
Delaying an update of the Symantec Installation Manager
Uninstalling or repairing the optional components
Uninstalling the IT Management Suite solutions
Viewing the Symantec Installation Manager logs
Disabling the creation of verbose Symantec Installation Manager logs

After you have installed the IT Management Suite solutions, you can manually
execute additional post-installation tasks on the Notification Server computer. For
example, you can perform post-installation tasks such as licensing, data migration,
updates, and repair or uninstallation of products on the Notification Server computer.
Alternatively, you can perform a few post-installation tasks, such as apply licenses,
and take a backup of Notification Server cryptographic keys during the first-time
installation of the IT Management Suite solutions.
You can execute the following post-installation tasks after the installation of the IT
Management Suite solutions is completed:
Launch the Symantec Installation Manager.

See Launching the Symantec Installation Manager on page 106.
Add a product listing file.

See Adding a product listing file on page 107.
Update the product listing file.

Install critical product listing updates.

Apply licenses to a product.

Install language packs, documentation, or the migration wizard.

See Installing language packs, documentation, or the migration wizard
on page 113.
Install hot fixes.

See Installing hot fixes on page 115.
Configure Notification Server to use HTTPS after ITMS installation is completed.
105

See Configuring Notification Server to use HTTPS after ITMS installation is

completed on page 117.
View an SSL certificate.

See Viewing an SSL certificate on page 131.
Back up Notification Server cryptographic keys.

Reconfigure an installed solution if the solution failed to configure automatically.

See Reconfiguring an installed product on page 133.
Repair the installation of an installed solution.

See Repairing the installation of an installed solution on page 134.
Create and install an installation package for offline installation.

on page 135.
Update an installation package for offline installation.

See Updating an installation package for offline installation on page 139.
Create a support package.

See Creating a support package on page 141.
Delay an update of the Symantec Installation Manager.

See Delaying an update of the Symantec Installation Manager on page 142.
Uninstall or repair the optional components.

See Uninstalling or repairing the optional components on page 144.
Uninstall the IT Management Suite solutions.

See Uninstalling the IT Management Suite solutions on page 145.
View the Symantec Installation Manager logs.

See Viewing the Symantec Installation Manager logs on page 147.
Disable the creation of verbose Symantec Installation Manager logs.

See Disabling the creation of verbose Symantec Installation Manager logs
on page 148.

After you have installed the IT Management Suite solutions, you use Symantec
Installation Manager to perform additional post-installation tasks and configuration
tasks. To perform these tasks, you must first start the Symantec Installation Manager
on the Notification Server computer.
106

If a new version of the Symantec Installation Manager is available, you are prompted
to update to the latest version when you start the Symantec Installation Manager.
You can either update the Symantec Installation Manager at that time or delay the
update of the Symantec Installation Manager to a later time.
Sometimes, the Symantec Installation Manager may detect pending restarts when
you launch the Symantec Installation Manager. If this situation occurs, the following
message is displayed:
Pending reboots detected on computer. Please restart your computer
first and run the Symantec Installation Manager again.
You can then restart the Notification Server computer and relaunch the Symantec
Installation Manager to perform the post-installation tasks. Alternatively, you can
restart Notification Server at a later time.
Note: You must restart Notification Server if Symantec Installation Manager detects
any pending reboots before installing or upgrading any solution.
To start the Symantec Installation Manager
Log on to the computer where you installed the IT Management Suite solutions
as an administrator.
On the Start menu, click All Programs > Symantec > Symantec Installation
Manager > Symantec Installation Manager.
By default, the Symantec Installation Manager displays the Installed Products
page after the IT Management Suite solutions are installed on the Notification
Server computer.

See Delaying an update of the Symantec Installation Manager on page 142.

The product listing file is a platform-neutral XML file that the Symantec Installation
Manager uses to install the IT Management Suite solutions. The product listing file
displays the IT Management Suite solutions that are installed on the computer and
the products that are available for installation.
The default product listing file is symantec_v2.pl.xml.zip file. The product listing
file can also be an uncompressed file.
107

You may be required to add a different product listing file manually in any of the
following situations:
When you install the ITMS solutions on a computer without Internet connectivity.
In such case, you download the latest product listing file from
http://www.solutionsam.com/solutions/pl/symantec_v2.pl.xml.zip and copy the
file to the computer that has no Internet connectivity.
When you purchase a product that has its own product listing file.
For example, the third-party products that have their own product listing files.
The Symantec Installation Manager accesses a product listing file that lists the
products you can install and update. By default, the Symantec Installation Manager
updates the product listing file once a day. Alternatively, you can set the time interval
of updating the file, or manually update the product listing file at any time. You can
also edit how frequently the Symantec Installation Manager gets the latest product
listing file.
To add a product listing file
On the computer, start the Symantec Installation Manager.

If the Install New Products page appears, click Cancel, and then click Yes
to confirm the cancellation.
On the Installed Products page, click Settings.
In the Settings dialog box, click Change product listing.
In the Manage Product Listings dialog box, click Add.
In the Add New Product Listing dialog box, specify the following information,
and then click OK:
In the Path field, browse and specify the path to the new product listing file.
In the Refresh Interval list, specify the time interval of when the product
listing file must be refreshed.
By default, the product listing file is refreshed daily.
(Optional) In the User name field and Password field, specify the login
credentials for the path of the product listing file.
108

In the Manage Product Listings dialog box, click OK.

By default, the product listing file that you specified is displayed as selected in
the Product Listings list.
In the Settings dialog box, click OK.

The Install New Products page displays the IT Management Suite solutions
that are available in the newly-added product listing file.

The Symantec Installation Manager accesses a product listing file that lists the
products you can install and update. By default, the Symantec Installation Manager
updates the product listing file once a day. Alternatively, you can manually update
the product listing file at any time. You can also edit how frequently the Symantec
Installation Manager gets the latest product listing file.
An updated product listing contains the latest IT Management Suite solutions that
are available for upgrade. During the latest product version release, the latest
product version is updated in the product listing file that is located at
http://www.solutionsam.com/solutions/pl/symantec_v2.pl.xml.zip. On detecting an
updated product listing file, the Symantec Installation Manager prompts you to
update the file. On confirming, the Symantec Installation Manager downloads the
updated product listing file, and checks whether there are any new solutions,
upgrades, hot fixes, or critical product listing updates available to the
currently-installed solutions.
You can also change the default product listing file to a new product listing file, and
use the new file for installation or upgrade.
To update the product listing file manually

109

In the Settings dialog box, click Update now.

The product listing file gets updated and the updated list of IT Management
Suite solutions are displayed on the Install New Products page.
To change how frequently an existing product listing file is updated

In the Settings dialog box, click Change product listing.
In the Manage Product Listings dialog box, select the product listing file, and
then click Edit.
In the Edit Product Listing dialog box, in the Refresh interval list, select the
time interval of when the product listing file must be updated, and then click
OK.
In the Manage Product Listings dialog box, click OK.
In the Settings dialog box, click OK.

The product listing file gets updated per the refresh interval that you specified.
For more information about updating the product-listing file, see the following video
in Symantec Connect:
Updating PL file and configuring proxy server settings

Sometimes, the Symantec Installation Manager displays a critical update message
for the product listing file. The critical update of the product listing file forces you to
resolve the critical update on the Notification Server computer. The critical update
lets you identify the computer, thereby moving the computer from an unsupported
state to a known state. The critical update contains a fix to the product listing file
that you used to install the IT Management Suite solutions.
When a critical update is required, the Symantec Installation Manager displays the
following message:
110

A critical update is required for the following installed products.
The critical update is mandatory, and you can postpone the critical update but you
cannot bypass the update. The Symantec Installation Manager does not let you
install, uninstall, or repair any IT Management Suite solution until the update is
completed.
To install the critical update on the Notification Server computer

On the critical update screen of the Symantec Installation Manager, click OK.
Follow the installation wizard to complete the remaining steps.


When you purchase any IT Management Suite solution, you receive license files
for every purchased product. You must use the Symantec Installation Manager to
apply licenses to the IT Management Suite solutions that you purchased. You can
apply the licenses when you install the IT Management Suite solution, or at a later
time after the installation is completed.
When you apply licenses for any of the IT Management Suite solutions, you can
add new licenses or update the existing licenses. If you do not apply the licenses
for the solutions, the Symantec Installation Manager applies trial licenses for the
solutions. If the computer is connected to the Internet, the Symantec Installation
Manager applies a trial license that is valid for at least 30 days. If the computer is
not connected to the Internet, the Symantec Installation Manager applies a trial
license that is valid for seven days.
When you migrate to the latest version of the IT Management Suite, you must first
copy your solution licenses to a specific location. This location must be accessible
from the computer where you installed the latest version of the IT Management
Suite. You can then use the Symantec Installation Manager to reapply the licenses.
For more information, see the Altiris IT Management Suite from Symantec Migration
Guide version 6x to 7.5 or the Altiris IT Management Suite from Symantec Migration
Guide version 7.0 to 7.5.
111

After a license is applied for the installed solutions, the license information appears
on the Product Licensing page of the Symantec Installation Manager. If a product
license has expired, the license still appears on the Product Licensing page. If an
IT Management Suite 7.x product has an expired license, the solution then uses a
trial license.
Note: Because a few Notification Server 6.x solutions bundle with solutions on IT
Management Suite 7.x, their licenses cannot be reused.
To apply licenses at any time after you install an IT Management Suite solution

On the Installed Products page, click Add/Update licenses.
On the Product Licensing page, click Install licenses.
In the Select License Files dialog box, browse and select the license files to
apply, and then click Open.
To select multiple licenses, press Ctrl and then select the license files.
Read the message that explains how the licenses affect the applicable products,
and then click Yes to proceed.
On the Product Licensing page, click Close.
On the dialog box that appears, click Restart services to restart Notification
Server services or Apply without restart to continue without restarting the
services.
If you restart Notification Server services, the licenses are applied immediately.
If you do not restart Notification Server services, the licenses might not be
applied for 30 minutes or more.
To save the task preference, select the Always perform this action when
installing licenses check box. The preference of whether to restart services
or apply licenses without restarting services gets saved. The dialog box does
not appear when you apply additional licenses to any solution.
The license is applied to the specific solution, and the license details are
displayed on the Installed Products page in the Symantec Installation
Manager.
112

Installing language packs, documentation, or the

migration wizard
After you have installed the IT Management Suite solutions, you can install optional
components, such as documentation, language packs, or the migration wizard at
a later time using the Symantec Installation Manager. You can also install the
optional solutions during the first-time installation of IT Management Suite solutions.
The Optional Installations page in the Symantec Installation Manager lets you
choose whether to install the optional components. These components are optional
because you may not need them. If you do not need them, you can choose not to
install them.
You can install any of the following optional components using the Symantec
Installation Manager:
Install Documentation
This option installs the documentation for the solutions that you selected, and
for any installed solutions that do not have installed documentation. You can
install this optional component only when you have any of the IT Management
Suite solutions installed on the computer.
Install Language Support

This option installs the language packs for any solutions that you selected, and
for any installed solutions that do not have installed language packs. You can
install this optional component only when you have any of the IT Management
Suite solutions installed on the computer.
Install Migration Wizard Components for migrating Notification Server data

This option installs the migration wizard components that you use to migrate
Notification Server 6.x or 7.0 data to the latest version of the IT Management
Suite using an off-box upgrade only. In case of on-box upgrade, the migration
wizard is not required.
See the section called Types of installation of the IT Management Suite 7.6
on page 12.
You can install the migration wizard components without installing any of the IT
Management Suite solutions.
113

Note: If you install the latest version of the IT Management Suite solutions on
your current Notification Server, you must migrate any Notification Server data
before you upgrade the operating system during an off-box upgrade only.
Migration wizard is not required if you perform an on-box upgrade. You can
install the Symantec Installation Manager on another computer and install only
the migration wizard components on that computer. You can then copy the
migration wizard installation package to your current Notification Server and
migrate Notification Server data.
For more information, see the following knowledge base article:
To install optional components after the installation of IT Management Suite
solutions is completed

On the Installed Products page, click Install optional components.
On the Optional Installations page, select the optional components that you
want to install and then click Next.
If an optional component is already installed, the option to install that component
is disabled. If all optional components are installed and no optional components
are available for installation, the Optional Installations page is not displayed.
On the End User License Agreement page, select the I accept the terms in
the license agreements check box, and then click Next.
On the Contact Information page, fill in the details and click Next.
If you have provided your contact information during the first-time installation
of the IT Management Suite solutions, the Contact Information page is not
displayed.
On the Review Installation Details page, verify the installation details, and
click Begin install.
The Symantec Installation Manager starts installing the selected optional
components.
114

(Optional) On the Product Licensing page, apply licenses for the solutions,
and then click Next.
This page is displayed only when you add new IT Management Suite solutions
for installation on the computer.
If you do not apply licenses, trial licenses are applied. You can use the
Symantec Installation Manager to apply licenses to the installed solutions at
any time.
Note: If you install the migration wizard, click Run Notification Server
Migration Wizard to execute the migration wizard.
For more information on migration from 7.0 environments, see the Altiris IT
Management Suite from Symantec Migration Guide version 7.0 to 7.5.
On the Installation Complete page, click Finish.
After you install an optional component, you can access the component on the
Installed Products page to uninstall or repair the optional component.

Hot fixes of the IT Management Suite solutions are small patches, which are
designed to address specific issues with the shipping solution, such as software
bug fixes. The hot fix is a small package release as opposed to a service pack,
which is a separate release.
The current IT Management Suite or Symantec Management Platform hot fixes are
available through the Symantec Management Platform and are applied to the
currently-installed solutions. The hot fix count starts after the last time you
downloaded or updated the product listing file. All other hot fixes are rolled out by
the Symantec Support team.
Following are the key UI elements that drive the hot fix installation based on your
current environment:
115

Table 3-1
Key UI elements on the Install Hot Fixes page
UI element
Description
Select All latest hot fix versions check box On clicking, all the latest available hot fixes
of all the Symantec products that can be
installed using SIM, are selected for
installation. For example, ITMS and Mobile
products.
If you do not want to install all the latest
applicable hot fixes, clear the Select All
latest hot fix versions check box. You can
then manually select the latest ITMS-specific
hot fixes for installation.
Show all hot fix versions check box
On clicking, all the hot fix versions of all

Symantec products that can be installed using
SIM, are displayed. You can then select the
individual hot fix that you want to apply on
your computer.
If you want to see only the latest hot fix
versions that are available for installation,
clear the Show all hot fix versions check
box.
To install hot fixes of IT Management Suite solutions
On the computer, start Symantec Installation Manager.

On the Installed Products page, click Install hot fixes.

The Install hot fixes option displays the available hot fixes for currently installed
solutions in green text.
On the Install Hot Fixes page, select the Show all hot fix versions check
box to see all the multiple versions of hot fixes that are available for download.
By default, only the latest versions of hot fixes are displayed on the Install Hot
Fixes page.
To see all the hot fix versions that are available for installation, select the Show
all hot fix versions check box.
To select all the latest available hot fixes for installation, select the Select All
latest hot fix versions check box.
116

On the Install Hot Fixes page, select any from the following types of hot fixes
that you want to install and then click Next:
Recommended hot fix

This type of hot fix contains the important fixes but are not critical to your
system.
Critical hot fix

This type of hot fix contains the essential fixes that may affect the security
of the computer and must be installed.
Note: In case of user change or after the Symantec Installation Manager
upgrade, the Contact Information page might appear after the End User
License Agreement page. On the Contact Information page, type the answers
for the requested information, and then click Next.
On the Review Installation Details page, verify the installation details, and
then click Begin install.
The Symantec Installation Manager starts installing the available hot fixes for
the currently-installed solution.
Configuring Notification Server to use HTTPS after

ITMS installation is completed
After the ITMS installation is completed, you can configure the Notification Server
and other components in your ITMS environment to use HTTPS mode.
Notification Server is automatically configured to use HTTPS if you select the
Require HTTPS to access the Management Platform on the Notification Server
Configuration page, in Symantec Installation Manager, during the installation of
IT Management Suite. When you roll out Symantec Management Agents from a
Notification Server that uses HTTPS, the Symantec Management Agents are also
automatically configured to use HTTPS.
If you install Notification Server without HTTPS support, you can manually configure
it later. You also have to redirect the Symantec Management Agents to use HTTPS
for communicating with Notification Server.
Following are the advantages of configuring your environment to use HTTPS mode:
117

Increased secure and reliable communication

HTTP is unsecured and is subject to man-in-the-middle and eavesdropping
attacks, which can let attackers gain access to website accounts and sensitive
information. HTTPS is designed to withstand such attacks and is considered
secure against such attacks. HTTPS mode of communication creates a secured
channel for a communication that is more reliable and improves communication
with client computers.
Ability to set up Cloud-enabled Management

After you configure your environment to use HTTPS mode, you can start setting
up Cloud-enabled Management. Cloud-enabled Management lets you manage
endpoints over the Internet even if the client computers are outside of the
corporate environment and cannot access the management servers directly.
For more information about setting up Cloud-enabled Management, see the
Setting up Cloud-enabled Management chapter in the IT Management Suite
7.6 Administration Guide
For more information about setting up HTTPS communication in your ITMS

environment, see the How to run ITMS on HTTPS feature card.
The process of setting up HTTPS communication in your ITMS environment involves
the following steps:
Table 3-2
Process of setting up HTTPS communication in your ITMS

environment
Step
Action
Description
Step 1
Create or import an appropriate

SSL certificate.
You must obtain an SSL certificate that is used to encrypt and

decrypt the information that is transferred over the network.
See Creating or importing an SSL certificate on page 120.
Step 2
Create an HTTPS binding.
You must create an HTTPS binding for a website by using the

newly-created SSL certificate.
See Creating an HTTPS binding on page 123.
Step 3
Verify the HTTPS binding by

making a request to the website.
After you have created an HTTPS binding, you must verify that
the selected website uses the HTTPS binding that you specified.
See Verifying the HTTPS binding on page 124.
Step 4
Configure your Notification Server Ensure that your Notification Servers are configured for HTTPS
and Symantec Management
access and that your Symantec Management Agents use HTTPS.
Agents to use HTTPS.
118

Table 3-2
Process of setting up HTTPS communication in your ITMS

environment (continued)
Step
Action
Description
Step 5
Apply a root certificate authority

Add the root certification authority (CA), which issued the SSL
certificate to a managed computer. certificate, to the list of trusted CA on all the managed computers.
This task involves manually exporting the root certificate from NS,
and then applying the exported root certificate to all managed
computers.
Step 6
Redirect the Symantec

Before you can bring a Symantec Management Agent under
Management Agent to
Cloud-enabled Management, you need to ensure that the agent
communicate to the HTTPS port of uses HTTPS for communicating with Notification Server.
ITMS.
Step 7
Configure a package server to

publish HTTPS package
codebases.
You can configure HTTPS on your package servers by using the

Package Service Settings page. This page specifies the global
package service settings that are applied to all package servers
that serve your Symantec Management Platform.
See Configuring a package server to publish HTTPS package
codebases on page 125.
Step 8
(Only
required for
setting up
Cloud-enabled
Management)
Configure site servers to use

HTTPS.
To serve CEM agents, site servers have to be configured to use

HTTPS. This process is automated by Cloud-enabled Management
Site Server Settings policy. When a new site server is assigned
to an Internet site, an SSL certificate is distributed and HTTPS
binding is created on the 443 port. By default, Cloud-enabled
Management Site Server Settings policy does not affect the
functionality of site servers that already use HTTPS. For example,
if you assign a site server with an existing HTTPS binding to an
Internet site, the binding is not overwritten.
See Configuring Cloud-enabled Management Site Server Settings
policy on page 126.
Step 9
Configure sites and site servers to The Cloud-enabled agents that are behind the Internet gateway
serve Cloud-enabled agents.
use Internet sites for determining site services. In the Symantec
(Only
Management Console, you must add your site servers to a
required for
predefined Default Internet Site or other Internet sites that you
setting up
want to use. You must also assign the Cloud-enabled computers
Cloud-enabled
to the sites that are based on resource targets. This manual
Management)
assignment ensures that each computer remains a member of the
appropriate site regardless of where it is physically located.
See Configuring sites and site servers to serve Cloud-enabled
agents on page 128.
119

Creating or importing an SSL certificate

The SSL certificate is used to encrypt and decrypt the information that is transferred
over the network, between Notification Server and the client computers. You can
import a commercial certificate or you can create a self-signed certificate.
Types of SSL certificates in ITMS environment

In the ITMS environment, you can use self-signed SSL certificate, or import and
use an existing commercial SSL certificate. A SSL certificate is issued by a
certification authority, or certificate authority (CA). Following are a few types of
certification authorities:
Commercial certificate authorities, who charge for their services.
Certificate authorities owned by institutions and governments for their own use.
Self-signed and community-driven certificate authorities, which are free of charge.
During HTTPS configuration, you are required to specify whether you want to use
a self-signed certificate or a commercial certificate. Therefore, you must make a
judicious decision about the type of SSL certificate that you use depending upon
your requirements. To help you choose the suitable certificate, the following table
compares and contrasts between commercial certificate, and SSL certificate.
Table 3-3
Differences between commercial SSL certificate and self-signed

SSL certificate
Commercial SSL certificate
Self-signed SSL certificate
Provided by third-party certification authorities Provided by creating locally self-signed

who charge a fee for their services.
certificates, and is community driven and
obtained for free of charge.
Certificate is obtained by creating a private Certificate is signed with its own private key.
key on a secure computer, generating a
certificate signing request, and then sending
the certificate to the certification authority
(CA). After receiving your certificate signing
request, the CA verifies the identity, and then
generates the public key and makes the key
available to you.
Require both parties to trust the certification If the parties know each other, trust each
authorities.
other to protect their private keys, and can
confirm transfer public keys then self-signed
certificates may decrease overall risk.
120

Table 3-3
Differences between commercial SSL certificate and self-signed

SSL certificate (continued)
Commercial SSL certificate
Self-signed SSL certificate
A compromised certificate can be revoked,

which prevents its further use.
A compromised certificate cannot be revoked

which may allow an attacker who has already
gained access to monitor and inject data into
a connection to hack an identity if a private
key has been compromised.
SSL certificate requirements

You can use commercial SSL that is authenticated through a certification authority.
To use a commercial certificate, it has to fulfill the following requirements:
Table 3-4
Symantec Management Platform requirements for SSL certificates
Digital signature
The certificate has a valid digital signature.
Trust
The certificate is issued by Certification Authority that is

trusted by the Notification Server computer.
Validity
The certificate is valid at least for 30 days from the import

date.
Enhanced Key Usage
The Enhanced Key Usage value of the certificate is Server

Authentication OID (1.3.6.1.5.5.7.3.1).
Subject name or subject

alternate name
Subject or subject alternate name matches the Notification

Server computer Fully Qualified Domain Name (FQDN).
You can specify multiple FQDN names separated by a ;.
Hashing algorithm
The certificate uses one of the following hashing algorithms:
SHA1
SHA256
SHA384
SHA512
Asymmetric algorithm
The certificate uses the RSA asymmetric algorithm.
File format
.pfx
Creating a self-signed SSL certificate

Self-signed certificate is not authenticated by a certification authority. Use this option
for server testing purposes or for troubleshooting third-party SSL certificates.
121

To create a self-signed SSL certificate on the Notification Server computer
Log on to the Notification Server computer as an administrator.
On the Start menu, click Administrative Tools > Internet Information

Services (IIS) Manager.
From the Connections pane on the left, select the required connection type.
Under the IIS area, double-click Server Certificates.
From the Actions pane, click Create Self-Signed Certificate, and then specify
the name for the certificate.
Click OK to save the changes.

A self-signed SSL certificate is created on the Notification Server computer.
The next step is to create an HTTPS binding by for a website by using the
For a detailed end-to-end process on setting up HTTPS communication in your
ITMS environment, See Configuring Notification Server to use HTTPS after ITMS
installation is completed on page 117.
Importing a commercial certificate

Use this option when you have SSL certificate that is authenticated by a third-party
certification authority (CA).
To import a commercial SSL certificate on the Notification Server computer

From the Connections pane on the left, select the required connection type.
On the Actions pane, click Import, and then, in the Import Certificate window,
enter the path to the certificate file and the certificate password.
Click OK.
The next step is to create an HTTPS binding by for a website by using the
ITMS environment, See Configuring Notification Server to use HTTPS after
ITMS installation is completed on page 117.
122

For server testing purposes or for troubleshooting third-party SSL certificates, you
can create and use a self-signed certificate. A self-signed certificate is not
authenticated through a certification authority. For a self-signed certificate, you
need to specify the certificate name.
The site server certificate generator tool AeXGenSiteServerCert.exe lets you
create a site server certificate. This tool is available in the base directory where you
installed the ITMS solutions, for example, in the C:\Program
Files\Altiris\Notification Server\Bin\Tools folder. The certificate name
must match the name of the site server. Also, this certificate is signed by the special
Notification Server certificate authority (CA) certificate for Cloud-enabled clients. If
you do not have your own corporate certificate authority, this tool lets you easily
set up HTTPS on your site servers.
Creating an HTTPS binding

Before you perform this step, ensure that you have created or imported an
appropriate SSL certificate.
After you create an SSL certificate, you must add bindings to a website for
establishing an HTTPS binding. This action lets you access the website by using
HTTPS communication protocol. For a website, you must set up HTTPS binding
on port 443 to use the newly-created SSL certificate and HTTP binding on port 80.
To create an HTTPS binding to use SSL certificate

From the list of different server sites in the left pane, select the required website.
Under the Edit Site area, click Bindings.
In the Add Site Binding dialog box, specify the following details, and then
click OK:
In the Type list, select https to specify the HTTPS communication protocol.
In the IP address list, select an existing IP address or type an IP address

that users can use to access this site.
123

In the Port field, type the port on which HTTP.sys must listen for the requests
that are made to this site.
The default port for HTTPS binding is 443. If you specify a different port
than port 443, then the client computers must specify the port number in
requests to the server or they cannot connect to the site.
In the SSL Certificate list, select the self-signed certificate that you want
the website to use for SSL.
The SSL certificate list appears only when you select HTTPS from the Type
list.
Click Close to save the changes.
The next step is to verify the HTTPS binding by making a request to the website.
See Verifying the HTTPS binding on page 124.
Verifying the HTTPS binding

Before you perform this step, ensure that you have added bindings to a website for
establishing an HTTPS binding.
After you have created an HTTPS binding, you must verify that the selected website
uses the HTTPS binding that you specified. You can open the websites default
page in a Web browser using the selected HTTPS binding.
To verify the HTTPS binding for a website

From the list of different server sites in the left pane, select the required website.
Under the Browse Web site area, click Browse *:443 (https).
124

In the Internet Explorer page for the selected website, select Continue to
this website (not recommended).
Note: Internet Explorer shows an error page because the self-signed certificate
was issued from the computer where you installed the IT Management Suite
solutions and not from a trusted certification authority. The Internet Explorer
trusts the SSL certificate if you add the certificate to the list of Trusted Root
Certification Authorities. The SSL certificate can be added as a trusted certificate
in the certificates store on the local computer, or in Group Policy for the domain.
Verify that the IP address of the website which appears in the Internet Explorer
starts with https://.
The next step is to configure your Notification Server and Symantec Management
Agents to use HTTPS.
Configuring a package server to publish HTTPS package codebases

Before you perform this step, ensure that you have generated and applied site
server certificate for Cloud-enabled Management access.
You can configure HTTPS on your package servers by using the Package Service
Settings page. This page specifies the global package service settings that are
applied to all package servers that serve your Symantec Management Platform.
Every package server computer must have its IIS configured to accept HTTPS
connections. You can use your internal corporate certificate authority to provide
the appropriate certificates. If you do not have an internal corporate certificate
authority, you can use a Notification Server command-line tool to generate the
necessary certificates for HTTPS configuration.
You need to ensure that your Cloud-enabled package servers can serve as the
download source for packages. Cloud-enabled agents and package servers are
only permitted to download packages using HTTPS across the Internet gateway.
To allow disconnected package servers to download packages, both Notification
Server and the package servers in the same site must publish HTTPS package
codebases. This configuration is required because when a package server has no
package sources available within its own site it must request them from somewhere
125

else. The package server first attempts to obtain packages from the package servers
that are located in the same site as Notification Server. If no package servers are
available, it then attempts to obtain packages from Notification Server itself.
To configure a package server to publish HTTPS package codebases
To configure HTTPS globally on all your package servers, do the following:
In the Symantec Management Console, on the Settings menu, click

Notification Server > Site Server Settings.
In the left pane, expand Site Management > Settings > Package Service
and then click Package Service Settings.
On the Package Service Settings page, under Global Package Service

Settings, click Publish HTTPS codebase.
Click Save changes.
To configure an individual package server to use HTTPS, create the following

registry key and values on each package server computer that is located in
the same site as Notification Server:
Registry location: HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\Altiris

Agent\Package Server
Key Type: DWORD
Name: EnableHTTPSOverride
Value: 1
This registry key overrides the HTTP codebase configuration on the package
server and makes it publish HTTPS codebases instead.
The next step is to configure sites and site servers to serve Cloud-enabled agents.
See Configuring sites and site servers to serve Cloud-enabled agents on page 128.
Configuring Cloud-enabled Management Site Server Settings policy

The process of setting up HTTPS communication between site servers, and
Cloud-enabled agents or intranet agents is now automated. Cloud-enabled
Management Site Server Settings policy delivers SSL certificates, signed by
Agent root Certificate Authority (CA) certificate from Notification Server, to site
servers. If Internet Information Services (IIS) on the site server computer has no
HTTPS binding, the binding is created, assigning the new certificate.
126

The Cloud-enabled Management Site Server Settings policy is enabled by default.

Note: The Cloud-enabled Management Site Server Settings policy is neglected
at the site server, when the Publish HTTPS codebase option is not checked on
the Package Service Settings page.
Policy processing actions depend on the policy details and the IIS configuration of
the site server.
Table 3-5
Processing of Cloud-enabled Management Site Server Settings

policy
Port of the existing

Force overwrite
HTTPS binding on the HTTPS binding
site server
Policy processing
Does not equal to the

Disabled
port that you specify in
the Cloud-enabled
Management Site
Server Settings policy.
A new SSL certificate is delivered, and

used to create a new SSL port binding.
The action is automated.
Equals to the port that Disabled

you specify in the
Cloud-enabled
Management Site
A new SSL certificate is delivered, but

no binding is created.
Note: Symantec recommends using this

configuration for new site servers.
In this case, the cloud-enabled clients

are not able to communicate with the
site server that is located in the
Notification Server internal network.
Note: Symantec recommends using this

configuration for site servers, that
already use HTTPS.
Does not equal to the
Enabled
port that you specify in
the Cloud-enabled
Management Site

127

Table 3-5
Processing of Cloud-enabled Management Site Server Settings

policy (continued)
Port of the existing

Force overwrite
HTTPS binding on the HTTPS binding
site server
Policy processing
Equals to the port that Enabled

you specify in the
Cloud-enabled
Management Site

Warning: The existing SSL port binding

is overwritten.
In this situation, the client computers
that have been using this port in HTTPS
mode to communicate with the site
server are not able to connect anymore.
This task is a step in the process for preparing your environment for Cloud-enabled
Management.
To configure the Cloud-enabled Management Site Server Settings policy

Notification Server > Cloud-enabled Management.
In the left pane, click Cloud-enabled Management > Policy > Cloud-enabled
Management Site Server Settings.
In the right pane, under Automated CEM certificate distribution to site

servers, specify the options that you want.
Click Save changes.
Configuring sites and site servers to serve Cloud-enabled agents

Before you perform this step, ensure that you have configured package servers to
publish HTTPS codebases.
See Configuring a package server to publish HTTPS package codebases
on page 125.
The computers that you want to manage over the Internet should be organized into
one or more sites. These sites should be dedicated to Cloud-enabled agents and
must not contain any directly managed agents. Note that the Symantec Management
Platform provides you with a predefined Default Internet Site with the All
Computers where the Cloud-enabled management feature is enabled target.
You should then assign the appropriate site servers to the predefined site or to the
sites that you create.
128

Cloud-enabled Management supports Internet package servers and Internet task

servers, which the Symantec Management Agent accesses through an Internet
gateway. Cloud-enabled Management also supports Cloud-enabled package
servers, which are package servers located in the same site as the Cloud-enabled
agents. Only the local agents can access a Cloud-enabled package server, and
they use a direct connection. However, Cloud-enabled task servers are not
supported.
Cloud-enabled computers must be manually assigned to sites that are based on
resource targets. Cloud-enabled agents do not recognize site assignments based
on IP addresses and subnets. Manual assignment ensures that each computer
remains a member of the appropriate site regardless of where the computer is
physically located.
You can manually assign a Cloud-enabled agent to multiple sites or site servers.
The site servers that are available to the agent are a union of all the site servers in
the assigned sites.
You can configure your site server settings for Cloud-enabled agents in the following
ways:
Create and configure
new sites.
You can create and configure as many sites as required to suit

your environment setup. A Cloud-enabled agent or package server
that is assigned to multiple sites receives the union of all the site
servers in the assigned sites.
Assign the
Cloud-enabled agents
directly to the site
servers.
You can assign a resource target directly to the site server to

ensure that the target members are given access to that particular
site server only. The assignment by site method makes all of the
site servers that are members of the assigned site available to the
targeted Cloud-enabled agents.
To configure an Internet site to serve the Cloud-enabled agents
(Optional) In the Symantec Management Console, create a new site and assign
the appropriate resource target to the site.
This resource target contains the Cloud-enabled agents and package servers.
You can reuse the same resource target that is applied to the Cloud-enabled
Management Settings policy.
Assign the appropriate site servers to the site in one of the following ways:
129

In the Symantec Management Console, on the

Settings menu, click Notification Server > Site
Server Settings.
In the left pane, expand Site Management > Site

Servers > your_site_server_name, and then click
Internet Sites.
In the right pane, under Detailed Information,

click New.
In the Select a Internet site dialog box, click the

Internet site to which you want to assign the site
server, and then click OK.
To assign the subnet(s) of the 1

local site servers to the site
In the Symantec Management Console, on the

Settings menu, click Notification Server > Site
Server Settings.
To manually assign the site

server to the site
In the left pane, click Site Management >

Subnets.
In the right pane, select the appropriate subnet.
On the toolbar, click Assign to site.
In the Select a site window, select the site to which

you want to assign the subnet.
Note: A local site server is one that exists in the same

disconnected site as the Cloud-enabled agents that it
serves.
This type of assignment requires the disconnected site
to have a unique subnet that does not overlap with
subnets of internal clients, if any. This configuration is
not common, so this approach is not generally
recommended.
To directly assign Cloud-enabled agents to a site server

Notification Server > Site Server Settings.
In the left pane, expand the site server that you want to modify, and then click
Manually Assigned Agents.
In the right pane, click New, specify the resource target that contains the
appropriate Cloud-enabled agents, and then click OK.
130



You can view the SSL certificates that are associated with a server in IIS. You can
view the names of certificates and the fully qualified domain names (FQDNs) of
hosts to which certificates have been issued. You can also view the FQDNs of the
servers that issued the certificates.
See Configuring Notification Server to use HTTPS after ITMS installation is
completed on page 117.
To view associated SSL certificates of the Notification Server computer
On the Notification Server computer, open the Server Manager.
In the Server Manager, navigate to Roles > Web Server (IIS).
In the Connections pane, select the server node for which you want to view
the associated SSL certificates.
In the IIS area, double-click Server Certificates.

The Server Certificates page appears which displays the list of SSL certificates
that are associated with the selected server.
Right-click any certificate and select View.

The Certificate dialog box appears that displays the SSL certificate details.
For example, the certificate name, certification path, certificate subject name,
signature used, expiry date and key algorithm, and so on.

A backup of Notification Server cryptographic keys is required for disaster recovery.
You can restore the database to a new server hardware using the backed up
Notification Server cryptographic keys. These keys are used to secure data inside
Notification Server database. The cryptographic keys are used to encrypt the
authentication credentials that are stored in the CMDB. Examples of authentication
credentials that are stored in the CMDB include the following:
Credentials that are used when you add a child Notification Server into a
hierarchy
131

Credentials that are used when you execute a run as operation during software
delivery
You can take a backup of Notification Server cryptographic keys after the installation
is completed. Alternatively, you can take a backup during the first-time installation
of the IT Management Suite solutions. This task is an optional step during the
first-time installation.
Authentication credentials cannot be used without these keys. If your server
hardware crashes, these credentials are lost unless you have taken a backup of
the keys in Symantec Installation Manager. A backup of your hard disk alone does
not save these keys.
The backup of the cryptographic keys is stored in a .kms file that includes the
cryptographic keys which are encrypted and cannot be transferred. There may be
multiple keys in one .kms file.
The following registry keys are created when you back up the keys:
KMSBackupPath
Tracks the location where the keys are backed up.
KMSBackupDate
Keeps a track of the date when the keys were backed up. If any keys have a
newer date, a new .zip file gets created.
To back Notification Server cryptographic keys
On the Install Products page, click Back up Notification Server

Cryptographic Keys.
On the Back up Notification Server Cryptographic Keys page, browse and

select the location where you want the key backups to be stored, or keep the
default path.
Alternatively, you can take a backup of Notification Server cryptographic keys
during the first-time installation of the IT Management Suite products. The
Back up Notification Server Cryptographic Keys page appears after the
installation is completed.
The key backups must be stored on a different server, in case the current
server hardware crashes.
Provide a password for the backup cryptographic keys file.

You need this password for unencrypting the keys during the restore process.
Make a note of the password and store it in a safe location.
Click Create Backup.
132

A confirmation message appears that states that the backup of Notification Server
cryptographic keys is complete.

You can use the KMS restore utility to restore the cryptographic keys from a
computer on which Symantec Management Platform is installed. The Symantec
Installation Manager deploys the KMS restore utility at the following location on
Notification Server computer:
<Install_Dir>\Program Files\Altiris\Symantec Installation
Manager\KMSRestoreUtility\KMS_Utility
To restore the cryptographic keys
Navigate to <Install_Dir>\Program
Files\Altiris\SIM\KMSRestoreUtility\, and copy the KMS_Utility folder
on the computer on which Symantec Management Platform is installed.
From the KMS_Utility folder, double click and run the KMSRestore.exe
executable file.
In the Restore Notification Server Cryptographic Keys dialog box, browse

to the location of the zip file containing the backup of KMS keys file.
In the Password field, enter the password that was used during the back-up
of the cryptographic keys.
Click Restore Keys.
Reconfiguring an installed product

The Symantec Installation Manager installs and automatically configures the IT
Management Suite solutions that you selected for installation. Generally, the
Symantec Installation Manager configures the installed products without any
problems. However, sometimes the Symantec Installation Manager can install a
product but cannot configure the installed product.
The failure to configure an installed product can be because of many different
issues. For example, a Web communication problem can cause the configuration
to fail. If the Symantec Installation Manager cannot configure an installed product,
a list of installed but unconfigured solutions appears at the end of the installation.
You can then access the unconfigured solutions on the Installed Products page
and attempt to reconfigure them.
133

If you reconfigure a solution and it is still not properly configured, you can uninstall
and reinstall the solution to resolve the configuration error. If reinstalling a solution
does not resolve the problem, create a support package and send the package to
Symantec Support team for verification.
See Creating a support package on page 141.
To reconfigure an installed solution

On the Installed Products page, in the Installed products list, check if there
is any solution available with the Reconfigure option.
If the Reconfigure option does not appear for any of the installed solutions,
then all the installed solutions are configured. The option to reconfigure a
solution appears only if a solution is installed but not configured.
If there are any solutions available for reconfiguration, click Reconfigure and
then click Yes on the dialog box that appears.
When the configuration is complete, click Finish on the Configuration

complete page.

You can repair the installation of IT Management Suite solutions using the Symantec
Installation Manager. All installation files are .msi format files. Therefore, the
Symantec Installation Manager starts the Windows Installer to repair a solution
installation. You can repair the installation errors of the IT Management Suite
solutions and the optional components that are installed on the computer.
To repair the installation of an installed solution

On the Installed Products page, in the Installed Products list, select the
solution that you want to repair.
Click Repair that appears after you select the solution to be repaired.
134

On the dialog box that appears, click Yes to confirm the repair operation.
The Repairing Software page is displayed and the Windows Installer starts
repairing the installation of the selected solution.
On the Repair Complete page, click Finish.
Creating and installing an installation package for

offline installation
To install the IT Management Suite (ITMS) solutions on a computer that does not
have an Internet connection, you must create an installation package. You create
an installation package using a computer that has IT Management Suite solutions
already installed on it. You then download or copy the entire installation package
on a computer that does not have an Internet connection, and then execute the
installation. The Symantec Installation Manager lets you create the installation
package in the form of a compressed executable file.
The installation package that can be used for offline installation contains the following
types of files:
Solution installer files

The .msi files are all the installation files that are required to install the solutions
and optional components that you selected when you created the package.
License files
The installation package includes any licenses that you purchased for the
solutions that are currently installed on the computer.
Product listing file

The product listing file, .pl.xml file is a platform-neutral XML file that the
Symantec Installation Manager uses to install the IT Management Suite solutions.
Symantec Installation Manager installer file

The Symantec Installation Manager installer file,
SymantecInstallationManagerSetup.exe file, lets you install the Symantec
Management Platform and IT Management Suite solutions.
You can use the Symantec Installation Manager to create an installation package
for 32-bit operating system and for 64-bit operating system. The Symantec
Management Platform 7.0 is a 32-bit platform, whereas the Symantec Management
Platform 7.6 is a 64-bit platform. You can use the same installation package to
install Symantec Management Platform 7.0 or Symantec Management Platform
7.6.You can also update the installation package that you had previously created.
135

See Updating an installation package for offline installation on page 139.

You can create an installation package even on a computer having an operating
system which does not support the installation of Notification Server, which is the
central component of the IT Management Suite. Only Microsoft Windows Server
2008/2012 platform supports the installation of Notification Server. Microsoft
Windows XP/7 does not support the installation of Notification Server, but they do
support the installation of the Symantec Installation Manager. However, not all
Symantec Installation Manager functionality is available on Windows XP (x86 and
x64) and Windows 7 (x86 and x64).
The following table describes the features of Symantec Installation Manager that
different Windows operating systems support.
Table 3-6
Available Symantec Installation Manager features on different

Windows operating systems
Operating system on which the

Symantec Installation Manager can be
installed
Available Symantec Installation Manager

features
Microsoft Windows Server 2008
All Symantec Installation Manager features
Microsoft Windows Server 2012
All Symantec Installation Manager features
Microsoft Windows XP
Create Installation Package feature
Microsoft Windows 7
Only the Create Installation Package feature
The procedure for creating an installation package and installing the IT Management
Suite solutions on a computer with no Internet connectivity involves the following
steps:
1.
Creating an installation package for offline installation.

You create an installation package using a computer that has IT Management
Suite solutions already installed on it.
See To create an installation package for offline installation on page 137.
2.
Installing the installation package on a computer with no Internet connectivity.

You download or copy the entire installation package to a computer that does
not have an Internet connection, and then execute the installation.
See To install the installation package on a computer with no Internet
connectivity on page 138.
136

To create an installation package for offline installation
Install the IT Management Suite solutions on a computer that has Internet

connectivity.
on page 91.
Start the Symantec Installation Manager on the computer.

If the Install New Products page appears, click Cancel, and click Yes to
confirm the cancellation.
On the Installed Products page, click Create installation package.
On the Products page, specify the following details, and then click Next:
In the Available Products list, select the solutions to be included in the

installation package.
In the Output location field, browse and select the path where the package
file must be created.
On the Optional Installations page, select the optional components that you
want to include in the package, and then click Next.
If you need to change the product selection, click Back twice.
On the Contact Information page, enter your contact information details, and
then click Next.
(Optional) On the Product Licensing page, apply licenses for the solutions
that you have selected, and then click Next.
If you do not apply licenses, then by default the trial licenses are applied when
the solutions are installed. You can use the Symantec Installation Manager to
apply licenses at any time after the installation is completed.
137

10 On the Review Package Details page, review the information about the
installation package, and click Begin build.
The package is created and is saved at the location that you specified. The
installation package follows the following naming convention:
Symantec_Install_Package_<date>_<timestamp in 24-hour format>.exe
11 On the Installation Package Complete page, click Finish.

You can store the installation package .exe file on a portable device or on a
shared folder of the computer. You can then copy the installation package to
a computer with no Internet connectivity where you want to install the ITMS
solutions.
To install the installation package on a computer with no Internet connectivity
Log on as an administrator on the computer without Internet connectivity where

you want to install the IT Management Suite solutions.
Copy the installation package .exe file to the computer where you want to
install the ITMS solutions.
Run the compressed executable file to extract the installation package files.
After the installation files are extracted, you are prompted to launch the
Symantec Installation Manager setup. Click OK to confirm the action.
The installation files are extracted at the Altiris\Components folder to the
location where you stored the .exe file.
On being prompted, confirm to select and start the installation of the Symantec
Upon completion of the Symantec Installation Manager installation, restart the

computer when prompted.
After you have restarted the computer, launch the Symantec Installation
Manager.
Install the required IT Management Suite solutions on the computer.

on page 91.
138

Updating an installation package for offline

installation
An installation package lets you install the IT Management Suite solutions on the
computers that do not have Internet connectivity.
on page 135.
On the servers that are connected to the Internet, the Symantec Installation Manager
automatically identifies product updates. This functionality is not available if the
computer is not connected to the Internet, and therefore the product listing file does
not get updated. On the computers that do not have Internet connection, the product
listing file and the installation package must be updated manually. The latest versions
of the IT Management Suite or Symantec Management Platform are available
through the product listing file. This product listing file and other installation files
must be updated by updating the installation package. The count starts after the
last time you downloaded the product listing file and used that file to create the
The procedure for updating the installation package involves the following steps:
1.
Exporting the product history of a computer that does not have Internet access.
On the computer that has no Internet access, the Symantec Installation Manager
lets you export your product history as an .xml file.
See To export the product history of the computer that does not have Internet
access on page 139.
2.
Importing the product history on a computer that has Internet access and then
updating the installation package.
You must then import the .xml file to a computer that has IT Management
Suite solutions previously installed on it and which has Internet access. This
import lets you create an installation package with only those products that
need to get updated.
See To import the product history on a computer that has Internet access and
then update the installation package on page 140.
To export the product history of the computer that does not have Internet access
Log on to the computer without Internet connectivity where IT Management

Suite is installed using administrator credentials.

139

On the Settings page, click Export Product History.
On the Save product install history file dialog box, browse and select the
location to save the .xml file, and then click Save.
You can save the .xml file on a portable device or shared driver of the
computer.
To import the product history on a computer that has Internet access and then
update the installation package
Log on as an administrator on the computer with Internet connectivity where

you installed the IT Management Suite solutions and which was used to create
the installation package previously.

If the Install New Products page appears, click Cancel, and click Yes to
confirm the cancellation.
On the Installed New Products page, click Create installation package.
On the Products page, click Import Installed History to import the other
server's history.
Browse to the location of the history file.
Click Open.
Mark all the solutions you want to update and click Next.
Select the optional components and click Next.
10 Accept the license agreements.

11 Enter your contact information.
12 Click Begin build. The Symantec Installation Manager now starts building the
13 Click Finish.
14 Copy the installation package to the Notification Server computer without
Internet connectivity.
15 Install Symantec Installation Manager and the IT Management Suite solutions.

140


The Symantec Installation Manager (SIM) lets you create a support package that
you can send to the Symantec Support team for the team's intervention. You can
create the support package when you encounter problems with the installation,
configuration, or execution of the IT Management Suite solutions. The name of the
support package is Support, with the date and the time that is appended to the
package folder. By default, the support package is created in the C:\Program
Files\Altiris\Symantec Installation Manager\Support directory on the
server.
The support package is a compressed .zip file that includes the following data:
Notification Server logs.
Symantec Installation Manager logs that contain data about SIM activities, such
as reading or parsing the package data file, downloading packages, and
accessing the licensing server.
Symantec Installation Manager performance logs that contain summary report

about details such as services are restarted, when packages are downloaded,
installed or configured.
Copy of current and all the earlier product listing files.
Installation history information that contains information about all the installed
solutions, their version number, and the installation date.
SIM Registry key information of the computer.
Note: The option Enable Windows Installer logging in the Symantec Installation
Manager's Settings dialog enables the creation of verbose logs. Verbose logs are
more detailed compared to the Symantec Installation Manager logs.
The verbose logs are valuable for troubleshooting and are enabled by default.
Before the IT Management Suite solutions are installed, the Symantec Installation
Manager logs are generated in the
C:\Users\<username>\AppData\Local\temp\SIM Logs directory. After the
installation of the IT Management Suite solutions, the logs are generated by default
in the C:\ProgramData\Symantec\SMP\Logs directory.
Symantec recommends that you send the following information to the Support team:
Operating system version that is installed on the host server and the virtual
machine.
141

Virtual machine version, if any.
Memory that is allocated to the server or the virtual machine.
Screen capture of the error or the error message that was displayed after an
error was encountered.
Support package that is created using the Symantec Installation Manager.
To create a support package

In the Settings dialog box, click Create support package.
To access the support package, in the dialog box that appears, select the Open
containing folder check box, and then click OK.
Alternatively, you can navigate to the following location on the computer to
view the support package files:
C:\Program Files\Altiris\Symantec Installation Manager\Support
Delaying an update of the Symantec Installation

Manager
The Symantec Installation Manager prompts you to update to the latest version of
the Symantec Installation Manager, as and when the latest version is available.
You can choose to update the Symantec Installation Manager immediately or you
can choose to delay the update. For example, the latest version of Symantec
Installation Manager must pass change control before you can use the Symantec
Installation Manager. In such cases, you can choose to delay the update of the
Symantec Installation Manager. You can delay the update until the new version of
Symantec Installation Manager is approved.
If you delay the update of the Symantec Installation Manager, you do not lose any
of the current functionality. However, the Symantec Installation Manager cannot
update the product listing file, which contains the latest products and updates. When
you do not update the Symantec Installation Manager, any features in the updated
product versions are not available on the computer where you have installed the
IT Management Suite solutions.
142

Note: Symantec recommends that you update the Symantec Installation Manager
when an updated version is available.
See To delay the update of Symantec Installation Manager on page 143.
When you delay updating the Symantec Installation Manager, you can specify when
the Symantec Installation Manager must remind you to perform the update. If you
then start the Symantec Installation Manager after the specified time has elapsed,
you are again prompted to perform the update. Each time the prompt appears, you
can update the Symantec Installation Manager or delay the update. If the specified
time to delay the update has not elapsed, you can update the product listing file to
begin the update process.
You can update the Symantec Installation Manager installer to the latest available
version even after you have specified to delay the update. In such case, you can
modify the Symantec Installation Manager settings such that the application ignores
the previously-selected option to delay the update, and prompts you to install the
latest available version.
To delay the update of Symantec Installation Manager

When the Update Symantec Installation Manager dialog box appears, select
when you want to be reminded to perform the update.
This dialog box appears only when an updated version of the Symantec
Installation Manager is available. If you previously selected to delay the update,
the dialog box does not appear until the delayed time expires.
You can select to be reminded about the Symantec Installation Manager update
in one day, three days, one week, or one month.
Click OK.
The update of the Symantec Installation Manager is postponed until the delayed
time has expired.
143

To update the Symantec Installation Manager after you have delayed the update
of the application
On the computer, click Start, in the Search field, type regedit.
On the Registry Editor page, click HKEY_LOCAL_MACHINE > SOFTWARE

> Altiris > AIM > Configuration > ProductListings.
In the right pane, note the value of the Current registry value.
By default, the value of the Current registry value is 0 which means that the
0 product listing file is in use. If you are using a different product listing file
other than the default one, you may have the Current registry value as 1, and
so on.
Under the ProductListings folder, click the folder per the value of the Current
registry.
For example, if the Current registry value is 0, then you must click the 0 folder
under the ProductListings folder. If the Current registry value is 1, then you
must click the 1 folder under the ProductListings folder, and so on.
In the right pane, right-click the NextPlUpdateTime registry value, and then
click Modify.
In the Edit String dialog box, in the Value data field, change the value of
registry key to the current date, and then click OK.
Restart the Symantec Installation Manager. If there are any available updates,
you will be prompted to update the Symantec Installation Manager.

The Symantec Installation Manager lets you uninstall or repair the optional
components, such as documentation packs, language packs, and migration wizard.
The Symantec Installation Manager has an Optional Installations page that lets
you choose which optional components to install. If you have installed any optional
components, you can use the Symantec Installation Manager to uninstall or repair
them.
See Uninstalling the IT Management Suite solutions on page 145.
144

To uninstall or repair the optional components

To display the optional components that are installed, on the Installed Products
page, press Ctrl+Shift+O.
If you press Ctrl+Shift+O again, the optional components are removed from
the Installed Products page.
In the list of installed products, select the optional component that you want to
uninstall or repair.
An optional component has (Optional component) displayed below the
component's name. When you select an optional component, the Repair and
Uninstall options appear.
To uninstall an optional component, complete the following steps:
Click Uninstall, and click Yes to confirm the removal of the product.
On the Uninstallation Complete page, click Finish.
To repair an optional component, complete the following steps:
Click Repair.
Windows Installer performs a repair of the installation.
On the Repair Complete page, click Finish.

You can uninstall the IT Management Suite solutions and the Symantec Installation
Manager from the computer where these applications are currently installed. The
Symantec Installation Manager lets you uninstall a specific IT Management Suite
solutions or a suite. When you uninstall the IT Management Suite using the
Symantec Installation Manager, all the dependent suites or solutions are uninstalled
except the following applications:
Symantec Installation Manager
Altiris Event Console
145

Altiris IT Analytics
Altiris Monitor Solution for Servers
Enhanced Console Views
To uninstall the remaining components, you must manually select and uninstall the
component from the Symantec Installation Manager.
You can also use the Windows Add/Remove Programs feature to uninstall the IT
Management Suite solutions. The Add/Remove Programs feature uninstalls the
Symantec Management Platform, all the installed IT Management Suite solutions,
and the Symantec Installation Manager. If you used the Symantec Installation
Manager to uninstall the IT Management Suite solutions, you can use the Windows
Add/Remove Programs feature to uninstall the Symantec Installation Manager.
In such case, you cannot install any IT Management Suite solutions at a later time.
You can also uninstall only the optional components.
To uninstall IT Management Suite solutions using the Symantec Installation Manager

On the Installed Products page, select the product to uninstall.

When you select a product, the Uninstall option appears.
Click Uninstall, and click Yes to confirm the removal of the product.
The product is uninstalled from the Symantec Management Platform. The
solution no longer appears in the console and all entries in the database are
deleted.
On the Uninstallation Complete page, click Finish.
To uninstall IT Management Suite solutions using the Windows Add/Remove

Programs feature
Click Start > Control Panel > Programs > Uninstall a program.
146

From the list of applications that are installed on the computer, click Symantec
Platform and Solutions, and click Remove.
Click Uninstall.
This action uninstalls the IT Management Suite solutions, the Symantec
Management Platform, and the Symantec Installation Manager.

The Symantec Installation Manager creates logs during installation, repair, and
uninstallation of any IT Management Suite solutions. The log entries help to view
the record of the tasks that were executed on the computer.
Following are the types of log files that the Symantec Installation Manager creates:
Verbose logs
Verbose logs contain detailed information about events and are more useful for
troubleshooting purposes. But the verbose logs can affect the computer's
performance by creating large log files.
Non-verbose logs
Non-verbose logs contain less information such as the event's timing and a
minimal description. The non-verbose logs contain less information as compared
to the verbose logs.
By default, the verbose logging is enabled. When you create a support package,
the log files are included in the package to facilitate troubleshooting.
See Disabling the creation of verbose Symantec Installation Manager logs

on page 148.
Following are the types of log entries that are included in the log files:
Install logs
These log entries contain detailed information about what happens during the
installation of all installed solution .msi files.
Uninstall logs
These log entries list the uninstall behavior of all solution .msi files that were
uninstalled.
Repair logs
These log entries lists what happened when a solution .msi file was repaired.
The logs are stored at any of the following locations on the computer where the IT
Management Suite solutions are installed:
147

Before the IT Management Suite solutions are installed, the Symantec Installation
Manager logs are generated in the
C:\Users\<username>\AppData\Local\temp\SIM Logs directory.
The user name refers to the user credentials through which the Symantec
Installation Manager was installed. The Symantec Installation Manager logs are
stored in this location even after the IT Management Suite solutions are installed.
After the installation of the IT Management Suite solutions, the logs are generated
by default in the C:\ProgramData\Symantec\SMP\Logs directory.
To view logs before the installation of the IT Management Suite solutions
On the computer, navigate to the

C:\Users\<username>\AppData\Local\temp\SIM Logs directory.
Note: The user name refers to the user credentials through which the Symantec
Installation Manager was installed.
View the Symantec Installation Manager logs that were generated.
To view logs after the installation of the IT Management Suite solutions
On the computer, navigate to the C:\ProgramData\Symantec\SMP\Logs

directory.
View the log files pertaining to the IT Management Suite solutions that you
installed.
Disabling the creation of verbose Symantec

Installation Manager logs
Verbose logging is turned on by default in Symantec Installation Manager. Verbose
logging contains detailed information and is useful for troubleshooting purposes.
However, the verbose logging can create large log files which can effectively slow
down the computer's performance.
148

To disable the creation of verbose logs on the computer where the IT Management
Suite solutions are installed

Clear the Enable Windows Installer logging check box.
149
Chapter
Upgrading to IT
Management Suite
About upgrade paths of IT Management Suite 7.6
Best practices for upgrading to IT Management Suite 7.6
Upgrading to IT Management Suite 7.6
Upgrading to Notification Server 7.6
Upgrading Symantec Management Agent
Upgrading site servers

This topic includes information about the following:
Introduction to upgrade
Supported upgrade paths of IT Management Suite 7.6
Notification Server upgrade setups
Introduction to upgrade
An upgrade is when you replace the previous versions of the IT Management Suite
(ITMS) with the latest version of ITMS using the same hardware, server operating
system, and database
You can perform an upgrade from previous versions of IT Management Suite to
the latest version under any of the following situations:
Upgrading to IT Management Suite

When you perform an upgrade on the same hardware of the server
When you plan to continue using the same server operating system
When both the IT Management Suite environments use the same IT Management
Suite Configuration Management Database (CMDB)
A migration is when you migrate from IT Management Suite 7.0 or 6.x to IT

Management Suite 7.6 on a new computer.
See About migrating to IT Management Suite 7.6 on page 184.
Supported upgrade paths of IT Management Suite 7.6

The supported upgrade paths of the IT Management Suite solutions and Symantec
Management Platform from the earlier release versions to the latest release version
are as follows:
ITMS 7.1 SP2 MP1.1

This includes the SMP build version 7.1.8401.
ITMS 7.5 SP1 HF5

This includes the SMP version 7.5.3300
Notification Server upgrade setups

The following table describes different upgrade and migration scenarios for IT
Management Suite 7.6 and the type of setups to be prepared:
151

Table 4-1
Different upgrade and migration scenarios supported for IT

Management Suite 7.6
Upgrade
component
Notification
Server type
ITMS
version
before
upgrade
ITMS version Upgrade type Operating

after upgrade
system
Database
Single
Notification
Server
Single
7.1 SP2
MP1.1 or
7.5 SP1
HF5
7.6
on-box
Windows
Server 2008
R2 >
Windows
Server 2008
R2
SQL Server
2008 > SQL
Server 2008
Single
7.1 SP2
MP1.1 or
7.5 SP1
HF5
7.6
on-box
Windows
Server 2008
R2 >
Windows
Server 2008
R2
SQL Server
2008 > SQL
Server 2012
Single
7.1 SP2
MP1.1 or
7.5 SP1
HF5
7.6
off-box
Windows
Server 2008
R2 >
Windows
Server 2012
R2
SQL Server
2008 > SQL
Server 2012
152

Best practices for upgrading to IT Management Suite 7.6
Table 4-1
Different upgrade and migration scenarios supported for IT

Management Suite 7.6 (continued)
Upgrade
component
Notification
Server type
ITMS
version
before
upgrade
ITMS version Upgrade type Operating

after upgrade
system
Database
Multiple
Notification
Servers in
hierarchy
Parent and Child

Notification Server
7.1 SP2
MP1.1 or
7.5 SP1
HF5
7.6
on-box
Windows
Server 2008
R2 >
Windows
Server 2008
R2
SQL Server
2008 > SQL
Server 2008
Parent and Child

Notification Server
7.1 SP2
MP1.1 or
7.5 SP1
HF5
7.6
on-box
Windows
Server 2008
R2 >
Windows
Server 2008
R2
SQL Server
2008 > SQL
Server 2012
Parent and Child

Notification Server
7.1 SP2
MP1.1 or
7.5 SP1
HF5
7.6
off-box
Windows
Server 2008
R2 >
Windows
Server 2012
R2
SQL Server
2008 > SQL
Server 2012
Best practices for upgrading to IT Management Suite

7.6
Following are the best practices for upgrading to the IT Management Suite (ITMS)
7.6 solutions:
In a hierarchy, Symantec recommends that you upgrade the child Notification

Servers first, and then upgrade the parent Notification Server. For information
about upgrading Notification Servers in a hierarchy, see the knowledge base
article Upgrading Notification Servers in a hierarchy.
Before you start a fresh installation of ITMS solutions or an upgrade to ITMS

7.6, you must check the SSL configuration for the SMP website. For the SMP
website in the IIS Manager, ensure that you do not select the Client Certificates:
Require option when the Require SSL option is selected.
For the SMP website, if the Client Certificates: Require option is selected in
Internet Information Services (IIS) Manager when the Require SSL option is
153

used, the configuration does not start and the installation process or upgrade
process fails. Additionally, a forbidden (403) error is displayed and an associated
warning is reported in the Altiris Log Viewer.
After upgrade to SMP 7.5 SP1, you can upgrade the Symantec Management
Agent (SMA) on the client computers to SMA 7.5 SP1. Additionally, you must
also upgrade the solution plug-ins to the same version of the SMA. An older
version of SMA can communicate with a latest version of SMP using the Legacy
Agent Communication (LAC) mode, but Symantec recommends that you upgrade
the SMA and the solution plug-ins to the latest version. Ensure that the SMA
and solution plug-ins are always of the same release version.

You can perform an upgrade if you move from earlier versions of IT Management
Suite to the latest version of IT Management Suite on same server hardware and
with the same configuration database.
See About upgrade paths of IT Management Suite 7.6 on page 150.
To ensure that your upgrade runs without problems, you must first ensure that your
computer meets the minimum requirements for the upgrade.
See Upgrade checklist for IT Management Suite 7.6 on page 156.
Table 4-2
Process for upgrading to IT Management Suite 7.6
Step
Action
Description
Step 1
Upgrade the
Notification Server
computer.
You must first upgrade Notification Server to the latest

version, and then proceed to upgrade other components
in your ITMS environment.
See Upgrading to Notification Server 7.6 on page 155.
Step 2
Upgrade the
Symantec
Management Agent
After upgrading to Notification Servers in your

environment, you must enable the Symantec
Management Agent upgrade rollout policy.
See Upgrading Symantec Management Agent
on page 166.
Step 3
Upgrade site servers. You must then enable the Task Service and Package
Service upgrade rollout policy.
See Upgrading site servers on page 168.
154

Table 4-2
Process for upgrading to IT Management Suite 7.6 (continued)
Step
Action
Description
Step 4
Upgrade solution
plug-ins.
If you have upgraded to the ITMS solutions which have

plug-ins, ensure that you upgrade the individual solution
plug-ins.

Following is the process for upgrading from earlier versions of Notification Server
to the latest version of Notification Server on the same server hardware and with
the same configuration database.
Table 4-3
Process for upgrading to Notification Server 7.6
Step
Action
Description
Step 1
Prepare to upgrade.
Before you upgrade, you must prepare your ITMS

environment for the upgrade.
See Upgrade checklist for IT Management Suite 7.6
on page 156.
Step 2
Perform the upgrade. After you prepare your environment, you can perform
the actual upgrade.
See Performing upgrade to Notification Server 7.6
on page 161.
Step 3
Perform
post-upgrade tasks.
Verify that the upgrade has been successful and

perform additional post-upgrade tasks.
See Performing post-upgrade tasks on page 164.
(Optional)
Step 4
Set up cloud-enabled The process of setting up Cloud-enabled Management

management
after an upgrade or a migration is similar to the process
of setting up Cloud-enabled Management after a fresh
installation.
See About setting up Cloud-enabled Management
after upgrade or migration on page 166.
For more information about upgrade, see the following videos in Symantec Connect:
Upgrading SMP or its products through SIM
155

Upgrade checklist for IT Management Suite 7.6

Before you begin the upgrade, ensure that the computer on which you plan to
upgrade to the latest version of the IT Management Suite (ITMS) meets the minimum
requirements.
The minimum requirements for upgrading to the latest version of the IT Management
Suite are as follows:
Table 4-4
Upgrade checklist
Item
Checklist
Description
Supported upgrade paths.
Before you start the upgrade, ensure that either of the

supported upgrade release version is installed on your SMP
Server.
If you have SMP 7.1.x installed on your computer, then you
must upgrade to ITMS 7.1 SP2 MP1.1 before upgrading to
ITMS 7.6.
If you have SMP 7.5 SP1 installed on your computer, then
you must install the latest hot fix available in ITMS 7.5 SP1
HF5, and then upgrade to ITMS 7.6.
Note: To select all the latest available hot fixes for

installation, select the Select All latest hot fix versions
check box on the Install Hot Fixes page. See Installing
hot fixes on page 115.
If you do not want to install all the latest ITMS and non-ITMS
hot fixes, do not select the Select All latest hot fix versions
check box. You can then manually select the latest
ITMS-specific hot fixes for installation.
For more information about the supported upgrade paths
and the recommended upgrade installation, see the following
156

Table 4-4
Upgrade checklist (continued)
Item
Checklist
Description
Version of .Net Framework
Check the .Net Framework version that is installed on the

computer. If .Net Framework 4.5 or 4.5.1 is installed on the
computer, then execute the following steps:
Enable UAC, by executing the following steps:

Click Start > Control Panel. In the search box, type
uac, and then click Change User Account Control
settings.
To turn on UAC, move the slider to choose when you
want to be notified, and then click OK.
Administrator permission is required. If you are
prompted for an administrator password or
confirmation, type the password or provide
confirmation.
Pause the Native Image Generator activity, by executing
the following steps in the command prompt:
%SYSTEMDRIVE%\Windows\Microsoft.NET\
Framework64\v4.0.30319\ngen.exe queue
pause
Framework64\v2.0.50727\ngen.exe queue
pause
Framework\v2.0.50727\ngen.exe queue
pause
Stop Symantec Management Agent service and Monitor

service, by executing the following tasks:
On the computer, click Start > Run, and then type
services.msc. The Windows Services window is
displayed.
Right-click Symantec Management Agent > Stop.
Right-click Altiris Monitor Agent > Stop.
157

Table 4-4
Item
Checklist
Description
CMDB and ITMS server backup.
If required, perform a backup of the ITMS server and the

CMDB database.
On the computer that has ITMS 7.1 installed on it, click Start
> All Programs > Microsoft SQL Server > SQL Server
Management Studio. In the left pane, expand the
Databases folder, right-click the name of your database,
and then click Tasks > Back Up. In the Back up Database
dialog box, specify the following information, and then click
OK:
In the Backup type list, click Full.
In the Backup set area, in the Name field, enter a name

for your backup.
In the Destination area, add the location where you
want your backup file to be stored. This location must
be a secure storage location, and must not be on the
local computer.
For more information about how to back up the CMDB

database, see the following knowledge base article:
4
Legacy Agent Communication.
Verify the setting of Legacy Agent Communication before

starting the upgrade process.
After you upgrade to Notification Server 7.6, the Legacy
Agent Communication (LAC) mode controls if the computers
that use older versions of Symantec Management Agent
can communicate with the upgraded Notification Server. If
LAC mode is turned on, the legacy Symantec Management
Agents can communicate with Notification Server 7.6 and
then proceed with the upgrade.
To upgrade from 7.1 SP2 MP1.1 to 7.6, ensure that the
Legacy Agent Communication mode is enabled.
To upgrade from 7.5 SP1 HF5 to 7.6, record the existing
Legacy Agent Communication mode setting so that you can
implement similar setting after the upgrade.
To see the current Legacy Agent Communication mode
setting, on the Symantec Management Console, click
Settings > All Settings > Notification Server >
Notification Server Settings > Processing > Legacy
Agent Communication.
158

Table 4-4
Item
Checklist
Description
ITMS configuration settings.
Ensure that you record the ITMS configuration settings, so

that you can implement similar settings after the upgrade
in cases where the configuration options may change.
In the Symantec Management Console, click Settings >
All Settings , and record the following configuration settings:
Hierarchy replication in an ITMS

environment.
Task server settings under Task Settings.
Agent communication settings under Agents/Plug-ins.
Policies refresh settings and membership update settings

under Notification Server > Resource and Data Class
Settings > Resource Membership Update.
Ensure that the hierarchy replication is disabled on

Notification Servers before the upgrade.
The Installation Readiness Check in the Symantec
Installation Manager detects whether replication is enabled.
If the replication is enabled, you must to disable the
replication before you can proceed with the upgrade.
For more information on upgrading Notification Servers in
a hierarchy, see the following knowledge base articles:
Completion of the replication jobs in the Ensure that all the replication jobs are completed in your
ITMS environment.
ITMS environment before the upgrade.
In the Symantec Management Console, on the Reports
menu, click All Reports > Notification Server
Management > Server > Replication > Current
Replication Activity.
Verify that the Current Replication Activity report is blank.
If the report returns any results, you must wait until all
replications jobs have been completed before performing
the upgrade. You can also cancel all current replication jobs.
Replication data is sent during the next replication job.
159

Table 4-4
Item
Checklist
Description
Review logs before installing new ITMS Review Notification Server logs for errors or for warnings
components.
that may cause instability with the product.
To open the Log Viewer, click Start > All Programs >
Symantec > Diagnostics > Altiris Log Viewer.
Check Symantec logs for existing errors or warnings. If any
errors or warnings are found, take note and try to resolve
them before the upgrade.
See Viewing the Symantec Installation Manager logs
on page 147.
Run "NS.packagerefresh" task.
(Optional)
Run the scheduled task "NS.packagerefresh".

Click Start > All Programs > Accessories > System Tools
> Task Scheduler > Microsoft.
Select the NS package refresh task and click Run.
Resolve any warnings or errors that occur before upgrading
from ITMS 7.1 SP2 to ITMS 7.5.
Note: Before upgrading to the latest version of the IT

Management Suite solutions, ensure that the schedule of
the NS package refresh task is disabled.
10
Completion of critical tasks in the ITMS

environment.
Ensure that all critical tasks are completed in your ITMS

environment.
During an upgrade, all services are stopped and any
outstanding tasks may fail, report up incorrectly, or be
terminated.
For more information about how to find the tasks that are
currently running in your environment, see the following
160

Table 4-4
Item
Checklist
Description
11
Agent plug-in status.
Identify the agent plug-ins in your ITMS environment.

You need to be aware of all of your agent plug-ins. For
example, which plug-ins are enabled, which plug-ins are
you upgrading, and what are their dependencies.
All plug-in policies are disabled during upgrade, so you need
to turn them on.
Any plug-ins that are not upgraded may cause conflicts with
newer software. A best practice is to upgrade all components
at the same time to ensure full compatibility.
12
Check for pending restarts and restart

the computer, if required.
Check whether there are any pending restarts on the

computer from other installations or updates and restart the
computer if required before proceeding.
You must restart the computer to complete pending
operations before starting the upgrade process. The
Symantec Installation Manager checks for any pending
restart tasks when you launch theSymantec Installation
Manager and during the install readiness check.
Performing upgrade to Notification Server 7.6

This topic includes the procedural information about upgrading to Notification Server
7.6.
You must first upgrade Notification Server to the latest version, and then proceed
to upgrade other components in your ITMS environment.
161

To upgrade to Notification Server 7.6
Click Start > All Programs > Symantec > Symantec Installation Manager,
right-click the Symantec Installation Manager icon, and then click Run as
administrator.
On the Installed Products page, ensure that you have the latest updated
product listing file, and that upgrades to the currently-installed solutions are
available.
An updated product listing contains the latest IT Management Suite solutions
that are available for upgrade. During the latest product version release, the
latest product version is updated in the product listing file that is located at
http://www.solutionsam.com/solutions/pl/symantec_v2.pl.xml.zip. On detecting
an updated product listing file, the Symantec Installation Manager prompts you
to update the file. On confirming, the Symantec Installation Manager downloads
the updated product listing file, and checks whether there are any upgrades
available to the currently-installed solutions. If upgrades to currently-installed
solutions are available, they are displayed in green text next to Upgrade
installed products. For example, the text might read: 2 product upgrades
available.
You can also manually update the product listing file to check whether there
are any upgrades available for the currently-installed solutions.
To upgrade the installed solutions to the latest version of the IT Management

Suite, click Upgrade installed products.
On the Upgrade Installed Products page, in the Upgrade to product version

list, click the latest version of the Symantec Management Platform that you
want to upgrade to, and then click Next.
The latest version is the default version. However, you can select an earlier
version if, for example, your change control process dictates it.
The Symantec Management Platform version determines which compatible
products can be upgraded.
The Products to be upgraded list displays the solution or the platform

version for which compatible upgrades are available.
The list is populated based on the version of the platform that you select.
The Products to be uninstalled list displays the products that are

uninstalled because they are no longer compatible with the selected product
version.
If there are no incompatible products, this list is not displayed.
162

During off-box upgrade, the End-of-life (EOL) products or incompatible

products are not uninstalled or unconfigured.
Note: A few of the check boxes in the Products to be uninstalled list may be
grayed out and cannot be deselected. The remaining check boxes can be
deselected. The grayed-out check boxes denote the solutions for which either
no compatible upgrade is available, or a product has been deprecated or been
merged with another solution. For example, the Symantec Administrator SDK
has been merged with Symantec Management Platform. A check box that can
be deselected might be found next to a third-party solution. You can choose
to deselect the check box to prevent the solution from being uninstalled, but
the solution may not work with the product version that you upgrade to.
On being prompted to confirm to remove the incompatible solutions and proceed

with the upgrade to ITMS 7.6, click Yes.
On the Contact Information page, verify or modify your contact information,

and then click Next.
On the Install Readiness Check page, resolve the requirements that are
marked with a red icon, and then click Next.
You cannot proceed with the upgrade unless you resolve these requirements
first. Then click Check install readiness again to ensure that they are fixed.
See 9 on page 93.
On the Review Installation Details page, review the installation summary,

and then click Begin install.
10 (Optional) After the installation is completed, on the Back up Notification

Server Cryptographic Keys page, browse and select the location where you
want the key backups to be stored, specify the password to encrypt the
individual cryptographic keys, and then click Next.
The option to back up Notification Server cryptographic keys is displayed only
after the installation is completed. You can take a backup of Notification Server
cryptographic keys after the installation is completed. To take a backup after
the installation is completed, click Close on the Back up Notification Server
Cryptographic Keys page.
163

11 (Optional) On the Product Licensing page, click Install Licenses, select the
product license file, and then click Next.
You can install the product licenses after the installation is completed. To
specify the product licenses after the installation is completed, click Close on
the Product Licensing page.
12 On the Installation Complete page, select either one or all of the following
options, and then click Finish.
Select the Run Notification Server Migration Wizard check box to run
the migration wizard. A dialog box appears that displays the instructions
for migrating Notification Server 6.x or Symantec Management Platform
7.0 data.
If you have installed the migration wizard, the Run Notification Server
Migration Wizard check box is selected by default on the Installation
Complete page.
To proceed with 6.x migration, see the chapter Migrating from Notification
Server 6.x in the Altiris IT Management Suite from Symantec Migration
To proceed with 7.0 migration, see the chapter Migrating from Symantec
Management Platform 7.0 in the Altiris IT Management Suite from Symantec
Migration Guide version 7.0 to 7.5.
Select the Launch Symantec Management Console check box to launch

the Symantec Management Console on the Notification Server computer.
The Internet Information Services (IIS) Manager redirects the console
request to the appropriate link with https://<IP address>/altiris/. You
can manually launch the Web console either from the Start menu of the
computer. Alternatively, you can manually launch the Web console if you
know the IP address of the Notification Server computer. For example:
https://<IP address>/altiris/console.
Performing post-upgrade tasks

After the upgrade, you must perform additional tasks to ensure that your ITMS 7.6
environment functions correctly. The tasks also let you revert to the ITMS
environment configurations that you had set up before the upgrade. You use the
Symantec Management Console of Notification Server to execute these tasks.
164

To ensure a successful upgrade to IT Management Suite 7.6
In the Symantec Management Console, click Settings, and compare the

configuration settings to the ones you recorded when you prepared to upgrade.
Revert to the settings that you recorded while preparing to upgrade to ITMS
7.6 to keep your system running as it did before the upgrade.
If you had hierarchy implemented in your environment previously and had

disabled the hierarchy during an upgrade, you must upgrade all the servers in
the hierarchy.
The recommended practice is to upgrade Notification Servers starting from the
lowest level to the highest level in the hierarchy. This means that you upgrade
the lowest-level child Notification Servers and gradually upgrade the servers
in the hierarchy till you reach the parent Notification Server. Ensure that each
child Notification Server is upgraded to a higher version before its parent. You
do not need to break any hierarchy relationships in the process. For more
information, see www.symantec.com/docs/HOWTO21657.
Recreate a hierarchical relationship between Notification Servers in your

environment, and enable the hierarchy replication that you had disabled before
the upgrade.
For more information on setting up hierarchy and upgrading Notification Servers
in a hierarchy, see the following knowledge base articles:
Review Notification Server logs after the upgrade for errors or for warnings
that may cause instability with the product.
To open the Log Viewer, click Start > All Programs > Symantec > Diagnostics
> Altiris Log Viewer, to open the Log Viewer.
Check Symantec logs for existing errors or warnings. If any errors or warnings
are found, take note and try to resolve them after the upgrade.
Perform a database defragmentation of the Symantec CMDB database to

compact the database and increase the disk performance.
For more information on performing a database defragmentation , see the
www.symantec.com/docs/HOWTO8589 or the Microsoft TechNet site.
For further information on configuring your environment, refer to the IT Management

Suite Administration Guide.
165

About setting up Cloud-enabled Management after upgrade or

migration
The process of setting up Cloud-enabled Management after an upgrade or a
migration is similar to the process of setting up Cloud-enabled Management after
a fresh installation. You configure Notification Server and Symantec Management
Agents to use HTTPS, configure Internet gateway, and install Symantec
Management Agent on disconnected computers. To bring the existing Symantec
Management Agents under Cloud-enabled Management, make sure that you add
these computers to the Cloud-enabled Management Settings policy.
For more information about setting up Cloud-enabled Management, see the IT
Management Suite Administration Guide.

After upgrade to Notification Server 7.6, you can upgrade the Symantec Management
Agent (SMA) on the client computers to SMA 7.6. Additionally, you must also
upgrade the solution plug-ins to the same version of the SMA. An older version of
SMA can communicate with a latest version of SMP using the Legacy Agent
Communication (LAC) mode, but Symantec recommends that you upgrade the
SMA and the solution plug-ins to the latest version. Ensure that the SMA and solution
plug-ins are always of the same release version.
You must verify the setting of Legacy Agent Communication before starting the
upgrade process.
After you upgrade to Notification Server 7.6, the Legacy Agent Communication
(LAC) mode controls if the computers that use older versions of Symantec
Management Agent can communicate with the upgraded Notification Server. If LAC
mode is turned on, the legacy Symantec Management Agents can communicate
with Notification Server 7.6 and then proceed with the upgrade.
To upgrade from 7.1 SP2 MP1.1 to 7.6, ensure that the Legacy Agent
Communication mode is enabled.
To upgrade from 7.5 SP1 HF5 to 7.6, record the existing Legacy Agent
Communication mode setting so that you can implement similar setting after the
upgrade.
To see the current Legacy Agent Communication mode setting, on the Symantec
Management Console, click Settings > All Settings > Notification Server >
Notification Server Settings > Processing > Legacy Agent Communication.
166

To upgrade to Symantec Management Agent 7.6
Open the Symantec Management Console on Notification Server 7.6.
Execute any of the following tasks:
To access the 64-bit Symantec Management Agent upgrade policy, click

Settings > All Settings. You then navigate to Agent/Plug-ins > Symantec
Management Agent > Windows > Site Server > Symantec Management
Agent for Windows x64 (Site Server Only) - Upgrade.
To access the 32-bit Symantec Management Agent upgrade policy, click

Settings > All Settings. You then navigate to Agent/Plug-ins > Symantec
Management Agent > Windows > Site Server > Symantec Management
Agent for Windows x86 (Site Server Only).
Specify your preferences, the target computer, and then click On on the top-right
corner of the right pane.
After the Symantec Management Agent on a site server is upgraded, the agent
sends out registration request to Notification Server to establish the communication.
You can view and manage the registration status in the Agent Registration Status
report.
For more information, See About agent registration after an upgrade on page 167.
About agent registration after an upgrade

The agent registration feature requires a client computer to be allowed to
communicate with Notification Server before this Notification Server can manage
the client computer. The agent registration feature works only for the agents that
are upgraded to the 7.5 version.
After you upgrade your Notification Server to version 7.5, the Legacy Agent
Communication (LAC) mode controls if the computers that use older versions of
Symantec Management Agent can communicate with the upgraded Notification
Server. If LAC mode is turned on, the legacy agents can communicate with
Notification Server and upgrade. Note that if you upgrade from 7.1 SP2 or earlier
7.1 versions, LAC mode is turned on by default.
After Symantec Management Agent is upgraded on your client computers, each
upgraded agent sends a registration request to Notification Server to establish
communication.
You can check and manage the registration requests in the Symantec Management
Console, on the Agent Registration Status page, under Reports > Notification
Server Management > Registration.
167

In addition to manually managing the registration requests, you can configure agent
registration policies that automatically allow or block the requests. By default, an
agent registration policy that allows all incoming requests is enabled on Notification
Server. During the upgrade process, Symantec recommends that you use only the
default agent registration policy. In this case, the client computers that you are
currently managing are automatically allowed to communicate with the upgraded
Notification Server. After most of the computers have been approved, you can
create more restrictive agent registration policies.
You can create an Agent Registration Policy in the Symantec Management
Console, under Settings > Agents/Plug-ins > Symantec Management Agent >
Settings > Registration Policies.
After you finish the upgrade process, Symantec recommends turning off LAC mode
on Notification Server.
You can manage LAC mode in the Symantec Management Console, on the
Notification Server Settings page, under Settings > Notification Server.
For more information, see the topics about creating an agent registration policy,
viewing the Agent Registration Status report, and Legacy Agent Communication in
the IT Management Suite Administration Guide.
Viewing the Legacy Agent Registration Requests report

The Legacy Agent Registration Requests report is a table that displays information
about legacy agents sending registration requests to Notification Server when
Legacy Agent Communication mode is disabled. You can use the data from the
report to schedule push installation to those client computers that have legacy agent
installed.
When push installation is executed, the data in Legacy Agent Registration
Requests report is removed. You can see the registration status in the Agent
Registration Status report.
Note: Legacy agent is a computer with Symantec Management Agent's version
lower or equal to 7.1 SP2.

You need to upgrade your site servers in a site before you redirect your managed
computers in the site to Notification Server 7.6. To upgrade a site server, redirect
it to the Notification Server 7.6 and upgrade its Symantec Management Agent.
Ensure the policies that upgrade the services are enabled to upgrade the site
168

servers. The Windows Package Server Agent Upgrade policy upgrades the
package servers. The Task Service Upgrade policy upgrades the task servers.
Step 1: Enable the Task Service Upgrade policy

After the Symantec Management Agent is upgraded to 7.6 version, you must enable
the Task Service upgrade rollout policy
To enable the policy
Open the Symantec Management Console on the 7.6 Release Preview

Notification Server.
Execute any of the following tasks:
To access the 64-bit task server agent upgrade policy, on the Settings
menu of the Symantec Management Console, click All Settings. You then
navigate to Notification Server > Site Server Settings > Task Service >
Advanced > Task Service Upgrade (x64).
To access the 32-bit task server agent upgrade policy, on the Settings
menu of the Symantec Management Console, click All Settings. You then
navigate to Notification Server > Site Server Settings > Task Service >
Advanced > Task Service Upgrade (x86).
Step 2: Enable the Package Service Upgrade policy

You can then enable the Package Service upgrade rollout policy. After a package
server establishes communication with Notification Server, it downloads any new
7.6 system-based packages that Notification Server 7.6 hosts. These packages
include all solution plug-ins. Any package that has not changed is not re-downloaded.
To enable the policy
Open the Symantec Management Console on Notification Server 7.6.
On the Settings menu, click All Settings. You then navigate to Settings >
Notification Server > Site Server Settings > Package Service > Advanced
> Windows > Windows Package Server Agent Upgrade.
The site servers are not upgraded until you enable the Symantec Management
Agent upgrade policy, Task Service upgrade policy, and Package Service upgrade
policy. If you do not want to upgrade the site servers but still want them to
communicate with the upgraded Notification Server, enable the Legacy Account
Communication. On the Symantec Management Console, click Settings > All Settings
169

> Notification Server/Notification Server Settings - Processing Tab). On the Settings

menu of the Symantec Management Console, click All Settings. You then navigate
to Notification Server > Notification Server Settings > Processing > Legacy
Agent Communication. Click On on the top-right corner of the right pane to enable
the legacy agent communication.
Symantec recommends you to keep the Legacy Agent Communication mode
enabled until all site servers are upgraded.
170
Chapter
Migrating Notification
Server data from Windows
Server 2008 R2 to Windows
Server 2012 R2
Migrating Notification Server data from Windows Server 2008 R2 to Windows

Server 2012 R2
Backing up Notification Server data from Windows Server 2008 R2
Migrating Notification Server data to Windows Server 2012 R2
Migrating Notification Server data from Windows

Server 2008 R2 to Windows Server 2012 R2
Migration is performed in the following scenarios:
You want to install IT Management Suite 7.6 on a new computer with Windows
Server 2012 R2 and SQL 2012 or 2014.
You want to install IT Management Suite 7.6 on a new computer with Windows
Server 2012 R2 and reuse SQL 2008 that you used for IT Management Suite
7.1 SP2 or IT Management Suite 7.5 SP1 HF5.
The migration process consists of the following phases:
Prepare
Migrating Notification Server data from Windows Server 2008 R2 to Windows Server 2012 R2
To minimize downtime and ensure success, create a migration plan for your
specific environment. Back up your existing data and create a test environment
for evaluating and validating the entire installation and migration process.
Install and migrate.

During this phase, you install Symantec Management Platform 7.6 on a computer
running the Windows Server 2012 R2 operating system. You also migrate
existing Symantec Management Platform 7.5 SP1 HF5 data from your previous
environment to Symantec Management Platform 7.6. You might have to manually
move some solution-specific data to Symantec Management Platform 7.6.
To refer to solutions that require manual copying of data, refer to the IT
Management Suite Migration Guide from the following location:
Validate
During the validation phase you confirm that you have set up and configured
the new Symantec Management Platform and solutions according to your
requirements. The migration wizard verifies the success of the data it imports.
However, you must browse to the migrated data such as policies, reports, and
packages and verify that their state has retained from the earlier set configuration.
After you validate the success of the installation and data migration, the groups
of managed computers are redirected to report to the new Notification Server
with Windows Server 2012 R2. Once the managed computers report to the new
server, use an agent upgrade policy to upgrade their agents.
Migrating the Notification Server computer data to Windows

Server 2012 R2
Before you migrate the Notification Server computer data from a Windows Server
2008 R2 computer with SQL 2008, install IT Management Suite 7.6 on a new server
that has Windows Server 2012 R2 and SQL 2012 or 2014.
If you plan to reuse the SQL 2008 database that you used in IT Management Suite
7.1 SP2 or IT Management Suite 7.5 SP1HF5, install IT Management Suite 7.6 on
a new server that has Windows Server 2012 R2 and connect to the SQL 2008
database.
Use the following steps to migrate Notification Server data from Windows Server
2008 R2 to Windows Server 2012 R2:
172
Table 5-1
Steps to migrate Notifications Server data to Windows Server 2012

R2
Steps
Action
Description
Step 1
Backup Notification Server data from your You must back up your Notification Server data
older Windows Server 2008 R2 computer. from Windows Server 2008 R2 computer before
you shut down the server.
See Backing up Notification Server data from
Windows Server 2008 R2 on page 173.
Step 2
Step 3
Install Symantec Management Platform

7.6 on a Windows Server 2012 R2
computer.
Before you migrate your Notification Server data,

install the new Symantec Management Platform.
Use the same server name and IP address for
your new server so that the client computers can
connect to the new server after the old server is
shut down and the new server is up.
Migrate the Notification Server computer Migrate the data from Windows Server 2008 R2
data to a Windows Server 2012 R2
to Windows Server 2012 R2 before your rollout
computer.
upgrade policies to the clients computers.
See Migrating Notification Server data to
Windows Server 2012 R2 on page 177.
Backing up Notification Server data from Windows

Server 2008 R2
Use the following steps to backup your Notification Server data from Windows
Server 2008 R2:
Table 5-2
Steps to perform on the Windows Server 2008 R2
Steps
Action
Step 1
Backup Configuration Management

Database (CMDB)
Description
You must backup CMDB from the server with

Windows Server 2008 R2 before beginning the
Note: This step is not required if you plan migration process. Store the backup at a secure
location.
to reuse your previous SQL 2008
database on the new computer with
See the section called Backing up the
Windows Server 2012 R2. When you
Configuration Management Database
install IT Management Suite 7.6 on
on page 175.
Windows Server 2012 R2, connect to the
SQL 2008 database.
173
Table 5-2
Steps to perform on the Windows Server 2008 R2 (continued)
Steps
Action
Description
Step 2
Run the Migration wizard
When you install Symantec Installation Manager,

to install the migration wizard, from the Install
optional components page, select and install
the Install Migration Wizard Components
option. You can use the migration wizard to
transfer the data from your old server to the new
server.
The migration wizard lets you migrate the following
Symantec Management Platform data:
KMS keys
Credential manager keys
Selected core settings
Email settings
Security roles
Some event log registry keys
Note: The migration wizard verifies the success

of the data it imports. However, you should browse
to the migrated data such as policies, reports, and
packages and verify their state.
See the section called Using the migration wizard
to create a data store file on page 176.
Alternatively, you can also refer to the following
For older versions of the Migration wizard, refer
to the following article:
http://www.symantec.com/docs/TECH174229
174
Table 5-2
Steps to perform on the Windows Server 2008 R2 (continued)
Steps
Action
Description
Step 3
Copy the data manually for few IT

Management solutions
You must manually migrate the data of the

following products:
Inventory Solution
Barcode Solution
Real-time System Management Solution
Real-Time Console Infrastructure Solution
Store the backup at a secure location.

For more information see the topics for individual
IT Management Suite solutions in the IT
Management Suite Migration Guide from the
following location:
Step 4
Shut down the Windows Server 2008 R2 After backing up all your Symantec Management
computer
Platform data from the Windows Server 2008 R2
computer, shut down the server.
Backing up the Configuration Management Database

Use the following steps to backup the Configuration Management Database (CMDB)
on the Windows Server 2008 R2 computer:
Open Microsoft SQL Manager Studio.
In the left pane, expand the Databases folder.
In the left pane, under Databases, right-click the name of your database.
In the right-click menu, click Tasks > Back Up.
In the Back up Database dialog box, in the Backup type drop-down list, click
Full.
In the Backup set section, enter a name for your backup.
In the Destination section, add the location where you want your backup file
to be stored.
This location should be a secure storage location, and should not be on the
local computer.
Click OK.
175
Using the migration wizard to create a data store file

If you have not installed the migration wizard during installation, open Symantec
Installation Manager and from the Install optional components page, select and
install the Install Migration Wizard Components option.
Install and run the migration wizard on the Symantec Management Platform
7.5 SP1 HF5 server.
After the migration wizard is installed on the Symantec Management Platform,
it starts in export mode. You can also manually run NSUpgradewizard.exe to
start the migration wizard manually. The migration wizard EXE is in the
C:\Program Files\Altiris\Upgrade directory by default.
Note: To run the migration wizard, you must be a member of the local
administrators group.
If the Welcome page of the migration wizard appears, click Next.
On the Export / Import Task Selection page, specify a name and location for
the data store file, and click Next.
The default name has three parts: the word Store, the date, and the time. The
data store extension must be .adb.
On the Password Protection page, if you want to encrypt the data, enter a
password.
You must then use this password when you import the data on the Symantec
Management Platform server.
On the Exporter Configuration page, select the data to export, and click Next.
The options on the Exporter Configuration page are as follows:
Products
Lets you select the products whose data you want to

migrate. Data is exported only for the products that are
checked.
Exporters
Displays the exporters for the product that you select in

the Products section. Data is exported only for the
exporters that are checked in the Enabled column.
176
Filters
Displays a dialog box that lets you filter the data that an
exporter 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.
Symantec recommends selecting all of the available data.
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 export.
To view an explanation of why the data is not included, click in the Message
column.
If the product readiness warning message appears, click Yes.

This message indicates that not all products meet the product readiness check.
To view the explanations for any product readiness warnings, click No, and
then click Back.
On the Task Summary page, verify that the migration wizard is about to perform
the correct tasks, and click Next.
When the message that the data export has completed successfully appears,
click OK.
If the data is not exported successfully, a message with instructions appears.
10 (Optional) To display details about each action, check Show Details.

11 Click Finish.
Migrating Notification Server data to Windows Server

2012 R2
Use the following steps to migrate Notification Server data from Windows Server
2008 R2 to Windows Server 2012 R2:
177
Table 5-3
Steps to perform on the Windows Server 2012 computer
Steps
Action
Description
Step 1
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.
Step 2
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 SP1
server.
If you host Microsoft SQL Server on-box, install it
on the Symantec Management Platform 7.6 server
and copy the backed-up database to the
Symantec Management Platform 7.6 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.
See the section called Restoring the CMDB data
on page 179.
Step 3
Import the data from the migration wizard Import the migration data store file to Symantec
data store file
Management Platform 7.6 server.
See the section called Importing the data from
the migration wizard data store file on page 179.
Step 4
Copy the manual data to Windows Server From the backup location, copy the data of the
2012 R2 computer
solutions that you copied manually.
For more information see the topics for individual
IT Management Suite solutions in the IT
Management Suite Migration Guide from the
following location:
178
Table 5-3
Steps to perform on the Windows Server 2012 computer (continued)
Steps
Action
Description
Step 5
View and manage the agent registration The Agent Registration Status report lets you
status to verify successful registration.
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
See the section called Viewing and managing
the agent registration status on page 181.
Restoring the CMDB data

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 SP1 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
1
Do one of the following to start the migration wizard in the import mode:
Install the migration wizard on the Symantec Management Platform 7.6

server with Symantec Installation Manager. By default, the migration wizard
starts after it is installed.
Run the migration wizard EXE manually.
179
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 SP1 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:
Products
Lets you select the products whose data you want to

migrate. Data is imported only for the products that are
checked.
Importers
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.
Filters
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.
180
(Optional) To display each actions sub-actions, check Show Details.
10 Click Finish.
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
181
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.
182
(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.
Allow
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.
Block
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.
Revoke
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.
183
Chapter
Migrating to IT
Management Suite 7.6
About migrating to IT Management Suite 7.6
Readiness checklist for IT Management Suite migration
Post-migration checklist for IT Management Suite migration
About migrating to IT Management Suite 7.6

A migration is when you install the latest version of the IT Management Suite
solutions on a new computer, and then migrate the data from the earlier ITMS
solutions to the latest version of the application.
You can perform a migration from IT Management Suite 6.x/7.0 to IT Management
Suite 7.6 under any of the following situations:
When you want to install the latest available version of IT Management Suite
on a new hardware or consolidated hardware (off box)
When you update the operating system of the computer
When you configure a new Configuration Management Database (CMDB)
When you plan to replace IT Management Suite 7.0 with IT Management Suite
7.6
When you plan to replace IT Management Suite 6.x with IT Management Suite
7.6
Note that the direct migration from IT Management Suite 6.x/7.0 to IT Management
Suite 7.6 is not supported.
Migrating to IT Management Suite 7.6

You must migrate the Notification Server 6.x or 7.0 data to either Notification Server
7.1 SP2 or Notification Server 7.5. After migrating the data, you must upgrade to
Notification Server 7.5 SP1. The migration process and the type of data that is
migrated depends on whether you use Notification Server 6.x or Symantec
Management Platform 7.0.
For more information about migration to ITMS, see any of the following documents:
Altiris IT Management Suite from Symantec Migration Guide version 6.x to 7.1
SP2
Altiris IT Management Suite from Symantec Migration Guide version 7.0 to 7.1
SP2
Altiris IT Management Suite from Symantec Migration Guide version 7.0 to 7.5.
Altiris IT Management Suite from Symantec Migration Guide version 6.x to 7.5.
Readiness checklist for IT Management Suite

migration
The following tables provide a readiness checklist for IT Management Suite migration
before and while you install IT Management Suite:
Table 6-1 Migration checklist - Before you install IT Management Suite 7.5
Table 6-2 Migration checklist - While you install IT Management Suite 7.5
Table 6-1
Migration checklist - Before you install IT Management Suite 7.5
Task
Description
Create a backup.
Create a backup of the computer with

Symantec Management Platform and the
CMDB database.
Review logs before installing new solutions. Review the Symantec Management Platform
logs for the errors or the warnings.
If you find errors or warnings, take note of
them and try to resolve them.
Ensure that the computer with IT
Management Suite 7.5 has a unique name
and IP address.
You must give the computer with IT

Management Suite 7.5 a name and an IP
address that is different from the name and
IP address of the computer with Notification
Server 6.x or IT Management Suite 7.0.
185

Table 6-1

(continued)
Task
Description
Identify the limitations of mixed-mode.
Symantec Management Platform 7.5 does

not support mixed mode. A Symantec
Management Platform 7.0 server or
Notification Server 6.x cannot communicate
with a Symantec Management Platform 7.5
server.
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.5,
you must have Notification Server 6.0 R13 or
later and the latest solutions installed. If you
do not have the latest version of Notification
Server 6.x, then you must first upgrade to the
latest version.
(Only for migration from Notification Server

6.x)
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
or later before you migrate to Symantec
Management Platform 7.5.
Copy the product licenses.
Copy the product licenses to a location that

is accessible from the computer that has IT
Management Suite 7.5.
Recreate Windows server user accounts.
You must recreate the Windows server user

accounts on the computer where you install
IT Management Suite 7.5.
186

Table 6-1

(continued)
Task
Description
Use the migration wizard to create a data

store file.
You must install the IT Management Suite

migration wizard on the computer with
Notification Server 6.x or IT Management
Suite 7.0 and create a data store file.
By default, a data store file is created in the
Altiris\Upgrade\Data directory. Copy
the data store file to a location that Symantec
Management Platform 7.5 computer can
access. You can also create a backup by
copying the file to another location.
For more information, see the following
Copy the solutions-specific files.
Table 6-2
You must manually copy solution-specific files

and settings to a secure location that is
accessible from the computer with IT
Management suite 7.5.
Migration checklist - While you install IT Management Suite 7.5
Task
Description
Ensure product parity.
From IT Management Suite version 7.1, a few

products replace or absorb 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 computer with Notification
Server 6.x or IT Management Suite 7.0.
Create a new database.
When you install the Symantec Management

Platform 7.5 products, you must create a new
database. You cannot run Symantec
Management Platform 7.5 against the 6.x
database.
(Only for migration from Notification Server

6.x)
Schema changes were made to the database

to increase the speed and to unify the
structure of the database.
187

Table 6-2
Migration checklist - While you install IT Management Suite 7.5

(continued)
Task
Description
Use same SQL collation.
When you restore CMDB, use the same

collation that was used for Symantec
(Only for migration from IT Management Suite
Management Platform 7.0. You can restore
7.0)
the database to the same instance of the SQL
Server that Notification Server 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.
Use same SIM installation path on 7.0 and When you install Symantec Installation
7.5 Symantec Management Platform server. Manager 7.5, you need to use the same
installation path that you used on the
(Only for migration from IT Management Suite
computer with Symantec Installation Manager
7.0)
7.0.
If you change the installation path, you cannot
upgrade the Symantec Management Agent
and the agent plug-ins.
Import the data from data store file using the Use the IT Management Suite migration
migration wizard.
wizard to import the data from the data store
file that you created on the previous computer
that had Notification Server 6.x or IT
Management Suite 7.0.
Post-migration checklist for IT Management Suite

migration
The following table provides a checklist for the migration tasks you must do after
you install IT Management Suite 7.5 and migrate the data:
188

Table 6-3
Migration checklist - After you install IT Management Suite and

migrate your data
Task
Description
Verify the migrated data manually.
You must browse the migrated data such as

policies, reports, and packages and verify
their state.
Redirect the managed computers.
After you validate the migrated data, redirect

the groups of managed computers to report
to the new Notification Server 7.5. Once the
managed computers report to Notification
Server 7.5, use an agent upgrade policy to
upgrade their agents.
Recreate hierarchical relationships.
After installing IT Management Suite, if you

have used hierarchical relationships and still
require them, you must recreate hierarchical
relationships and enable replication.
189

Table 6-3
Migration checklist - After you install IT Management Suite and

migrate your data (continued)
Task
Description
Configure additional network ports for

performing different communication tasks.
Verify and configure the additional network

ports for executing specific communication
tasks in your environment.
Notification Server and endpoints
communicate with each other using the
standard web ports. By default, the standard
web ports, such as port 80 for HTTP
communication and port 443 for HTTPS
communication, are configured on the
computers.
Apart from the standard web ports that are
configured on computers, you might have to
configure additional network ports to perform
specific communication tasks. For example,
the following tasks require configuration of
additional network ports on the computer:
Enabling the hierarchy and replication on

the Notification Server computer.
Downloading packages from Notification
Server or package server on the client
computer.
Downloading the agent for UNIX, Linux,
or Mac operating systems from
Notification Server on the client computer.
The following knowledge base article provides

information about all the additional
communication tasks and their associated
network ports that you can configure in your
IT Management Suite 7.5 environment:
190
Chapter
Troubleshooting
information
Troubleshooting installation issues
Troubleshooting upgrade issues

The troubleshooting tips related to the installation and configurations of the IT
Management Suite 7.6 are as follows:
Table 7-1
Issue or error message
Description
The following error message The Symantec Installation Manager

appears:
is not compatible with the Federal
Information Processing Standard
Symantec Installation
(FIPS). The FIPS cryptographic
Manager failed to
module conflicts with the
initialize. See log
Installation Requirements Checks
for details.
(IRCs), which are encrypted.
Workaround
To execute the Symantec Installation Manager on
a server, you must to disable FIPS on that server.
For information on how to disable FIPS on the
server, see the following article:
TECH159352.
Troubleshooting information
Table 7-1
Troubleshooting installation issues (continued)
Description
The following error message Exception occurs in the Symantec

is displayed:
Installation Manager when an
invalid certificate is imported.
The certificate failed
The SSL certificate that you
the validity tests.
imported using the Symantec
Installation Manager does not pass
the validation compliance points.
Workaround
You must ensure that the SSL certificate that you
use for configuring HTTPS communication passes
the following validation compliance checks:
Certificate is not between the not before and

not after dates.
The SSL certificate is valid between the from
to date and up to date, and these certificate
validity dates must be configured correctly.
Certificate must use supported signature
algorithm.
The SSL certificate passes the validation
compliance if any of the following hash sets is
used in the signature algorithm: sha1RSA,
sha256RSA, sha384RSA, sha512RSA.
Certificate must use supported key exchange

algorithm.
The SSL certificate must support the
RSA-PKCS1-KeyEx key exchange algorithm.
Certificate name must contain the local system

Fully Qualified Domain Name (FQDN).
The Subject Alternative Name (SAN) of the
SSL certificate must contain the FQDN of the
computer where you plan to install the IT
Management Suite.
Certificate key exchange key must not too
small: Minimum recommended 1024.
The key exchange of the SSL certificate must
be greater than or equal to 1024 bits.
Extended Key Usage information is present
and it must indicate that the certificate support
server authentication.
The SSL certificate must have the Extended
Key Usage information with the Server
Authentication key set to 1.3.6.1.5.5.7.3.1.
Certificate must have a valid signature.
The SSL certificate must be valid as per the
cryptography principles.
The Symantec Installation Manager throws

validation errors if the SSL certificate does not pass
any of the validation checks.
192
Table 7-1
Troubleshooting installation issues (continued)
Description
The following error message Exception occurs in the Symantec

is displayed:
Installation Manager when an
invalid certificate is imported.
The certificate failed
The SSL certificate that you
the validity tests.
imported using the Symantec
Installation Manager does not pass
the validation compliance points.
Workaround
Additionally, you must ensure the following points
while importing a valid SSL certificate using the
Symantec Installation Manager:
A certificate with .pfx file extension must be

selected for import.
Symantec recommends that you do not import
a .cer file type.
The .pfx certificate file must be password

protected.
The password can be entered when you import
the SSL certificate.
The SSL certificate must be a trusted
certificate.
Symantec recommends that you do not import
a certificate that is not a trusted file. For
example, a file that shows the following error
message:
This certificate is not trusted.
To enable trust, install this
certificate in the Trusted Root
Certification Authorities store.
The IT Management Suite

(ITMS) installation or upgrade
fails if the Symantec
Management Platform
website is configured to
Require SSL option with
Client Certificates: Require
option.
After the Symantec Management

Platform (SMP) website is
configured to Require SSL option
with Client Certificates: Require
option in the Internet Information
Services (IIS) Manager, the
configuration does not start and the
installation process or the upgrade
process fails. Additionally, a
forbidden (403) error is displayed
and an associated warning is
reported in the Altiris Log Viewer.
Workaround: Before you start a fresh installation

of ITMS solutions or an upgrade to ITMS 7.5, you
must check the SSL configuration for SMP website.
In the IIS Manager, for the SMP website, ensure
that you do not select the Client Certificates:
Require option when the Require SSL option is
selected.
For more information on IT Management diagnostics tools, download the IT

Management Suite Technical Resource Kit at
www.symantec.com/docs/HOWTO77027.
193

The troubleshooting tips related to the upgrade to the IT Management Suite 7.6 are
as follows:
Table 7-2
Description
Workaround or knowledge base article link
Upgrade process fails

because of missing registry
entries or corrupted
registry file.
SIM automatically creates a

registry backup in the support
folder before starting the
installation, upgrade, or hot
fix installation of Symantec
Management Platform or IT
Management Suite solutions . By
default, the registry backup is
available at the following location:
If you encounter errors because of missing registry

entries or corrupted registry file, then execute any
of the following workarounds:
Restore the previous registry entries and then

execute the installation process or
upgrade process. To restore the previous
registry entries, navigate to the registry
backup and then double-click the latest
AIMRoot.reg file.
C:\Program
Files\Altiris\Symantec
Installation
Manager\Support
Create new registry keys.

You can create new registry keys for existing
database validation for upgrade to 7.6, for
partial upgrade validation on Install New
Products page, and for pending restart check.
194
Table 7-2
Troubleshooting upgrade issues (continued)
Description
Upgrade to 7.6 fails because If you encounter errors during

of failed existing database
upgrade to 7.6 because of failed
validation.
existing database validation, then
you can create a new Windows
registry key to cancel the validation
of existing database.

To create registry key for existing database
validation for upgrade to 7.5 SP1, execute the
following steps:
1
Click Start, click Run, type regedit in the

Open box, and then click OK. The Windows
Registry Editor window is displayed.
Navigate to the following location:

HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\AIM
Right-click AIM > New > Key, and then

specify IgnorAltaDBUpgradeValidation as
the key name.
Right-click IgnorAltaDBUpgradeValidation
> New > DWORD (32-bit) Value, and then
specify Enable as the value name.
Right-click Enable > Modify, and then type

1 in the value data.
Specify 1 as the Enable value to skip the
validation of existing database. Specify 0 as
the Enable value to perform the validation of
existing database.
Click OK.
195
Table 7-2
Description

of failed partial upgrade
upgrade to 7.6 because of failed
check.
partial upgrade check, then you
can create a new Windows registry
key to cancel the partial upgrade
check.

To create registry key for partial upgrade
validation on Install New Products page,
execute the following steps:
1



specify UpgradePopupRequired as the key
name.
Right-click UpgradePopupRequired > New

> DWORD (32-bit) Value, and then specify
Display as the value name.
Right-click Display > Modify, and then type

Specify 1 as the Display value to skip partial
upgrade check. Specify 0 as the Display value
to perform the partial upgrade check.
Click OK.
196
Table 7-2
Description

SIM has detected pending
upgrade to 7.6 because SIM has
restarts.
detected pending restarts on the
computer, then you can create a
new Windows registry key to
cancel the detection of pending
restarts.

To create registry key for pending restart check,
execute the following steps:
1



specify IgnorPendingReboot as the key
name.
Right-click IgnorPendingReboot > New >

DWORD (32-bit) Value, and then specify
Display as the value name.
Right-click Enable > Modify, and then type

Specify 1 as the Enable value to skip pending
restart check. Specify 0 as the Enable value
to perform the pending restart check.
6
Upgrade from ITMS 7.1 SP2
to ITMS 7.5 fails because of
symhelp_7_5_x64.msi
install failure.
IT Management Suite (ITMS)

7.5 does not support different
versions of the Symantec
Management Agent (SMA)
and plug-ins.
Click OK.
The upgrade fails because of .NET

framework configuration issue on
the SMP server. .NET Framework
3.5.1 or later along with ASP.NET
must be installed on the computer
on which ITMS is installed.
Additionally, the Classic.NET
AppPool must be running under
.NET framework for the Altiris web
service to run successfully.
Workaround: Ensure that .NET framework

configuration is correct for the upgrade to complete.
For more information about .NET framework
configuration, see the following knowledge base
article:
If the SMA version and plug-in

version are different after you
upgrade to ITMS 7.5, then this
scenario is not supported on the
ITMS 7.5 environment.
Workaround: After you upgrade to ITMS 7.5, you

must upgrade the SMA on client computers to SMA
7.5. Additionally, you must upgrade the plug-ins to
the latest versions that are available in ITMS 7.5.
TECH212756
197
Appendix
Reference topics
This appendix includes the following topics:
Solutions of IT Management Suite
About Cloud-enabled Management
Symantec Installation Manager shortcut keys
IT Management solutions and their dependent solutions

Table A-1
IT Management Suite solutions and components
Suite/Platform
Solution/Component Description
Asset Management
Suite
Asset Management
Solution
Asset Management Solution lets you set up and manage different

asset management processes. It helps you accurately value your
assets, track ownership, and maintain associations with related
documents. Additionally, it aligns with ITIL standards.
CMDB Solution
CMDB Solution lets you model configuration items, resources,

and the relationships between them in a central database. It lets
you facilitate the identification of all components and relationships,
and instigate any required changes. The solution actively manages
resources according to user-specified instructions in jobs, tasks,
configuration policies, and custom CMDB rules.
Deployment Solution
Deployment Solution helps to reduce the cost of deploying and

managing servers, desktops, and notebooks from a centralized
location in your environment. It offers operating system
deployment, configuration, personality migration of computers,
and software deployment across different hardware platforms and
operating systems.
Client Management
Suite
Reference topics
Table A-1
Suite/Platform
IT Management Suite solutions and components (continued)
Inventory Solution
Inventory Solution lets you gather inventory data about the

computers, users, operating systems, and installed software
applications in your environment. You can collect inventory data
from the computers that run Windows, UNIX, Linux, and Mac.
After you gather inventory data, you can analyze it using predefined
or custom reports.
IT Analytics
IT Analytics Solution software complements and expands upon

the traditional reporting that is offered in most Altiris solutions. It
brings exciting new features and capabilities to Notification Server
because it incorporates multi-dimensional analysis and robust
graphical reporting and distribution features.
This functionality allows users to explore data on their own, without
advanced knowledge of databases or third-party reporting tools.
It empowers users to ask and answer their own questions quickly,
easily, and effectively.
Patch Management
Solution
Patch Management Solution for Windows lets you scan Windows

computers for the updates that they require, and view the results
of the scan. The system lets you automate the download and
distribution of software updates. You can create filters of the
computers and apply the patch to the computers that need it.
Patch Management Solution for Linux lets you scan Red Hat and
Novell Linux computers for security vulnerabilities. The solution
then reports on the findings and lets you automate the download
and distribution of needed errata, or software updates. The solution
downloads the required patches and provides wizards to help you
deploy them.
Patch Management Solution for Mac lets you scan Mac computers
for the updates that they require. The solution then reports on the
findings and lets you automate the downloading and distribution
of needed updates. You can distribute all or some of the updates.
Symantec Remote
Access Connector
Symantec Remote Access Connector is an IT Management Suite

7.6 functionality that lets you configure and integrate a third-party
remote connection tool such as Microsoft Remote Desktop
Connection or Bomgar Remote Support Solution with IT
Management Suite.
199
Reference topics
Table A-1
Suite/Platform
Real-Time System
Manager
Real-Time System Manager provides you detailed real-time

information about a managed computer, and lets you remotely
perform different administrative tasks in real time.
Real-Time System Manager also lets you run some of the
management tasks on a collection of computers. You can run the
tasks immediately, or on a schedule.
Software Management
Solution
Software Management Solution provides intelligent and

bandwidth-sensitive distribution and management of software from
a central Web console. It leverages the Software Catalog and
Software Library to ensure that the required software gets installed,
remains installed, and runs without interference from other
software.
Software Management Solution supports software virtualization
technology, which lets you install software into a virtual layer on
Software Management Solution also lets users directly download
and install approved software or request other software.
Workflow Solution
Symantec Workflow is a security process development framework

that you can use to create both automated business processes
and security processes. These processes provide for increased
repeatability, control, and accountability while reducing overall
workload.
The Symantec Workflow framework also lets you create Workflow
processes that integrate Symantec tools into your organization's
unique business processes. Once deployed, Workflow processes
can respond automatically to environmental variables. Workflow
processes can also allow for human interface points when a
process calls for someone to make a decision with accountability.
Server Management
Suite
Deployment Solution
Deployment Solution helps to reduce the cost of deploying and

managing servers, desktops, and notebooks from a centralized
location in your environment. It offers operating system
deployment, configuration, personality migration of computers,
and software deployment across different hardware platforms and
operating systems.
200
Reference topics
Table A-1
Suite/Platform
Inventory Solution
Inventory Solution lets you gather inventory data about the

computers, users, operating systems, and installed software
applications in your environment. You can collect inventory data
from the computers that run Windows, UNIX, Linux, and Mac.
After you gather inventory data, you can analyze it using predefined
or custom reports.
Inventory Pack for

Servers
Inventory Pack for Servers gathers server-based inventory data

from servers. It runs on top of Inventory Solution and uses the
same Inventory plug-ins, tasks, and wizards.
IT Analytics
IT Analytics Solution software complements and expands upon

the traditional reporting that is offered in most Altiris solutions. It
brings exciting new features and capabilities to Notification Server
because it incorporates multi-dimensional analysis and robust
graphical reporting and distribution features.
This functionality allows users to explore data on their own, without
advanced knowledge of databases or third-party reporting tools.
It empowers users to ask and answer their own questions quickly,
easily, and effectively.
Altiris IT Analytics Symantec Endpoint Protection Pack is also
included in this solution.
Monitor Solution
Monitor Solution for Servers lets you monitor various aspects of

computer operating systems, applications, and devices. These
aspects can include events, processes, and performance. This
ability helps you ensure that your servers and your devices work
and reduces the costs of server and network monitoring.
Monitor Pack for Servers Monitor Pack for Servers works with the Monitor Solution core
components of the Symantec Management Platform. It lets you
monitor operating system performance, services, and events of
your Windows, UNIX, and Linux server environment.
201
Reference topics
Table A-1
Suite/Platform
Patch Management
Solution
Patch Management Solution for Windows lets you scan Windows

computers for the updates that they require, and view the results
of the scan. The system lets you automate the download and
distribution of software updates. You can create filters of the
computers and apply the patch to the computers that need it.
Patch Management Solution for Linux lets you scan Red Hat and
Novell Linux computers for security vulnerabilities. The solution
then reports on the findings and lets you automate the download
and distribution of needed errata, or software updates. The solution
downloads the required patches and provides wizards to help you
deploy them.
Patch Management Solution for Mac lets you scan Mac computers
for the updates that they require. The solution then reports on the
findings and lets you automate the downloading and distribution
of needed updates. You can distribute all or some of the updates.
Real-Time System
Manager
Real-Time System Manager provides you detailed real-time

information about a managed computer, and lets you remotely
perform different administrative tasks in real time.
Real-Time System Manager also lets you run some of the
management tasks on a collection of computers. You can run the
tasks immediately, or on a schedule.
Software Management
Solution
Software Management Solution provides intelligent and

bandwidth-sensitive distribution and management of software from
a central Web console. It leverages the Software Catalog and
Software Library to ensure that the required software gets installed,
remains installed, and runs without interference from other
software.
Software Management Solution supports software virtualization
technology, which lets you install software into a virtual layer on
Software Management Solution also lets users directly download
and install approved software or request other software.
Virtual Machine
Management
Virtual Machine Management is a component of Server

Management Suite that lets you perform the virtualization process
on your network. You can create virtual environments of servers,
storage devices, and network resources on a single physical
server. Virtualization enhances the efficiency and productivity of
the hardware resources and helps to reduce administrative costs.
202
Reference topics
Table A-1
Suite/Platform
Workflow Solution
Symantec Workflow is a security process development framework

that you can use to create both automated business processes
and security processes. These processes provide for increased
repeatability, control, and accountability while reducing overall
workload.
The Symantec Workflow framework also lets you create Workflow
processes that integrate Symantec tools into your organization's
unique business processes. Once deployed, Workflow processes
can respond automatically to environmental variables. Workflow
processes can also allow for human interface points when a
process calls for someone to make a decision with accountability.
See About IT Management Suite on page 10.

Cloud-enabled Management lets you manage endpoints over the Internet even if
the client computers are outside of the corporate environment and cannot access
the management servers directly. The managed computers do not need to use a
VPN connection to your organization's network.
You can apply Cloud-enabled Management in the following scenarios:
An organization with many employees traveling or working outside of the office

(outside the corporate intranet).
A managed service provider (MSP), managing external companies.
Highly distributed companies with many small offices or employees working

from home.
When you implement Cloud-enabled Management, the Notification Server computer

and site servers are not directly exposed to the Internet. Therefore, Symantec
Management Agent communicates with the Notification Server computer and the
site servers through an Internet gateway. Usually two or more Internet gateways
should be available to maintain reliable management of Cloud-enabled clients and
to provide failover options. Each Internet gateway can support routing to multiple
independent Notification Servers.
To use cloud-enabled management, you must install an Internet gateway server.
The Internet gateway works as a tunneling proxy. It ensures the privacy and safety
of the data that is passed between an agent and a management server with HTTPS
communications. The Internet gateway is located in a demilitarized zone (DMZ)
203
Reference topics
between two firewalls. It accepts incoming connections from authorized client

computers on the Internet and forwards them to the appropriate Notification Servers
and site servers inside your network. The Internet gateway blocks any connection
attempts by unauthorized clients.
The Symantec Management Agent automatically determines whether routing the
communication through the Internet gateway is needed or not. If a Cloud-enabled
computer has direct access to the local network using VPN, the agent automatically
switches to a direct communication with Notification Server. If a Cloud-enabled
computer is outside the corporate network, then the agent routes all communication
on the Internet to Notification Server through the Internet gateway.
Note: Cloud-enabled Management is supported on Microsoft Windows computers
and Mac OS X computers.
Not all solutions support Cloud-enabled Management in IT Management Suite 7.6.
For more information on Cloud-enabled Management support for a particular
solution, refer to the solution documentation.
Figure A-1
To take advantage of the Cloud-enabled Management feature, you must perform

the following tasks:
Set up the infrastructure and configure your servers and client computers to use
SSL.
Install and configure the Internet gateways, configure the Cloud-enabled

Management policies, and set up the Symantec Management Agents to support
the Cloud-enabled Management environment.
204
Reference topics
(Optional) Perform troubleshooting and maintenance tasks.

Symantec Installation Manager provides the following hotkeys or keyboard shortcuts
to execute a few tasks during the installation of the IT Management Suite solutions.
Table A-2
Hotkey
Task description
User Interface of the Symantec

Installation Manager
Ctrl + Shift + P
Shows a list of all partial solution

installations.
Installed Products page
Press the same hotkey combination

to revert to the previous view.
Ctrl + Shift + X
Shows the product listing file as

interpreted by the SIM
Install New Products page
Ctrl + Shift + V
Shows verbose reason as to why a

greyed out item is unavailable.
Install New Products page, Upgrade

installed products page, and Create
installation package page.
Ctrl + Shift + P
Shows the MSI files to be installed,

Installation Summary page
switching between the product and the
package view.
Ctrl + Shift + S
Switches between the installation

Installation Summary page
order and the alphabetical order view.
Ctrl + Shift + O
Shows the optional components

Installed Products page
(documentation, language packs, and
migration) that are installed along with
other installed solutions, and lets you
repair or uninstall the solutions.
Press the same hotkey combination
to revert to the previous view.
IT Management solutions and their dependent

solutions
Symantec Installation Manager provides the following solutions for installation on
a computer. A suite or a solution may have dependent solutions that get installed
205
Reference topics
automatically along with the solution or suite that you select for installation. The
following table informs you about the dependent solution for every suite or solution.
This information lets you make a judicious decision about selecting solutions for
installation on a computer.
For a selected solution, a few dependent solutions are displayed as grayed out.
The grayed out solutions are already packaged or bundled along with the
originally-selected solution, and are not available for selection.
For a selected solution, a few dependent solutions get automatically selected. These
automatically-selected solutions are not bundled together with the originally-selected
solution.
Table A-3
Solution
Grayed-out solution
Altiris Asset Management Solution 7.6 NA

Altiris Asset Management Suite 7.6
Altiris Client Management Suite 7.6
Altiris CMDB Solution 7.6

Altiris Asset Management Solution Altiris IT Analytics 7.6
7.6
Altiris IT Analytics Client Server

Management Pack 7.6
Symantec Barcode Solution 7.6
Symantec ITMS Admin 7.6
Altiris Client Management Suite

Portal Page
Altiris Deployment Solution 7.6
Altiris Event Console 7.6
Altiris Inventory Solution 7.6

Management Pack 7.6
Altiris Patch Management Solution
7.6
Altiris Power Scheme Task 7.6
Automatically-selected solution
Altiris Real-Time Console

Infrastructure 7.6
Altiris Real-Time System Manager
7.6
Altiris Software Management
Solution 7.6
Altiris IT Analytics 7.6
Enhanced Console Views 7.6
206
Reference topics
IT Management solutions and their dependent solutions (continued)
Table A-3
Solution
Grayed-out solution
Altiris Client Management Suite Portal NA

Page

7.6
NA
Altiris Inventory Pack for Servers 7.6
NA
NA

Management Pack 7.6
NA
Altiris IT Analytics ServiceDesk Pack NA

7.6
Altiris IT Analytics Symantec Endpoint NA

Protection Pack 12.1.2
207
Reference topics
Table A-3
Solution
Grayed-out solution
Altiris IT Management Suite
Altiris Asset Management Solution

7.6
Altiris Asset Management Suite 7.6
Altiris Client Management Suite 7.6
Altiris Client Management Suite

Portal Page
Altiris Event Pack for Servers 7.6

Management Pack 7.6
Altiris IT Analytics ServiceDesk
Pack 7.6
Altiris IT Analytics Symantec
Endpoint Protection Pack 12.1.2
Altiris Monitor Pack for Servers 7.6
NA
Altiris Patch Management Solution 7.6 NA


7.6
7.6
Altiris Real-Time Control
Infrastructure 7.6
Altiris Virtual Machine Management
7.6
Altiris Server Management Suite
7.6
Portal Page
7.6
Solution 7.6
208
Reference topics
Table A-3
Solution
Grayed-out solution
Altiris Real-Time System Manager 7.6 NA
Altiris Real-Time Control Infrastructure

7.6
Altiris Recovery Solution
NA
NA
Altiris Server Management Suite 7.6
Altiris Inventory Pack for Servers

7.6

7.6
Altiris Server Management Suite Portal NA

Page 7.6

Management Pack 7.6
7.6
7.6
Portal Page 7.6
Solution 7.6
7.6
Altiris Software Management Solution NA

7.6

7.6
Infrastructure 7.6
7.6
Solution 7.6
Infrastructure 7.6
209
Reference topics
Table A-3
Solution
Grayed-out solution
Dell Management Console Pack 7.6

7.6
Deployment Solution for Dell x64

SP1

7.6

SP1
Dell Management Console
Dell Solutions
Deployment Solution for Dell 7.1

SP1 HF1
Dell Solutions

Management Pack 7.6
7.6
7.6
7.6
Portal Page 7.6
Solution 7.6
7.6
Portal Page 7.6
Dell Common
NA
Deployment Solution for Dell 7.1 SP1 NA

HF1
Deployment Solution for Dell x64 SP1 NA
210
Reference topics
Table A-3
Solution
Grayed-out solution
Deployment Solution for Solaris 1.0

SP1
NA

SP1

Infrastructure 7.6

Infrastructure 7.6
DeskView
DeskView (Core)
DeskView Client for Symantec

Management Platform
NA
NA
DeskView Integration for Symantec

Management Platform 7 (Business
Clients) Solution
NA
DeskView Integration for Symantec

Management Platform 7 (Business
Clients) Solution

Infrastructure 7.6
DeskView (Core)
eiPower Saver Solution 7.1
NA
Front Office for Symantec 7.1 SP1
NA
NA
NA
NA
NA
Symantec IT Analytics Critical System NA

Protection Pack
Symantec IT Analytics Data Loss

Protection Pack 2.0
NA
Symantec Mobile Framework 7.2 SP1 NA
NA
Symantec Mobile Management 7.2

SP1
Symantec Mobile Framework 7.2

SP1
NA
211
Reference topics
Table A-3
Solution
Grayed-out solution
Symantec Mobile Security
NA
Symantec Mobile Framework 7.2 SP1
Symantec Mobile Security MR1
NA
Symantec Mobile Framework 7.2

SP1
Symantec Mobile Security
Symantec ServiceDesk Solution 7.6

SP1
NA
Symantec System Recovery 2013

Installer x64-x86
NA

Management Solution x64

LightsOut Restore x64-x86
NA


Linux Management Solution x64
NA


NA

212
Glossary
Active Directory Import A feature of the Symantec Management Platform that lets the user import Active
Directory objects such as users, computers, sites, and subnets, into the CMDB
(Configuration Management Database).
AeXGenClientCert.exe
A command-line tool that generates the client certificates that Cloud-enabled

Management requires.
AeXGenSiteServerCert.exe A command-line tool that generates the site server certificates.

AeXRevokeCertificate.exe A tool that revokes certificates.
agent registration policy A policy that lets the user automate the agent registration process. Agent registration
policy is a set of rules that determine how the incoming registration requests are
processed.
alert
A notification about issues, failures, and particular states of the system. The user
can customize which alerts are sent, logged, and where the alerts are sent.
Alert Manager
A feature that generates a ticket when an event occurs, and sends notification
messages to the designated users.
applicability rule
A rule that determines whether a computer has the correct environment for an
installation of a specific software package.
application identity of
An account under which Notification Server runs.
Notification Server
automated action
An action that runs in response to an event. Automated actions can generate alerts,
execute tasks, create reports, and send emails.
automation policy
A rule in XML format that defines the attributes of a resource such as its groups,
relationships, and wanted states. Automation policy initiates automated actions to
update the resource and bring its attributes into compliance.
Basic filter
A type of filter that filters the computers according to the static parameters.
blockout period
The time when all communication between the agent and the Notification Server
computer is disabled.
CEM (Cloud-enabled
A feature that lets the user manage the client computers outside the corporate
network without a VPN (virtual private network).
Management)
client certificate
A certificate that allows a client computer or a site server to identify itself to

Glossary
client computer
A computer that has Symantec Management Agent installed on it and can be

managed from the Notification Server computer through Symantec Management
Console.
client task
A task that is executed on a client computer.
Client Task Agent
A sub-agent that runs on client computers. Client Task Agent accepts tickles from
a task server and receives job and task information. It then passes this information
to a handler and sends status information back to the task server. This sub-agent
is installed automatically with the Symantec Management Agent.
Cloud-enabled agent
An agent that is allowed to communicate with Notification Server through an Internet

gateway.
CMDB (Configuration
The central database that stores all the data that Symantec Management Platform
Management Database) uses and generates.

Command-Line Builder
A tool that is used to create a syntactically correct command.
complete hierarchy
A process that replicates all objects and data in the hierarchy.
replication
Complete Update
schedule
A schedule that completely recreates the membership of all filters, organizational

groups, and targets, regardless of inventory status or any changes to policies.
connection profile
A group of settings that defines which network protocols are used to communicate
with the network devices.
Credential Manager
A secure store for the credentials that Notification Server and installed solutions
use.
Data Connector
A component of the Symantec Management Platform that lets the user transfer
data between external data sources and the CMDB (Configuration Management
Database).
delta update schedule
A schedule that updates the membership of the filters that have had membership
changes, all dynamic organizational groups, and invalid targets.
detection rule
A rule that determines if specific software is installed on a computer.
differential hierarchy
A process that replicates the objects and the data that have changed since the last
replication.
replication
discovery
The process of searching for computers or other resources on the network that
meet specific requirements.
Documentation Library
A collection of help content that is installed with each IT Management Suite

component.
event
Any action that Notification Server can monitor.
filter
A query that identifies a dynamic group of resources that share common criteria.
214
Glossary
Full Windows Installer

Repair
A policy or task that runs on client computers and verifies that all of the component
resources of the Windows Installer applications are installed correctly. If any element
of a component is not installed correctly, Full Windows Installer Repair initiates the
repair of that component.
global exclude entry
A way to exclude application data from being saved in any application layer. Global
exclude entry is used to prevent the loss of data when an application layer is reset.
hierarchy
An organizational structure of multiple Notification Servers that identifies a parent

Notification Server. It then replicates the relevant data to any number of child servers,
which can be located on different structural levels.
Internet gateway
A computer that tunnels communication between client computers outside the

corporate network and the Symantec Management Platform infrastructure. Setting
up an Internet gateway is required to use Cloud-enabled Management.
Inventory Rule
The software feature that lets the user create, edit, and delete rules and the
expressions that make up rules.
Management
item
Any object that belongs to CMDB (Configuration Management Database), such as

a policy, a folder, or a computer that can be managed. Each item has a name,
description, GUID, and attributes, and can be cloned, imported, exported, presented,
and secured. Items can be linked with references or named relations between them.
job
A sequence of tasks that are executed on a target. Jobs can include the conditions
that specify when the task runs.
Jobs and Tasks Portal
A page in the Symantec Management Platform that lets the user create and schedule
tasks to run on the managed resources.
LAC (Legacy agent
A feature of IT Management Suite that lets the user control whether the computers
that use older versions of the Symantec Management Agent can communicate with
the upgraded Notification Server.
Communication )
layer exclude entry
A way to exclude application data from being saved in a specific application layer.
Layer exclude entry is used to prevent the loss of application data when an
application layer is reset.
legacy agent
Symantec Management Agent that has the version that is previous to the Notification
Server version. For example, in IT Management Suite 7.5 a legacy agent is
Symantec Management Agent 7.1.
Legacy Software
Delivery
A policy that delivers software to a client computer and is created from an earlier
version of a software delivery policy.
Log Viewer
A tool that lets the user monitor several locations of logs for different components.
maintenance window
A scheduled period of time when maintenance operations may be performed on a

client computer.
215
Glossary
managed computer
A computer on which the Symantec Management Agent is installed. Another term

for a client computer.
Managed Delivery
A policy that can perform complex software delivery tasks. Managed Delivery can
perform recurring software deliveries, check for compliance, perform remediation,
and install dependency software. It can also deliver multiple software resources
and uninstall superseded software.
migration
A process of moving Symantec Management Platform data from an older platform

version to a newer one. Migration is performed when the Configuration Management
Database (CMDB) is not compatible with the newer version of the platform.
migration wizard
A tool that is used to perform a migration. Migration wizard is shipped with Symantec
My Portal page
The default page that opens when a new user runs the Symantec Management
Console.
Network Discovery
A process of discovering all IP devices that are connected to a network.
Network Discovery task A scheduled task that discovers either a single device or multiple devices on a
network.
Network Discovery
A tool that is used to create a Network Discovery task.
wizard
Notification Server
The main component of Symantec Management Platform communicates with

Symantec Management Agent and the CMDB (Configuration Management
Database), and provides the user interface and the background that the solutions
that are part of the IT Management Suite require. Notification Server processes
events, facilitates communications with managed computers, and coordinates the
work of the other Symantec Management Platform services.
NS Configurator
A tool that lets you change most core Notification Server configuration settings.
These settings include many that are not accessible from the Symantec Management
Console.
NSE (Notification Server An XML file that is transferred between Notification Server and Symantec
Event)
Management Agent. NSE can contain the following information: event processing,
basic or full inventory, success or failure of a package download.
A file that is used to install Symantec Management Agent on computers outside

the corporate network. It contains an executable installation file that is generated
on the Notification Server computer, and a Cloud-enabled Management policy.
package
organizational group
A set of resources that are grouped by common properties or similar features for
management and security purposes.
organizational view
A hierarchical grouping of resources that reflects a real-world structure of an

organization.
216
Glossary
package
A file that is intended for installation on client computers.
Package Delivery task
A task that delivers and installs the software on client computers.
package server
A type of site server that is used to distribute packages from Notification Server to
client computers.
permission
An ability of a particular user or group to perform specific actions on a resource and

access particular items.
policy
A set of rules that are applied to a resource or a set or resources that control the
execution of automated actions. Policies can be scheduled or based on the incoming
data that triggers an immediate action. Policies determine when an action should
start and how the results of the action are processed.
Policy Update schedule A schedule that updates the membership of filters that a policy uses if the policy
has changed since the last update.

portal page
A customizable Symantec Management Console page.
privilege
A setting that determines the actions in the Symantec Management Console that
a user or a group of users can perform.
Purge Maintenance
A script that deletes old and obsolete data from CMDB (Configuration Management
Database).
Query Builder
A tool that lets the user configure the query SQL to build the filter query.
Query filter
A type of filter to which the user can add the criteria from a default filter criteria list.
When the user creates a new filter, it is automatically created as a Query filter.
Quick Delivery
A task that lets the user deliver the software without the need to know which package
to select or how to create the command line.
replication
A one-way transfer of data between Notification Server and a client computer or

another Notification Server.
replication rules
The regulations that define the data that needs to be replicated to other Notification
Servers.
report drilldown
An action that is performed when the user clicks on an item in the report results.
resource
Any item that Notification Server can track or manage, such as a user, site, installed
application, computer, switch, router, or handheld device.
resource import rule
A regulation that lets the user specify the resources that should be imported from
Active Directory.
Resource Manager
A feature that displays information about a resource, such as its properties and
current state. Resource Manager also lets the user troubleshoot and perform actions
on managed resources.
217
Glossary
resource report
A report that lets the user drill down on a particular resource to view full details in
the Resource Manager.
resource scoping
A security and resource management feature that limits the data that a user can
access based on the security role membership. Resource scoping is implemented
by assigning permissions to organizational groups.
resource target
A framework that lets the user apply tasks and policies to a dynamic collection of
resources.
rule expression
A combination of symbols (identifiers, values, and operators) that yields a result

upon evaluation. These symbols form the instructions that define the items that a
rule should check the client computer for.
schedule
A set time and date when an action, for example, a task, is executed. Actions can
be scheduled to execute only once or with a set interval.
security role
An organizational group that contains Symantec Management Platform users. A

security role is characterized by name, permissions, and the privileges that are
assigned to the role.
Security Role Manager
A console that lets administrators set permissions for security roles.
server task
A task that is executed on the Notification Server computer.
shared schedule
A schedule that a number of items, such as policies or tasks, use.
site
A group of client computers that is usually based on one or more subnets.
site server
A middleware component that is used to provide packages, tasks, and PXE

configuration to Symantec Management Agents. Site servers are used to reduce
the load on the Notification Server computer.
smart rule
A rule that determines whether a package is installed on a client computer.
Software Catalog
A catalog that contains a list of known applications and predefined software products.
Software Catalog is regularly updated to include the new inventory data.
Software Library
The physical location of the software packages that are defined in the Software
Catalog. The Software Library is the source of the definitive, authorized versions
of the software packages.
Software Management
An interface that lets the user create and manage the software resources that are
in the Software Catalog, and the packages in the Software Library.
Framework
Software Portal
A web-based portal that lets the user request and install software with little or no
outside intervention.
Software Virtualization An agent that contains the SVS (Software Virtualization Solution) File System Filter
Agent
Driver that manages virtual software layers. A licensed version of the agent is
required to install software into a virtual layer.
218
Glossary
solution
A product that leverages the services of the Symantec Management Platform and
adds specific functionality to the platform.
solution plug-in
A piece of software that is installed on a client computer and adds functionality to

the Symantec Management Agent. A plug-in provides specific functions for the
solution with which it is associated.
Source Patch Update
A policy or task that updates Windows Installer applications with resilient source
paths.
SQL filter
A type of filter for which the user can edit the query SQL.
standard rule
A rule that determines whether a specific software application is installed on a client

computer. Standard rule expressions are static.
Symantec Management The software that is installed on the computers that you want to manage. It facilitates
Agent
interactions between Notification Server and a managed computer. The agent

receives requests for information from Notification Server, sends data to Notification
Server, and downloads files. The Symantec Management Agent also lets you install
and manage solution plug-ins that add functionality to the agent.
Symantec Management A web-based user interface that lets the user manage the Symantec Management
Console
Platform and any other installed solutions.
Symantec Management The platform that provides a set of services for IT-related solutions. These services
Platform
include security, scheduling, client communications and management, task

execution, file deployment, reporting, centralized management, and CMDB
(Configuration Management Database) services.
target
A framework that lets the user perform actions on dynamic sets of resources. A
target consists of at least one organizational view and a number of filters.
task
An action that is performed on a client computer or a group of client computers.

Server tasks are run on Notification Server. Client tasks are run on managed
computers.
task server
A site server that distributes task information from Notification Server to client
computers.
upgrade
A process of patching the IT Management Suite to the newest version. This process
is performed with Symantec Installation Manager. In contrast to migration, the
upgrade can use the same CMDB (Configuration Management Database).
user-based policy
A policy that is executed based on the user that is logged in on a given computer.
virtual data class
A data class that lets the user integrate third-party system data with the Symantec
Management Platform CMDB (Configuration Management Database) without the
need to import data to CMDB.
virtual software archive A portable format of a virtual software layer. Its installation requires a licensed
file
version of the Software Virtualization Agent.
219
Glossary
virtual software layer
A collection of files and registry settings that are placed in SVS (Software
Virtualization Solution) redirection areas. A virtual software layer can contain one
or more applications or a set of data.
Windows Installer
A policy or task that runs on client computers and verifies that all of the component
resources of the Windows Installer applications are installed correctly. If any element
of a component is not installed correctly, the policy or task initiates the repair of that
component.
Repair
220
Index
A
agent trust
upgrade 167
history
product, exporting, and importing 139
hot fix installation 15
backing up
KMS keys 131
IIS role services

required 31
importing
product history 139
installation
about 17
adding products 105
applying licenses 105
hot fix 15
offline 14
optional components 105
planning 16
process 85
reconfiguring a product 105
repairing 105, 134
updating 105
installation logs
viewing 105
installation package
creating 135
installed product
reconfiguring 133
Installed Products page 105
Installing
documentation 113
IT Management Suite 91
language packs 113
Symantec Installation Manager 88
Symantec Management Platform 91
IT Management
about 10
IT Management Suite
installing 91
C
Certificates
in Notification Server 97
about 203
setting up 166
configuration
redoing 133
context-sensitive help 21
D
Disabling
verbose logs in Symantec Installation
Manager 148
documentation 21
installing 113
uninstalling 144
E
exporting
product history 139
F
Flash
requirements 30
fully qualified domain name 96
H
help
context-sensitive 21
Index
J
Java
requirements 31
K
KMS keys
automatically backing up 131
L
language packs
installing 113
uninstalling 144
licenses
applying 111
logs
installation, viewing 105
M
Microsoft Access 2010
OLEDB driver 30
migration wizard
installing 113
uninstalling 144
N
Notification Server
configuring for Cloud-enabled Management 125
O
creating installation package 135
OLEDB driver
Microsoft Access 2010 30
optional components
installing 105
uninstalling 144
P
package servers
configuring for Cloud-enabled Management 125
publishing HTTPS codebases 125
product listing
adding a .pl file 107
updating 109
products
adding 105
products (continued)
applying licenses 105, 111
reconfiguring 105
repairing an installation 105, 134
uninstalling 105, 145
updating 105
R
reboots, pending 106
reconfiguration
installed product 133
Release Notes 21
S
Silverlight
requirements 31
site
configuring for Cloud-enabled agents 128
site servers
assigning to a site 128
configuring for Cloud-enabled agents 128
software, third-party
requirements 29
solutions
IT Management Suite 198
SQL Server
recommendations 29
support package
creating 105, 141
about 17
delaying the update 142
installing 88
starting 106
Symantec Installation Manager logs
disabling verbose 148
viewing 147
installation process 85
installation, about 17
planning the installation 16
uninstalling 145
system requirements
IIS role services 31
T
troubleshooting
creating a support package 105, 141
222
Index
U
update
delaying 142
updating
installation package 139
Upgrade to IT Management Suite 7.6
performing 154
Upgrade to Notification Server 7.6
performing 155
Upgrading
to IT Management Suite 7.6 154
to Notification Server 7.6 155
V
Verbose logs
in Symantec Installation Manager 148
Viewing
Symantec Installation Manager logs 147
viewing
installation logs 105
W
Web site configuration
troubleshooting 96
223

ITMS 7 6 Installation and Upgrade Guide English

Enviado por

Dados do documento

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

ITMS 7 6 Installation and Upgrade Guide English

Enviado por

Direitos autorais:

Formatos disponíveis

Symantec IT Management

Suite 7.6 powered by Altiris

Symantec IT Management Suite 7.6 powered by

Telephone and/or Web-based support that provides rapid response and

Upgrade assurance that delivers software upgrades

Global support purchased on a regional business hours or 24 hours a day, 7

Premium service offerings that include Account Management Services

Contacting Technical Support

Product release level

Available memory, disk space, and NIC information

Version and patch level

Router, gateway, and IP address information

Error messages and log files

Troubleshooting that was performed before contacting Symantec

Recent software configuration changes and network changes

Licensing and registration

Questions regarding product licensing or serialization

Product registration updates, such as address or name changes

General product information (features, language availability, local dealers)

Latest information about product updates and upgrades

Information about upgrade assurance and support contracts

Information about the Symantec Buying Programs

Advice about Symantec's technical support options

Nontechnical presales questions

Issues that are related to CD-ROMs, DVDs, or manuals

Support agreement resources

Europe, Middle-East, and Africa

North America and Latin America

Technical Support ............................................................................................... 4

Introducing IT Management Suite installation ............. 10

Installing the IT Management Suite solutions .............. 24

Performing the post-installation tasks ......................... 104

Installing critical product listing updates ...........................................

Upgrading to IT Management Suite ............................... 150

Upgrading Symantec Management Agent ........................................

Migrating Notification Server data from Windows

Migrating to IT Management Suite 7.6 ......................... 184

Troubleshooting information .......................................... 191

Reference topics ................................................................ 198

Glossary ............................................................................................................. 213

About IT Management Suite

About installing the IT Management Suite

About the Symantec Installation Manager

Best practices for installing the IT Management Suite

Where to get more information

About IT Management Suite

Introducing IT Management Suite installation

Linux operating systems. In addition, the same management disciplines are

About installing the IT Management Suite

Suites and solutions to be installed

Types of installation of the IT Management Suite 7.6

IT Management Suite 7.6 installation scenarios

Suites and solutions to be installed

Introducing IT Management Suite installation

Client Management Suite

Server Management Suite

Asset Management Suite

Types of installation of the IT Management Suite 7.6

Introducing IT Management Suite installation

Types of installation of the IT Management Suite

A fresh installation is when you install the IT Management

See Installing the IT Management Suite on page 85.

An on-box upgrade is when you upgrade from ITMS 7.1

Off-box upgrade from 7.1 SP2 MP1.1 or 7.5 SP1 HF5