ITMS 6xmigration Guide

Altiris IT Management Suite from Symantec Migration Guide version 6.x to 7.
1 SP2
Altiris IT Management Suite from Symantec Migration Guide version 6x to 7.1SP2

The software described in this book is furnished under a license agreement and may be used only in accordance with the terms of the agreement.
Legal Notice
Copyright 2011 Symantec Corporation. All rights reserved. Symantec and the Symantec Logo, Altiris, and any Altiris or Symantec trademarks are 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 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, "Rights in Commercial Computer Software or Commercial Computer Software Documentation", as applicable, and any successor regulations. 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 Web site 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: www.symantec.com/business/support/ 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: www.symantec.com/business/support/
Customer service
Customer service information is available at the following URL: www.symantec.com/business/support/ 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 Europe, Middle-East, and Africa North America and Latin America customercare_apac@symantec.com semea@symantec.com supportsolutions@symantec.com
Contents
Technical Support ............................................................................................... 4 Chapter 1 Introducing IT Management Suite ................................... 13

About IT Management Suite ........................................................... What's new in IT Management Suite ................................................ Solutions of IT Management Suite .................................................. Components of the Symantec Management Platform .......................... Where to get more information ....................................................... 13 14 14 16 17
Chapter 2
Overview of migrating to IT Management Suite ........... 19

About this migration guide ............................................................ How to use this guide .................................................................... Recommended reading .................................................................. About product parity between versions 6.x and 7.1 ............................. About migrating to Symantec Management Platform 7.1 ..................... About testing IT Management Suite ........................................... About post migration configuration ........................................... About validating a migration .................................................... About reusing existing hardware to migrate ...................................... 19 20 21 22 24 26 26 26 27
Chapter 3
Migrating Symantec Management Platform ................. 29

Best practices for migrating to Symantec Management Platform 7.1 ....................................................................................... Important things to know when migrating from Notification Server 6.x ....................................................................................... About supported IT Management Suite migration paths ...................... Migrating from Notification Server 6.x ............................................. Backing up the Notification Server Database ............................... Preparing for the migration ..................................................... About redirecting sites and agents to Notification Server 7.1 ................................................................................. Redirecting managed computers to Symantec Management Platform 7.1 .................................................................... About the Symantec Management Agent upgrade policies ............. 29 31 33 33 37 38 39 40 42
Contents
Upgrading the Altiris Agent and the agent plug-ins ...................... About removing sub-agents or agent plug-ins from managed computers ...................................................................... About upgrading package servers .............................................. Migrating managed computers ................................................. About migrating licenses to Symantec Management Platform 7.1 ................................................................................. About data migration .................................................................... About data migration when migrating from Notification Server 6.x ................................................................................. About the Symantec Notification Server Migration Wizard ............ About the data that the migration wizard migrates from Notification Server 6.x ...................................................... About installing the Symantec Notification Server Migration Wizard ........................................................................... Migrating data to Symantec Management Platform 7.1 with the migration wizard ............................................................. Exporting Notification Server 6.x data to a data store file .............. Importing Notification Server 6.x data from a data store file ................................................................................ Exporter Configuration or Importer Configuration page ................ About the 6.x data that you must manually migrate to Symantec Management Platform 7.1 ................................................. About the data store file ................................................................ About the Store Browser .......................................................... Viewing the data in a data store file ........................................... Exporting data from a data store file .......................................... Comparing two data store files .................................................
43 45 46 47 48 48 49 50 51 53 56 57 59 60 61 62 62 63 64 65
Chapter 4
Migrating Inventory Solution ............................................ 69

Before you migrate Inventory Solution ............................................. About Inventory Solution migration with Symantec Notification Server Migration Wizard ......................................................... About manual Inventory Solution migration ..................................... Manually migrating custom inventory script files .............................. Backing up custom inventory script files .................................... Copying custom inventory script files to the Notification Server 7.1 computer ................................................................... About creating an .INI file for custom inventory .......................... Prerequisites for creating a custom inventory software resource package .......................................................................... 69 70 72 73 78 78 80 81
Contents
Creating a software resource with a package and a command line for custom inventory script files ......................................... Creating the Quick Delivery task for a custom inventory script file ................................................................................ Creating and customizing a data class ........................................ Creating a custom inventory script task ..................................... Customizing the custom inventory sample script for Windows ........................................................................ Customizing the custom inventory sample script for UNIX, Linux, and Mac ......................................................................... Manually migrating Inventory Solution baseline configuration files ..................................................................................... Backing up Inventory Solution baseline configuration files ............ Copying Inventory Solution baseline configuration files to the Notification Server 7.1 computer ........................................ Verifying the migration of baseline configuration files .................. About migrating Inventory for Network Devices ................................
81 83 84 85 88 92 94 96 96 97 99
Chapter 5
Migrating Patch Management Solution ........................ 101

About migrating Patch Management Solution for Windows ................ About migrating Patch Management Solution for Linux .................... About migrating Patch Management Solution for Mac ....................... Data that can be migrated from the 6.x version of Patch Management Solution for Windows ............................................................ 101 102 102 102
Chapter 6
Migrating Software Delivery to Software Management Solution ................................................ 105

Things to know about migrating from 6.x to 7.1 ............................... Items that can and items that cannot be migrated from software delivery solutions 6.x ............................................................ Migrating from Software Delivery Solution 6.x to Software Management Solution 7.1 ...................................................... Migration Wizard objects ....................................................... About validating Software Package Migration ............................ Promoting migrated Software Packages into the Software Library ......................................................................... Enabling legacy software delivery policies ................................. About migrated Managed Software Delivery sequential tasks ............................................................................ Viewing migrated task server infrastructure software delivery tasks ............................................................................ 105 106 110 111 112 113 115 116 116
10
Contents
Chapter 7
Migrating Deployment Solution ..................................... 117

About migration of Deployment Solution ....................................... About reason to migrate Deployment Solution 6.9 ............................ About architecture and features of Deployment Solution 7.1 SP1 .................................................................................... About advantages of using Deployment Solution 7.1 SP1 over 6.9 ..................................................................................... About comparison of Deployment Solution 6.9 features with 7.1 SP1 .................................................................................... About comparison of Deployment Solution 6.9 tasks with 7.1 SP1 ... 1 2 8 About import of predefined computers in Deployment Solution 7.1 SP1 .................................................................................... Importing predefined computers ................................................... Installing the Deployment Solution 7.1 SP1 agent and plug-in ............ Uninstalling the Deployment Solution 6.9 agent .............................. Limitations of migrating from Deployment Solution 6.9 to 7.1 SP1 ... 1 3 4 Migrating from Deployment Solution 6.9 to 7.1 SP1a MR1 ................. 117 118 118 122 124
131 132 133 133
134
Chapter 8
Migrating Monitor Solution ............................................. 137

About migrating Monitor Solution ................................................. 137 About migrating Monitor Pack for Servers ...................................... 138
Chapter 9
Migrating Real-Time System Manager Solution .......... 139

About Real-Time System Manager migration to version 7.1 or later ................................................................................... Manually migrating Real-Time System Manager to version 7.1 or later ................................................................................... About manually migrating Real-Time System Manager files and settings .............................................................................. How to validate Real-Time System Manager after the migration ......... 139 140 141 141
Chapter 10
Migrating Real-Time Console Infrastructure ............... 143

About Real-Time Console Infrastructure migration to version 7.1 or later ................................................................................... 143 Manually migrating Real-Time Console Infrastructure to version 7.1 or later ............................................................................... 144 About manually migrating Real-Time Console Infrastructure files and settings ......................................................................... 144
Contents
11
How to validate Real-Time Console Infrastructure after the migration ............................................................................ 145
Chapter 11
Migrating Carbon Copy Solution .................................... 147

About migrating from Carbon Copy 6.x .......................................... Advantages of using pcAnywhere over Carbon Copy ......................... Before you begin the 6.x migration with pcAnywhere ........................ Migrating from Carbon Copy 6.x .................................................... 147 148 148 149
Chapter 12
Migrating Out of Band Management Component ...................................................................

About Out of Band Management Component migration ..................... Manually migrating Out of Band Management Component ................. Migrating the Intel AMT database ................................................. Reconfiguring the Intel AMT database ........................................... Redirecting the Altiris Agents from Notification Server 6.x ................ About fine-tuning Out of Band Management Component after migration ............................................................................
151 151 152 153 154 155 156
Chapter 13 Chapter 14
Migrating CMDB Solution ................................................ 159

About migrating CMDB Solution ................................................... 159
Migrating Barcode Solution ............................................. 161

About migrating Barcode Solution ................................................. Manually migrating your Barcode Solution files and settings .............. Synchronizing data ..................................................................... Verifying asset data .................................................................... Backing up the Barcode Solution default synchronization profile ................................................................................ Restoring the Barcode Solution default synchronization profile .......... 161 162 163 164 165 165
Chapter 15
Migrating Asset Management Solution ........................ 167

About migrating Asset Management Solution .................................. 167 About data migration special cases ................................................ 168 Migrating legacy software license items .......................................... 169
Chapter 16
Migrating Workflow Solution .......................................... 171

About migrating Symantec Workflow ............................................. 171 Process for upgrading Workflow ................................................... 171
12
Contents
Determining the persistence settings of a project ............................. 174 Creating a version of a project ....................................................... 176
Chapter 17 Chapter 18 Chapter 19
Migrating Inventory Pack for Servers Solution ........... 179

About migrating Inventory Pack for Servers .................................... 179
Migrating Power Scheme Solution ................................. 181

About migrating Power Scheme .................................................... 181
Migrating Recovery Solution ........................................... 183

About migrating Recovery Solution ............................................... 183 Further information about Recovery Solution .................................. 183
Chapter 20
Migrating Mobile Management Solution ...................... 185

About migrating Mobile Management Solution ................................ 185 Further information about Mobile Management Solution .................. 185
Chapter 21 Chapter 22 Chapter 23
Migrating Wise Connector Solution ............................... 187

About migrating Wise Connector ................................................... 187
Migrating from Helpdesk Solution ................................. 189

About migrating from Helpdesk Solution 6.x ................................... 189
Migrating Virtual Machine Management Solution .........................................................................
191
About migrating Virtual Machine Management data ......................... 191
Chapter 24
Migrating IT Analytics Solution ...................................... 193

About migrating IT Analytics data ................................................. 193
Index ................................................................................................................... 195
Chapter
Introducing IT Management Suite

This chapter includes the following topics:

About IT Management Suite What's new in IT Management Suite Solutions of IT Management Suite Components of the Symantec Management Platform 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, and Mac. 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 is comprised of the following management capabilities:
Server management The server management capabilities support not only the Windows operating system, but also the UNIX and the Linux operating systems. In addition, the
14
Introducing IT Management Suite What's new in IT Management Suite
same management disciplines are applied to both physical systems and virtual systems, including both Microsoft Hyper-V and VMware.
Client management The client management capabilities support Windows and a growing number of other platforms, including Mac OS and Linux 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 track 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.
What's new in IT Management Suite

In addition to full server-side 64-bit support, IT Management Suite (ITMS) includes many new features. The new workflow engine lets you automate human and system interactions to help you complete the sequential tasks that are required for efficient service management. Imaging, deployment, and remote control features are now integrated. The central catalog, the software library, and the new user views deliver a deeper functional integration. New IT Analytics capabilities and the central Software Catalog provide greater intelligence. The following are some of the key new features in IT Management Suite:
Optimized scalability and performance This release increases the overall scalability of the Symantec Management Platform. Each Notification Server computer now scales to support more endpoints than the previous versions supported. The overall goal is to streamline your implementations by using less hardware. In addition to numerous improvements in overall performance, the two key changes are to user interaction and to reporting. With the new management interface, page loads are significantly improved. The advanced IT Analytics features let you gain the efficiency of OLAP cubes. The features create faster reporting times by off-loading report data from the operational database.
See About IT Management Suite on page 13.
Solutions of IT Management Suite

IT Management Suite includes many solutions and components.
Introducing IT Management Suite Solutions of IT Management Suite
15
Table 1-1 Suite/Platform

Symantec Management Platform 7.1
IT Management Suite 7.1 solutions and components
Solution/Component
Includes the components such as Network Discovery, Notification Server, Symantec Management Console, and Symantec Management Agent

Symantec Workflow 7.1 IT Analytics 7.1
Asset Management Suite 7.1 Asset Management Solution 7.1

Barcode Solution 7.1 CMDB Solution 7.1
Client Management Suite 7.1 Deployment Solution 7.1 SP1 with a license for 6.9 SP5

Inventory Solution 7.1 IT Analytics Client and Server Pack 7.1 IT Analytics SEP Pack 7.1 Out-of-Band Management Component 7.1 Patch Management Solution 7.1 pcAnywhere Solution 12.6 Real-Time System Manager 7.1 Software Management Solution 7.1 Symantec Endpoint Protection Integration Component 7.1 Wise Connector 7.1 Workspace Virtualization 7.1 Wise Connector 7.1
Server Management Suite 7.1 Deployment Solution 7.1 SP1 with a license for 6.9 SP5

Inventory Solution 7.1 Inventory Pack for Servers IT Analytics Client and Server Pack 7.1 IT Analytics SEP Pack 7.1 Monitor Pack for Servers 7.1 Monitor Solution 7.1 Patch Management Solution 7.1 Real-Time System Manager 7.1 Software Management Solution 7.1 Symantec Endpoint Protection Integration Component 7.1 Virtual Machine Management 7.1 Wise Connector 7.1 IT Analytics ServiceDesk Pack 7.1
Other
16
Introducing IT Management Suite Components of the Symantec Management Platform
See About IT Management Suite on page 13.
Components of the Symantec Management Platform

The Symantec Management Platform includes the following core components:
Notification Server and Symantec Management Console The Symantec Management Platform service that processes events, facilitates communications with managed computers, and coordinates the work of the other Symantec Management Platform services. The console is the Notification Server computer's Web-based user interface that lets you manage the platform and its solutions. Configuration Management Database (CMDB) The database that stores all of the information about managed computers. Site servers The Symantec Management Platform can host several types of middleware components, such as package services, task services, and deployment site services. The official name for a middleware component is "site service." Any component that hosts a site service is known as a site server. Site servers can host one or more of these services. Symantec Management Agent The software that is installed on a computer to enable Notification Server to monitor and manage it. After the Symantec Management Agent is installed, that computer becomes a managed computer. Software Management Framework An interface that lets you create and manage the software resources that are in the Software Catalog. It also lets you manage the packages that are in the Software Library. The Software view provides a central location for initiating the software-related tasks that are performed in your organization. Reports A way to gather automated information. You can view reports for any managed computer from the Symantec Management Console.
Note: Symantec Management Agent was formerly called Altiris Agent, and Symantec Management Console was formerly called Altiris Console. The Data Connector Solution is also now part of the Symantec Management Platform.
Introducing IT Management Suite Where to get more information
17
Where to get more information

Use the following documentation resources to learn about and use this product. See About IT Management Suite on page 13. Table 1-2 Document
Release Notes
Documentation resources Location

The Product Support page, which is available at the following URL: http://www.symantec.com/business/support/all_products.jsp When you open your product's support page, look for the Documentation link on the right side of the page.
Description
Information about new features and important issues.
User guides
Information about how to use this product, including detailed technical information and instructions for performing common tasks. 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 Product Support page, which is available at the following URL: http://www.symantec.com/business/support/all_products.jsp When you open your products support page, look for the Documentation link on the right side of the page.
Help
The Documentation Library, which is available in the Symantec Management Console on the Help menu. Context-sensitive help is available for most screens in the Symantec Management Console. You can open context-sensitive help in the following ways:
The F1 key when the page is active.
Help is available at the The Context command, which is available in the Symantec Management Console on the Help menu. solution level and at the suite level. 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.
18
Introducing IT Management Suite Where to get more information
Table 1-3 Resource

Best practices Support Knowledgebase
Symantec product information resources Location
Description
Compilation of "how to" http://www.symantec.com/docs/HOWTO32608 and best practice articles for IT Management Suite. Articles, incidents, and issues about Symantec products. http://www.symantec.com/business/theme.jsp?themeid=support-knowledgebase
SymWISE Support Knowledgebase Symantec Connect
An online resource that http://www.symantec.com/connect/endpoint-management contains forums, articles, blogs, downloads, events, videos, groups, and ideas for users of Symantec products.
Chapter
Overview of migrating to IT Management Suite


About this migration guide How to use this guide Recommended reading About product parity between versions 6.x and 7.1 About migrating to Symantec Management Platform 7.1 About reusing existing hardware to migrate
About this migration guide

This guide is intended to help you upgrade and migrate your infrastructure to version 7.1 SP2. The guide includes information about the following categories of information:
Migration wizard instructions This release includes a tool that is called the migration wizard. Migration wizard is designed to automate the gathering of data from your previous system so you can bring it into your new system. When you run the wizard, it gathers this data and stores it in a file. After you install version 7.1 SP2 you can use the wizard to import the data in this file into your new system. See About data migration on page 48. Manual data migration instructions
20
Overview of migrating to IT Management Suite How to use this guide
Some data is not stored in your current installed database. The data migration wizard is unable to locate and migrate this data. You must manually copy this data from its previous location to its new equivalent location. After the data has been moved there may be additional steps you must take to make that data function in your new environment. See About the 6.x data that you must manually migrate to Symantec Management Platform 7.1 on page 61. Note: Notification Server was renamed Symantec Management Platform (SMP) on December 03, 2010. All previously categorized articles and references that are listed as Notification Server are now found under Symantec Management Platform. This document lists all Notification Server references for 7.1 as Symantec Management Platform. It lists version 6.0 of the comparable architectural objects by their previous names (Notification Server 6.0, etc.) See Recommended reading on page 21.
How to use this guide

This guide presents a plan to migrate your infrastructure from 6.x to IT Management Suite (ITMS) version 7.1 SP2. This guide includes specific migration functions that you need to follow to migrate data from older versions of Altiris products. To perform an upgrade from ITMS 7.1 or 7.1 SP1 to ITMS 7.1 SP2, in IT Management Suite Planning and Implementation Guide 7.1 SP2 see the topic Upgrading from ITMS 7.1 to ITMS 7.1 SP2. You can also view this information at the following URL: Upgrading to ITMS 7.1 SP2 - Best Practices Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. In addition to this guide, you can use the following guides to help you migrate to IT Management Suite 7.1 SP2:

IT Management Suite Planning and Implementation Guide 7.1 SP2 Symantec Management Platform 7.1 SP2 User Guide Solution-specific user guides
See Where to get more information on page 17.
Overview of migrating to IT Management Suite Recommended reading
21
Each of the guides plays an important role in the migration process, and this guide references them and is a complement to them. Many of the topics in the listed guides are found only in those guides and are not duplicated in this migration guide. See Recommended reading on page 21.
Recommended reading
Before you start the migration process it is important to create a plan to migrate your infrastructure to version 7.1 SP2. The IT Management Suite Planning and Implementation Guide v7.1 SP2 contains migration information about prerequisites, infrastructure architecture, performance tuning, and the installation:
Prerequisites As you develop your migration plan and before you attempt a migration, you should understand migration concepts. For example, you use the Symantec Installation Manager to access the migration wizard tool. This tool is made available to you when you complete a new installation of IT Management Suite. You can then copy the tool to your previous server to use it to harvest previous data. This process works well if you use new hardware to host your new environment. However, if you attempt to reuse previous hardware, then you must access the migration wizard tool before you install IT Management Suite. At actual installation time, your previous Notification Server no longer exists because it was reconfigured with a 64-bit operating system. Infrastructure architecture You must determine the best means to upgrade your specific infrastructure. Infrastructure components can include items such as agents, sub-agents, package servers, and task servers. The decisions you make for upgrading infrastructure components are dependent on your specific scenario. The means that you employ may also depend on the limitations of your IT policies or limitations of your network infrastructure. For example, if your organization has many managed computers, you may not want to immediately enable many management settings during a large agent migration. By not enabling the settings, you reduce the initial load on your Notification Server when the agents initially check in and begin the upgrade. However, after the agents have been successfully migrated, you can then increase the amount of management operations according to your migration plan.
22
Overview of migrating to IT Management Suite About product parity between versions 6.x and 7.1
You can use your previous 6.x Notification Sever to force managed computers to report to your new 7.1 Notification Server. However, if your previous Notification Server is not available at the time you choose to migrate your managed computers, then you cannot leverage this method of agent migration.
Installation You must complete a new IT Management Suite installation regardless of the migration path that you choose. IT Management Suite 7.1 SP2 requires a 64-bit operating system, but its previous versions did not run on a 64-bit operating system. There is no automated way to upgrade your existing IT Management Suite 32-bit installation. For example, if you intend to reuse existing 64-bit capable Notification Server hardware, you must install the 64-bit operating system first. The IT Management Suite Planning and Implementation Guide 7.1 SP2 contains the steps to install IT Management Suite.
You must make similar considerations when you upgrade agents. See About this migration guide on page 19.
About product parity between versions 6.x and 7.1

In IT Management Suite 7.1, some products are replaced or absorbed by another product, or have a new product name. When you install IT Management Suite, you must install at least the same equivalent products that you installed on the 6.x Notification Server. Table 2-1 6.x product
Inventory for Network Devices
6.x to 7.1 Product parity 7.1 equivalent product

Inventory
Comments
Inventory for Network Devices is now part of Inventory Solution. See About Inventory Solution migration with Symantec Notification Server Migration Wizard on page 70.
Overview of migrating to IT Management Suite About product parity between versions 6.x and 7.1
23
Table 2-1 6.x product
6.x to 7.1 Product parity (continued) 7.1 equivalent product

Inventory
Comments
Application Metering is now part of Inventory Solution. See About Inventory Solution migration with Symantec Notification Server Migration Wizard on page 70.
Application Metering
IT Analytics Reporting Pack
Symantec Management Platform
IT Analytics Reporting Pack is now part of the Symantec Management Platform. Workflow Management is now part of the Symantec Management Platform. The full Workflow Management product is part of the Symantec Platform installation and is available to all customers.
Workflow
Symantec Management Platform
Carbon Copy
pcAnywhere
Carbon Copy users are entitled to pcAnywhere. Software Delivery is now called Software Management. Application Management is part of Software Management. ServiceDesk does not upgrade or install over Helpdesk Solution. See About migrating from Helpdesk Solution 6.x on page 189.
Software Delivery
Software Management
Application Management Software Management
Helpdesk
ServiceDesk
24
Overview of migrating to IT Management Suite About migrating to Symantec Management Platform 7.1
Table 2-1 6.x product
6.x to 7.1 Product parity (continued) 7.1 equivalent product

Mobile Management
Comments
Mobile Management Solution is not a part of IT Management Suite 7.1. Handheld Management users are not entitled to Mobile Management 7.1. See About migrating Mobile Management Solution on page 185. See Further information about Mobile Management Solution on page 185.
Handheld Management
VirtualCenter options
Virtual Machine Management
The VirtualCenter options that were part of Deployment Solution 6.9 are now part of Virtual Machine Management.
Software Virtualization
Workspace Virtualization
See Solutions of IT Management Suite on page 14.
About migrating to Symantec Management Platform 7.1

Symantec Management Platform 7.1 requires the Microsoft Windows Server 2008 R2 (64-bit) operating system to host Notification Server. Because Notification Server 6.x used a different operating system than Windows Server 2008 R2, you cannot do an automated, on-box upgrade to 7.1. Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. See About supported IT Management Suite migration paths on page 33. For more information, see topics on system requirements in the IT Management Suite Planning and Implementation Guide.
25
Note: If you have Notification Server 6.x installed on a 64-bit server, you can install the Symantec Management Platform 7.1 products on that computer. However, before you install the Windows 2008 R2 operating system, you must complete specific migration steps. Because some of these migration steps might not complete successfully, Symantec discourages the reuse of the current server. For more information about installing the Symantec Management Platform 7.1 products on your current server, see HOWTO32427. When you migrate to Symantec Management Platform 7.1, you have to create a new database. However, you can migrate a lot of the data that is in your 6.x Notification Server Database although some of the migrated data is read-only. You can also migrate data that is not in the database. See About data migration when migrating from Notification Server 6.x on page 49. For more information, see the documents at https://www-secure.symantec.com/ connect/articles/altiris-endpoint-management-migrations-and-upgrades-71. Note: Symantec Management Platform 7.1 does not support a mixed mode of Notification Servers. A 6.x Notification Server cannot communicate with a 7.1 Notification Server. The migration process consists of the following phases:
Prepare To minimize downtime and ensure success, use the documentation to 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. Symantec recommends that you maintain the test environment for ongoing validation and testing of updates, maintenance packs, and service packs. Install and migrate During this phase, you install Symantec Management Platform 7.1 on a computer running the Windows 2008 R2 operating system. You also migrate existing Notification Server 6.x data from your previous environment to Symantec Management Platform 7.1. You may also manually move some solution-specific data to Symantec Management Platform 7.1. 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 should browse to the migrated data such as policies, reports,
26
and packages and verify their state. After you validate the success of the installation and data migration, you redirect groups of managed computers to report to the new 7.1 Notification Server. Once the managed computers report to the 7.1 server, you use an agent upgrade policy to upgrade their agents.
About testing IT Management Suite

A test server is recommended when you prepare for upgrades or migrations with IT Management Suite 7.1 and future versions. Symantec recommends that you test the migration process, and then familiarize yourself with the new features of 7.1. Ensure that business functional parity is met on the 7.1 configuration. Many of the features have changed with 7.1, but the business functions the tools provide are much greater than with 6.x. When the migration process is complete, Symantec recommends that you continue to maintain the test server to test each update, service pack, or maintenance release that you intend to use in production. See About post migration configuration on page 26. See About validating a migration on page 26.
About post migration configuration

After you have migrated your data, browse through the product and ensure that the data is where it is expected to be. Data that gets migrated is available for different actions, and in some cases for review only. Take some time to familiarize yourself with the data, and ensure that the product is configured to get the data that is not migrated. See About validating a migration on page 26. See About testing IT Management Suite on page 26.
About validating a migration

Much of the effort you make to migrate data is in itself a validation. However, tools are also available to help validate data migration. For example, the migration wizard has a validation process. Other types of data need to be validated manually by browsing through the content in the console. Many of the migration steps in the solution sections of this document enable both the configuration and validation of the data. Because validation is often performed
Overview of migrating to IT Management Suite About reusing existing hardware to migrate
27
as part of the migration process, this document does not include validation-only procedures. See About post migration configuration on page 26. See About testing IT Management Suite on page 26.
About reusing existing hardware to migrate

Symantec recommends that you use a new server to migrate to IT Management Suite 7.1. Keep the 6.x Notification Server available for a duration that fits the needs of your organization. By using a new server, you reduce the downtime that results from re-provisioning the operating system of the Notification Server computer. Before you turn off or re-provision your old server, be sure that the new server meets your business need; otherwise, you may lose data. Keep the old server running so that you can capture any data on it that was not migrated. Also, by keeping the old server running, you can use it for reporting and configuration reference. If you must migrate using the existing hardware that currently houses Notification Server, you must take the following actions:
Thoroughly test the migration process using a test computer to ensure that you capture the data properly before re-provisioning. Ensure that your business functional needs and requirements are not offline for lengths of time outside of SLAs Develop a reliable agent re-direct process. You must know the new server name before you re-provision Notification Server. The agent migration process involves using 6.x policies and agents settings to point agents to the new server.
28
Overview of migrating to IT Management Suite About reusing existing hardware to migrate
Chapter
Migrating Symantec Management Platform


Best practices for migrating to Symantec Management Platform 7.1 Important things to know when migrating from Notification Server 6.x About supported IT Management Suite migration paths Migrating from Notification Server 6.x About data migration About the data store file
Best practices for migrating to Symantec Management Platform 7.1

Before you begin the migration process, you should develop a migration plan. As you develop your migration plan, you should consider these best practices. See About migrating to Symantec Management Platform 7.1 on page 24. Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise.
30
Migrating Symantec Management Platform Best practices for migrating to Symantec Management Platform 7.1
Table 3-1 Best practice

Use a test environment.
Best practices for migrating to Symantec Management Platform 7.1
Description
Before you install Symantec Management Platform 7.1 in a production environment, create a test environment for evaluating and validating the entire installation and migration process. Symantec recommends that you maintain the test environment for ongoing validation and testing of updates, maintenance packs , and service packs. Use a small group of managed computers as a pilot group to test the migration to Symantec Management Platform 7.1. During this pilot test, leave the remaining managed computers supported by the previous version of Notification Server. Make note of the following configuration settings in your current setup before you start the migration process:

Use a pilot test group.
Make note of configuration settings before migrating
Task Server settings Agent communication settings Policy refresh settings Membership update settings
After you have completed the migration you can then revert to these settings if you want. Check logs for errors or warnings Use the Altiris Log Viewer to check the logs for errors or warnings. If you find any errors or warnings, try to resolve them before the upgrade. To open the Log Viewer , in Windows click Start > All Programs > Symantec > Diagnostics > Altiris Log Viewer. Redirect managed computers You can redirect 8,000 computers to a single Notification Server at the same time. in stages. After you have successfully redirected a group of computers, upgrade the Symantec Management Agent and agent plug-ins for that group. To upgrade an agent or an agent plug-in, you enable the upgrade policy for the agent or the agent plug-in.
Note: If you redirect more than 8,000 computers at a time, disable any policies and
tasks that communicate frequently with the Symantec Management Agent. For example, disable the inventory, software delivery, and patch policies. Disabling the policies and tasks prevents the console and Notification Server from being very slow. See About redirecting sites and agents to Notification Server 7.1 on page 39. See About the Symantec Management Agent upgrade policies on page 42.
Migrating Symantec Management Platform Important things to know when migrating from Notification Server 6.x
31
Table 3-1
Best practices for migrating to Symantec Management Platform 7.1 (continued)
Best practice
Keep your previous Notification Server.
Description
Maintain your previous Notification Server computers as a record for historical data, policy configuration details, and other settings and data. The following are some examples of when you might remove the old server:

After the business functional uses on the old server are matched on the new server. After the data saturation on the new server has the needed depth. When the data in the new Configuration Management Database (CMDB) qualifies against your regulatory standards.
Migrate using a new computer.
You must install the Symantec Management Platform 7.1 products on a computer that is running the Windows Server 2008 R2 operating system. Because this operating system is different from what was required for 6.x, Symantec recommends that you install the 7.1 products on a new computer.
Note: If you have Notification Server 6.x installed on a 64-bit server, you can install
the Symantec Management Platform 7.1 products on that computer. However, before you install the Windows 2008 R2 operating system, you must complete specific migration steps. Because some of these migration steps might not complete successfully, Symantec discourages the reuse of the current server. For more information about installing the Symantec Management Platform 7.1 products on your current server, see HOWTO32427.
Important things to know when migrating from Notification Server 6.x

A migration from Notification Server 6.x involves many steps. You should be careful to complete these steps in the recommended order. See Migrating from Notification Server 6.x on page 33. You should also pay particular attention to the following items to avoid major problems during the migration process:
Required version of Notification Server 6.x Before you migrate from Notification Server 6.x to Symantec Management Platform 7.1, you must have Notification Server 6.0 R13 and the latest solutions installed. If you do not have the latest version of Notification Server 6.x, upgrade to the latest version. You must also upgrade your 6.x solutions and the agents on your managed computers. For example, if you have Notification Server 6.0 R11 installed, you must upgrade to 6.0 R13 before you migrate to Symantec Management Platform 7.1.
32
Migrating Symantec Management Platform Important things to know when migrating from Notification Server 6.x
Database and server backup Before you begin the migration, you need to back up the 6.x Notification Server Database and the 6.x Notification Server. If you encounter problems during the migration process, you can then revert to these backups. Back up the Notification Server Database to a secure storage location. Making backups before major migration steps can provide more granular recovery from any issues or unplanned outages that might occur during the process. New database requirement When you install the Symantec Management Platform 7.1 products, you must create a new database. You cannot run Symantec Management Platform 7.1 against the 6.x database. Schema changes were made to the database to increase the speed and to unify the structure of the database. Product parity When you install the Symantec Management Platform 7.1 products, you must install at least the same equivalent products that you installed on the 6.x Notification Server. Before you begin the migration, create a list of the 6.x products that you currently have installed. Warning: Failure to have minimum product parity can result in the inability to migrate 6.x data to the 7.1 database. Keep in mind that some products have been replaced or absorbed by another product, or have a new product name as follows:
Application Management Solution is now part of Software Management Solution. Application Metering Solution is now part of Inventory Solution. pcAnywhere Solution has replaced Carbon Copy Solution. ServiceDesk has replaced Helpdesk Solution. Out of Band Management Solution is now part of Symantec Management Platform. Real-Time System Manager Solution is now part of Client Management Suite. Software Delivery Solution is now Software Management Solution. Software Virtualization Solution is now Workspace Virtualization.
Server name and IP address Symantec recommends that you give the 7.1 server a name and an IP address that is different from the name and IP address of the 6.x server.
Migrating Symantec Management Platform About supported IT Management Suite migration paths
33
Mixed mode Symantec Management Platform 7.1 does not support mixed mode. A Symantec Management Platform 6.x server cannot communicate with a Symantec Management Platform 7.1 server.
About supported IT Management Suite migration paths

Symantec supports migrating to IT Management Suite 7.1 if you currently have one of the following combinations of products installed:
Notification Server 6.x R13 and IT Management Suite 7.0
See Migrating from Notification Server 6.x on page 33.
Migrating from Notification Server 6.x

You must install the Symantec Management Platform 7.1 products on a computer that is running the Windows Server 2008 R2 operating system. Because this operating system is different from what was required for 6.x, Symantec recommends that you migrate to a new computer. For more information, see topics on system requirements in the IT Management Suite Planning and Implementation Guide. Note: If you have Notification Server 6.x installed on a 64-bit server, you can install the Symantec Management Platform 7.1 products on that computer. However, before you install the Windows 2008 R2 operating system, you must complete specific migration steps. Because some of these migration steps might not complete successfully, Symantec discourages the reuse of the current server. For more information about installing the Symantec Management Platform 7.1 products on your current server, see HOWTO32427. When you migrate from Notification Server 6.x to Symantec Management Platform 7.1, you have to create a new database. However, you can use the migration wizard to migrate much of the data that is in your 6.x Notification Server Database. Most of the data that the migration wizard migrates is actionable although some of it is read-only. You can also migrate data that is not in the database. See Important things to know when migrating from Notification Server 6.x on page 31.
34
Migrating Symantec Management Platform Migrating from Notification Server 6.x
See About the data that the migration wizard migrates from Notification Server 6.x on page 51. See About data migration when migrating from Notification Server 6.x on page 49. For more information, see the documents at https://www-secure.symantec.com/ connect/articles/altiris-endpoint-management-migrations-and-upgrades-71. Note: Symantec Management Platform 7.1 does not support a mixed mode of Notification Servers. A 6.x Notification Server cannot communicate with a 7.1 Notification Server. Table 3-2 Step
Step 1
Process for migrating from Notification Server 6.x Description

You must back up the 6.x Notification Server Database before you begin the migration process. You should also back up the 6.x Notification Server. If you encounter problems during the migration process you can then revert to these backups. Back up the database to a neutral storage location.
Action
Back up the 6.x Notification Server Database and the 6.x Notification Server.
Warning: Before proceeding verify that the 6.x Notification

Server Database and the 6.x Notification Server have been successfully backed up. See Backing up the Notification Server Database on page 37. Step 2 Prepare for the migration. On the 6.x Notification Server, complete the precautionary steps before you start the migration process. See Preparing for the migration on page 38.
35
Table 3-2 Step

Step 3
Process for migrating from Notification Server 6.x (continued) Description

The 7.1 server must be running the Microsoft Windows 2008 R2 operating system. Symantec recommends that you give the 7.1 server a different name and IP address from the name and IP addres of the 6.x server. Because the Windows server user accounts are not migrated during the migration, you must recreate them on the 7.1 server the migration process. You should also install the following items:

Action
Prepare the 7.1 server for the installation.
SSL and certificates if you use them. Third-party plug-ins that the products you install require. These plug-ins include Microsoft Silverlight 4.0, Adobe Flash Player 10, and Sun Java Runtime 6.
Step 4
Install Symantec Installation Manager You use Symantec Installation Manager to install the on the 7.1 server. Symantec Management Platform 7.1 products. For more information, see topics on installing Symantec Installation Manager in the IT Management Suite Planning and Implementation Guide.
Step 5
Install the Symantec Management Platform 7.1 products.
You install the Symantec Management Platform 7.1 products with Symantec Installation Manager. Install the same or the equivalent products that you had installed on the 6.x server. When you install the Symantec Management Platform products, you should also install the migration wizard components. During the installation process an Optional Installations page appears where you have the option to install the migration wizard components. You can also install the migration wizard components at any time with Symantec Installation Manager. At the end of the installation process, Symantec Installation Manager prompts you to apply licenses to the solutions you installed. You can also run Symantec Installation Manager at a later time to apply the licenses. For more information, see topics on installing the Symantec Management Platform products in the IT Management Suite Planning and Implementation Guide.
36
Table 3-2 Step

Step 6
Action
Migrate Notification Server 6.x data to You use the migration wizard to migrate 6.x data. the 7.1 server with the migration See Migrating data to Symantec Management Platform 7.1 wizard. with the migration wizard on page 56. See About the data that the migration wizard migrates from Notification Server 6.x on page 51. The migration process consists of the following steps: Install the migration wizard on the 6.x Notification Server. See About installing the Symantec Notification Server Migration Wizard on page 53. Export 6.x data from the 6.x Notification Server to a data store file. See Exporting data from a data store file on page 64. Copy the data store file from the 6.x server to the 7.1 server or to a location that the 7.1 server can access. If a PackageFiles folder exists in the directory where the data store file is created on the Symantec Management Platform 7.0 server, copy that folder to the same directory on the Symantec Management Platform 7.1 server to which the data store files are copied. Import 6.x data from the data store file to the Symantec Management Platform 7.1 server. See Importing Notification Server 6.x data from a data store file on page 59.
Step 7
Verify that the 6.x data was successfully migrated.
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.
Step 8
Move solution-specific items from the Some solution-specific items are not migrated with the 6.x server to the 7.1 server and Notification Server Database or with the migration wizard. configure the solutions. You must manually move these items from the 6.x server to the 7.1 server. See About the 6.x data that you must manually migrate to Symantec Management Platform 7.1 on page 61. You must also configure each of the 7.1 solutions. For more information, see topics on configuration in the documentation for each solution.
37
Table 3-2 Step

Step 9

Before you configure your site servers, you should determine how many site servers you need. You must then create the sites and configure the site servers. For recommendations on the number of site servers that you need, see the IT Management Suite Planning and Implementation Guide. See About redirecting sites and agents to Notification Server 7.1 on page 39. For more information, see topics on site servers in the Symantec Management Platform User Guide.
Action
Configure site servers.
Step 10
Upgrade package servers
If you have 6.x package servers, you must redirect them to the 7.1 Notification Server and upgrade their Altiris Agents with the Symantec Management Agent. The upgrade of the agents also upgrades the site servers. See About upgrading package servers on page 46.
Step 11
Download packages to upgraded package servers
If you upgrade the agent on a package server from a 32-bit to a 64-bit, all packages must be downloaded again. See Promoting migrated Software Packages into the Software Library on page 113.
Step 12
Migrate managed computers
From your 6.x Notification Server, you need to redirect your managed computers so that they report to your new 7.1 Notification Server. You then need to upgrade the Altiris Agent and agent plug-ins on these computers See Migrating managed computers on page 47.
Backing up the Notification Server Database

Backing up the Notification Server Database is the most important fail-safe measure that you can take during the migration process. You can use the backup to restore your database to a known good state if anything should happen to compromise your database. See Migrating from Notification Server 6.x on page 33. To back up the Notification Server Database
1 2
Open Microsoft SQL Manager Studio. In the left pane, expand the Databases folder.
38
3 4 5 6 7
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.
Preparing for the migration

See Migrating from Notification Server 6.x on page 33. On the 6.x Notification Server, complete the following tasks in order: Table 3-3 Step
Step 1 Step 2
Process for preparing for the migration Description

Verify the completion of all outstanding tasks and policies. Document the Windows Server user accounts you have set up on the 6.x server. You must recreate these accounts manually on the 7.1 server.
Action
Verify outstanding tasks Document the Windows Server user accounts
Step 3
Create a backup of the software package Create a backup of your software package files. files Create a list of currently installed products Create a list of the products that you currently have installed. You need to install the equivalent products on the 7.1 server so that the migration wizard can properly migrate the 6.x data. Copy your product licenses to a location that is accessible from the 7.1 server. You must reapply the licenses because they do not migrate. If your licenses are not downloaded or available, you can download them from the Symantec Licensing Portal. For more information about licenses and using the licensing portal, see the Customer Care Information Center. See About migrating licenses to Symantec Management Platform 7.1 on page 48.
Step 4
Step 5
Copy product licenses
39
Table 3-3 Step

Step 6
Process for preparing for the migration (continued) Description

Back up the 6.x database again to capture the most recent data.
Action
Backup 6.x database
About redirecting sites and agents to Notification Server 7.1

Before you redirect sites and agents to the new Notification Server computer, you should develop a redirection plan. Use the guidelines and information in this topic to help you develop that plan. See Redirecting managed computers to Symantec Management Platform 7.1 on page 40. Symantec recommends that you keep the 6.x Notification Server and the Symantec Management Platform 7.1 server running at the same time. Over time you incrementally move groups of client computers to the Symantec Management Platform 7.1 server. By maintaining your 6.x Notification Server, you preserve a historical record of your settings and data. You also have more control over what client computers you move and when you move them. Use the following guidelines when you redirect sites and their package servers to the 7.1 Notification Server:
When you redirect a site, Symantec recommends that you redirect and upgrade its package server before you redirect any other agents within the site. If there is more than one package server for a location or logical group, migrate the package servers with their clients in proportional groups. You redirect and upgrade the package servers first so that they are available in the new environment when the agents in the site are redirected. After a package server is redirected to the 7.1 Notification Server, you must remove the package server from the 6.x Notification Server as soon as possible. You remove a package server from the 6.x Notification Server to prevent the agents that are still in the 6.x environment from communicating with it. After you redirect a package server to the 7.1 Notification Server, upgrade the package server immediately. To upgrade a package server, upgrade the Altiris Agent. You use the Symantec Management Agent upgrade policies on the Symantec Management Platform 7.1 server to upgrade the agent. After the agent is upgraded, the package server is upgraded automatically because the upgrade policy is enabled by default. See About upgrading package servers on page 46. See About the Symantec Management Agent upgrade policies on page 42. See Upgrading the Altiris Agent and the agent plug-ins on page 43.
40
How you redirect sites and agents depends on whether you have sites defined and the number of agents in your environment as follows:
No sites are defined. If the number of agents is less than 8,000, any package servers should be redirected to the new Notification Server and then the Altiris Agents in the site. If the number of agents is more than 8,000, Symantec recommends that you first define sites in the 6.x Notification Server. Each site should have at least one package server and no site should have more than 8,000 agents. After you define the sites, redirect each site to the new Notification Server. When you redirect a site, redirect the package servers and then the agents within the site.
Sites are defined.
If a site has less than 8,000 agents, redirect each package server to the new Notification Server. When you redirect a site, redirect the package servers and then the agents within the site. If a site has more than 8,000 agents, Symantec recommends that you divide the site into smaller sites. If multiple sites share a package server and the sites have a total of less than 8,000 agents, redirect the package servers and sites together. If multiple sites share a package server and the sites have a total of more than 8,000 agents, temporarily remove the package server from the 6.x system. After you redirect all the sites to the new Notification Server, recreate the shared package server.
Redirecting managed computers to Symantec Management Platform 7.1

The Altiris Agents that previously reported to the 6.x Notification Server need to be redirected to Symantec Management Platform 7.1. When you redirect a group of computers, create a filter for the first group of computers that you want to move. You then target the filter with the targeted Altiris Agent Settings policy and exclude it from the targets of other policies. You can then expand the membership of the filter as needed until it includes all computers. See About redirecting sites and agents to Notification Server 7.1 on page 39. Although 20,000 computers can be managed with a single Notification Server, Symantec recommends that you redirect no more than 8,000 computers at the
41
same time. However, it is possible to redirect up to 15,000 computers to a single Notification Server at the same time. Note: If you redirect more than 8,000 computers at a time, disable any policies and tasks that communicate frequently with the Symantec Management Agent. Disabling the policies and tasks prevents the console and Notification Server from being very slow. See Best practices for migrating to Symantec Management Platform 7.1 on page 29. For more information, see topics on the Altiris Agent Settings in the Altiris Notification Server 6.x Help. To redirect computers to Symantec Management Platform 7.1
In the 7.1 environment, install a package service and a task service on a site server to handle clients as they are redirected. By default, a task service is installed on the Symantec Management Platform server. However, Symantec recommends that you always set up at least one task server to service the client computers. Your environment might require multiple site servers. You might elect to redirect a package server and then the clients that use that package server to ensure that packages are available regionally. You can also use virtual machines to serve as temporary site servers during the redirection process. After all the agents for those sites have upgraded, you should then remove the virtual machines.
Remove all sub-agents or plug-ins from your managed computers. However, on your Package Servers do not remove the Package Server Agent. See About removing sub-agents or agent plug-ins from managed computers on page 45.
In the 6.x console, on the Configuration tab, click Altiris Agent > Altiris Agent Configuration, and select the policy that contains the agents that you want to redirect to 7.1. On the policys Altiris Agent Settings page, click the Advanced Settings tab. In the Alternate URL for accessing NS section, specify the URL for the 7.1 Notification Server as follows:
4 5
Server Name Symantec recommends that you use the fully qualified domain name.
42
Server Web The Server Web address should be in the following format: https://<NS_FQDN>:<port>/Altiris/
Click Apply.
About the Symantec Management Agent upgrade policies

You use a Symantec Management Agent upgrade policy to upgrade the Altiris Agent on your managed computers. To perform the upgrade, you select and enable the appropriate policy and apply it to a set of computers. Upgrade the Altiris Agent with the Symantec Management Agent before you upgrade the agent plug-ins. See Upgrading the Altiris Agent and the agent plug-ins on page 43. The Symantec Management Agent has a set of site server upgrade policies and a set of upgrade policies for all other computers. Both sets have one policy for upgrading 64-bit computers and another policy for upgrading 32-bit computers. The 64-bit upgrade policies update computers to the 7.1 SP2 64-bit agent, while the 32-bit policies update computers to the 7.1 SP2 32-bit agent. The upgrade polices for the Symantec Management Agent are in a Non Site Server folder and a Site Server folder. To access these folders, on the Settings menu, click Agents/Plug-ins > Symantec Management Agent and expand the Windows folder. Note: The upgrade policy for the Symantec Management Agent for UNIX/Linux/Mac is in the UNIX/Linux/Mac folder. When you install a 64-bit agent on a computer, 64-bit sub-agents or plug-ins are installed when they are available. If a 64-bit plug-in is not available, a 32-bit plug-in is installed, and it runs in a surrogate service that was created for this scenario. When you install a 32-bit agent on a 64-bit computer, 32-bit sub-agents or plug-ins are installed. Warning: If you install the 32-bit agent on a 64-bit computer, the agent may have trouble returning some inventory data because it is runs in the WOW64 memory space. Applications that run in the WOW64 memory space do not see the actual registry and file system on a 64-bit computer. For more information, see topics on file system redirector and registry redirector in the Microsoft MSDN library.
43
Note: When you install the Symantec Management Agent with a scheduled push install on a 64-bit computer, the 64-bit agent is installed by default. However, if you check the Force installation of 32-bit Symantec Management Agent on 64-bit systems option, the 32-bit agent is installed. The option to force a 32-bit installation is on the Symantec Management Agent Installation Options dialog box. You access this dialog box when you click the Settings option on the Symantec Management Agent Install page.
Upgrading the Altiris Agent and the agent plug-ins

After you migrate to Symantec Management Platform 7.1, you need to upgrade the Altiris Agent and agent plug-ins on the client computers. Upgrade the Altiris Agent before you upgrade the agent plug-ins. You upgrade the Altiris Agent with the Symantec Management Agent upgrade policy. See About the Symantec Management Agent upgrade policies on page 42. See Migrating from Notification Server 6.x on page 33. Warning: If you install the 32-bit agent on a 64-bit computer, the agent may have trouble returning some inventory data because it is runs in the WOW64 memory space. Applications that run in the WOW64 memory space do not see the actual registry and file system on a 64-bit computer. For more information, see topics on file system redirector and registry redirector in the Microsoft MSDN library.
Note: Symantec recommends that you keep your 6.x Notification Server running for six months to 12 months for reporting and configuration reference.
44
To upgrade the Altiris Agent and the agent plug-ins
Remove the sub-agents or agent plug-ins from all of the managed computers. Symantec recommends that you remove all agent sub-agents or agent plug-ins from your managed computers to avoid any potential problems during the upgrade process. However, on your package servers, you should also leave the Package Server Agent. See About removing sub-agents or agent plug-ins from managed computers on page 45.
In Notification Server 6.x, redirect the managed computers to Symantec Management Platform 7.1. See About redirecting sites and agents to Notification Server 7.1 on page 39. See Redirecting managed computers to Symantec Management Platform 7.1 on page 40.
In Symantec Management Platform 7.1, use filters and targets to create a test group of clients on which to test the upgrade of the agent and the installation of the agent plug-ins. Note: If you did not remove a 6.x sub-agent, you would use an upgrade policy to install the 7.1 plug-in. However, because Software Management Solution, pcAnywhere Solution, and Inventory Solution, do not have an equivalent 7.1 product, you must use an installation policy to install the plug-ins for these products.
4 5
For the test group, enable the Symantec Management Agent upgrade policy. For the test group, enable the installation policies for the agent plug-ins that correspond to the plug-ins that were installed on client computers before you migrated to 7.1. For the test group, validate that policies, tasks, and other functionality works correctly.
45
For the rest of your client computers, repeat the preceding steps that you performed on the test group. You can broaden the scope a few thousand clients at a time. Symantec recommends that you do not upgrade more than 8,000 clients at the same time. You can upgrade up to 15,000 clients at the same time. However, you should then disable any policies and tasks that communicate frequently with the Symantec Management Agent.
For the clients that are not available during the migration, ask your network team to make the following change:

Delete the Altiris Notification Server 6.0 DNS A Record. Create DNS Alias (CNAME) to direct the host name for Notification Server 6.x to Symantec Management Platform 7.1.
Keep these settings in place until the upgrade of the agent and the agent plug-ins is completed on all of the remaining clients.
About removing sub-agents or agent plug-ins from managed computers

Before you redirect your 6.x managed computers to Symantec Management Platform 7.1, Symantec recommends that you remove all sub-agents or agent plug-ins from those computers. You should remove these sub-agents from your managed computers to avoid any potential problems during the migration process. You should leave only the Altiris Agent on the managed computers. However, on your package servers, you should also leave the Package Server Agent installed. See Upgrading the Altiris Agent and the agent plug-ins on page 43. See Redirecting managed computers to Symantec Management Platform 7.1 on page 40. Before you remove the sub-agents, create a record of where the sub-agents are installed. You can use the collections that target the currently installed sub-agents to create the record. After the sub-agents are removed, you have no way to determine where they were installed. However, if you create a record, you can use this record to ensure that you use the same distribution when you install the 7.1 plug-ins. You can also export the 6.x collections for agent distribution to CSV files. You can then import the CSV files to create new static filters that you can use to distribute the 7.1 plug-ins. The preferred method for removing the plug-ins is to use predefined collections and policies. You can also run AeXagentUtil.exe with the /UninstallAgents parameter.
46
About upgrading package servers

You need to upgrade your package servers before you redirect your managed computers to the 7.1 Notification Server. To upgrade a package server, redirect it to the 7.1 Notification Server and upgrade its Symantec Management Agent. Make sure the policies that upgrade the services are enabled to upgrade the site servers. The Legacy Windows Package Server Agent Upgrade policy upgrades the package servers. See Upgrading the Altiris Agent and the agent plug-ins on page 43. See About redirecting sites and agents to Notification Server 7.1 on page 39. For a lengthy migration, Symantec recommends that you set up temporary package servers or move your package servers in proportional groups along with their clients. For example, suppose you have 10,000 clients pointing to a Notification Server and four package servers. You do not want to leave either your old or new Notification Server with no package servers. You should either add temporary site servers or move 1/4 of your package servers with 1/4 of your clients. When you set up package servers, you prepare the network topology for the agent packages that are available from regional package servers. If you have remote sites with a slow connection, you should upgrade their package servers before you upgrade the agents on the clients. By upgrading the package servers, you reduce the load of the package traffic. Warning: Do not upgrade package servers before their client base is targeted to be upgraded. If you upgrade the agent on a package server to a 64-bit agent, its 32-bit assemblies are removed and 64-bit assemblies are installed. The existing registry and folder structure for packages remains intact. If you upgrade the agent on a package server to a 32-bit agent, the package server is also upgraded to 32-bit. After a package server is upgraded, it downloads any new 7.1 system-based packages that the 7.1 Notification Server hosts. These packages include all solution plug-ins. Any package that has not changed is not re-downloaded. To access the package server agent upgrade policy, on the Settings menu, click All Settings. You then navigate to Settings > Notification Server > Site Server Settings > Package Service > Advanced > Windows > Legacy Windows Package Server Agent Upgrade.
47
Migrating managed computers

After you have successfully installed the Symantec Management Platform products, migrated Notification Server data, and configured the solutions, you need to migrate the managed computers. See Migrating from Notification Server 6.x on page 33. Table 3-4 Step
Step 1
Process for migrating managed computers Description

Symantec recommends that you remove all sub-agents or agent plug-ins from your managed computers. You should leave only the Altiris Agent on the managed computers. For package servers, you should also leave the Package Server Agent. See About removing sub-agents or agent plug-ins from managed computers on page 45.
Action
Remove sub-agents or agent plug-ins from your managed computers
Step 2
Redirect the Altiris Agents to the new server.
The Altiris Agents that previously reported to the 6.x Notification Server need to be redirected to the 7.1 Notification Server. See Redirecting managed computers to Symantec Management Platform 7.1 on page 40.
Step 3
Upgrade the Altiris Agent and the agent After you have successfully redirected a group of computers, plug-ins. upgrade the Altiris Agent and agent plug-ins for the clients in the group. Upgrade the Altiris Agent before you upgrade the plug-ins. You upgrade the Altiris Agent with the Symantec Management Agent upgrade policy. To upgrade an agent or an agent plug-in, you enable the upgrade policy for the agent or plug-in. See Upgrading the Altiris Agent and the agent plug-ins on page 43. See About the Symantec Management Agent upgrade policies on page 42. For more information, see topics on Symantec Management Agent settings and configuring the agent upgrade in the Symantec Management Platform User Guide.
48
Migrating Symantec Management Platform About data migration
Table 3-4 Step

Step 4
Process for migrating managed computers (continued) Description
Action
Verify that the Altiris Agent is migrated Symantec Management Platform provides multiple reports to the new Symantec Management that assist in validating the migration process. Platform 7.1 Server and also that the To access the reports, on the Reports menu, click All Agent version is upgraded. Reports. In the left pane click Reports > All Reports > Notification Server Management > Agent. Some of the common reports to use are:

Agent Version Agent Requests
About migrating licenses to Symantec Management Platform 7.1

When you migrate from Notification Server 6.x to Symantec Management Platform 7.1, the licenses for your products are not migrated. You must copy the 6.x licenses to a location where you can access them on the Symantec Management Platform 7.1 server. See Migrating from Notification Server 6.x on page 33. After you migrate the licenses, you must apply them. You can apply the licenses when you install a product or at a later time. You apply the licenses on the Product Licensing page in Symantec Installation Manager. For more information, see topics on applying licenses in the IT Management Suite Planning and Implementation Guide. If your licenses are not available, you can download them from the Symantec Licensing Portal. If you cannot apply your old licenses in Symantec Installation Manager, then you must also download new licenses from the licensing portal. For more information about licenses and using the licensing portal, see the Customer Care Information Center. Note: Because some Notification Server 6.x solutions bundle with other solutions on Symantec Management Platform 7.1, their licenses cannot be reused.
About data migration

When you migrate to Symantec Management Platform 7.1, you can also migrate the Notification Server 6.x data to Symantec Management Platform 7.1.
49
See About data migration when migrating from Notification Server 6.x on page 49. Symantec provides the following tools to assist in the process of migrating data to Symantec Management Platform 7.1:
Symantec Installation Manager You use the Symantec Installation Manager to install the migration wizard components. The migration wizard components give you access to the Symantec Notification Server Migration Wizard. See About installing the Symantec Notification Server Migration Wizard on page 53. Symantec Notification Server Migration Wizard You use the Symantec Notification Server Migration Wizard to migrate Notification Server 6.x data to Symantec Management Platform 7.1. See About the Symantec Notification Server Migration Wizard on page 50. See About the data that the migration wizard migrates from Notification Server 6.x on page 51. Deployment Solution migration tools Deployment Solution includes a tool for migrating 6.x images to 7.1. See About architecture and features of Deployment Solution 7.1 SP1 on page 118.
For more information, see the documents at https://www-secure.symantec.com/ connect/articles/altiris-endpoint-management-migrations-and-upgrades-71.
About data migration when migrating from Notification Server 6.x

When you migrate from Notification Server 6.x, you use the Symantec Notification Server Migration Wizard to migrate Notification Server 6.x data. Some of the 6.x data that you can migrate is actionable, while some it is read-only. See About the data that the migration wizard migrates from Notification Server 6.x on page 51. See About data migration on page 48. See About the Symantec Notification Server Migration Wizard on page 50. Consider the following before you use the migration wizard to migrate 6.x data to Symantec Management Platform 7.x:
Some 6.x data is more difficult to replace than other data. Asset data represents the physical items that you may not be able to gather automatically after you migrate to Symantec Management Platform 7.1. This data represents a lot of manual data entry and is an excellent candidate for
50
data migration. On the other hand, inventory data is replaced within a week after you migrate to Symantec Management Platform 7.1. Consequently, the inventory data is not as good a candidate for migration as the asset data.
Symantec Management Platform 7.1 cannot use some 6.x data. After you migrate data, some of it is not editable and some is not actionable because of fundamental changes in how Symantec Management Platform works. For example, when you migrate the 6.x collections, the collections are actionable but not editable. Because Symantec Management Platform 7.x uses filters instead of collections, Symantec recommends that you convert your collections to filters. Migrated 6.x custom reports are also read-only. You cannot update the 6.x custom reports to include 7.1 information. However, you can use your 6.x reports for audit and reference purposes. Some 6.x data requires your configuration after migration. Some 6.x data requires your configuration before you can use it in Symantec Management Platform 7.1. For example, you can migrate custom agent settings policies, but you should apply filters to the policies to replace the 6.x collections.
About the Symantec Notification Server Migration Wizard

When you migrate to Symantec Management Platform 7.1, you use the Symantec Notification Server Migration Wizard to migrate the existing Notification Server 6.x data. See About the data that the migration wizard migrates from Notification Server 6.x on page 51. See About data migration on page 48. Migrating data with the migration wizard involves the following steps:

Export the data to a data store file with the migration wizard. Copy the data store file to a location that the Symantec Management Platform 7.1 server can access. If a PackageFiles folder exists in the directory where the data store file is created on the Symantec Management Platform 7.0 server, copy that folder to the same directory on the Symantec Management Platform 7.1 server to which the data store files are copied. Import the data from data store file with the migration wizard.
See About the data store file on page 62. To migrate data with the migration wizard, you must install the migration wizard on your 6.x server and on the 7.1 server.
51
See About installing the Symantec Notification Server Migration Wizard on page 53. The migration wizard uses exporters to export data and a corresponding set of importers to import data. Each product that has data to migrate has its own set of exporters and importers. By default, the migration wizard exports and imports all of the data. Symantec recommends that you use the default setting to export and import all of the data. The EXE for the migration wizard is NSUUpgradeWizard.exe, and it is in the C:\Program Files\Altiris\Upgrade directory by default. To run the migration wizard, you must be a member of the local administrators group.
About the data that the migration wizard migrates from Notification Server 6.x
When you migrate from Notification Server 6.x, you use the Symantec Notification Server Migration Wizard to migrate Notification Server 6.x data. Some of the 6.x data that you can migrate is actionable, while some it is read-only. See About data migration on page 48. See About data migration when migrating from Notification Server 6.x on page 49. See About the Symantec Notification Server Migration Wizard on page 50. Note: You cannot migrate 6.x custom menu items with the migration wizard. You must manually export the 6.x menus from the 6.x console and import them into the 7.1 console. Table 3-5 Platform data that the migration wizard migrates from Notification Server 6.x
Data
Security roles
Description
You can migrate predefined security roles and custom security roles.
Note: If you create a custom 6.x security role and give it permissions on predefined items such
as reports or policies, the permissions are not migrated. However, permissions on custom items are migrated. Certificates - KMS/ You can migrate KMS and Credential Manager keys. PPA keys
52
Table 3-5
Platform data that the migration wizard migrates from Notification Server 6.x (continued)
Data
Collections
Description
You can migrate the non-default collections, and they are actionable but not editable. If you use the collections, you should validate that they work correctly. Because Symantec Management Platform 7.x uses filters instead of collections, Symantec recommends that you convert your collections to filters. After you migrate your custom collections, you can use them as a reference when creating filters. You can migrate custom notification policies and custom agent settings policies. The custom notification policies are read-only, but the custom agent settings policies are actionable. You can migrate task-based policies, and they are actionable. These policies are referred to as client task schedules in the 6.x console. You can migrate predefined and custom reports, but they are read-only. You can use the reports for audit and reference purposes. You should replace the 6.x reports with 7.1 reports to reflect your current data. Some of the reports you migrate may try to use the data that did not migrate and the reports then have incomplete data. You should validate the migrated reports against the reports in the 6.x console.
Policies
Task-based policies Reports
Jobs and Tasks Resource association Packages
You can migrate 6.x jobs and tasks, and they are actionable. You can migrate 6.x resource associations, and they are actionable.
You can migrate the Software Delivery packages that are stored locally and their command lines. If a package and a command line are linked to a 6.x task, they are linked to the corresponding 7.1 task or policy after migration. A 6.x task becomes a 7.1 task or policy as follows:

A Software Delivery task becomes a Legacy Delivery task. A Sequential Software Delivery task becomes a Managed Software Delivery policy. A Software Delivery Task Server task becomes a Package Delivery task.
A migrated package is not associated with a software resource or placed in the Software Library by default. Before you deliver a package with Quick Delivery, Managed Software Delivery, or the Software Portal, associate the package with a software resource. When you import a software delivery package, it is imported to the same location it had on the 6.x server unless you specify an alternate location. See Promoting migrated Software Packages into the Software Library on page 113. You can also migrate all patch packages regardless of where they are stored. The packages are imported into the default location.
53
Table 3-5
Platform data that the migration wizard migrates from Notification Server 6.x (continued)
Data
Portal pages and Web parts Console view
Description
You can migrate portal pages and Web parts, and they are actionable.
You can migrate console views, and they are actionable.
Right-click actions You can migrate the user-defined actions that you have added to a right-click menu. Rules You can migrate predefined and custom 6.x Inventory Forwarding rules. When you migrate these rules, they are converted to 7.1 replication rules. You can also migrate Connector rules and Active Directory Import rules.
Warning: The migration wizard changes the CMDB rules Update Mode from Append to Update
even if it is originally set to Append in 6.x. The rules migrate and work. However the way they function is not the same. A rule that has its Update Mode set to Append in 6.x, has after the migration to 7.1 changed its mode to Update.
For information about the solution-specific data that the migration wizard migrates, see the following:
Patch Management Solution See Data that can be migrated from the 6.x version of Patch Management Solution for Windows on page 102. Inventory Solution See About Inventory Solution migration with Symantec Notification Server Migration Wizard on page 70. Software Management Solution See Items that can and items that cannot be migrated from software delivery solutions 6.x on page 106. Asset Management Solution See About data migration special cases on page 168.
About installing the Symantec Notification Server Migration Wizard

You use the Symantec Notification Server Migration Wizard to migrate data from Notification Server 6.x to Symantec Management Platform 7.1. To migrate data with the migration wizard, you must install the migration wizard on your 6.x server and on the 7.1 server. See About data migration on page 48. See About the Symantec Notification Server Migration Wizard on page 50.
54
Note: To install the migration wizard, .NET Framework 2.0 is required.
Note: To run the migration wizard, you must be a member of the local administrators group. Table 3-6 About installing the Symantec Notification Server Migration Wizard How to install the migration wizard
Use Symantec Installation Manager on the computer to install the migration wizard components. After you select the products to install, Symantec Installation Manager displays an Optional Installations page that includes the Install Migration Wizard Components option. If you check this option, the migration wizard components are installed with the selected products. You can also access the Optional Installations page at a later time to install the migration wizard components.
Where you want to install the migration wizard

Symantec Management Platform 7.1 server computer
55
Table 3-6
About installing the Symantec Notification Server Migration Wizard (continued) How to install the migration wizard
Copy the migration wizard installation package from the Symantec Management Platform 7.1 server. The migration wizard installation package has a 32-bit and a 64-bit version. Copy the 32-bit version. You then run the installation package to install the migration wizard. The migration wizard installation package is only available on the 7.1 server if you have installed the optional migration wizard components on that computer. By default, the migration wizard installation package is installed at C:\Program Files\Altiris\Symantec Installation Manager\MigrationPackage.
Where you want to install the migration wizard

Notification Server 6.x computer
Note: The MigrationPackage folder contains

four files. Two of the files include the word "silent" in their name. Use the migration package files that do not contain the word "silent" to install the migration wizard.
Note: You can install 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 6.x Notification Server computer and migrate its data. You might install just the migration wizard if you need to install the Symantec Management Platform 7.1 products on your 6.x Notification Server computer. However, Symantec discourages the reuse of your current server. For more information about installing the Symantec Management Platform 7.1 products on your current server, see HOWTO32427.
56
Migrating data to Symantec Management Platform 7.1 with the migration wizard
You use the Symantec Notification Server Migration Wizard to migrate Notification Server 6.x data to Symantec Management Platform 7.1. This topic provides an overview of the process of migrating data with the migration wizard. See About the Symantec Notification Server Migration Wizard on page 50. See About the data that the migration wizard migrates from Notification Server 6.x on page 51. Table 3-7 Process for migrating data to Symantec Management Platform 7.1 with the migration wizard Description
Step
Step 1
Action
Install the migration wizard on the 6.x Before you can migrate data with the migration wizard, you Notification Server. must first install it. You use Symantec Installation Manager to install the migration wizard components on the 7.1 server. You then copy the migration wizard installation package to your current Notification Server and install it. See About installing the Symantec Notification Server Migration Wizard on page 53.
Step 2
Export 6.x data to a data store file.
After the migration wizard is installed on the 6.x Notification Server, it starts in export mode. The migration wizard lets you export 6.x data to a data store file. You can also manually run the migration wizard and export data multiple times. See Exporting Notification Server 6.x data to a data store file on page 57. See About the data store file on page 62.
Step 3
(Optional) View the data in the data store file.
After you export data to a data store file, you can use Store Browser to view the data that was exported. See Viewing the data in a data store file on page 63.
Step 4
(Optional) Compare two data store files. If you export 6.x data multiple times, you can use StoreDiff to compare two data store files. StoreDiff creates a data store file that contains the differences between the two data store files. You can then use Store Browser to view these differences. See Comparing two data store files on page 65.
57
Table 3-7
Process for migrating data to Symantec Management Platform 7.1 with the migration wizard (continued) Description
You need to copy the migration data to a location that is accessible to the Symantec Management Platform 7.1 server. By default, a data store file is created in the Altiris\Upgrade\Data directory. If package files are exported, this directory also contains a PackageFiles folder. You must put the PackageFiles in the same directory where you put the data store file. You may also want to copy this data to a neutral location to back up the data.
Step
Step 5
Action
Copy the migration data to the Symantec Management Platform 7.1 server.
Step 6
Import the 6.x data to Symantec Management Platform 7.1.
On the Symantec Management Platform 7.1 server, use the migration wizard to import the 6.x data. If the migration wizard is not installed on this computer, you must first install it. See About installing the Symantec Notification Server Migration Wizard on page 53. See Importing Notification Server 6.x data from a data store file on page 59.
Step 7
Configure 6.x data that is not compatible with 7.x features.
You must configure some 6.x data after it is migrated to make it compatible with new 7.x features. For example, a migrated 6.x software delivery package is not compatible with Quick Delivery and Managed Software Delivery in Software Management Solution. Before you can use these delivery methods to deliver the migrated package, you must promote the package to the Software Library. See Promoting migrated Software Packages into the Software Library on page 113.
Exporting Notification Server 6.x data to a data store file

When you migrate to Symantec Management Platform 7.1, you use the Symantec Notification Server Migration Wizard to migrate Notification Server 6.x data. When you use the migration wizard, one step in the migration process is to export the 6.x data to a data store file. By default, the data store file is saved in the C:\Program Files\Altiris\Upgrade\Data directory. See Migrating data to Symantec Management Platform 7.1 with the migration wizard on page 56.
58
See About data migration on page 48. See About the data store file on page 62. When the migration wizard runs in export mode, it uses exporters to export data. Each product that has data to migrate has its own set of exporters. By default, the migration wizard exports all of the data. Symantec recommends that you use the default setting to export all of the data. When you export data, additional data migration files may be created and saved in this same directory. For example, when you export locally saved software package files, a PackageFiles folder is created that contains folders for all of the package files. To export Notification Server 6.x data to a data store file
Install and run the migration wizard on the 6.x Notification Server. After the migration wizard is installed on the 6.x Notification Server, 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. See About installing the Symantec Notification Server Migration Wizard on page 53. See About the Symantec Notification Server Migration Wizard on page 50.
2 3
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 7.1 server.
On the Exporter Configuration page, select the data to export, and click Next. Symantec recommends that you select all of the available data. See Exporter Configuration or Importer Configuration page on page 60.
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.
59
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.
8 9
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.
Importing Notification Server 6.x data from a data store file

You use the Symantec Notification Server Migration Wizard to migrate Notification Server 6.x data to Symantec Management Platform 7.1. When you use the migration wizard, one step in the migration process is to import the 6.x data from a data store file. See Migrating data to Symantec Management Platform 7.1 with the migration wizard on page 56. See About the data store file on page 62. See About the Symantec Notification Server Migration Wizard on page 50. When the migration wizard runs in import mode, it uses importers to import data. Each product that has data to migrate has its own set of importers. By default, the migration wizard imports all of the data. You can import all of the data at one time or perform multiple imports and import the data in stages. For example, you can perform an import for each product and then check the data after each import. If you do not import all of the data initially, you must manually run the migration wizard for subsequent imports. If you import the same data twice, the last import overwrites any previous import. To import Notification Server 6.x data from a data store file
Do one of the following to start the migration wizard in the import mode:
Install the migration wizard on the Symantec Management Platform 7.1 server with Symantec Installation Manager. By default, the migration wizard starts after it is installed. See About installing the Symantec Notification Server Migration Wizard on page 53.
60
See About the Symantec Notification Server Migration Wizard on page 50.
Run the migration wizard EXE manually. When you install the optional migration wizard components, the migration wizard EXE is installed. The EXE for the migration wizard is NSUpgradeWizard.exe, and by default it is in the C:\Program Files\Altiris\Upgrade directory.
2 3 4 5
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 6.x 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. See Exporter Configuration or Importer Configuration page on page 60.
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.
7 8
On the Task Summary page, verify the migration tasks the wizard is about to perform, and click Next. When the message that the data import has completed successfully appears, click OK. If the data is not imported successfully, a message with instructions appears.
(Optional) To display each actions sub-actions, check Show Details.
10 Click Finish.
Exporter Configuration or Importer Configuration page

These configuration pages let you select the products whose data you want to migrate. For each product, you can select the exporters or importers to use. These exporters or importers define what data is migrated. For each exporter or importer, you can filter the data to export or import. To access these configuration pages, run Symantec Notification Server Migration Wizard. The Exporter Configuration page appears when the migration wizard runs in export mode. The Importers Configuration page appears when the migration wizard runs in import mode. See About data migration on page 48.
61
See About the Symantec Notification Server Migration Wizard on page 50. Table 3-8 Option
Products
Options on the configuration pages Description

Displays the products whose data you can migrate. Data is exported or imported only for the products that are checked. Displays the exporters or importers for the product that is selected in the Products section. Data is exported or imported only for the exporters or importers that are checked in the Enabled column. Displays a dialog box that lets you filter the data that an exporter or 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.
Importers or Exporters
Filters
About the 6.x data that you must manually migrate to Symantec Management Platform 7.1
When you migrate from Notification Server 6.x to Symantec Management Platform 7.1, not all of the data is migrated with the migration wizard. You must manually migrate some data from the 6.x server to the 7.1 server. For some of the migrated data, you must also complete additional manual steps to make the data fully functional. See Migrating from Notification Server 6.x on page 33. See About migrating licenses to Symantec Management Platform 7.1 on page 48. The following products require some manual migration steps:
Inventory Solution See About manual Inventory Solution migration on page 72. Software Delivery Solution See Migrating from Software Delivery Solution 6.x to Software Management Solution 7.1 on page 110. Patch Management Solution
62
Migrating Symantec Management Platform About the data store file
Asset Management Solution See About migrating Asset Management Solution on page 167. Barcode Solution See Manually migrating your Barcode Solution files and settings on page 162. Out-of-band Management Solution See Manually migrating Out of Band Management Component on page 152. Real-Time System Management Solution See About manually migrating Real-Time System Manager files and settings on page 141. Real-Time Console Infrastructure Solution See About manually migrating Real-Time Console Infrastructure files and settings on page 144.
You must also copy the licenses of your Notification Server 6.x products to a location that is accessible from the 7.1 server.
About the data store file

A data store file stores Notification Server data. When you migrate Notification Server 6.x to Symantec Management Platform 7.1 with the migration wizard, you use a data store file. First, you export the 6.x data to a data store file. You then import the data from the data store file into Symantec Management Platform 7.1. See About the Symantec Notification Server Migration Wizard on page 50. By default, the data store file is saved in the C:\Program Files\Altiris\Upgrade\Data directory. It has an .adb extension, is easy to copy and back up, and is not dependent on SQL. You can view the data in a data store file with the Store Browser. If you perform multiple imports, you can view the data to determine which data to import next. The data store file organizes all the data except key data by product. The data for each product is stored in tables. The name of each table is ProductName.TableName. See Viewing the data in a data store file on page 63.
About the Store Browser

The Store Browser lets you do the following with data store files:
Analyze the data before you import it.
63
The Store Browser lets you view each table and the data in each row of a table before you import the data. If you perform multiple imports, you can view the data to determine what data to import next.
Export specific data to create a smaller data store file. If you encounter errors when you import data, you may need to send a data store file that contains the data to Symantec Technical Support. The Store Browser lets you export specific data to create a smaller data store file that is more portable. See Exporting data from a data store file on page 64. View differences between two data store files. If you have two similar data store files, you can use the StoreDiff utility to create a data store file that highlights their differences. The Store Browser lets you open this data store file and view the differences. See Comparing two data store files on page 65.
See About the data store file on page 62. See Viewing the data in a data store file on page 63. By default, the EXE for the Store Browser is installed at C:\Program Files\Altiris\Upgrade. It is installed whenever the migration wizard is installed.
Viewing the data in a data store file

You use Symantec Notification Server Migration Wizard to migrate Notification Server 6.x data to Symantec Management Platform 7.1. When you migrate data with the migration wizard, you export the data to a data store file and then import the data from the data store file. After you create a data store file, you can use the Store Browser to view the data in the data store file. See About data migration on page 48. See About the data store file on page 62. See About the Store Browser on page 62. To view the data in a data store file
Double-click StoreBrowser.exe. By default, this file is installed at C:\Program Files\Altiris\Upgrade.
2 3
In the Store Browser, on the File menu, click Open and select the data store file. In the Table Name column, select a table. The rows of the table appear in the right pane.
64
To search for specific data in a table, use the following options at the bottom of the right pane:
Starting index Type a number of a table row, and click Refresh. The table row becomes the first row in the right pane. Type the search criteria, and select the columns of the table in which to perform the search. All rows in the table that match the search criteria are highlighted. To use regular expressions for the search criteria, check Regex. Check this option to highlight the text that does not match the search criteria. Check this option to perform a search with regular expressions. You then type the regular expression in Find. Click this option to complete the search. Click this option to move to the next row that matches the search criteria.
Find
Inverse
Regex
Refresh Find Next
If a table row has an Xml column, do the following to view the XML:

Double-click the row. In the Data View for table dialog box, on the first Column drop-down list, click the XML entry. The XML appears in the Value pane. On the second Column drop-down list, click View as XML.
Exporting data from a data store file

If you encounter errors when you import data from a data store file, you may need to send the file to Symantec Technical Support. For a large file, you can use Store Browser to create a data store that is a subset of the original data store file. You can export the data that causes the errors and then send this smaller file to support so that they can help resolve the problem. See About the Store Browser on page 62. See About the data store file on page 62. When you export data with the Store Browser, you can select the data tables to export and the specific rows in the data tables. You can specify the rows to export with row numbers, row ranges, or a data string.
65
To export data from a data store file
Double-click StoreBrowser.exe. By default, this file is installed at C:\Program Files\Altiris\Upgrade. It is installed whenever the migration wizard is installed.
2 3 4
In the Store Browser, on the File menu, click Open, and select the data store file that contains the data. On the File menu, click Export Data. In the Export Data Form dialog box, in the Export column, check the tables whose data you want to export. The NSCore.ExporterVersionInfo table is always exported. It contains the data that the migration wizard needs to import the data from the data store file.
To export the data for specific rows of a table, click in the Rows to Export column and specify the rows as follows:

In the Export Options Form dialog box, click Specified Rows. To specify rows by row number, check Row Ranges, and list the rows. To specify the rows that contain a data string, check Containing String, and define the string. Click OK.
6 7
In the Export Data Form dialog box, in Destination Store, specify the name and location for the new data store file. Click Export.
Comparing two data store files

You can export the same type of 6.x data to a data store file multiple times. If the data on the 6.x server changes between exports, then subsequent data store files contain differences. You can use the StoreDiff utility to compare two data store files. When you compare two data store files that are different, a data store file is created that contains the differences. You then use Store Browser to view this data store file and see the differences. You can use this information to determine the data to import. The data store file that StoreDiff creates cannot be used to import data into Symantec Management Platform 7.1. See About the data store file on page 62. See About the Store Browser on page 62.
66
To compare two data store files
Start the StoreDiff utility. By default, the EXE for the StoreDiff utility is installed in the C:\Program Files\Altiris\Upgrade directory. It is installed whenever the migration wizard is installed.
2 3
On the Compare Data Stores dialog box, click Browse to select each of the data store files. In Diff Store, specify the name and location for the new data store file. This data store file highlights the differences between the two data stores.
4 5
Click Generate Diff. On the message that appears, click OK. The message either states that the two data store files are identical or that a new data store file is generated. If a new data store file is generated, the Store Browser opens.
6 7
In the Store Browser, on the File menu, click Open, and select the new data store file. On the Diff Store Summary dialog box, click OK. This dialog box lists the data store files that are compared in this new data store file. This dialog box also has the following color key for the differences between the two data store files:
Green Yellow Salmon New data that exists only in the second data store. Deleted data that exists only in the first data store. Data that exists in both data stores but is different.
In the left pane of the Store Browser, select a table that is shaded with one of the three colors. Only the tables that have differences between the two data store files are shaded.
In the right pane, view the rows that have differences between the two data store files.
10 If a table row has an Xml column, do the following to view the XML:
Double-click the row.
67
In the Data View for table dialog box, on the first Column drop-down list, click the XML entry. The XML appears in the Value pane. On the second Column drop-down list, click View as XML.
68
Chapter
Migrating Inventory Solution


Before you migrate Inventory Solution About Inventory Solution migration with Symantec Notification Server Migration Wizard About manual Inventory Solution migration Manually migrating custom inventory script files Manually migrating Inventory Solution baseline configuration files About migrating Inventory for Network Devices
Before you migrate Inventory Solution

Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. To successfully migrate Inventory Solution, perform the following preliminary actions:
If your Inventory Solution version is earlier than 6.1.1075 SP2, you must upgrade it to the latest 6.x Service Pack before migration. Before the upgrade to the latest Service Pack, ensure that the following steps are performed:
Normalize the inventory data classes that are available for normalization.
70
Migrating Inventory Solution About Inventory Solution migration with Symantec Notification Server Migration Wizard
In the Altiris Console 6.0, you can view these data classes at Configuration > Solutions Settings > Assets and Inventory > Inventory > Windows > Normalize. In the Altiris Console 6.5, you can view these data classes at Configure > Solutions > Inventory > Windows > Normalize. Normalization can take a long time depending on the size of the tables of the data classes target.
Remove predefined special groups. You can leave your custom special groups, though no upgrade is supported for them. In the Altiris Console 6.0, you can view your special groups and AeX SW data classes at Configuration > Resource Settings > Data Classes > Inventory > Software. In the Altiris Console 6.5, you can view your special groups and AeX SW data classes at View > Configuration > Resource Settings > Data Classes > Inventory > Software. For more information about removing the predefined special groups, see the article at http://www.symantec.com/docs/HOWTO7373.
Check which items are not migrated with Symantec Notification Server Migration Wizard, and then back up the items. See About Inventory Solution migration with Symantec Notification Server Migration Wizard on page 70. See About manual Inventory Solution migration on page 72.
About Inventory Solution migration with Symantec Notification Server Migration Wizard
Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. To successfully migrate Inventory Solution, you perform the following types of product migration:
Migration with the Symantec Notification Server Migration Wizard. See Before you migrate Inventory Solution on page 69. See About the Symantec Notification Server Migration Wizard on page 50. See Migrating from Notification Server 6.x on page 33.
Migrating Inventory Solution About Inventory Solution migration with Symantec Notification Server Migration Wizard
71
Note: When the Altiris Agent 6.x is upgraded to the Symantec Management Agent 7.1, error messages appear in Notification Server logs. The messages notify you about failure to process some Notification Server events and load inventory. This behavior is expected in the transition period because the 6.x inventory policies and data classes do not yet exist in the 7.1 database. After Inventory agents (known as plug-ins in the 7.1 environment) get installed, the new inventory policies and items are referenced. As a result, the errors no longer occur in the logs. Manual migration. See About manual Inventory Solution migration on page 72.
The following solution-specific items are automatically migrated with the Symantec Notification Server Migration Wizard:
Predefined and custom 6.x inventory policies and tasks are upgraded to the equivalent 7.1 task-based policies. Note: For successful migration, 6.x custom inventory tasks should be located in the predefined folders. Currently, migration is not supported for custom created folders with custom inventory tasks. The schedules and advanced options of the policies are not migrated. The tasks are not scheduled. Predefined and custom 6.x application metering policies are migrated. The migrated policies preserve their settings. That is, the policies that are enabled in 6.x stay enabled, and the policies that are disabled in 6.x stay disabled. The policies are applied to all computers with the Application Metering Plug-in installed. Note: The schedules and advanced options of the policies are not migrated. 6.x predefined data classes are migrated into the legacy 6.x data classes in the 7.1 database for reporting purposes. New inventory data that is collected in the 7.1 environment goes into the 7.1 predefined data classes. 6.x custom data classes are migrated into the legacy 6.x data classes in the 7.1 database for reporting purposes.
72
Migrating Inventory Solution About manual Inventory Solution migration
New relevant custom inventory data that is collected in the 7.1 environment goes into these migrated data classes.
6.x inventory data from 6.x data classes.
The following solution-specific items are not migrated with the Symantec Notification Server Migration Wizard due to extensive changes in the database structure:

Inventory agent is not upgraded but Inventory Plug-in gets installed instead. Inventory Solution 6.x configuration settings. Predefined and custom 6.x inventory reports. Note: During the upgrade, 7.1 inventory reports are updated to show the 6.x data. So you can view the information from 6.x predefined inventory reports in 7.1 reports. Application Metering Solution 6.x configuration settings. 6.x application metering predefined and custom reports, data classes, and data. 6.x history data classes. Stand-alone inventory packages. You cannot migrate your stand-alone packages from version 6.x due to extensive changes in the data class schema for stand-alone packages and the different format for sending Notification Server events. Consequently, if you attempt to use your 6.x stand-alone packages after the migration, the information fails to load into the Symantec Configuration Management Database. Custom inventory script files for Windows and for UNIX, Linux, and Mac. See Manually migrating custom inventory script files on page 73. Inventory baseline configuration and snapshot files. See Manually migrating Inventory Solution baseline configuration files on page 94.
About manual Inventory Solution migration

Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise.
Migrating Inventory Solution Manually migrating custom inventory script files
73
When you perform Inventory Solution migration with the Symantec Notification Server Migration Wizard, some solution-specific files and settings do not migrate. This situation occurs because of the extensive changes in the database structure. To preserve these files and settings, you must manually migrate them from your previous Notification Server computer. After you move these files to your new environment, you must complete configuration steps to make them operate correctly. See Before you migrate Inventory Solution on page 69. See the following list for information about manually migrating Inventory Solution items:
Custom inventory script files for Windows and for UNIX, Linux, and Mac. You can manually migrate your custom inventory script files. However, you must perform custom configuration steps to make them operate correctly in the new environment. See Manually migrating custom inventory script files on page 73. Inventory baseline configuration and snapshot files. You can use the Symantec Notification Server Migration Wizard to migrate the baseline files. However, you have to perform some additional steps to verify that the data has migrated successfully. See Manually migrating Inventory Solution baseline configuration files on page 94.
Manually migrating custom inventory script files

You can manually migrate your custom inventory script files. However, you must perform custom configuration steps to make them operate correctly in the new environment. Table 4-1 Process for manually migrating 6.x custom inventory script files for Windows Action
Create a backup of your custom inventory script files.
Step
Step 1
Description
Before you migrate your custom inventory files, create a backup copy of them in a neutral storage location. See Backing up custom inventory script files on page 78.
74
Table 4-1
Process for manually migrating 6.x custom inventory script files for Windows (continued) Action
Perform Inventory Solution migration with the Symantec Notification Server Migration Wizard.
Step
Step 2
Description
Inventory Solution migration with the Symantec Notification Server Migration Wizard lets you automatically migrate a number of Inventory Solution items. See About Inventory Solution migration with Symantec Notification Server Migration Wizard on page 70.
Step 3
Copy your custom inventory script Copy your custom inventory script files files to your Notification Server to your Notification Server 7.1 7.1 computer. computer. When you install or upgrade to Symantec Management Platform 7.1 on Windows computers, it automatically creates a package directory for storing your custom inventory. See Copying custom inventory script files to the Notification Server 7.1 computer on page 78.
Step 4
Create .INI files.
In version 6.x, there are several .INI files that control the inventory processes that run on client computers. To run 6.x custom inventory in the 7.1 environment, you need to create similar .INI or batch files to execute the desired command lines. See About creating an .INI file for custom inventory on page 80.
Step 5
Meet the prerequisites to create a Before setting up the software resource custom inventory software package, you must ensure that the resource package. certain prerequisites are met on your Notification Server 7.1 computer. See Prerequisites for creating a custom inventory software resource package on page 81.
75
Table 4-1
Process for manually migrating 6.x custom inventory script files for Windows (continued) Action Description
Step
Step 6
Create a software resource with a You need to create a software resource package and a command line. with a package and a command line before performing Quick Delivery tasks. A software resource is similar to the software delivery package in 6.x. A software resource contains the package definition that includes the path to the package, and the program definition that includes the desired command line. See Creating a software resource with a package and a command line for custom inventory script files on page 81.
Step 7
Create the Quick Delivery task for To successfully use manually migrated a custom inventory script file. custom inventory script files in the new environment, you need Software Management Solution to create and perform the Quick Delivery tasks. See Creating the Quick Delivery task for a custom inventory script file on page 83.
Step 8
Create a custom data class.
Create a custom data class for a custom inventory script task. When you create the custom data class, ensure that you enter the name and the description for the data class from your manually migrated custom inventory script file. See Creating and customizing a data class on page 84.
76
Table 4-1
Process for manually migrating 6.x custom inventory script files for Windows (continued) Action
Create a custom inventory script task.
Step
Step 9
Description
Create a custom inventory script task that gathers the custom inventory. See Creating a custom inventory script task on page 85. When you customize the custom inventory script task, ensure that you add the logic to gather the data and populate the attribute variables in the script according to the data in your manually migrated custom inventory script file. See Customizing the custom inventory sample script for Windows on page 88.
Table 4-2
Process for manually migrating 6.x custom inventory script files for UNIX, Linux, and Mac Action
Create a backup of your custom inventory script files.
Step
Step 1
Description
Before you migrate your custom inventory files, create a backup copy of them in a neutral storage location. See Backing up custom inventory script files on page 78.
Step 2
Perform Inventory Solution migration with the Symantec Notification Server Migration Wizard.
Inventory Solution migration with the Symantec Notification Server Migration Wizard lets you automatically migrate a number of Inventory Solution items. See About Inventory Solution migration with Symantec Notification Server Migration Wizard on page 70.
77
Table 4-2
Process for manually migrating 6.x custom inventory script files for UNIX, Linux, and Mac (continued) Action Description
Step
Step 3
Copy your custom inventory script Copy your custom inventory script files files and packages to your and packages to your Notification Notification Server 7.1 computer. Server 7.1 computer. During installation or upgrade on UNIX, Linux, and Mac platforms, Symantec Management Platform 7.1 does not create any special directory for storing your custom inventory. You can define by yourself where to store your custom inventory script files for UNIX, Linux, and Mac. See Copying custom inventory script files to the Notification Server 7.1 computer on page 78.
Step 4
Create a custom data class.
Create a custom data class for a custom inventory script task. When you create the custom data class, ensure that you enter the name and the description for the data class from your manually migrated custom inventory script file. See Creating and customizing a data class on page 84.
Step 5
Create a custom inventory script task.
Create a custom inventory script task that gathers the custom inventory. See Creating a custom inventory script task on page 85. When you customize the custom inventory script task, ensure that you copy and paste the script text from your manually migrated custom inventory script file. See Customizing the custom inventory sample script for UNIX, Linux, and Mac on page 92.
78
Backing up custom inventory script files

This task is a step in the process for manually migrating your custom inventory script files. See Manually migrating custom inventory script files on page 73. Before you migrate your custom inventory files, create a backup copy of them in a neutral storage location. To back up custom inventory script files for Windows
On your previous Notification Server computer, copy all of your custom inventory script files (.CIT, .XML, etc.) to a neutral storage location. By default, your custom inventory script files are located on your previous Notification Server computer in the following location:
C:\Program Files\Altiris\Notification Server\NSCap\Bin\Win32\X86\Inventory Solution
The default location may not include other locations where you have placed your custom inventory script files. Ensure that you also back up the custom inventory script files that you have created outside of the default location.
On your previous Notification Server computer, copy all of your custom inventory .INI files to a neutral storage location. These .INI files invoke the AeXCustInv.exe file. By default, the naming convention for these files is aexinvsoln*.EXE.
To back up custom inventory script files for UNIX, Linux, and Mac
On your previous Notification Server computer, copy all of your custom inventory script files (.CIT, .XML, etc.) to a neutral storage location. By default, your custom inventory script files are located on your previous Notification Server computer in the following locations:
C:\Program Files\Altiris\Notification Server\NSCap\Bin\Mac\Inventory
C:\Program Files\Altiris\Notification Server\NSCap\Bin\Unix\Inventory\<PLATFORM>\<PROCESSOR TYPE>
Copying custom inventory script files to the Notification Server 7.1 computer
This task is a step in the process for manually migrating your custom inventory script files. See Manually migrating custom inventory script files on page 73.
79
When you install or upgrade to Symantec Management Platform 7.1 on Windows computers, it automatically creates a package directory for storing your custom inventory. By default, the path to the custom inventory directory for Windows is C:\Program
Files\Altiris\Notification Server\NSCap\bin\Win32\X86\Inventory\Custom Inventory 6.1.
The package directory for Windows contains the following files:
AeXInvSoln.exe
This file is the same as the file in 6.1 SP2. This file launches AeXCustInv.exe and AeXNSInvCollector.exe as specified in AeXInvSoln.ini.
AeXCustInv.exe
This file differs from the file in 6.1 SP2. This file has bug fixes.
AeXNSInvCollector.exe
This file differs from the file in 6.1 SP2. This file behaves in a similar way to the 6.1 SP2 file. However, this file generates Notification Server events (NSEs) in the new format that is required to store inventory to your Notification Server 7.1 computer.
AeXNSEvent.dll
This file is new. AeXNSInvCollector.exe uses this file for generating NSEs in the new format.
AeXInvSoln.ini
This file specifies an example of how to launch the AeXCustInv.exe and AeXNSInvCollector.exe files.
AeXCustInvStd.cit
This file is a sample custom inventory script from version 6.1 SP2. On UNIX, Linux, and Mac platforms, Symantec Management Platform 7.1 does not create any special directory for storing your custom inventory. You can define by yourself where to store your custom inventory script files for UNIX, Linux, and Mac.
80
To copy custom inventory files to the Notification Server 7.1 computer
Copy all of your custom inventory script files for Windows (.CIT, .XML, etc.) to C:\Program Files\Altiris\Notification Server\NSCap\bin\Win32\X86\Inventory\Custom Inventory 6.1. Copy all of your custom inventory script files for UNIX, Linux, and Mac to the directory previously defined by you.
(Windows only) Copy all of your custom inventory .INI files to C:\Program
Files\Altiris\Notification Server\NSCap\bin\Win32\X86\Inventory\Custom Inventory 6.1.
By default, the naming convention for these files is aexinvsoln*.EXE.
About creating an .INI file for custom inventory

(Windows only) The task of creating an .INI file is a step in the process for manually migrating your custom inventory script files. See Manually migrating custom inventory script files on page 73. In version 6.x, there are several .INI files that control the inventory processes that run on client computers. These .INI files contain batch type commands, similar to the following:
aexauditpls.exe /hidden /output xml aexmachinv.exe aexcustinv.exe /in .\AeXCustInvStd.cit /out AeXCustInvStd.nsi aexsnplus.exe /output xml aexnsinvcollector.exe /hidden /nsctransport /v default /useguid
To run 6.x custom inventory in the 7.1 environment, you need similar .INI or batch files to execute the desired command lines. These files need to be in the same directory as the source .CIT or .XML files. By default, this directory is
C:\Program Files\Altiris\Notification Server\NSCap\bin\Win32\X86\Inventory\Custom Inventory 6.1.
A sample .INI file AeXInvSoln.ini is included in this directory by default. You can include all desired custom inventory script files in a single .INI file and have a single software resource, package, command line, and task. However, you may prefer to create multiple .INI files: one for each custom inventory or set of custom inventory processes. Then each .INI file contains a software resource, package, command line, and task for each custom inventory script file.
81
Typically, the updated .INI file should do nothing more than run one or more aexcustinv.exe command lines, followed by aexnsinvcollector.exe as the last command in the file. However, it may also be necessary to include custom commands or programs in the .INI file. In this scenario, it may be necessary to run a third-party or custom application to collect data, create output data, and have custom inventory gather that data and report it to Notification Server. The .INI file is essentially a batch file that the client agent executes. Consequently, it is possible to include other pertinent commands in the .INI file. Following is an example of how an .INI file for a custom inventory task can look:
aexcustinv.exe /in .\win32_useraccount.xml /out win32_useraccount.nsi aexnsinvcollector.exe /hidden /nsctransport /v default /useguid
A good practice is to keep the source .XML file name and the .NSI output file name identical.
Prerequisites for creating a custom inventory software resource package

(Windows only) The task of meeting the prerequisites is a step in the process for manually migrating your custom inventory script files. See Manually migrating custom inventory script files on page 73. Before setting up the software resource package, you must ensure that the following prerequisites have been met on your Notification Server 7.1 computer:

Java 2 JRE 1.6 is required for some Symantec Management Console screens. The appropriate interpreters for Perl, Python, VBScript, etc. must be installed. The Symantec Management Agent and Software Management Solution plug-in must be installed on each client computer. The 7.1 version of aexinvcollector.exe must exist on the Notification Server 7.1 computer. This file is installed by default as part of the installation. Ensure that the 6.x custom inventory data classes are migrated. Create new custom inventory data classes if needed.
Creating a software resource with a package and a command line for custom inventory script files
(Windows only)
82
This task is a step in the process for manually migrating your custom inventory script files. See Manually migrating custom inventory script files on page 73. A software resource is similar to the software delivery package in 6.x. A software resource contains the package definition that includes the path to the package, and the program definition that includes the desired command line. To create a software resource for custom inventory script files
1 2 3
In the Symantec Management Console, on the Manage menu, click Software Catalog. On the Manage Software Catalog page, click Import. On the Import Software: Specify Software page, perform the following steps:
Software type Package source Select Software Release. In the Source field, select Access Package from an existing UNC. In the Location field, browse to: \\local_NS7_servername\nscap\bin\win32\x86\Inventory\Custom Inventory 6.1 Package contents Click Display Location and select AeXInvSoln.exe. Click Set Installation File. Click Next.
4 5 6 7 8 9
Select Create a new software resource and enter a name for the package. Make sure that Open software resource for editing when finished is checked. Click OK. On the Software Resource editing page, click the Package tab. In the Command Lines section, click Add command. aexinvsoln.exe should be the command line. Click Edit.
83
10 On the Add or Edit Command Line page, perform the following steps:
Name Command line requires a package Package Enter Custinv - Win32_UserAccount - CommandLine Select this option.
Select the name that you entered when you created the software resource package. Select EXE Software Installation File. Select Custom. Enter AeXInvSoln.exe /s win32_useraccount
Installation File Type Command Type Command Line
11 Click OK. 12 Click Save Changes.
Creating the Quick Delivery task for a custom inventory script file
(Windows only) This task is a step in the process for manually migrating your custom inventory script files. See Manually migrating custom inventory script files on page 73. To successfully use your manually migrated custom inventory script files, you need Software Management Solution to perform the Quick Delivery tasks. For more information, see the topics about managed software delivery in the Software Management Solution User Guide. To create the Quick Delivery task for a custom inventory script file
1 2 3 4 5 6
In the Symantec Management Console, on the Manage menu, click Jobs and Tasks. In the left pane, expand System Jobs and Tasks > Software. Right-click the Quick Delivery folder under which you want to create a task, and then click New > Task. In the Create New Task dialog box, in the left pane, under Software, click Quick Delivery. Change the Name of the task. Under Software, select a custom inventory software resource package to deliver.
84
7 8 9
Under Command line, select a command line. Under Package, select an installation package. Click OK.
10 (Optional) To run the task immediately, click Quick Run.

Alternatively, you can click New Schedule to schedule the task.
Creating and customizing a data class

This task is a part of the process for manually migrating your custom inventory script files. See Manually migrating custom inventory script files on page 73. From the Symantec Management Console, you can create a custom data class. You can add, edit, and delete attributes of the data class and you can change the position of the attribute. You can also find the GUID and view the data in the data class. Be aware that every time you modify an attribute and you save the changes, the data class is assigned a new GUID. For more information, see the topics about custom inventory data classes and about gathering custom inventory in the Inventory Solution User Guide. To create and customize a data class
1 2 3
In the Symantec Management Console, on the Settings menu, click All Settings. In the left pane, under Settings, expand Discovery and Inventory > Inventory Solution, and then click Manage Custom Data classes. To create a data class, do the following:

On the Manage Custom Data Classes page, click New data class. On the New Data Class page, enter a name and a description for the data class and click OK. The name of the new data class must be unique.
To customize a data class, on the Manage Custom Data Classes page, in the data classes list, click the data class. You customize the data class by adding, editing, and deleting its attributes.
(Optional) To add an attribute to the data class, do the following:

Click Add attribute. In the Data Class Attributes dialog box, specify the details of the attribute.
85
To add an attribute that uniquely defines a row in the data class, in the Key drop-down list, click Yes. You enforce that the attribute always has a unique value that is other than NULL. To add an attribute that should never be empty or blank, in the Data required drop-down list, click Yes. If in the Key drop-down list, you click Yes, the Data required option is automatically set to Yes. You cannot change it unless in the Key drop-down list, you click No.
Click OK.
6 7
(Optional) To edit or delete the attributes, select the attribute, and then click the Edit or Delete symbols. (Optional) To let the data class store inventory of multiple objects, on the Manage Custom Data Classes page, check Allow multiple rows from a single computer resource. The data class can store the inventory of services, user accounts, files, network cards, and other objects. (Optional) To specify the sequence of the attributes, on the Manage Custom Data Classes page, click the attribute, whose position you want to change, and then click the up arrow or down arrow. When you report inventory values for the columns in a Notification Server Event (NSE), the attributes are identified by the column ID and not by the column name. As a result, the order of attributes in a data class must be correct.
Click Save changes. Warning: The final step of saving changes is very important. When you create any data class or add any attributes, all the information is stored in memory. Nothing is created in the database and on details page, no GUID is yet assigned. As a result, a 00000000-0000-0000-0000-000000000000 GUID is displayed in the property of the data class. Only after you click Save changes on the Manage Custom Data Classes page, the data class is saved in the database, and the GUID is generated. Note that the GUID changes every time you make changes to the definition of the data class and save it.
Creating a custom inventory script task

This task is a part of the process for manually migrating your custom inventory script files. See Manually migrating custom inventory script files on page 73.
86
After you have created the custom inventory data class, you create a custom inventory script task that gathers the custom inventory. The script task is configured with the script to gather the custom inventory and the schedule of the task. See Creating and customizing a data class on page 84. To create a custom inventory script task, you can clone a sample script task and modify it with the custom data classes that you created. You can also create and confgure a custom inventory script task on the Jobs and Tasks portal page. When you customize your custom inventory script, you can benefit from different options that let you easily insert a token to the script and create or edit tokens for use in the script. Note: The process of creating a custom inventory script task is the same across all platforms: Windows, UNIX, Linux, and Mac. However, the scripting language and the logic that is used in the scripts are different. For more information, see the topics about gathering custom inventory in the Inventory Solution User Guide. To clone a sample custom inventory script task
1 2 3 4 5
In the Symantec Management Console, on the Manage menu, click Jobs and Tasks. In the left pane, under Jobs and Tasks, expand Samples > Discovery and Inventory > Inventory samples > Custom. Right-click the sample custom inventory script task and click Clone. In the Clone dialog box, give the cloned script a descriptive name and click OK. (Optional) Customize the sample script, and then click Save changes. Depending on the selected script type, you have different options to customize the sample script. See Customizing the custom inventory sample script for Windows on page 88. See Customizing the custom inventory sample script for UNIX, Linux, and Mac on page 92.
Under Task Status, do one of the following:
To schedule the task to run on client computers, click New Schedule.
87
To perform a quick run of the task on client computers, click Quick Run.
Click Save changes.
To create a custom inventory script task
1 2
In the Symantec Management Console, on the Manage menu, click Jobs and Tasks. In the left pane, navigate to the folder where you want to create a custom inventory script task, right-click the folder, and then click New > Task. For example, to create the task in the Jobs and Tasks folder, right-click Jobs and Tasks, and then click New > Task. To create the task in the Inventory folder, expand Jobs and Tasks > System Jobs and Tasks > Discovery and Inventory, right-click Inventory, and then click New > Task.
3 4 5 6
In the Create New Task dialog box, in the left pane, click Run Script. In the right pane, enter a descriptive name for the task. In the Script type drop-down list, select the script type. Enter your own script or copy a sample custom inventory script to the script editor. To easily insert a token to your custom inventory script, do the following:

In the Insert token drop-down list, select the token that you want to insert. Click Insert.
To access a sample custom inventory script, do the following:
In the Symantec Management Console, on the Manage menu, click Jobs and Tasks. In the left pane, under Jobs and Tasks, expand Samples > Discovery and Inventory > Inventory samples > Custom.
(Optional) In the Create New Task dialog box, in the script editor, customize the copied sample script or your own script. Depending on the selected script type, you have different options to customize the script. See Customizing the custom inventory sample script for Windows on page 88. See Customizing the custom inventory sample script for UNIX, Linux, and Mac on page 92.
88
(Optional) To configure the advanced options for running the custom inventory script task, do the following:
Click Advanced, and on the Script tab, specify the user account that the task runs in and other script options. In the Task options tab, specify the settings for running the script task simultaneously with other tasks and the maximum possible length of the script task. Click OK.
In the Create New Task dialog box, click OK.
10 On the Run Script page, under Task Status, do one of the following:

To schedule the task to run on client computers, click New Schedule. To perform a quick run of the task on client computers, click Quick Run.
11 Click Save changes.
Customizing the custom inventory sample script for Windows

(Windows only) This task is a part of the process for manually migrating your custom inventory script files. See Manually migrating custom inventory script files on page 73. The easiest way to create a new custom inventory script task is to clone the existing sample and customize it according to your needs. The sample script for Windows already contains the required code for a WMI query. You only need to add your own logic to gather the data that you want and to populate the attribute variables in the script. Note: Every time you create or edit an existing custom data class, the data class is assigned a new GUID. You must manually update the script with the new GUID, if it refers to the older GUID for the same custom data class. See Creating a custom inventory script task on page 85. For more information, see the topics about gathering custom inventory in the Inventory Solution User Guide.
89
To customize the custom inventory sample script for Windows
1 2
Clone or open an existing sample of the custom inventory script task. Specify the values that you want to gather. Example:
strComputer = "." Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") 'Fire WMI Query Set objCIMObj = objWMIService.ExecQuery("select * from CIM_processor")
Replace the GUID with the GUID of the data class that you created. Example:
set objDCInstance = nse.AddDataClass ("{e8220123-4987-4b5e-bc39ec6eaea312ef}")
To access the GUID of the data class that you created, do the following:
In the Symantec Management Console, on the Settings menu, click All Settings. In the left pane, under Settings, expand Discovery and Inventory > Inventory Solution, and then click Manage Custom Data classes. On the Manage Custom Data Classes page, select the data class and click the Details symbol.
90
Update attributes of the data class. Example:

For each objInfo in objCIMObj 'Add a new row dim objDataRow set objDataRow = objDataClass.AddRow 'Set columns objDataRow.SetField 0, objInfo.DeviceID objDataRow.SetField 1, objInfo.L2CacheSize objDataRow.SetField 2, objInfo.L2CacheSpeed Next
Click Save changes.
Custom inventory sample script for Windows

(Windows only) The sample inventory script for Windows does the following:

Creates a WMI object, runs a WMI query, and stores the result set. Creates a Notification Server event (NSE) object. Creates an Inventory data block and associates it with a specific custom data class. Loops through each row in the result set and populates each row of the result set into a row in the data block. Processes and sends the NSE to Notification Server.
See Customizing the custom inventory sample script for Windows on page 88. The following is a sample script:
'The following is a sample custom inventory script gathering information about the processor of a computer and posting data to the server using Altiris NSE Component '======================================================================================== ' On Error Resume Next 'Create instance of Wbem service object and connect to namespace
91
strComputer = "." Set objWMIService = GetObject("winmgmts:" & "{impersonationLevel=impersonate}!\\" & strComputer & "\root\cimv2") 'Fire WMI Query Set objCIMObj = objWMIService.ExecQuery("select * from CIM_processor") '======================================================================================== 'Create instance of Altiris NSE component dim nse set nse = WScript.CreateObject ("Altiris.AeXNSEvent") ' Set the header data of the NSE ' Please don't modify this GUID nse.To = "{1592B913-72F3-4C36-91D2-D4EDA21D2F96}" nse.Priority = 1 'Create Inventory data block. Here assumption is that the data class with below guid is already configured on server dim objDCInstance set objDCInstance = nse.AddDataClass ("{e8220123-4987-4b5e-bc39ec6eaea312ef}") dim objDataClass set objDataClass = nse.AddDataBlock (objDCInstance) For each objInfo in objCIMObj 'Add a new row dim objDataRow set objDataRow = objDataClass.AddRow 'Set columns objDataRow.SetField 0, objInfo.DeviceID objDataRow.SetField 1, objInfo.L2CacheSize objDataRow.SetField 2, objInfo.L2CacheSpeed
92
Next nse.SendQueued
Customizing the custom inventory sample script for UNIX, Linux, and Mac
(UNIX, Linux, and Mac only) This task is a part of the process for manually migrating your custom inventory script files. See Manually migrating custom inventory script files on page 73. The custom inventory script for UNIX, Linux, and Mac generates a text output that contains the collected inventory data in a specified format. This data is used to create the NSE and is posted into the Configuration Management Database (CMDB). The logic of creating the NSE and posting the data is hidden from the user. When you customize the sample script, you can modify the output that the script generates. See Creating a custom inventory script task on page 85. For more information, see the topics about gathering custom inventory in the Inventory Solution User Guide. To customize the custom inventory sample script for UNIX, Linux, and Mac
Clone or open an existing sample of the custom inventory script task. Note that the first lines of the script should not be changed. Changes should be made after the # SCRIPT_BEGINS_HERE label.
Specify the data class. Example:

echo UNIX_PS_List
Specify the delimiters. Example:

echo "Delimiters=\" \" "
Specify the data type and the length of each column. Example:
echo string20 string20 string20 string256
93
Specify the column names. Example:

echo PID Terminal Time Command
Note that the column names are not used in 7.x custom inventory. The column names are left for backward compatibility with 6.x Inventory Solution. You can leave this line empty in 7.x but keep the echo command intact. Example:
echo
Specify commands to retrieve data from system. Example:

ps -e
Click Save changes.
Custom inventory sample script for UNIX, Linux, and Mac

(UNIX, Linux, and Mac only) The sample inventory script for UNIX, Linux, and Mac does the following:
Includes a helper script that implements the logic of creating NSE and posting it to Configuration Management Database (CMDB). Specifies the data class. Specifies delimiters for use in parsing the data that is returned from the command that runs. Specifies the data type and length of each column. Specifies the column names. The column names are only required when the command that runs does not already include column headings. Runs the desired command. In this case, appropriate platform-specific commands run.
See Customizing the custom inventory sample script for UNIX, Linux, and Mac on page 92. The following is a sample script:
. `aex-helper info path -s INVENTORY`/lib/helpers/custominv_inc.sh # # Sample script for custom inventory
94
Migrating Inventory Solution Manually migrating Inventory Solution baseline configuration files
# The first line of code should be always included at the begin of the script # Actual script for collecting inventory data begins after the following label: # SCRIPT_BEGINS_HERE #!/bin/sh echo UNIX_PS_List echo "Delimiters=\" \" " echo string20 string20 string20 string256 echo PID Terminal Time Command if [ "`uname -s`" = "Darwin" ] ; then ps -ax | sed -e "1d" | awk '{print $1 " " $2 " " $4 " " $5 " " }' else ps -e | sed -e "1d" | awk '{print $1 " " $2 " " $3 " " $4 " " }' fi
Manually migrating Inventory Solution baseline configuration files

(Windows only) You can use the Symantec Notification Server Migration Wizard to migrate the baseline files. However, you have to perform some additional steps to verify that the data has migrated successfully. Table 4-3 Process for manually migrating Inventory Solution baseline configuration files Action
Create a backup of your baseline configuration files.
Step
Step 1
Description
Before you decommission your previous Notification Server computer, back up your baseline configuration files to a neutral storage location. See Backing up Inventory Solution baseline configuration files on page 96.
95
Table 4-3
Process for manually migrating Inventory Solution baseline configuration files (continued) Action
Export your baseline configuration file data.
Step
Step 2
Description
Export your baseline configuration file data to a data store file. You perform this step with the Symantec Notification Server Migration Wizard. During the export, make sure that the following actions are done on the Exporter Configuration page: Under Products, select Application Management Solution. Under Exporters, make sure that Enable is checked for Baseline Package Resource File Exporter. Click Filters to view the Filters for Baseline Package Resource File Exporter dialog box, and then ensure that the dialog entry is populated and enabled.
See Exporting Notification Server 6.x data to a data store file on page 57. Step 3 Copy your baseline configuration After you install the Symantec files and the data store file to the Management Platform, copy your Notification Server 7.1 computer. baseline configuration files and the exported data store file to the Notification Server 7.1 computer. See Copying Inventory Solution baseline configuration files to the Notification Server 7.1 computer on page 96. Step 4 Import your baseline configuration file data. Import your baseline configuration file data from a data store file. You perform this step with the Symantec Notification Server Migration Wizard. See Importing Notification Server 6.x data from a data store file on page 59.
96
Table 4-3
Process for manually migrating Inventory Solution baseline configuration files (continued) Action
Verify that your baseline configuration files are successfully migrated.
Step
Step 5
Description
After you imported your baseline configuration files on the Notification Server 7.1 computer, you should verify that your baseline configuration files are successfully migrated. See Verifying the migration of baseline configuration files on page 97.
Backing up Inventory Solution baseline configuration files

(Windows only) This task is a step in the process for manually migrating your Inventory Solution baseline configuration files. See Manually migrating Inventory Solution baseline configuration files on page 94. Before you decommission your previous Notification Server computer, back up your baseline configuration files to a neutral storage location. To back up Inventory Solution baseline configuration files
On your previous Notification Server computer, copy all of your baseline configuration files in the folders FileBaselinePackage and RegBaselinePackage to a neutral storage location. By default, your baseline configuration files are located on your previous Notification Server computer in the following location:
%InstallDir%\Altiris\Notification Server\NSCap\Bin\Win32\X86\Application Mgmt Solution
Baseline configuration files may be located in locations other than the default location. Ensure that you also back up the baseline configuration files that you have created outside of the default location.
Copying Inventory Solution baseline configuration files to the Notification Server 7.1 computer
(Windows only)
97
This task is a step in the process for manually migrating your Inventory Solution baseline configuration files. See Manually migrating Inventory Solution baseline configuration files on page 94. After you install the Symantec Management Platform, copy your baseline configuration files and the exported data store file to the Notification Server 7.1 computer. To copy Inventory Solution baseline configuration files and the exported data store file to the Notification Server 7.1 computer
1 2
Copy the FileBaselinePackage and RegBaselinePackage folders with your baseline configuration files from your neutral storage location. On your Notification Server 7.1 computer, paste the copied baseline configuration files to the following recommended location:
%InstallDir%\Program Files\Altiris\Upgrade\Data
Copy the exported data store file from your previous Notification Server computer. By default, the data store file is saved in the C:\Program Files\Altiris\Upgrade\Data directory. The data store file has an .adb extension, is easy to copy and back up, and is not dependent on SQL. See About the data store file on page 62.
On your Notification Server 7.1 computer, paste the exported data store file to the location of your baseline configuration files. The recommended location is %InstallDir%\Program Files\Altiris\Upgrade\Data Create the Data folder if it is not already created.
Verifying the migration of baseline configuration files

(Windows only) This task is a step in the process for manually migrating your Inventory Solution baseline configuration files. See Manually migrating Inventory Solution baseline configuration files on page 94. After you imported your baseline configuration files on the Notification Server 7.1 computer, you should verify that your baseline configuration files are successfully migrated.
98
To verify the migration of baseline configuration files
Verify that the imported baseline configuration files are located at the following locations:
The entire file that is related to the file baseline should be located at
%InstallDir%\Altiris\Notification Server\NSCap\bin\Win32\X86\Inventory\Application Management\FileBaselinePackage\6.x.
The entire file that is related to the registry baseline should be located at
%InstallDir%\Altiris\Notification Server\NSCap\bin\Win32\X86\Inventory\Application Management\RegBaselinePackage\6.x.
Verify that the 6.x baseline task is imported into the Configuration Management Database. You can view the baseline task in the Symantec Management Console, on the Manage menu, at Jobs and Tasks > System Jobs and Tasks > Discovery and Inventory > Inventory > Baseline Task 6.x.
On the Run sample baseline page, verify that the files that are associated with the 6.x baseline task are associated with the imported baseline task in the 7.1 environment. (Optional) Perform manual steps to associate the unassociated baseline configuration files to the imported baseline task.
To manually associate a baseline configuration file to a baseline task
Copy a baseline configuration file from the 6.x Notification Server computer to the Notification Server 7.1 computer.
For the file baseline .bls files, the recommended folder is

%InstallDir%\Altiris\Notification Server\NSCap\bin\Win32\X86\Inventory\Application Management\FileBaselinePackage.
For the registry baseline .bls files, the recommended folder is

%InstallDir%\Altiris\Notification Server\NSCap\bin\Win32\X86\Inventory\Application Management\RegBaselinePackage.
On the Notification Server 7.1 computer, in the Symantec Management Console, on the Manage menu, click Jobs and Tasks.
Migrating Inventory Solution About migrating Inventory for Network Devices
99
In the left pane, under Jobs and Tasks, click System Jobs and Tasks > Discovery and Inventory > Inventory > Baseline Task 6.x > Run sample baseline. On the Run sample baseline page, perform one of the following steps, depending on your requirement:
Click Compile a baseline snapshot, and then click Use custom baseline configuration. Click Compare with a baseline snapshot, and then click Compare with custom baseline snapshot.
Click Browse, and then browse to the baseline configuration file that you have copied in step 1. The following is an example of the baseline configuration file path:
\\localhost\NSCap\bin\Win32\X86\Inventory\Application Management\FileBaselinePackage\6.x\sample.bls.
Click Save changes.
About migrating Inventory for Network Devices

You perform the product migration from the version 6.x according to the migration scenario for Inventory Solution and IT Management Suite. See Before you migrate Inventory Solution on page 69. See Migrating from Notification Server 6.x on page 33. See About data migration on page 48. See About the Symantec Notification Server Migration Wizard on page 50. During the migration from Inventory for Network Devices version 6.x , the following data is migrated:
100
Migrating Inventory Solution About migrating Inventory for Network Devices
The data class list from 6.x to 7.x.
Inv_SNMP_Host_Devices Inv_SNMP_Host_Resources Inv_SNMP_NW_Adapters Inv_SNMP_NW_Disk_Storage Inv_SNMP_NW_NLM Inv_SNMP_NW_Partitions Inv_SNMP_NW_Printers Inv_SNMP_NW_Server Inv_SNMP_NW_Settings Inv_SNMP_NW_Settings_Descriptions Inv_SNMP_NW_Volume Inv_SNMP_Physical_Entities
Inv_SNMP_Printer (changes its name to Inv_SNMP_HP_Printer in 7.x) Inv_SNMP_Software

Inv_SNMP_Storage Inv_SNMP_Win32_Print_Queues Inv_SNMP_Win32_Services Inv_SNMP_Win32_Shares SNMPDeviceMap SNMPTableMap
SNMP data mapping tables.
MIB files.
All MIB files in the 6.0 NetworkInventory\Mibs directory are imported into the database during the upgrade.
Chapter
Migrating Patch Management Solution


About migrating Patch Management Solution for Windows About migrating Patch Management Solution for Linux About migrating Patch Management Solution for Mac Data that can be migrated from the 6.x version of Patch Management Solution for Windows
About migrating Patch Management Solution for Windows

You migrate the product data according to the process that is defined in the "Migrating Symantec Management Platform" chapter. Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. For Patch Management Solution for Windows, only certain settings can be migrated. Software update policies and software update packages cannot be migrated. Exporting software update packages from the 6.x server is not necessary. Symantec recommends that in the Migration Wizard, on the Exporter Configuration page, you click Patch Management Solution for Windows, and then in the right pane, uncheck Patch Management Package Items Physical Files Exporter.
102
Migrating Patch Management Solution About migrating Patch Management Solution for Linux
After the migration, verify and validate that the solution settings have been migrated correctly. Then you can configure the solution and start distributing software updates. For more information on configuring the solution, and downloading and distributing software updates, see the Patch Management Solution for Windows 7.1 SP2 User Guide at the following URL: http://www.symantec.com/docs/DOC4814 When you create the software update policies, associated software update package files are downloaded from the vendor. The Legacy Windows Software Update Policies report lets you view the information about the software update policies that existed in 6.x. You can use this report as a reference if you decide to re-create software update policies using the same bulletins. See Data that can be migrated from the 6.x version of Patch Management Solution for Windows on page 102.
About migrating Patch Management Solution for Linux

Upgrading from Patch Management Solution for Linux 6.x is not supported and no data can be migrated. Install and use the clean installation of Patch Management Solution for Linux 7.1 SP2. For more information, see the Patch Management Solution for Linux 7.1 SP2 User Guide at the following URL: http://www.symantec.com/docs/DOC4816
About migrating Patch Management Solution for Mac

There was no 6.x version of Patch Management Solution for Mac.
Data that can be migrated from the 6.x version of Patch Management Solution for Windows
Some of the Patch Management Solution for Windows 6.x items can be migrated.
Migrating Patch Management Solution Data that can be migrated from the 6.x version of Patch Management Solution for Windows
103
Table 5-1
Patch Management Solution for Windows 6.x data migration reference Can it be Description migrated?
Yes No Custom severities list is migrated. Custom severities assignments are not migrated. Your existing Software Update Agent policies (for example, your computer restart and notification settings) are migrated and converted into their version 7.1 SP2 equivalents. This setting is migrated.
Item in 6.x
Custom severities list Bulletin custom severity
Software Update Agent policies settings
Yes
Core Services settings - To location
Yes
Core Services settings - From No location Patch package staging status No
This setting is not migrated.
Patch packages are not compatible with 7.1 SP2. Patch packages are not compatible with 7.1 SP2. You should run the Import Patch Data for Windows (PMImport) task as soon as possible after the installation of Patch Management Solution. Your reporting history is re-created after you install the Symantec Management Agent 7.1 SP2 and Software Update Plug-in 7.1 SP2 on the target computers. The reporting history re-creates automatically after the plug-in is installed and has sent the data to the Notification Server computer. A new agent database is used on the client computer, but the same data classes are used in version 7.1 SP2 as in version 6.x. Default patch collections are not migrated. Patch bulletins are not compatible with 7.1 SP2.
Patch packages
No
PMImport
No
Reporting history for each client
No
Default patch collections Status of bulletins (Enabled/Disabled)
No No
104
Migrating Patch Management Solution Data that can be migrated from the 6.x version of Patch Management Solution for Windows
Chapter
Migrating Software Delivery to Software Management Solution


Things to know about migrating from 6.x to 7.1 Items that can and items that cannot be migrated from software delivery solutions 6.x Migrating from Software Delivery Solution 6.x to Software Management Solution 7.1
Things to know about migrating from 6.x to 7.1

The following are things to consider if you want to migrate from Software Delivery Solution 6.x to Software Management Solution 7.1: Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise.
When you copy the software package migration data during an off-box upgrade, the migration can fail. You must place both the package files folder and the data store (ADB) file in the same location on the 7.x Notification Server computer. Only upgrade from Software Delivery Solution 6.1 SP3 or SP4 is supported.
106
Migrating Software Delivery to Software Management Solution Items that can and items that cannot be migrated from software delivery solutions 6.x
The Software Virtualization Solution must be upgraded to the latest released version, which is 2.1.3062. Symantec recommends that you apply any additional point hot fixes to Software Delivery SP3 before upgrade. Having the hot fixes installed does not affect the upgrade if you do have them applied. The only physical packages that are migrated are the ones that are on the local Notification Server drive. The packages are not converted into the software catalog resources. You must take additional steps to move these packages into software resources in the catalog. For packages physically located on a UNC share, the UNC path will be migrated. For 7.1, you are not conducting an actual in-place upgrade, but are exporting supported data from the old database and then using the migration wizard to put that data into the new structure after 7.1 is installed. This is called an off-box upgrade. Because you perform an off-box upgrade, take the following into consideration:
If physical software packages were stored on the 6.x Notification Server computer, you must manually move the physical files to the new 7.1 server. Migration Wizard does not move these files. If you were using a custom local path for the software resources on the 6.x Notification Server, you must recreate the same file structure on the new 7.1 server. For example, if the software resources were located on disk F:, you must have disk F: on the new 7.1 computer too, otherwise the Software Management Solution will not work. If a path that is used in a software resource is longer than 248 characters, the physical files cannot be migrated. For example, Microsoft SQL Server 2008 folder structure can exceed 248 symbols. You can recreate the folder structure and migrate such files manually.
The packages on the client computers are not kept and will be re-downloaded.
Items that can and items that cannot be migrated from software delivery solutions 6.x
Data from the following 6.x software delivery solutions can be migrated to 7.1:

Software Delivery Solution (for Windows) 6.x Software Delivery Solution for Linux, UNIX, and Mac 6.x
107
Software Vitalization Solution 6.x
Data from the following 6.x software management solutions cannot be migrated to 7.1:
Application Management Solution 6.x
The following tables show the 6.x items that can or cannot be migrated. Table 6-1 Item in 6.x
Software Delivery packages
Software delivery items that can and cannot be migrated Can it be Details migrated?
Yes Software packages from Software Delivery Solution 6.x and Software Vitalization Solution 6.x are imported as Software Package resources Packages can be migrated. However, you must manually promote each package into the Software Library. The estimated manual effort is about 1 minute per package to promote a package into the new framework.
Software Delivery programs Yes
Software programs from Software Delivery Solution 6.x and Software Vitalization Solution are imported as Program items. The association between a software package and program is maintained during the migration process. Migrated software packages and programs do not get automatically associated with an entry in the Software Catalog. Following the migration process, administrators can use the migrated software packages (and related program data) to create new entries in the Software Catalog or associate them with existing entries in the Software Catalog. In case a 6.x program had the uninstall command defined, in 7.1 it will appear as a separate Software Command Line resource with uninstall prefix in its name. The association of migrated uninstall command line with Software Resource is maintained. The Execution Environment details set in the actual Program object have been moved to their equivalent in 7.1; execution environment resides in Tasks, not in the Program Items.
108
Table 6-1 Item in 6.x
Software delivery items that can and cannot be migrated (continued) Can it be Details migrated?
Yes Software Delivery Solution 6.x tasks are migrated using the following rules: Software Delivery tasks are imported as Legacy Software Delivery policies Software Delivery Task Server tasks are imported as Package Deliveries Sequential Software Delivery tasks are imported as Managed Delivery policies
Software Delivery tasks
Sequential Software tasks
Yes
Sequential Software Tasks are imported as Managed Delivery policies. Symantec Workspace Vitalization (SWV) Solution 6.x tasks are migrated using the following rules: Virtual Software tasks are imported as Legacy Software Delivery policies SWV Task Server tasks are imported as SVS Command tasks
Software Virtualization Solution tasks Symantec Workspace Virtualization (SWV) Solution 6.x tasks
Yes
Software Delivery custom reports
Yes and No Software Management Solution has more robust, comprehensive reports that consolidate like data and provide a greater range of flexibility. Some custom reports can be migrated from 6.0 to 7.1 for historical reporting purposes and configuration only. Other Custom Reports are not migrated. This is due to the following reasons: The events/tables, etc. are not the same between Software Delivery 6.x and the Software Management Solution 7.1 Task migrations do not include any event data captured from the 6.x framework Event data is not migrated with the Core Notification Server migration Task Server drives the majority of Tasks in the 7.1 Framework
109
No Application Management Solution 6.x installation state policies cannot be migrated to 7.1. Application Management is joined with Software Management Solution. The functionality can then be incorporated into the larger Software Management Framework, extending the possibilities. No Application Management policies are migrated between 6.x and 7.1. Record Settings and Configurations for all active policies being used within Application Management must be re-created. The Windows Installer applications and tasks to update Windows Installer source paths must be re-created as Application Management tasks. The Installation state management policies must be re-created as Managed Delivery policies.
Application Management
Application Management Solution 6.x tasks to repair Windows Installer applications and tasks to update Windows Installer source paths Data for new features
No
Application Management Solution 6.x tasks to repair Windows Installer applications and tasks to update Windows Installer source paths must be re-created as Application Management tasks in Software Management Solution.
No
There are new software features for which there is not equivalent migration data to populate. This includes metadata within the Software Catalog. These are new areas where there currently is no data defined. No Software Portal requests can be migrated. This includes the automatically generated items of a software request type, data related to Software Portal requests submitted by users and the policies created to fulfill requests.
Software Portal Requests
No
110
Migrating Software Delivery to Software Management Solution Migrating from Software Delivery Solution 6.x to Software Management Solution 7.1
No Software Portal tasks are not migrated. This includes tasks that are generated either by an automatically approved request or generated by a manually approved request. The links to the single computer collections generated, including sequential tasks, are not migrated. Alert Manager Portal Requests are not migrated. This includes the Helpdesk/Alert Manager incidents that are created when someone requests software that requires approval. Software Portal Security settings are not migrated. Security determines what software a user can see based on what permissions that user has been given to the Package/Program. Take snapshots of all of your Portal configurations before you migrate. These configurations can be found under the Software Portal tab of a Package/Program or a Sequential Task. Software Portal configuration settings for a software delivery package (e.g. Install Software and Install on Approval) can be migrated.
Software Portal Tasks
Software Portal Alert Manager requests
No
Software Portal Security settings
No
Software Portal configuration settings
Yes
Migrating from Software Delivery Solution 6.x to Software Management Solution 7.1
To upgrade Software Delivery Solution you must understand how its old data structure relates to the new data structure of the Software Management Framework. Many Software Delivery objects are upgraded into Symantec Management Platform 7.1; however, not all objects can be migrated.
111
Table 6-2
Process for migrating Software Delivery Solution 6.x to Software Management Solution 7.1 Action
Use the Symantec Management Platform Migration Wizard to migrate the majority of your Software Delivery data.
Step
Step 1
Description
See topics about ITMS migration in this guide. See Migration Wizard objects on page 111. See Things to know about migrating from 6.x to 7.1 on page 105. See Items that can and items that cannot be migrated from software delivery solutions 6.x on page 106.
Step 2
Validate package migration. You must complete additional manual migration steps to reach complete functional parity. See About validating Software Package Migration on page 112.
Step 3
Convert the Software Delivery packages.
You must convert each of your Software Delivery packages into the equivalent resource detail in the Software Catalog. See Promoting migrated Software Packages into the Software Library on page 113.
Step 4
Enable legacy software delivery policies. Review the sequential software delivery tasks. Review the task server infrastructure tasks.
See Enabling legacy software delivery policies on page 115. See About migrated Managed Software Delivery sequential tasks on page 116. See Viewing migrated task server infrastructure software delivery tasks on page 116.
Step 5
Step 6
Migration Wizard objects

The following table lists the objects of the Migration Wizard.
112
Table 6-3 Object
Software Delivery Solution objects in Migration Wizard Description

Migrates your Software Delivery Solution license over to the new Software Management Solution.
Software Delivery Solution for Windows License Certificate Exporter/Importer Software Delivery Package and Program Exporter/Importer Software Delivery Package File Exporter/Importer
Exports or imports all Packages and Programs, as they were previously defined. Exports or imports locally stored package files, not UNC or HTTP based. This option is deselected by default. Exports or imports standard Software Delivery Tasks.
Software Delivery Task Exporter/Importer Virtual Software Package and Program Exporter/Importer
Similar to the software delivery package and program exporter/importer except only SVS objects of the same kind are targeted. Exports or imports physical VSP files stored locally on the Notification Server computer . This option is deselected by default. Similar to SWD but for SVS Tasks.
Virtual Software Package File Exporter/Importer
Virtual Software Task Exporter/Importer
Sequential Software Delivery Task Exports or imports specific Sequential Tasks, including Exporter/Importer the links to the multiple Packages and Programs. Delivery Software Task Exporter/Importer Exports or imports Task Server-based Tasks run by the Software Delivery Agent for the Task Server Plug-in. SVS Tasks contained within Task Server.
Virtual Software Command Task Exporter/Importer
Virtual Software Data Class Data Exports or imports Events and Inventory for SVS. Exporter /Importer
About validating Software Package Migration

After you migrate, the data can be used. By default the migrated packages can be used with Software Delivery and Quick Delivery Tasks within the Task Server infrastructure.
113
You can find the migrated packages in the Symantec Management Console under Manage > Resources > Organizational Views > Default > All Resources > Package > Software Package. You should review the list to ensure that the packages you had created on the 6.x platform are displayed correctly in this location. The following article contains information about how to use these objects using the same basic structure and functions from Software Delivery 6.1 in the 7.1 framework: https://www-secure.symantec.com/community/article/5929/ introduction-software-management-notification-server-70-part-1-software-delivery
Promoting migrated Software Packages into the Software Library

Packages can be migrated; however you must manually promote each package into the Software Library. The estimated manual effort is about 1 minute per package to promote a package into the new framework. You cannot promote a package after you have completed these steps, so Symantec recomends you verify the accuracy of the options carefully at each stage. To promote your packages to the Software Library, use the following procedures:

See To promote a package to a new software resource on page 113. See To promote a package to an existing software resource on page 114. See To promote several packages to new software resources on page 114.
To promote a package to a new software resource
In the Symantec Management Console, on the Manage menu, go to Resources > Organizational Views > Default > All Resources > Package > Software Package. On the package that you want to promote, right-click on the package and click Resource Manager. In the left pane, click Assign to Software Resource. In the Assign Package to Software Resource wizard, in the Select software resource dialog, click Create new software resource. Enter a name for the software resource. Choose a Type for the software resource. If you are unsure of what type to use, select Software Release. Use the Version field to track updates and changes to the software resource.
2 3 4 5 6 7
114
Click Next. The conversion takes a Package/Program from 6.x and converts it into a Package and Command line for the 7.1 Platform. When promoting the package, the command line goes with it and can be configured at this point. During the migration, the installation file type is set to what is believed that the type should be. Review to ensure that it is accurate.
Click Finish.
To promote a package to an existing software resource
In the Symantec Management Console, on the Manage menu, go to Resources > Organizational Views > Default > All Resources > Package > Software Package. Right-click the package that you want to promote, and click Resource Manager. In the left pane, click Assign to Software Resource. Select Use Existing software resource. Click Select software resource. In the list of software resources, select the resource that you want to promote your package to become. Review the command-line parameters to ensure that they are set correctly. Click Finish.
2 3 4 5 6 7 8
To promote several packages to new software resources
In the Symantec Management Console, on the Manage menu, go to Resources > Organizational Views > Default > All Resources > Package > Software Package. In the left pane, Ctrl+click to multi-select the packages that you want to promote. If the packages you want do not display in the window, you may need to enter a filter to access them. In this case the multi-select feature still functions correctly and you can continue to select multiple packages.
3 4
Right-click one of the packages that you selected and then click Assign to Software Resources. In the Assign Packages to Software Resources page, verify that all the packages you intended to assign are displayed. Schedule the task to Run now. This task converts the packages into software resources, and stores them in the software library.
115
Enabling legacy software delivery policies

The migration wizard converts your previous software delivery tasks into legacy software delivery policies. It stores these policies in a folder called Legacy Software Delivery. After migration, these legacy policies are disabled by default. If you want a specific policy to run you must enable it. You should review the configuration and settings carefully before you choose to enable a legacy software delivery policy. Some policies may fail to work correctly because not all settings are migrated precisely due to the changes in the software delivery functionality in Software Management Solution 7.x. For example, in version 6 you may have chosen to have a task target the collection all computers with software delivery agent. The software delivery agent is no longer used. In this example the policy would be migrated, but the target for that policy would be blank. You might need to target the policy to the filter of computers, all computers with software management agent/plug-in to make it work as you expect. To enable legacy software delivery policies
1 2 3
In the Symantec Management Console, on the Manage menu, go to Policies > Software > Legacy Software Delivery. Select a policy that you want to enable. Review the settings to make sure that they meet your requirements. Consider the following items:
The Go to Package link opens a page with details about the legacy package. It does not reference the resource in the Software Library. The Go to Program link opens the command-line interface. In version 7, the resource type Program has been replaced by Command-line. The Advanced tab displays the execution environment as it was previously defined in the type Program in version 6. The former collection that was assigned to the Software Delivery task is now called Target. Depending on the previous collection, the policy may have a correct target assigned. You can now view and modify the policy's target in the Applies To section.
4 5 6
Expand the schedule section and create a schedule for the policy. Click Save Changes. On the Policy Rules/Actions bar turn the policy on.
116
About migrated Managed Software Delivery sequential tasks

The sequential tasks you created previously are converted into managed software delivery policies. Even though they have been migrated, not all sequential tasks convert into Managed Software Delivery policies correctly. Before you attempt to use one of these migrated Managed Software Delivery policies, you should review its settings carefully to determine if it meets your expectations. You can access the migrated sequential tasks in the Symantec Management Console on the Manage menu at Policies > Software > Managed Software Delivery. Determine whether creating a new Managed Software Delivery policy or a new task server job can better meet the needs that you met with a sequential task. You can still use your migrated packages (software resources) and your migrated programs (command lines) when you create new policies and jobs. Task server jobs are best for the following: multiple software rollouts, additional complex operations such as AMT functions or scripting, or working on unmanaged targets. Managed Software Delivery policies are best for application state management, versioning control, and intelligent deployment.
Viewing migrated task server infrastructure software delivery tasks

During migration, the migration wizard converts the task server software delivery tasks into the new Package Delivery tasks. You can still use a Quick Delivery task with the task server. However, for these tasks to work correctly, you must manually convert your packages and programs into software resources with command lines. The new Package Delivery task contains links to the package and program (software resource and command line). To view your migrated task server plug-in tasks
1 2 3
In the Symantec Management Console, on the Manage menu, click Jobs and Tasks > System Jobs and Tasks > Software > Package Delivery. Select the task that you want to view. The window displays what package and command line the task uses. Click Advanced to view task-related information, including the execution environment. If you modify the task, click Save Changes. To schedule the task, use the schedule utility in the Task Status section.
4 5
Chapter
Migrating Deployment Solution


About migration of Deployment Solution About reason to migrate Deployment Solution 6.9 About architecture and features of Deployment Solution 7.1 SP1 About advantages of using Deployment Solution 7.1 SP1 over 6.9 About comparison of Deployment Solution 6.9 features with 7.1 SP1 About comparison of Deployment Solution 6.9 tasks with 7.1 SP1 About import of predefined computers in Deployment Solution 7.1 SP1 Importing predefined computers Installing the Deployment Solution 7.1 SP1 agent and plug-in Uninstalling the Deployment Solution 6.9 agent Limitations of migrating from Deployment Solution 6.9 to 7.1 SP1 Migrating from Deployment Solution 6.9 to 7.1 SP1a MR1
About migration of Deployment Solution

The Altiris IT Management Suite 7.1 SP2 release contains the previously released version of Deployment Solution 7.1 SP1a MR1 and hence you can migrate Deployment Solution 7.1 (ITMS 7.0) to Deployment Solution 7.1 SP1a MR1.
118
Migrating Deployment Solution About reason to migrate Deployment Solution 6.9
About reason to migrate Deployment Solution 6.9

Deployment Solution 6.9 is a standalone product and is not designed to be integrated with Symantec Management Platform. Deployment Solution 7.1 SP1 onwards offers the core imaging and deployment capabilities of Deployment Solution 6.9 that are natively integrated on the Symantec Management Platform. Hence, Deployment Solution 7.1 SP1 does not require its own agent, console, or database infrastructure separate from what is already provided with Symantec Management Platform. Instead, Deployment Solution 7.1 SP1 plugs in and extends the capabilities natively offered by Symantec Management Platform. Though Deployment Solution 7.1 SP1 supports most of the features of Deployment Solution 6.9, you cannot migrate jobs and tasks from version 6.9. You have to manually recreate the supported jobs and tasks. The process for recreating these tasks is exceptionally valuable since many of the attributes of these items can be made broadly consumable by many tasks. See About comparison of Deployment Solution 6.9 tasks with 7.1 SP1 on page 128. You can only migrate Ghost and RapiDeploy images. If you want to migrate your existing images, you must create a backup copy of them on a neutral storage location before you upgrade. After you upgrade to version 7.1 SP1, you can then restore them to their correct location.
About architecture and features of Deployment Solution 7.1 SP1

The functionality and architecture of Deployment Solution 7.1 SP1 and later versions are different from that of Deployment Solution 6.9. The features and functions of Deployment 7.1 SP1 and later versions are as follows: Table 7-1 Architectural and functionality concepts of Deployment Solution 7.1 SP1
Architecture/Functionality Description
Symantec Management Platform integration Deployment Solution 7.I SP1 is integrated with Symantec Management Platform, which has centralized management capabilities. It leverages the capabilities of Symantec Management Platform's agent, console, servers, and database infrastructure.
Migrating Deployment Solution About architecture and features of Deployment Solution 7.1 SP1
119
Table 7-1
Architectural and functionality concepts of Deployment Solution 7.1 SP1 (continued)
Agent With Deployment Solution 7.1 SP1, AClient and DAgent are no longer necessary. The Symantec Management Agent and two plug-ins (the Altiris Client Task Agent and the Deployment Solution plug-in) provide the required imaging, deployment, and other functionalities. These plug-ins can be viewed through the Symantec Management Agents console. Symantec Management Platforms Configuration Management Database (CMDB) stores all inventory, configuration, and settings information that Deployment Solution collects or requires. This information is available to Deployment Solution 7.1 SP1 processes and any other solution that is implemented on the same Symantec Management Platform environment. Likewise, the information and the capabilities that are made available by other SMP solutions are available to Deployment Solution 7.1 SP1. The configuration and on-going administration of Deployment Solution 7.1 SP1 relies on the Symantec Management Console. Configuration of initial settings, infrastructure management, job creation and execution, and access to Deployment Solution reports can be performed from the console. Task Server provides the task-execution capabilities in Deployment Solution 7.1 SP1. It supports immediate task execution matching that of Deployment Solution 6.9. Deployment Solution 7.1 SP1 jobs can also include the tasks from other solutions that are installed on the same server as Deployment Solution. Furthermore, in Deployment Solution 6.9 the task engine was embedded in the Deployment Solution Server functionality. However, with Deployment Solution 7.1 SP1, this functionality can co-reside or execute remotely from the back-end server. Symantec Management Platform allows multiple task servers to be assigned to the same back-end server. For example, Notification Server. This feature gives Deployment Solution 7.1 SP1 unprecedented task-execution scalability. For more information, search for topics on Task Server in the Symantec Management Platform User Guide.
CMDB
Console
Task server
120
Table 7-1
Tasks and jobs Deployment Solution 7.1 SP1 offers both tasks and jobs as the means for performing work. Tasks are individual units of work, while jobs are sequences of tasks or other jobs. Jobs can include branching a logic that causes different paths in the job to be executed, depending on the result of previous operations. Unlike Deployment Solution 6.9, where only jobs can be executed, Deployment Solution 7.1 SP1 allows individual tasks to be scheduled. It eliminates the need for the jobs that contain only a single task. Jobs and tasks can be scheduled to be run immediately, at a later time, or with a specific frequency. The tasks that are available in Deployment Solution 6.9 and the jobs that are provided in 7.1 are correlated. All task types in Deployment Solution 7.1 SP1 are located in the console, under the Manage > Jobs and Tasks > Deployment and Migration folder. From there, you can right-click Add > New Job to bring up the Add Task dialog box. See About comparison of Deployment Solution 6.9 tasks with 7.1 SP1 on page 128. Imaging tasks The following are the important differences to keep in mind as you create the imaging tasks: Tasks do not make assumptions about the environment they are running on, such as the preboot operating system or production operating system. The job that invokes imaging tasks needs to make sure that the computer is rebooted to the appropriate environment. It ensures the reboot environment by specifying whether a computer should reboot to production or automation, independent of the current environment and its place of execution inside a job. The traditional imaging tasks have been divided into smaller tasks to enable custom processing from within an imaging job. These tasks need to be placed in an imaging job in the correct sequence to ensure proper execution. See About comparison of Deployment Solution 6.9 tasks with 7.1 SP1 on page 128.
121
Table 7-1
System configurations In Deployment Solution 7.1 SP1, system configurations are centralized resources. They are the means for remotely assigning computer and domain names, as well as local account and network settings, to a computer. Multiple configurations can be defined using the console and then applied as part of imaging jobs and configuration tasks. Deployment Solution 7.1 SP1 includes the 6.9 tokens. Tokens can be used inside scripts, as parameters in tasks, and in answer files. Users can specify custom tokens in the console. After tokens are centrally specified, they can be used in the same manner as predefined tokens. This functionality removes the need to include and maintain SQL queries inside various scripts. Deployment Solution 7.1 SP1 provides PXE capabilities as the means to accomplish zero-touch, bare-metal deployments. In Deployment Solution 7.1 SP1, PXE servers are configured though a centralized policy. After the PXE policy is configured and enabled from the Symantec Management Console, PXE services are installed. Then, the automation configurations are created on all targeted computers.
Predefined and custom tokens
PXE
Note: Each PXE server generates its automations using the

Boot Disk Creator that is installed on its own hard drive. Automation folder Deployment Solution 7.1 SP1 provides zero-touch re-imaging through its automation folder feature. This feature provides the same benefit as the automation partition capability of Deployment Solution 6.9. Using the automation folder rather than PXE for re-imaging is encouraged because of its speed and lower bandwidth requirements.
122
Migrating Deployment Solution About advantages of using Deployment Solution 7.1 SP1 over 6.9
Table 7-1
Stand-alone tools Many of the Deployment Solution 6.9 stand-alone tools are still available in Deployment Solution 7.1 SP1. Their use is integrated with the normal operation of Deployment Solution. The most commonly used tools are as follows:

PC Transplant Editor Boot Disk Creator Image Explorer Ghost Explorer
DeployAnywhere
DeployAnywhere is used to implement hardware independent imaging (HII). If DeployAnywhere is selected in the image task, it ensures that the critical drivers in an image match the target system. Otherwise, DeployAnywhere reconciles the differences. Deployment Solution 7.1 SP1 includes a database of NIC and mass storage drivers that DeployAnywhere uses to retarget an image to a specific computer. You can add drivers through Symantec Management Console > Settings > Deployment > Driver Database Management.
About advantages of using Deployment Solution 7.1 SP1 over 6.9

The key benefits of using Deployment Solution 7.1 SP1 and later versions over Deployment Solution 6.9 are as follows: Table 7-2 New capability
Server configuration synchronization
Advantages of using Deployment Solution 7.1 SP1 over 6.9 Details

Automatic synchronization of computers, jobs, scripts, security settings, system configurations, drivers, images, software packages, pre-OS, personality templates, and custom tokens across Deployment Solution servers. A central policy manages the PXE servers. Each PXE server generates images based on the configuration policy.
PXE management reliability and scalability
Migrating Deployment Solution About advantages of using Deployment Solution 7.1 SP1 over 6.9
123
Table 7-2
Advantages of using Deployment Solution 7.1 SP1 over 6.9 (continued) Details
Full customization of the menus, computers, and tasks that are visible to custom-defined roles. You can specify what roles have sufficient rights to modify jobs and tasks and what roles can only run those jobs and tasks. Out-of-the-box reports listing deployment run jobs, success status, and other pertinent information. Ability to create custom reports (grids, charts, etc.). Computer groups can be defined in terms of any given number of characteristics. Any computers that match the specified criteria automatically appear as members of those groups. A computer can belong to one or more groups.
New capability
UI customization / role-based management
Reports
Dynamic groups
Decision branching in Branch the logic that is supported inside jobs. Visual display shows jobs the portions of the job that execute if a certain condition is true. The decision check can be a multi-part logic statement that includes ANDs and ORs. Enhanced AD integration Superior capabilities for importing data from Active Directory and keeping it synchronized. Includes the ability to map roles to AD groups and leverage AD authentication information on an ongoing basis. Support for: Command Script, JavaScript, Perl Script, PowerShell, Python Script, and VBScript.
Extended scripting support
Filtered computer and Filter the computer list by any substring in the name, OS, IP job views address, and filters. You can also filter jobs by any substring in their name. This process expedites use and significantly reduces the drag-and-drop accidents. Automation folder No pre-allocation is required of contiguous disk sectors. Greater reliability and improved compatibility with full disk encryption. Task engine operation can be offloaded to one or more servers, adding to the already superior scalability of Symantec Management Platform.
Horizontal scalability through Task Server
Central custom tokens Custom tokens are extensions to predefined tokens. You can change a custom token in one place and all tasks, scripts, and answer files can access that change.
124
Migrating Deployment Solution About comparison of Deployment Solution 6.9 features with 7.1 SP1
Table 7-2
Advantages of using Deployment Solution 7.1 SP1 over 6.9 (continued) Details
Keep track of the licenses employed. The Linux Scripted OS Install has been streamlined and closely follows the recommended practices.
New capability
Streamlined scripted OS install
Tasks can be reused in Tasks are reusable, you do not need to re-defined them each time multiple jobs they are required in a job. Changing a task in one place automatically updates all jobs that include it. Extensibility through Being integrated with Symantec Management Platform, other IT management Deployment Solution 7.1 SP1 supplements the core imaging and solutions deployment capabilities of Symantec Management Platform-based solutions.
About comparison of Deployment Solution 6.9 features with 7.1 SP1

Table 7-3 lists the Deployment Solution 6.9 features and how they are implemented in Deployment Solution 7.1 SP1. Table 7-3 Comparison of Deployment Solution 6.9 features with 7.1 SP1
Deployment Solution Implementation in Deployment Solution 7.1 SP1 6.9 feature

64-bit support The Deployment Solution 7.1 SP1 is supported on 64-bit operating systems. Answer files are supported in Scripted OS Install and imaging jobs. Token replacement is also supported. Automation folders provide this functionality with some added benefits as described in preceding sections. The relationship between enclosures and individual computing units is discovered and displayed. Deployment Solution 7.1 SP1 does not display the status of a client connection. Erase/wipe tasks are available in Deployment Solution 7.1 SP1.
Answer files
Automation partition
Blade/rack enclosure view Connection status
Erase/wipe disk
125
Table 7-3
Comparison of Deployment Solution 6.9 features with 7.1 SP1 (continued)

ESX provisioning ESX Server provisioning jobs are not available out-of-the-box in Deployment Solution 7.1 SP1. This feature is planned for a future release. The entire set of Ghost Standard Tools is included in Deployment Solution 7.1 SP1.
Ghost imaging tool
Hardware independent The DeployAnywhere capabilities of Deployment Solution 6.9 are imaging included in Deployment Solution 7.1 SP1. ImageX/WIM integration Deployment Solution 7.1 SP1 does not provide scripts out-of-the-box that use ImageX/WIM. This feature is planned for a future release. The RapiDeploy multicast capabilities of Deployment Solution 6.9 are available in Deployment Solution 7.1 SP1. The imaging capabilities in Deployment Solution 7.1 SP1 match those of 6.9, with some enhancements noted in the preceding sections.
Image multicast
Imaging tasks
Imaging task progress Task completion is reported and can be viewed from the Symantec feedback Management Console. Deployment Solution 7.1 SP1 also offers progress feedback by the Altiris Log Viewer. This tool can be found under All Programs > Altiris > Diagnostics. Initial deploy Deployment Solution 7.1 SP1 offers comparable Initial Deploy capabilities as Deployment Solution 6.9.
126
Table 7-3

Inventory Deployment Solution 7.1 SP1 collects the inventory information that is included in 6.9. It also collects the following inventory information that 6.9 does not report:

Connectivity Percentage (High Speed, P2P, None) Last Logon User Last Login Domain Primary User (Month, Name, Domain) Computer Role Routable Physical Adapter Flag
TCPIPv6 (MAC, IP address, Device, Host Name, Primary DNS Suffix, Node Type, DNS server, DHCPv6, Scope ID, Gateway, Physical Adapter Flag) Virtualization (Product, Manufacturer, Version, VM GUID) OS migration (PC transplant) Deployment Solution 7.1 SP1 offers the same OS migration capabilities as 6.9, including personality capture and distribution from a central location. Deployment Solution 7.1 SP1 offers the same disk partition capabilities as 6.9.
Partition disk
Predefined computers Only the UUID field is consumed. A system configuration task is required. PXE The management of PXE servers in Deployment Solution 7.1 SP1 offers various advantages over Deployment Solution 6.9. With Deployment Solution 7.1 SP1, PXE server management is done centrally by using a policy. Boot images are no longer distributed across the wire to the other PXE servers. Instead, each PXE server automatically generates their own images based on their configuration policy. Deployment Solution 7.1 SP1 does not offer remote control capabilities. Users can get remote control through pcAnywhere or Client Management Suite. Deployment Solution 7.1 SP1 does not support the blades rip and replace functionality of Deployment Solution 6.9.
Remote control
Ripand replace
127
Table 7-3

Scripted OS install Deployment Solution 7.1 SP1 matches the Scripted OS Install capabilities of 6.9 with the added enhancements of Linux Scripted OS Install. The Deployment Solution 7.1 SP1 Copy File task provides comparable capabilities to 6.9 and the added ability to run a program as part of the task. This added feature can be used for such purposes as installing applications after copying the installation files. Deployment Solution 7.1 SP1 does not provide support for Mac deployments. The Deployment Solution 7.1 SP1 is supported on Windows Server 2008 R2. System configurations The support for System Configurations in Deployment Solution 7.1 SP1 provides various benefits over the Deployment Solution 6.9 implementation. You do not have to replicate configuration information from one server to the other servers. This process is automated in Deployment Solution 7.1 SP1. Task/Job status and history Deployment Solution 7.1 SP1 offers comparable job status and history capabilities as those in 6.9. In addition, Deployment Solution 7.1 SP1 provides an out-of-the-box report on all Deployment tasks. Deployment Solution 7.1 SP1 does not offer support for thin clients. Support for thin clients is planned for a future release. Deployment Solution 7.1 SP1 supports token replacement in the same scenarios as Deployment Solution 6.9. The predefined tokens in Deployment Solution 7.1 SP1 are a subset of the 6.9 list. Custom tokens in Deployment Solution 7.1 SP1 are centralized and can easily be added. Virtualization hostVM view Symantec Management Platforms Resource Manager displays virtualization hosts and associated virtual computers.
Software distribution
Supported OS
Thin clients
Tokens
128
Migrating Deployment Solution About comparison of Deployment Solution 6.9 tasks with 7.1 SP1
About comparison of Deployment Solution 6.9 tasks with 7.1 SP1

You can manually recreate the tasks that you had created in Deployment Solution 6.9, but with some limitations. Table 7-4 lists the equivalent tasks that you can recreate in Deployment Solution 7.I SP1 and their limitations. Table 7-4 Comparison of Deployment Solution 6.9 tasks with 7.1 SP1 Tasks in Deployment Solution 7.1 SP1
Run Script
Tasks in Deployment Solution 6.9

Run Script
Comments
aeximport utility, aexschedule utility, and WLogEvent utility are not supported in Deployment Solution 7.1 SP1. Modify the run script tasks that are created using these utilities in Deployment Solution 6.9 while recreating them in Deployment Solution 7.1 SP1. Review the script tasks that are created using tokens as some of the Deployment Solution 6.9 tokens are not supported.
Power Control Distribute Software
Power Control
No limitation
Copy file task with option to No limitation execute the task. Another option is to use Software Management Solution.
Copy file
Copy file task with the option to execute task
No limitation
129
Table 7-4
Comparison of Deployment Solution 6.9 tasks with 7.1 SP1 (continued) Tasks in Deployment Solution 7.1 SP1 Comments

Modify Configuration
Apply system configuration First create the system configuration settings from Settings > Deployment and Migration > System Configuration. Then you can create and execute the Apply system configuration task. You can create two equivalent tasks: Create Image task to capture backup image. This task is created to take a backup of a computer. The backup image is deployed on the same computer. Create Image task to capture disk image. This task is created to take a generic image that is deployed on multiple computers.
Create Disk Image
Only Ghost and RapiDeply imaging tools are supported in Deployment Solution 7.I SP1 for creating and deploying images. To create a backup image, perform the following tasks sequentially:

Reboot to Automation
Create Image (backup image ) Reboot to Production To create a disk image task, perform the following tasks sequentially: Prepare for Image Capture Reboot to Automation
Create Image (disk image) Reboot to Production
130
Table 7-4
Comparison of Deployment Solution 6.9 tasks with 7.1 SP1 (continued) Tasks in Deployment Solution 7.1 SP1
You can create two equivalent tasks:

Distribute Disk Image
Comments
You can import Deployment Solution 6.9 images to Deployment Solution 7.I SP1 Restore Back-up Image using the resource import task to deploy the backup tool. The Deployment image. Solution 6.9 images do not Deploy Image task to a contain the Symantec deploy disk image on Management Agent. When multiple computers. you deploy these images on client computers, they become unmanaged computers. To perform a Restore Back-up Image task, perform the following tasks sequentially:

Reboot to Automation Restore Back-up Image Reboot to Production
To perform a Deploy Image task, perform the following tasks sequentially:

Reboot to Automation Deploy Image Reboot to Production
Capture Personality Deploy Personality
Capture Personality Deploy Personality
No limitation No limitation
Migrating Deployment Solution About import of predefined computers in Deployment Solution 7.1 SP1
131
Table 7-4
Comparison of Deployment Solution 6.9 tasks with 7.1 SP1 (continued) Tasks in Deployment Solution 7.1 SP1
You can create two equivalent tasks:


Scripted OS Install
Comments
To perform an Install Windows OS task, perform the following tasks sequentially:

Install Windows OS Install Linux OS
Reboot to Automation Install Windows OS
To perform a Install Linux OS task, perform the following tasks sequentially:

Reboot to Automation Install Linux OS
See About reason to migrate Deployment Solution 6.9 on page 118.
About import of predefined computers in Deployment Solution 7.1 SP1

If you intend to use the Deployment Solution 6.9 CSV file in Deployment Solution 7.1 SP1, you can use it after modifying it to adhere to Deployment Solution 7.1 SP1 CSV template. In the new Deployment Solution 7.1 SP1 CSV template file, the MAC, UUID, and serial number are mandatory fields. If information in any of these fields is not provided, the mapping to the actual computer fails. When the mapping fails, a duplicate resource is created for the actual computer. Some of the fields in Deployment Solution 6.9 CSV file template are ignored in the Import predefined computer feature of Deployment Solution 7.1 SP1. The following are the fields that are ignored:

Computer Name Domain Flag Domain Controller Name Use Preferred Tree Flag Preferred Server Preferred Tree NetWare User
132
Migrating Deployment Solution Importing predefined computers
NDS Context Run Scripts Flag User Organization Key Password Never Expires Flag Cannot Change Password Flag Must Change Password Flag Username Full Name Groups Password Contact Department Email Mailstop Phone Site Computer Group Event Event Start Time
Importing predefined computers

You can import a predefined computer to assign jobs to unmanaged computers. An unmanaged computer does not yet have the Symantec Management Agent or the Deployment plug-in installed on it. When a computer performs a PXE Boot, the PectAgent sends the basic inventory from preboot environment of the imported computer in form of the new computers name and MAC address. Hence name and MAc address are mandatory fields.
Migrating Deployment Solution Installing the Deployment Solution 7.1 SP1 agent and plug-in
133
Ensure that you have set the preboot image to respond to predefined computers. In case the preboot image is not set, an error is displayed when you import the predefined computers. To import predefined computer
1 2
In the Symantec Management Console, on the Settings menu, click Deployment > Predefined Computers. Click Import Computers, and then navigate to the.txt or the .csv file containing the information about the computers to import. You can copy a sample Pre-DefinedComputers.csv file from the \Program
Files\Altiris\Notification Server\NSCap\bin\Win32\X86\Deployment\Sample\PreDefinedComputers
folder.
From the Manage menu, select Computers to view the details of imported predefined computers.
Installing the Deployment Solution 7.1 SP1 agent and plug-in

The Symantec Management Agent and the Deployment plug-in replace the Deployment Solution 6.9 clients and agent software (DAgent and adlagent). To install the 7.I SP1 agent and plug-in
1 2 3
Install Symantec Management Agent using the Symantec Management Agent Install page. Install the Deployment Plug-in using the appropriate Plug-in policy for Windows (x86 or x64) and Linux computers. Uninstall the DAgent/adlagent from the client. See Uninstalling the Deployment Solution 6.9 agent on page 133.
Uninstalling the Deployment Solution 6.9 agent

You can uninstall Deployment Solution 6.9 agents using the Runscript task to execute the following commands for different agents:
Vista and earlier version computers (AClient) C:\Program Files\Altiris\AClient\aclient.exe -remove -silent -all
134
Migrating Deployment Solution Limitations of migrating from Deployment Solution 6.9 to 7.1 SP1
Vista and later version computers (DAgent) For Linux or UNIX (adlagent)
msiexec.exe /X {6C8D5E56-CA12-42B2-9075-044B4C7067A9} /qn /opt/altiris/deployment/adlagent/bin/uninstall
Limitations of migrating from Deployment Solution 6.9 to 7.1 SP1

The following is the list of limitations that you encounter when you migrate from Deployment Solution 6.9 to Deployment Solution 7.I SP1:

Return code handling in DS 6.9 is different. Few tokens from DS 6.9 are supported. No support for standalone utilities like aexschedule and aeximport. Functionalities of Deployment Solution 6.9, like imaging, Scripted OS install, Copy File, and Script are provided, but you have to recreate these tasks. Script task functionality does not work due to limitations in command-line utilities, token, and lack of WLogEvent utility. Drivers that are added to the Preboot driver database need to be added manually. Client computers become unmanaged when the images are imported from Deployment Solution 6.9 using the import tool, ResourceImportTool.exe. The Deployment Solution 6.9 images do not contain the Symantec Management Platform Agent. To manage the client computers, install the Symantec Management Platform Agent on them.
See About reason to migrate Deployment Solution 6.9 on page 118.
Migrating from Deployment Solution 6.9 to 7.1 SP1a MR1

Deployment Solution 6.9 is a standalone product and is not designed to be integrated with Symantec Management Platform. Deployment Solution 7.1 SP1a MR1 offers the core imaging and deployment capabilities of Deployment Solution 6.9 that are natively integrated on the Symantec Management Platform. Hence, Deployment Solution 7.1 SP1a MR1 does not require its own agent, console, or database infrastructure separate from what is already provided with Symantec Management Platform. Instead, Deployment Solution 7.1 SP1a MR1 plugs in and
Migrating Deployment Solution Migrating from Deployment Solution 6.9 to 7.1 SP1a MR1
135
extends the capabilities natively offered by Symantec Management Platform. Though Deployment Solution 7.1 SP1a MR1 supports most of the functionalities of Deployment Solution 6.9, you cannot migrate jobs and tasks from version 6.9. You have to manually recreate the supported functionalities. The process for recreating these tasks is exceptionally valuable since many of the attributes of these items can be made broadly consumable by many tasks. You can only migrate Ghost and RapiDeploy images. To migrate your existing images, you must do the following:
1 2
Take a backup of theITMS 7.1SP2. Create a backup copy of the database on a neutral storage location before you upgrade or migrate. Use C:\Program Files\Altiris\Altiris Agent\Agents\Deployment\Task Handler\Tools\ResourceImportTool.exe to import DS 6.9 images to DS 7.1.SP1aMR1.
After you upgrade to version 7.1 SP1a MR1, you can then restore the data to the correct location.
See About reason to migrate Deployment Solution 6.9 on page 118. See About advantages of using Deployment Solution 7.1 SP1 over 6.9 on page 122.
136
Migrating Deployment Solution Migrating from Deployment Solution 6.9 to 7.1 SP1a MR1
Chapter
Migrating Monitor Solution


About migrating Monitor Solution About migrating Monitor Pack for Servers
About migrating Monitor Solution

You perform the product migration according to the migration scenario for IT Management Suite. The majority of the solution-specific data is migrated when you migrate according to the process that is defined in the Migrating Symantec Management Platform chapter. Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. See Migrating from Notification Server 6.x on page 33. See About data migration on page 48. Agent-based resources are not available after migration. To make agent-based resources available, you need to first upgrade the Symantec Management Agent with the Monitor Plug-in. To upgrade you need to redirect the needed resources to the Symantec Management Platform 7.1 from the old platform. For more information, see topics on Symantec Management Agent in the Symantec Management Platform User Guide. You then need to enable the applicable upgrade policy for the Monitor Plug-in. See About migrating Monitor Pack for Servers on page 138.
138
Migrating Monitor Solution About migrating Monitor Pack for Servers
About migrating Monitor Pack for Servers

When migrating Monitor Solution 6.x items to Monitor Solution 7.1, modified items (such as policies, metrics, rules, and new monitor packs) are all migrated. If an item has not been modified but is referenced by another item that has been modified, the referenced item will be migrated. For example, if you modified a metric, but not a rule that the metric references, then both the metric and the rule are migrated. Default unchanged policies, metrics, and rules do not migrate. See About migrating Monitor Solution on page 137.
Chapter
Migrating Real-Time System Manager Solution


About Real-Time System Manager migration to version 7.1 or later Manually migrating Real-Time System Manager to version 7.1 or later About manually migrating Real-Time System Manager files and settings How to validate Real-Time System Manager after the migration
About Real-Time System Manager migration to version 7.1 or later

You can migrate from Real-Time System Manager 6.x to Real-Time System Manager 7.1 or later. In addition to using the migration wizard to migrate, you must complete some manual steps. You need to manually move and store some XMLfiles on the 7.1 or later computer. Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. See Manually migrating Real-Time System Manager to version 7.1 or later on page 140.
140
Migrating Real-Time System Manager Solution Manually migrating Real-Time System Manager to version 7.1 or later
Manually migrating Real-Time System Manager to version 7.1 or later

You can use the Symantec Notification Server Wizard to help you migrate Real-Time System Manager to version 7.1 or later. Table 9-1 Process for manually migrating Real-Time System Manager 6.x to version 7.1 or later Action
Export the data from the previous Notification Server computer.
Step
Step 1
Description
Use the Symantec Notification Server Migration Wizard to migrate the items that are not stored in the SQL database. When you use the migration wizard, you must export Notification Server data to a data store file. See Exporting Notification Server 6.x data to a data store file on page 57.
Step 2
Import the exported data from the previous Notification Server computer to the Symantec Management Platform 7.1 or later.
You use the Symantec Notification Server Migration Wizard to migrate the previous Notification Server data to Symantec Management Platform 7.1 or later. When you use the migration wizard, you must import the data from a data store file. See Importing Notification Server 6.x data from a data store file on page 59.
Step 3
Move and store Real-Time System Manager files and settings.
You need to move and store some XML files from the old Notification Server computer to the Symantec Management Platform 7.1 or later computer. See About manually migrating Real-Time System Manager files and settings on page 141.
Migrating Real-Time System Manager Solution About manually migrating Real-Time System Manager files and settings
141
About manually migrating Real-Time System Manager files and settings

The Real-Time System Manager Migration Wizard contains the following exporter and importer objects:

Boot Redirection task Network Filtering task Password Management task Process Management task Service Management task Network Filtering task
The majority of your Real-Time System Manager data is migrated using the migration wizard. However, to have full predefined functionality, you must move some files. You need to manually move and store these files from the old Notification Server computer to the new 7.1 or later computer. By default, the files that need to be moved are located on your previous Notification Server in specific locations. Table 9-2 Real-Time System Manager files path Symantec Management Platform 7.1 or later path
Notification Server path
C:\Program To the following location on the new 7.1 or Files\Altiris\RTSM\UIData\CBFilters.xml later Symantec Management Platform: C:\Program Files\Altiris\RTSM\Web\UIData\CBFilters.xml
How to validate Real-Time System Manager after the migration

After you finish the migration process, it is necessary to validate the migrated items. In fact, you need to make sure that these items have been correctly migrated to your new 7.1 or later Symantec Management Platform environment. They still should have the same predefined functionality. You need to check the following items:
Connection settings and credential profiles
142
Migrating Real-Time System Manager Solution How to validate Real-Time System Manager after the migration
If you have used a security certificate in your connection settings, you need to make sure that it has a correct server name and location. For more information, see the topics about connection profiles in the Symantec Management Platform User Guide.
Network filters For more information, see the topics about filtering network traffic on multiple computers in the Real-Time System Manager User Guide. Boot Redirection You need to manually move and store your redirection images from your old Notification Server to your new 7.1 or later Symantec Management Platform environment. For more information, see the topics about booting multiple computers from another device in the Real-Time System Manager User Guide. Network Filtering You need to manually move and store your predefined custom network filters from your old Notification Server to your new 7.1 or later Symantec Management Platform environment. For more information, see the topics about filtering network traffic on multiple computers in the Real-Time System Manager User Guide. Password Management For more information, see the topics about resetting a local user password on multiple computers in the Real-Time System Manager User Guide. Process Management For more information, see the topics about running or stopping a process on multiple computers in the Real-Time System Manager User Guide. Service Management For more information, see the topics about running or stopping a service on multiple computers in the Real-Time System Manager User Guide.
Chapter
10
Migrating Real-Time Console Infrastructure


About Real-Time Console Infrastructure migration to version 7.1 or later Manually migrating Real-Time Console Infrastructure to version 7.1 or later About manually migrating Real-Time Console Infrastructure files and settings How to validate Real-Time Console Infrastructure after the migration
About Real-Time Console Infrastructure migration to version 7.1 or later

You can migrate from Real-Time Console Infrastructure 6.x to Real-Time Console Infrastructure 7.1 or later. In addition to using the migration wizard to migrate, you must complete some manual steps. You need to manually move and store some XML files on the 7.1 or later computer. Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. See Manually migrating Real-Time Console Infrastructure to version 7.1 or later on page 144.
144
Migrating Real-Time Console Infrastructure Manually migrating Real-Time Console Infrastructure to version 7.1 or later
Manually migrating Real-Time Console Infrastructure to version 7.1 or later

You can use the Symantec Notification Server Migration Wizard to help you migrate Real-Time Console Infrastructure to version 7.1 or later. Table 10-1 Process for manually migrating Real-Time Console Infrastructure 6.x to version 7.1 or later Action Description
Step
Step 1
Export data from the Use the Symantec Notification Server previous Notification Server. Migration Wizard to migrate the items computer. that are not stored in the SQL database. When you use the migration wizard, you must export Notification Server data to a data store file. See Exporting Notification Server 6.x data to a data store file on page 57.
Step 2
Import the exported data from the previous Notification Server computer to the Symantec Management Platform 7.1 or later.
You use the Symantec Notification Server Migration Wizard to migrate the previous Notification Server data to Symantec Management Platform 7.1 or later. When you use the migration wizard, you must import the old data from a data store file. See Importing Notification Server 6.x data from a data store file on page 59.
Step 3
Move and store Real-Time Console Infrastructure files and settings.
You need to move and store some XML files from the old Notification Server computer to the Symantec Management Platform 7.1 or later computer. See About manually migrating Real-Time Console Infrastructure files and settings on page 144.
About manually migrating Real-Time Console Infrastructure files and settings

The majority of your Real-Time Console Infrastructure Solution data is migrated when you migrate your Real-Time Console Infrastructure to your new 7.1 or later
Migrating Real-Time Console Infrastructure How to validate Real-Time Console Infrastructure after the migration
145
Symantec Management Platform. However, you must manually migrate some files. To migrate these files, you use your previous Notification Server computer files and move them to your new 7.1 or later Symantec Management Platform environment. Table 10-2 Real-Time Console Infrastructure files path Symantec Management Platform 7.1 or later path
Old Notification Server path
C:\Program The following location on the 7.1 or later Files\Altiris\RTSM\UIData\PortCheck.xml Symantec Management Platform: C:\Program Files\Altiris\RTCI\Web\UIData\PortCheck.xml
How to validate Real-Time Console Infrastructure after the migration

You need to check if your previous settings and options have been correctly migrated. In addition, if you had any scheduled tasks on your old Notification Server computer, check that those predefined tasks have been correctly migrated. Predefined tasks may consist of the predefined time schedule, computer profiles, connection profiles, and credential profiles as follows:
Connection and credential profiles If you have used a security certificate in your connection settings, you need to make sure that it has a correct server name and location. For more information, see the topics about connection profiles in the Symantec Management Platform User Guide. Get out-of-band inventory For more information, see the topics about collecting and viewing Intel AMT and DASH inventory in the Real-Time Console Infrastructure User Guide. Power management For more information, see the topics about managing the power state of computers remotely in the Real-Time Console Infrastructure User Guide. Update Intel AMT credentials For more information, see the topics about updating Intel AMT credentials in the Real-Time Console Infrastructure User Guide. Update Intel AMT settings
146
Migrating Real-Time Console Infrastructure How to validate Real-Time Console Infrastructure after the migration
For more information, see the topics about updating Intel AMT settings and configuring Intel AMT in the Real-Time Console Infrastructure User Guide.
Update out-of-band alert settings You need to make sure that you have a correct SNMP server for Intel AMT and ASF and the correct Destination URL for DASH. For more information, see the topics about updating Intel AMT and DASH alert settings in the Real-Time Console Infrastructure User Guide.
Chapter
11
Migrating Carbon Copy Solution


About migrating from Carbon Copy 6.x Advantages of using pcAnywhere over Carbon Copy Before you begin the 6.x migration with pcAnywhere Migrating from Carbon Copy 6.x
About migrating from Carbon Copy 6.x

pcAnywhere 12.6 replaces Carbon Copy 6.x. When you install the pcAnywhere plug-in on a client computer, it automatically removes the Carbon Copy agent. If you have client computers with the Carbon Copy agent installed and you do not install the pcAnywhere plug-in on them, the Carbon Copy agent does not uninstall automatically. When you install the pcAnywhere plug-in on a client computer, it installs the pcAnywhere host on each targeted client computer. The installation package that is sent to each targeted computer is approximately 50MB. If you customize the communication ports on the 6.x server, be sure to customize the ports on the current server as well. Note: In this guide, the information that applies to current version of the product also applies to later releases of the product unless specified otherwise.
148
Migrating Carbon Copy Solution Advantages of using pcAnywhere over Carbon Copy
You can migrate Carbon Copy events and inventory data to the current release. However, you can only use the data to view legacy reports and view historical data. The data is not usable by pcAnywhere. In the migration wizard export settings, Carbon Copy data is included under the pcAnywhere node. See Before you begin the 6.x migration with pcAnywhere on page 148. See Migrating from Carbon Copy 6.x on page 149. See Advantages of using pcAnywhere over Carbon Copy on page 148.
Advantages of using pcAnywhere over Carbon Copy

The advantages of using pcAnywhere over Carbon Copy are as follows:

Remote/Viewer supports Windows Mobile. pcAnywhere supports Mac OS X. pcAnywhere supports Linux. pcAnywhere includes robust security in the form of serialization and mandatory passwords. pcAnywhere includes platform improvements such as a client-side mirror driver. pcAnywhere includes an access server, which provides remote session connectivity.
See About migrating from Carbon Copy 6.x on page 147. See Migrating from Carbon Copy 6.x on page 149.
Before you begin the 6.x migration with pcAnywhere

Before you begin the migration from 6.x, complete the following tasks:

Back up your current 6.x server and database. Validate the success of the backups before you proceed. Review the solutions you have currently installed in the source 6.0 system and capture the information. You should have the same installed solutions on the target server (wherever applicable) for the migration wizard to properly place the data that has been gathered from the 6.0 source computer. Verify that all IT Management Suite licenses are stored in a safe location.
Migrating Carbon Copy Solution Migrating from Carbon Copy 6.x
149
If the licenses are not downloaded or available, you can regain them from the Symantec Licensing Portal .
Migrating from Carbon Copy 6.x

In the current IT Management Suite, pcAnywhere Solution replaces Carbon Copy 6.x. After pcAnywhere is integrated with Symantec Management Platform, it leverages the platform capabilities. Ensure that you have completed the required tasks before you start migrating to the current IT Management Suite. See About migrating from Carbon Copy 6.x on page 147. See Before you begin the 6.x migration with pcAnywhere on page 148. To migrate from Carbon Copy 6.x
Prepare the target server for the installation of IT Management Suite. IT Management Suite requires and is currently only supported on Microsoft Windows 2008 R2 SP1. For SSL and other certificates, make sure that they are in place on the target server before you install Symantec Installation Manager or solutions.
2 3 4
Install IT Management Suite or pcAnywhere onto the target server (including the migration components within the optional components). Use the migration wizard to export 6.x data from the source 6.x server. Copy the x86 migration package from the IT Management Suite server onto 6.x server. The package is located at Program Files\Symantec Installation
Manager\Migration Package\
Multiple migration packages are launched and installed for pcAnywhere.
5 6 7
Run the copied migration package on 6.X server. This exports KMS and CM keys into a data store file (*adb) Back up the data store file (*adb). Restore the backed up data store file onto IT Management Suite server .
150
Migrating Carbon Copy Solution Migrating from Carbon Copy 6.x
8 9
Run the x64 migration wizard and import the backed up.adb file. Enable deploy policies for the Symantec Management Agent and the pcAnywhere plug-ins. The Symantec Management Agent and the pcAnywhere agents replace the older Altiris Agent and the Carbon Copy Agent.
Chapter
12
Migrating Out of Band Management Component


About Out of Band Management Component migration Manually migrating Out of Band Management Component Migrating the Intel AMT database Reconfiguring the Intel AMT database Redirecting the Altiris Agents from Notification Server 6.x About fine-tuning Out of Band Management Component after migration
About Out of Band Management Component migration

Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. To successfully migrate Out of Band Management Component to Notification Server 7.1, you perform the two types of product migration:
Migration with the Symantec Notification Server Migration Wizard You use the Symantec Notification Server Migration Wizard to migrate your previous Notification Server data that is stored in the Configuration Management Database (CMDB). See About the Symantec Notification Server Migration Wizard on page 50. Manual migration
152
Migrating Out of Band Management Component Manually migrating Out of Band Management Component
In addition to using the migration wizard, you need to manually migrate the items that are not stored in the CMDB. To preserve the Intel AMT database, you must manually migrate it from your previous Notification Server computer. After you move the Intel AMT database to your new environment, you must complete configuration steps to make it operate correctly. See Manually migrating Out of Band Management Component on page 152.
Manually migrating Out of Band Management Component

See About Out of Band Management Component migration on page 151. Table 12-1 Process for manually migrating Out of Band Management Component 6.x Action
Export data from Notification Server 6.x.
Step
Step 1
Description
Use the Symantec Notification Server Migration Wizard to migrate the items that are not stored in the Configuration Management Database (CMDB). When you use the migration wizard, you export the 6.x data to a data store file. See Exporting Notification Server 6.x data to a data store file on page 57.
Step 2
Manually migrate the Intel AMT database to the Symantec Management Platform 7.1.
The Intel AMT database is not migrated through the migration process. To preserve it, you must manually migrate it from Notification Server 6.x to the Symantec Management Platform 7.1. See Migrating the Intel AMT database on page 153.
Step 3
Reconfigure the Intel AMT database on the Symantec Management Platform 7.1.
After you migrate the Intel AMT database to your new environment, you must validate it and make sure that it operates correctly. See Reconfiguring the Intel AMT database on page 154.
Migrating Out of Band Management Component Migrating the Intel AMT database
153
Table 12-1
Process for manually migrating Out of Band Management Component 6.x (continued) Action
Import the exported 6.x data to the Symantec Management Platform 7.1.
Step
Step 4
Description
You use the Symantec Notification Server Migration Wizard to migrate the 6.x data to the new version of Symantec Management Platform. When you use the migration wizard, you import the 6.x data from a data store file. See Importing Notification Server 6.x data from a data store file on page 59.
Step 5
Redirect the Altiris Agents on managed computers from Notification Server 6.x to Notification Server 7.1.
The Altiris Agents that previously reported to Notification Server 6.x need to be redirected to Notification Server 7.1. See Redirecting the Altiris Agents from Notification Server 6.x on page 155.
Step 6
Fine-tune Out of Band Management Component after migration.
After you have finished all the migration steps, you can fine-tune Out of Band Management Component. See About fine-tuning Out of Band Management Component after migration on page 156.
Migrating the Intel AMT database

The Intel AMT database is not migrated through the migration process. To preserve it, you must manually migrate it from the previous Notification Server to Notification Server 7.1. You can do so by detaching Intel AMT database from the previous Notification Server database, and then attaching it to the Notification Server 7.1 database. You can use Microsoft SQL Server Management Studio to manually move the Intel AMT database to your new environment. This task is a step in the process for manually migrating Out of Band Management Component. See Manually migrating Out of Band Management Component on page 152.
154
Migrating Out of Band Management Component Reconfiguring the Intel AMT database
To detach the Intel AMT database on the previous Notification Server computer
1 2 3 4 5 6
On the previous Notification Server computer, open Microsoft SQL Server Management Studio. In Object Explorer, connect to an instance of the Microsoft SQL Server Database Engine, and then expand that instance. In Object Explorer, expand Databases. Right-click the Intel AMT database that you want to detach, and then click Tasks > Detach. In the Detach Databases dialog box, under Databases to detach, verify that the Database Name column displays the name of the Intel AMT database. (Optional) By default, the detach operation retains any out-of-date optimization statistics when detaching the database; to update the existing optimization statistics, check Update Statistics. To disconnect any active connections that the database has, check Drop Connections. Click OK.
7 8
To attach the Intel AMT database on the Notification Server 7.1 computer
1 2 3 4 5
On the Notification Server 7.1 computer, open Microsoft SQL Server Management Studio. In Object Explorer, connect to an instance of the Microsoft SQL Server Database Engine, and then expand that instance. Right-click Databases, and then click Attach. In the Attach Databases dialog box, click Add to specify the database to be attached. In the Locate Database Files dialog box, select the disk drive where the database resides and browse to the .mdf file of the Intel AMT database that you want to attach. Click OK. (Optional) To refresh the view to display the newly attached database, on the View menu, click Refresh. The newly attached database displays in Object Explorer > Databases.
6 7
Reconfiguring the Intel AMT database

After you move the Intel AMT database to your new environment, you must validate it and make sure that it operates correctly. In addition, make sure that
Migrating Out of Band Management Component Redirecting the Altiris Agents from Notification Server 6.x
155
the correct address of the SQL Server and SQL Login is specified in the Out of Band Management Component settings. This task is a step in the process for manually migrating Out of Band Management Component. See Manually migrating Out of Band Management Component on page 152. To reconfigure the Intel AMT database
1 2 3 4
In the Symantec Management Console, on the Home menu, click Remote Management > Out of Band Management. In the left pane, under Configure Additional OOB Site Server, click Configure and Assign OOB Site Servers. Click Site Management > Settings > OOB Service > OOB Service Settings. Under Global OOB site service installation settings, under SQL settings, specify the SQL server name where the Intel AMT database is now located.
If you have used the default Intel AMT database name on your previous Notification Server, and you have transferred it to a 7.1 environment with the same name, Out of Band Management Component 7.1 automatically accepts the previous database. In some cases, before the installation of out-of-band site servers, you need to modify out-of-band site server settings with your custom database name. For more information, see the topics about configuring the out-of-band site server installation settings in the Out of Band Management Component Implementation Guide.
Redirecting the Altiris Agents from Notification Server 6.x

On managed computers, you need to redirect the Altiris Agents that previously reported to Notification Server 6.x. You can redirect them by changing the server name and server Web address to Notification Server 7.1. This task is a step in the process for manually migrating Out of Band Management Component. See Manually migrating Out of Band Management Component on page 152. To redirect the Altiris Agents from Notification Server 6.x
1 2
In the Altiris Console 6.5, click Configure > Agents > Desktop Settings. On the Altiris Agent Settings page, click the Advanced Settings tab.
156
Migrating Out of Band Management Component About fine-tuning Out of Band Management Component after migration
Under Alternate URL for accessing NS, check Specify an alternative URL for the Altiris Agent to use to access the NS, and then specify the URL for Notification Server 7.1 as follows:
Server Name Symantec recommends that you use the fully qualified domain name. Server Web The Server Web address should be in the following format:
https://<NS_FQDN>:<port>/Altiris/
Click Apply.
About fine-tuning Out of Band Management Component after migration

You can start to fine-tune Out of Band Management Component after you complete the steps for manual migration. The task of fine-tuning Out of Band Management Component is a step of the process for manually migrating Out of Band Management Component. See Manually migrating Out of Band Management Component on page 152. After Out of Band Management Component migration, you need to consider the following:
Active Directory integration reinitiation Active Directory integration cannot be migrated from the Out of Band Management Component 6.2 to 7.1. You must manually reinitiate the Active Directory integration in the Out of Band Management Component portal, on the Configure General Settings page. Secure TLS profiles If you previously used Secure TLS profiles, then you need to request a new security certificate for the 7.1 version of Symantec Management Platform. For more information, see the topics about configuring TLS in the Out of Band Management Component Implementation Guide.
You may get the following error messages that help you to tune the performance of Out of Band Management Component after migration:
Configuration saved but cannot be applied. Please check that currently selected Intel SCS is installed and running on Service Location page
157
This message displays on the Service Location page. This message is an expected issue. It means that you do not have an Out of Band Management Component site server installed. You need to install an out-of-band site server. The SQL settings must be applied to the out-of-band site server. For more information, see the topics about installing an out-of-band site server in the Out of Band Management Component Implmentation Guide.
Obsolete Intel AMT Setup and Configuration Services
You may get this error message after you migrate Out of Band Management Component from 6.2 to 7.1. It means that the Out of Band Management Component site server database contains the data about Notification Server 6.2. On the Obsolete Intel AMT Setup and Configuration Services page, you can delete the obsolete site servers or upgrade them. You access the page by clicking the error message.
158
Chapter
13
Migrating CMDB Solution

About migrating CMDB Solution
About migrating CMDB Solution

You perform the product migration from 6.x according to the migration scenario for Asset Management Solution and IT Management Suite. Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. See About migrating Asset Management Solution on page 167. See Migrating from Notification Server 6.x on page 33. See About data migration on page 48. See About the Symantec Notification Server Migration Wizard on page 50.
160
Migrating CMDB Solution About migrating CMDB Solution
Chapter
14
Migrating Barcode Solution


About migrating Barcode Solution Manually migrating your Barcode Solution files and settings Synchronizing data Verifying asset data Backing up the Barcode Solution default synchronization profile Restoring the Barcode Solution default synchronization profile
About migrating Barcode Solution

In addition to using the migration wizard to migrate Barcode Solution, you must complete some manual steps. See Manually migrating your Barcode Solution files and settings on page 162. Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. Before you migrate your data, you need to take the following actions:
Ensure that handheld devices have uploaded their data to the previous Notification Server computer. See Synchronizing data on page 163. Ensure that all batches in the upload verification section have been processed. See Verifying asset data on page 164. Back up the default synchronization profile.
162
Migrating Barcode Solution Manually migrating your Barcode Solution files and settings
See Backing up the Barcode Solution default synchronization profile on page 165.
Manually migrating your Barcode Solution files and settings

The majority of your Barcode Solution data is migrated when you migrate your Configuration Management Database (CMDB) using the migration wizard. However you must first manually migrate your default synchronization profile settings. To migrate these settings you use the console to export them into an XML file. You then import this XML file after you install your new Symantec Management Platform. In addition, Symantec recommends that you finish synchronizing all your data from the handheld devices. Also, ensure that you verify your asset data before you load it into the CMDB by processing all batches. See About migrating Barcode Solution on page 161. Table 14-1 Process for manually migrating your Barcode Solution files and settings Action
Handheld devices have uploaded their data to the previous Notification Server computer.
Step
Step 1
Description
You must finish synchronizing all your data from the handheld device to the Barcode Solution before you migrate. Failure to do this means you may lose data. You cannot upload the data from the old version of Barcoder to the new version Barcode Solution. You have to upload to the old version of the Barcode Solution first and then migrate the data over again. See Synchronizing data on page 163.
Step 2
All batches in the upload verification section have been processed.
All batches in the upload verification section have been processed. See Verifying asset data on page 164.
Migrating Barcode Solution Synchronizing data
163
Table 14-1
Process for manually migrating your Barcode Solution files and settings (continued) Action
Back up the Barcode Solution default synchronization profile.
Step
Step 3
Description
Use the Symantec Management Console to export your default synchronization profile settings into an XML file. Store this file on a neutral storage location. See Backing up the Barcode Solution default synchronization profile on page 165.
Step 4
Use the Symantec Notification Use the Symantec Notification Server Server Migration Wizard to export Migration Wizard to export and import and import your data. your data. See Exporting Notification Server 6.x data to a data store file on page 57. See Importing Notification Server 6.x data from a data store file on page 59.
Warning: Since Barcode Solution relies

on CMDB Solution, the CMDB data must be imported at the same time or before you import your barcode data. For this reason ensure that you have CMDB Solution selected in the Exporter Configuration page of the Symantec Notification Server Migration Wizard . Step 5 Restore the Barcode Solution default synchronization profile file Use the Symantec Management Console to import your default synchronization profile settings from an XML file. See Restoring the Barcode Solution default synchronization profile on page 165.
Synchronizing data
Any data that is specified in the user profile and the Manage Handheld Device page is uploaded to the barcode device in the initial synchronization. It may involve the transfer of a significant amount of data. Ensure a good connection (either wireless or through a cradle) with the Notification Server computer.
164
Migrating Barcode Solution Verifying asset data
This task is part of the process for manually migrating your Barcode Solution files settings. After you complete this task, you can complete the rest of the process. See Manually migrating your Barcode Solution files and settings on page 162. To synchronize data
1 2 3 4
Make sure that the barcode device has a connection to the host computer, either wireless or through a synchronization cradle. On the barcode device, click Start > Programs > Symantec Altiris Barcoder. Select Synchronize from the menu option. Enter your security credentials and click Login. Your password and user name are cached for an hour on the handheld device. If you do not use it for over an hour, you must reenter your security credentials. Closing the application clears the cached credentials; they need to be reentered on launching the application again.
5 6
Select the synchronization profile to use, and click Next. Choose one of the synchronization options, and click Sync.
Verifying asset data

By default, you need to verify your asset data before you load it into the Configuration Management Database. You verify asset data from the Upload Verification page. This task is part of the process for manually migrating your Barcode Solution files settings. After you complete this task, you can complete the rest of the process. See Manually migrating your Barcode Solution files and settings on page 162. To verify asset data
1 2 3 4 5
In the Altiris Console, on the Home menu, click Tasks. In the left pane, click Tasks > Barcode > Manage Changes > Upload Verification. In the Batch Summary Table in the right pane, select the batch of uploaded data that you want to verify. Click Batch Details. In the Batch Details dialog box, select a resource and click Resource Details to view its changed details.
Migrating Barcode Solution Backing up the Barcode Solution default synchronization profile
165
6 7
Click Apply, and close the Batch Details dialog box. In the Batch Summary Table select the relevant batch and click Apply to save changes.
Backing up the Barcode Solution default synchronization profile

Before you decommission your previous Notification Server computer, back up your Barcode Solution default synchronization profile to a neutral storage location. Name the clone default profile Default profile 6.x or similar. Since the default profile already exists on 7.1, renaming the cloned default profile ensures that it can be identified differently in the 7.1 environment. By being uniquely identifiable, the cloned default profile is not overwritten. This task is part of the process for manually migrating your Barcode Solution files settings. After you complete this task, you can complete the rest of the process. See Manually migrating your Barcode Solution files and settings on page 162. To back up the Barcode Solution default synchronization profile:
1 2 3 4 5
On your previous Notification Server computer, in the Altiris Console, select the Configuration tab. In the left pane, expand Configuration > Solutions Settings > Assets and Inventory > Barcode Solution > Synchronization Profile > Default. Right-click Default, and click Export. Save the Default.xml file to a neutral storage location. Clone the default profile to ensure that it can be identified in the 7.1 environment.
Restoring the Barcode Solution default synchronization profile

After you install Symantec Management Platform and have run the migration wizard, you can restore your Barcode Solution default synchronization profile. This task is part of the process for manually migrating your Barcode Solution files settings. After you complete this task, you can complete the rest of the process. See Manually migrating your Barcode Solution files and settings on page 162.
166
Migrating Barcode Solution Restoring the Barcode Solution default synchronization profile
To restore the Barcode Solution default synchronization profile:
1 2 3 4 5
On your new Notification Server computer, in the Symantec Management Console, go to Home > Service and Asset Management > Barcode. In the left pane, expand Barcode Solution > Synchronization Profiles > Default. Right-click the Synchronization Profiles folder, and click Import. Browse to the default synchronization file. Click Open.
Chapter
15
Migrating Asset Management Solution


About migrating Asset Management Solution About data migration special cases Migrating legacy software license items
About migrating Asset Management Solution

You perform the product migration from Asset Management Solution 6.x according to the migration scenario for IT Management Suite. Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. See Migrating from Notification Server 6.x on page 33. See About data migration on page 48. After you migrate your data from a Notification Server 6.x environment, you must do the following:
Review and reconfigure the asset-specific security access rights because they are not copied to the corresponding 7.1 roles automatically. See About data migration special cases on page 168. Migrate the legacy software license items. See Migrating legacy software license items on page 169.
168
Migrating Asset Management Solution About data migration special cases
About data migration special cases

When you migrate from Notification Server 6.x, there are some data migration special cases that you need to know about. See About migrating Asset Management Solution on page 167. Table 15-1 Data
Pre-6.5 Legacy Receiving Types
About data migration special cases
Description
Legacy Receiving Types are not upgraded. If any existing Legacy Receiving Type is found, the Legacy Receiving Types Check exporter fails and gives a warning message.
The schedules that The following CMDB Solution schedules become tasks and are accessible from the Jobs/Tasks are converted to page: tasks Assign Computer's Ownership to be the Primary User

Clean Ownership Duplicate Computer Merge Duplicate User Merge Inventory Clean Up Inventory To Asset Synchronization Resource Merge Rule Update Network Resource Location
The following Asset Management Solution schedules become tasks and are accessible from the Jobs/Tasks page:

Depreciable Items Cost Evaluation Software License Evaluation
Notification Policies
The 6.x Notification Policies are moved to the Legacy Notification Policies folder under Settings > Notification Server. Existing folder structure is retained. Note that Asset Management Solution and CMDB Solution do not upgrade the Task/Job and Message Action Policy items because the Task Management Solution owns them.
Accounting Period If the accounting period is configured in 6.5, then it is also regenerated in 7.1 based on the accounting period item details. Cost Model Upgrade logic The 6.5 data class is not able to record a situation where all owners are removed from an asset. A new upgrade logic is able to populate the correct tables even when all the ownership information is deleted. All Asset 6.5 roles are renamed to Role Name+(legacy). You must review their security access rights and make appropriate changes if necessary.
Asset Roles
Migrating Asset Management Solution Migrating legacy software license items
169
Migrating legacy software license items

After you complete the task of migrating data from a Notification Server 6.x environment, you must migrate legacy software license items to Symantec Management Platform 7.1. Asset Management Solution 7.1 includes a wizard that helps you go through this process. See About migrating Asset Management Solution on page 167. To migrate legacy software license items
1 2
Complete the steps to migrate data from Notification Server 6.x. Make sure that your Migrate Legacy Software Licenses settings are correct. For more information, see the topics about configuring settings for migrating legacy software licenses in the Asset Management Suite User Guide.
Make sure that the Software Catalog is populated and current. You can use manual entry, run the Software Discovery task, or run an inventory policy. For more information, see the topics about populating the Software Catalog in the Symantec Management Platform User Guide.
4 5
In the Symantec Management Console, on the Home menu, click Service and Asset Management > Software Licensing. In the right pane, in the Legacy Licenses Requiring Migration Web part, click Legacy License Count: n. The Legacy License Count n indicates the number of legacy software license items that need to be migrated.
In the List of legacy 6.5 Software Licenses to be migrated list, right-click a license that you want to migrate, and then click Migrate Legacy Software License. Note that you migrate each software license one by one and it takes two to three minutes to migrate each license in case you have all the software purchase and software product data available in the Configuration Management Database (CMDB).
7 8
In the Migrate Legacy Software License wizard, follow the on-screen instructions for each software license item that you need to migrate. Click Finish. After a software license item is migrated, it appears in the Software License list. The Legacy License Count indicates the number of software license items that still need to be migrated. Note that you must right-click in the Web part, and then click Refresh to display the changes.
170
Migrating Asset Management Solution Migrating legacy software license items
Chapter
16
Migrating Workflow Solution


About migrating Symantec Workflow Process for upgrading Workflow Determining the persistence settings of a project Creating a version of a project
About migrating Symantec Workflow

You perform the Symantec Workflow data migration from 6.x according to the migration scenario for IT Management Suite. Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. See Migrating from Notification Server 6.x on page 33. See About data migration on page 48. After you migrate your data, you must upgrade your Workflow processes. See Process for upgrading Workflow on page 171.
Process for upgrading Workflow

Refer to the following steps if you upgrade Workflow.
172
Migrating Workflow Solution Process for upgrading Workflow
If you want to install Workflow for the first time, see the following installation topic. The installation of Workflow is set up so you do not damage a previous installation of Workflow. For example, the current version of Workflow uses a different file structure than previous versions of Workflow. Instead of using an Altiris-branded folder in the file system directory, the current version of Workflow uses a Symantec-branded folder. If you install Workflow on a server that does not have a previous version of Workflow, the installation uses a Symantec-branded folder. However, if you install Workflow on a server that does have a previous version of Workflow, the installation uses the old file system settings. The installation uses the old file system settings in order not to break running processes, file persistence, and other file-based dependencies. Workflow also has a new name for its Windows service. In previous versions of Workflow, the Windows service had the name LogicBase 2006 Server Extensions. For the current version of Workflow, the Windows service has the name Symantec Workflow Server. If the name LogicBase 2006 Server Extensions exists on the server when you install Workflow, the installation does not replace the service. When you install Workflow, the installation includes a silent installation of Workflow Server on your Symantec Management Platform computer. However, if you already have Workflow Server running on a Symantec Management Platform computer, installing Workflow does not upgrade Workflow Server. Upgrading Workflow Server would break running processes. Instead, the Workflow installation adds a message in the Symantec Management Console that Workflow Server should be upgraded manually. In this case, Symantec recommends scheduling a service stop, upgrading Workflow Server, testing published processes, and then resuming service. Warning: If you are upgrading from 6.x to 7.x, you can disrupt currently running processes by installing Workflow if you do not retain the same persistence settings. Ideally, you should use the same persistence settings with a later version of Workflow that you used for the earlier version of Workflow. During installation you can set the persistence settings for Workflow. If you do not know which persistence settings your current version of Workflow uses, refer to the following topic: See Determining the persistence settings of a project on page 174.
Migrating Workflow Solution Process for upgrading Workflow
173
Table 16-1 Step

Step 1
Process for upgrading currently running processes Description

Create packages for all your projects, and store these packages on a safe directory. For more information about creating a project package, see the Symantec Workflow User Guide. See Creating a version of a project on page 176.
Action
Back up your projects.
Step 2
Back up the Process Manager database. Install Workflow on a testing server.
Create a backup of your Process Manager database. Store the database backup on a safe directory. Install Workflow in a testing environment, or upgrade your existing Workflow testing server. When you install on your testing server, make sure that you do the following: Use the same Workflow persistence settings as in your earlier version of Workflow configuration. If you do not know which persistence settings you used in the earlier version of Workflow, see the following topic: See Determining the persistence settings of a project on page 174. If you use persistence settings that are not supported by Workflow, see the following topic: See Creating a version of a project on page 176. Set Workflow to have access to a Symantec Management Platform server (Notification Server).
Step 3
Step 4
Revise your projects.
Open each project and make the necessary changes for it to be compatible with Workflow and the Symantec Management Platform. If you can, use the same persistence settings for your Workflow projects as you used for your earlier versions of Workflow projects. See Determining the persistence settings of a project on page 174.
Step 5
Publish revised projects Publish the revised projects to the Workflow server. For more information to the Workflow server. about publishing projects, see the Symantec Workflow User Guide. Test revised projects. Conduct thorough tests to ensure that your projects work properly in a Workflow and Symantec Management Platform environment. If you encounter any problems, fix the project and republish.
Step 6
Warning: Publishing untested processes in a production environment can

cause significant problems. Symantec recommends that you test all processes thoroughly before you publish them to a production environment.
174
Migrating Workflow Solution Determining the persistence settings of a project
Table 16-1 Step

Step 7
Process for upgrading currently running processes (continued) Description
Action
Install Workflow on the Install Workflow on your production server. When you install, make sure production server. that you use the same persistence settings as in your earlier version of configuration. If you have legacy projects, check the persistence settings before you select a setting during the installation. See Determining the persistence settings of a project on page 174.
Step 8
Publish revised projects Publish all of your revised projects to the Workflow production server. For to the production more information about publishing projects, see the Symantec Workflow server. User Guide.
Determining the persistence settings of a project

Persistence refers to how a running process is stored in memory to improve the performance of Workflow. Workflow Installer sets up persistence during installation, and the settings are stored in SymQ. Persistence is set at the project level, but most projects use the default setting that you set when Workflow was installed, usually file-based. You can determine persistence settings as follows:
In Workflow Explorer, identify persistence settings of a current project. To determine the default persistence setting in the Workflow Explorer On the legacy Workflow Server, identify persistence settings of legacy projects that you want to migrate during an upgrade. Note that if you have a much older project that you created in a legacy version of Workflow, you may see the persistence settings in the Publishing tab. To determine the persistence settings of a legacy project for upgrade purposes
The following table describes the persistence options: Table 16-2 Persistence option
LogicBase.Components.Ensemble.WSWorkQueue
Persistence options Description

Uses the Process Manager SQL database settings. The Workflow project uses the Process Manager database for persistence. No Workflow equivalent of this setting exists.
Migrating Workflow Solution Determining the persistence settings of a project
175
Table 16-2 Persistence option
Persistence options (continued) Description

Uses Exchange for persistence. This setting is the most common persistence setting and uses either file-based or SQL-based persistence over Exchange. The Workflow equivalent of this option is Exchange (file-based) or SQL-based persistence. You set the persistence option when you install Workflow. For information about determining whether this setting uses file-based or SQL-based persistence, see the following procedure: See To determine the default persistence setting in the Workflow Explorer on page 176.
LogicBase.Components.Default.ExchangeAdapters. LogicBaseExchangeWorkQueue
LogicBase.Core.Workflow.FileSystemAdapters. FileSystemWorkQueue
Uses direct file-based persistence. No Workflow equivalent of this setting exists.
LogicBase.Core.Models.Workflow.InMemoryWorkQueue Uses internal Workflow memory. No Workflow equivalent of this setting exists. LogicBase.Core.Workflow.SQLServerAdapters. SQLServerWorkQueue Uses direct SQL-based persistence. No Workflow equivalent of this setting exists.
Your projects are probably set to use LogicBase.Components.Default.ExchangeAdapters.LogicBaseExchangeWorkQueue. In this case, you can determine whether the exchange is set to file-based or SQL-based persistence in Workflow Explorer. See To determine the default persistence setting in the Workflow Explorer on page 176. If any of your projects use a persistence setting other than LogicBase.Components.Default.ExchangeAdapters.LogicBaseExchangeWorkQueue, you should create a version to avoid losing process data. See Creating a version of a project on page 176. This task is a step in the process for upgrading Symantec Workflow. See Process for upgrading Workflow on page 171.
176
Migrating Workflow Solution Creating a version of a project
To determine the default persistence setting in the Workflow Explorer
1 2 3 4
Click Start > Programs > Symantec > Workflow Designer > Tools > Workflow Explorer. In the Symantec Workflow Explorer window, click the SymQ Configuration tab. In the left pane, click SymQ_Local_Defaults. In the right pane, double-click local.workflow-. If the Deliver To Queue property is set to LBME.Workflow- (with a prefix), the default persistence setting is file-based. If the Deliver To Queue property is set to workflowsqlexchange (with a prefix), the default persistence setting is SQL-based.
To determine the persistence settings of a legacy project for upgrade purposes
1 2
On the legacy Workflow Server, click Start > Programs > Symantec > Workflow Designer > Tools > Local Machine Info editor. In the Symantec Workflow Server section, in the Default Persistence property, you see the persistence settings. Legacy persistence settings map to persistence settings for a current installation as follows:
If the legacy persistence setting is type: file, the current setting should be Based on Exchange. If the legacy setting is type: SQL, the current setting should be Based on SQL Server Database.
Creating a version of a project

The preferred persistence setting for Workflow is SymQ. If you upgrade Workflow and have an earlier version of a Workflow project that uses a different persistence setting, the earlier setting may not be supported in the current version of Workflow. In this case you should create a version of the project. See Determining the persistence settings of a project on page 174. When you upgrade Workflow and want to ensure that a new version of a project does not overwrite a legacy version of the same project, you can create a version. Creating a version ensures that you do not lose any process data (such as tasks). The term project refers to the named entity (the project that you develop and name). The term process refers to the project as it runs.
177
Project versions are handled in IIS. When you publish a workflow project, a new virtual directory is created in IIS, unless one of the same name already exists. If an identical directory exists, the new process overwrites the process that is already published there. To preserve both projects, you must create a new virtual directory to contain the updated project while the legacy process is allowed to run in its virtual directory. The following steps assume that you have a currently running process that you want to replace with an update. You can create a version only with the Publish Application to Server publishing option. Because the other publishing options do not let you set the virtual directory name, you cannot create versions with them. This task is a step in the process for upgrading Symantec Workflow. See Process for upgrading Workflow on page 171. To create a version of a project
At the top level of the project tree, change the service ID of the project. The new version must have a different service ID than the previous version. No two published workflows should ever have the same service IDs.
2 3
In Workflow Designer, when you are ready to publish your updated project, click File > Deploy Project > Publish Project. In the Virtual Directory field, add the updated version number to the end of the name of the virtual directory. For example, if the old process is in a virtual directory called PurchaseOrder, call the new virtual directory PurchaseOrder2.0. Warning: If you publish without changing the name of the virtual directory, your new process completely replaces the old one. The new process also breaks any of its current instances.
4 5
Complete the publishing process as normal. Repoint the invocation links to the virtual directory of the updated process. In other words, whatever invoked the old process must be repointed to the new virtual directory that contains the process. As examples, a Process Manager service catalog item or an external link can invoke an old process.
After the old process has finished all activity, delete its virtual directory.
If you have one or more legacy projects, you can find the persistence settings in the project, on the Publishing tab.
178
To identify the persistence settings of a legacy project
1 2 3
Open the project. Click the Publishing data tab. Look at the Work Queue Service Name property to see if the legacy setting is file or SQL.
For more information about data tabs, see the Symantec Workflow User Guide.
Chapter
17
Migrating Inventory Pack for Servers Solution

About migrating Inventory Pack for Servers
About migrating Inventory Pack for Servers

Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. You perform the product migration from the version 6.x according to the migration scenario for Inventory Solution and IT Management Suite. See Before you migrate Inventory Solution on page 69. See Migrating from Notification Server 6.x on page 33. See About data migration on page 48. See About the Symantec Notification Server Migration Wizard on page 50.
180
Migrating Inventory Pack for Servers Solution About migrating Inventory Pack for Servers
Chapter
18
Migrating Power Scheme Solution

About migrating Power Scheme
About migrating Power Scheme

No manual solution-specific migration steps are required. The solution-specific data is migrated when you migrate the product data according to the process that is defined in the Migrating Symantec Management Platform chapter. Note: In this guide, the information that applies to version 7.1 of the product also applies to later releases of the product unless specified otherwise. You should verify and validate that the solution data and settings have been migrated correctly. See Migrating from Notification Server 6.x on page 33. See About data migration on page 48.
182
Migrating Power Scheme Solution About migrating Power Scheme
Chapter
19
Migrating Recovery Solution


About migrating Recovery Solution Further information about Recovery Solution
About migrating Recovery Solution

For detailed instructions about how to migrate Recovery Solution, see the Recovery Solution 7.1 release notes. They are available at the following URL: http://www.symantec.com/docs/DOC4396 Recovery Solution is not a part of IT Management Suite 7.1. Do not upgrade from 6.x to IT Management Suite 7.1 if you want to keep the Recovery Solution features.
Further information about Recovery Solution

For more information about new versions and upgrades, visit the support page for Recovery Solution.You can also contact the Symantec Business Sales team.
184
Migrating Recovery Solution Further information about Recovery Solution
Chapter
20
Migrating Mobile Management Solution


About migrating Mobile Management Solution Further information about Mobile Management Solution
About migrating Mobile Management Solution

Mobile Management Solution is not a part of IT Management Suite 7.1. Do not upgrade from 6.x to IT Management Suite 7.1 if you want to keep the Mobile Management Solution features. Until Mobile Management Solution 7.1 is released, you must run a dual environment to use both IT Management Suite 7.1 and Mobile Management Solution.
Further information about Mobile Management Solution

For more information about new versions and upgrades, visit the support page for Mobile Management Solution.You can also contact the Symantec Business Sales team.
186
Migrating Mobile Management Solution Further information about Mobile Management Solution
Chapter
21
Migrating Wise Connector Solution

About migrating Wise Connector
About migrating Wise Connector

Wise Connector replaces Wise Integration Component that integrates Wise Package Studio with Altiris Notification Server. Wise Connector is not an upgrade of Wise Integration Component. Wise Connector is a new product that is designed for the new functionality in Symantec Management Platform 7.0 SP3 and later. Data migration does not apply to Wise Integration Component 6.x.You cannot migrate from Wise Integration Component 6.x to a latest version of Wise Connector. You must install and use a clean installation of Wise Connector. For more information, see Wise Connector User Guide.
188
Migrating Wise Connector Solution About migrating Wise Connector
Chapter
22
Migrating from Helpdesk Solution

About migrating from Helpdesk Solution 6.x
About migrating from Helpdesk Solution 6.x

Symantec ServiceDesk 7.1 replaces the functionality of Helpdesk Solution 6.5 and earlier. ServiceDesk does not upgrade or install over Helpdesk Solution because ServiceDesk is installed on a different server and uses different databases. During the migration process you upgrade Altiris 6.x to Symantec Management Platform 7.1 and install Symantec ServiceDesk 7.1. Helpdesk Solution data can be migrated with ServiceDesk application software. For more information, see ServiceDesk Implementation Guide.
190
Migrating from Helpdesk Solution About migrating from Helpdesk Solution 6.x
Chapter
23
Migrating Virtual Machine Management Solution

About migrating Virtual Machine Management data
About migrating Virtual Machine Management data

Virtual Machine Management does not exist as a separate component in any 6.x version. Deployment Solution 6.9 has a Virtual Machine Management function but it has been taken out of Deployment Solution in the 7.1 release. This function is therefore not migrated. Virtual Machine Management Solution replaces this functionality in 7.1.
192
Migrating Virtual Machine Management Solution About migrating Virtual Machine Management data
Chapter
24
Migrating IT Analytics Solution

About migrating IT Analytics data
About migrating IT Analytics data

IT Analytics Solution is a new component for IT Management Suite 7.1 and therefore cannot be migrated from an earlier version of ITMS. To upgrade IT Analytics Solution and the associated packs you use Symantec Installation Manager. For more information, see topics on installing the Symantec Management Platform products in the IT Management Suite Planning and Implementation Guide at the following URL: http://www.symantec.com/docs/doc4827.
194
Migrating IT Analytics Solution About migrating IT Analytics data
Index
Symbols
6.x data copying manually 61 exporting 57 importing 59
assign jobs and tasks predefined computer 132 unmanaged computer 132
B
Barcode Solution migrating 161 restore default synchronization profile 165 Barcode Solution migration about 161 backing up synchronization profile 165 migrating files 162 migrating settings 162 synchronizing data 163 verifying asset data 164 before you begin IT Management Suite licenses 148 best practices migrating 31
A
About Out-of-Band Management Component migration 151 Real-Time Console Infrastructure migration to 7.1 or later 143 Real-Time System Manager migration to 7.1 or later 139 about Inventory for Network Devices migration 99 Inventory Pack for Servers migration 179 Inventory Solution migration 69 migration from version 6.9 to 7.1 118 About manually migrating Real-Time Console Infrastructure files and settings 144 Real-Time System Manager files and settings 141 ADB file default location 62 agentless inventory migration. See Inventory for Network Devices Altiris Agent redirecting 40, 47 redirecting from Notification Server 6.x 155 upgrading 42, 47 architecture and functionality Deployment Solution 7.1 SP1 118 Asset Management Solution migrating 167 Asset Management Solution migration about 167 legacy software license items 169 special cases 168
C
carbon copy solution 6.x migration wizard 147 CMDB Solution migrating 159 CMDB Solution migration about 159 concepts architecture and functionality 118 context-sensitive help 17
D
data migration about 48 exporting data 57 filtering data 60 importing data 59 selecting data 60 solution-specific items 36 tools 48
196
Index
data migration (continued) viewing data store file 63 data store file about 62 comparing 65 default location 62 exporting data from 64 exporting to 57 importing from 59 viewing 63 Deployment Solution feature comparison 124 migration from version 6.9 to 7.1 118 Deployment Solution 6.9 agent uninstall 133 Deployment Solution 6.9 CSV file modifications 131 Deployment Solution 6.9 tasks recreate 128 Deployment Solution 7.1 SP1 advantages 122 install 133 documentation 17
E
existing hardware 27
F
feature comparison Deployment Solution 6.9 features with 7.1 SP1 124 Fine-tuning Out of Band Management Component after migration 156
H
help context-sensitive 17 How to validate Real-Time Console Infrastructure after the migration 145 Real-Time System Manager after the migration 141
I
install Deployment Solution 7.1 SP1 133
Intel AMT database Migrating 153 reconfiguring 154 Inventory for Network Devices migration 99 Inventory Pack for Servers migration 179 Inventory Solution about creating .INI files for custom inventory 80 about migration 70 automatic migration 70 automatically migrated items 71 backing up baseline configuration files 96 backing up custom inventory script files 78 copying baseline configuration files to the Notification Server 7.1 computer 96 copying custom inventory script files 78 creating a custom data class for a custom inventory script task 84 creating a custom inventory script task 85 creating a software resource for custom inventory script files 81 creating the Quick Delivery task for a custom inventory script file 83 custom inventory sample script for UNIX, Linux, and Mac 93 custom inventory sample script for Windows 90 customizing the custom inventory sample script for UNIX, Linux, and Mac 92 customizing the custom inventory sample script for Windows 88 items that are not automatically migrated 72 manual migration 7172 manual migration of baseline configuration files 94 manual migration of custom inventory script files 73 manually migrated items 72 migration with Symantec Notification Server Migration Wizard 70 pre-migration steps 69 prerequisites for creating a custom inventory software resource package 81 verifying the migration of baseline configuration files 97 IP address 32 IT Analytics migrating 193
Index
197
IT Management about 13 features 14 IT Management Suite supported migration paths 33
L
licenses migrating 48 limitations Deployment Solution 6.9 migration 134 linux support advantages 148
M
managed computers 47 Manually migrating Out of Band Management Component 152 Manually migrating Real-Time Console Infrastructure to version 7.1 or later 144 Migrating Intel AMT database 153 migrating about 24 Mobile Management Solution 185 Power Scheme 181 Recovery Solution 183 Virtual Machine Management 191 migrating Out of Band Management Component manually 152 migration agentless inventory. See Inventory for Network Devices best practices 29, 31 Deployment Solution 6.9 118 Inventory for Network devices 99 Inventory Pack for Servers 179 Inventory Solution 69 licenses 48 preparing 38 migration data about 48 comparing 65 exporting 57 filtering 60 importing 59
migration data (continued) selecting 60 viewing 63 migration from version 6.9 to 7.1 Deployment Solution 118 migration guide about 19 using 20 migration off-box 6.x to 7.1 33 migration paths supported 33 migration process 6.x to 7.1 33 migration to Deployment Solution 7.1 SP1 limitations 134 migration wizard about 50 EXE location 51, 58, 60 installation package 53 installing 53 overview 56 Mobile Management Solution migrating 185 modifications in CSV file use predefined computers in 7.1 SP1 131 Monitor Pack for Servers migrating 138 Monitor Pack for Servers migration about 138 Monitor Solution migrating 137 Monitor Solution migration about 137
N
Notification Server overview 16 Notification Server data migrating 56 Notification Server Database backing up 34, 37 NSUpgradeWizard.exe 51, 58, 60
O
Out of Band Management Component fine-tuning after migration 156
198
Index
Out-of-Band Management Component migration About 151
P
package servers upgrading 46 persistence settings determining 174 plug-ins removing 45 post migration configuration 26 validation 26 Power Scheme migrating 181 predefined computer assigning jobs and tasks 132 predefined computers modifications in CSV file 131 product parity IT Management Suite 22 project creating a version 176 project versions 176
recreation of tasks Deployment Solution 6.9 tasks 128 in Deployment Solution 7.1 SP1 128 Redirecting Altiris Agent from Notification Server 6.x 155 Release Notes 17
S
server name 32 Software Management Framework about 16 solutions IT Management Suite 14 Store Browser about 62 EXE location 63 StoreDiff utility 65 sub-agents removing 45 Symantec Management Agent redirecting 40 Symantec Management Platform about 16 components 16 Symantec Notification Server Migration Wizard about 50 installing 53 Symantec Workflow migrating 171
R
Real-Time Console Infrastructure after the migration How to validate 145 Real-Time Console Infrastructure files and settings About manually migrating 144 Real-Time Console Infrastructure migration to 7.1 or later About 143 Real-Time Console Infrastructure to version 7.1 or later Manually migrating 144 Real-Time System Manager after the migration How to validate 141 Real-Time System Manager files and settings About manually migrating 141 Real-Time System Manager migration to 7.1 or later About 139 recommended reading 21 Reconfiguring Intel AMT database 154 Recovery Solution migrating 183
T
tasks recreation in Deployment Solution 7.1 SP1 128 testing IT Management Suite 26
U
uninstall Deployment Solution 6.9 agent 133 unmanaged computer assigning jobs and tasks 132 upgrade best practices 29 upgrading 171 about 24
Index
199
V
version creating for a project 176 Virtual Machine Management migrating 191
W
Workflow 6.x upgrading 171

ITMS 6xmigration Guide

Uploaded by

Document Informationclick to expand document information

Copyright:

Available Formats

ITMS 6xmigration Guide

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ITMS 6xmigration Guide

Uploaded by

Copyright:

Available Formats

Altiris IT Management Suite from Symantec Migration Guide version 6.x to 7.

Altiris IT Management Suite from Symantec Migration Guide version 6x to 7.1SP2

Symantec Corporation 350 Ellis Street Mountain View, CA 94043 http://www.symantec.com

Contacting Technical Support

Product release level

Licensing and registration

Support agreement resources

Technical Support ............................................................................................... 4 Chapter 1 Introducing IT Management Suite ................................... 13

Overview of migrating to IT Management Suite ........... 19

Migrating Symantec Management Platform ................. 29

Migrating Inventory Solution ............................................ 69

Migrating Patch Management Solution ........................ 101

Migrating Software Delivery to Software Management Solution ................................................ 105

Migrating Deployment Solution ..................................... 117

131 132 133 133

Migrating Monitor Solution ............................................. 137

Migrating Real-Time System Manager Solution .......... 139

Migrating Real-Time Console Infrastructure ............... 143

Migrating Carbon Copy Solution .................................... 147

Migrating Out of Band Management Component ...................................................................

151 151 152 153 154 155 156

Migrating CMDB Solution ................................................ 159

Migrating Barcode Solution ............................................. 161

Migrating Asset Management Solution ........................ 167

Migrating Workflow Solution .......................................... 171

Chapter 17 Chapter 18 Chapter 19

Migrating Inventory Pack for Servers Solution ........... 179

Migrating Power Scheme Solution ................................. 181

Migrating Recovery Solution ........................................... 183

Migrating Mobile Management Solution ...................... 185

Chapter 21 Chapter 22 Chapter 23

Migrating Wise Connector Solution ............................... 187

Migrating from Helpdesk Solution ................................. 189

Migrating Virtual Machine Management Solution .........................................................................

About migrating Virtual Machine Management data ......................... 191

Migrating IT Analytics Solution ...................................... 193

Index ................................................................................................................... 195

Introducing IT Management Suite

About IT Management Suite

Introducing IT Management Suite What's new in IT Management Suite

What's new in IT Management Suite

See About IT Management Suite on page 13.

Solutions of IT Management Suite

Introducing IT Management Suite Solutions of IT Management Suite

Table 1-1 Suite/Platform

IT Management Suite 7.1 solutions and components

Symantec Workflow 7.1 IT Analytics 7.1

Asset Management Suite 7.1 Asset Management Solution 7.1

Barcode Solution 7.1 CMDB Solution 7.1

Introducing IT Management Suite Components of the Symantec Management Platform

See About IT Management Suite on page 13.

Components of the Symantec Management Platform

Introducing IT Management Suite Where to get more information

Where to get more information

Documentation resources Location

The F1 key when the page is active.

Introducing IT Management Suite Where to get more information

Table 1-3 Resource