Symantec ALTIRIS IT MANAGEMENT SUITE 7.0 MR2 - RELEASE NOTES Release Note

Altiris™ IT Management Suite

7.0 MR2 Release Notes

Altiris™ IT Management Suite 7.0 MR2 Release Notes

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.

Documentation version: 7.0 MR2.1

Legal Notice

Copyright © 2010 Symantec Corporation. All rights reserved.

Symantec and the Symantec Logo are trademarks or registered trademarks of Symantec
Corporation or its affiliates in theU.S.andother 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
Support’s 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 workswith Product Engineering
and Symantec Security Response to provide alerting services and virus definition
updates.

Symantec’s 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 Symantec’s 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, incase it is necessary toreplicate
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 ourtechnical
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 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:

[e-mail]-Pacific and Japan

[e-mail], Middle-East, and Africa

[e-mail] America and Latin America

IT Management Suite 7.0
MR2 Release Notes

This document includes the following topics:

■ Introduction

■ Installation and Upgrade

■ Fixed Issues in this Release

Introduction

IT Management Suite from Symantec is the industry’s most comprehensive and
integrated suite for reducing the cost and complexity of owning and managing
corporate IT assets including desktops, laptops, thin clients, servers, and
heterogeneous platforms including Windows, UNIX, Linux, and Mac to promote
effective service delivery.

IT Management Suite is a collection of solutions and components that run on the
Symantec Management Platform.

For more information about the solutions and components, see theIT Management
Suite 7.0 Release Notes (knowledge base article 51492).

Installation and Upgrade

New Installation

You can install this product by using the Symantec Installation Manager. If you
do a new install of ITMS or any of the components, the MR2 version is installed.

For more information, see Installing the Symantec Management Platform products
(knowledge base article 45732).

Upgrade

You can upgrade this product from ITMS 7.0 by using the Symantec Installation
Manager.

In the Symantec Installation Manager, on the Product Updates page, you see the
available MRs for all of the components of ITMS. Installing MRs is optional. You
can choose to install one or more MRs. If you select the ITMS product, all
component MRs are installed.

Note, that upgrading from ITMS 6.x to ITMS 7.0 MR2 is not supported.

Upgrading the Symantec Management Agent on managed computers

After installing MR2, you must make sure that all managed computers have the
latest version of the Symantec Management Agent.You do this by enabling the
policy to upgrade the Symantec Management Agent.

To upgrade the Symantec Management Agent on managed computers

1

In the Symantec Management Console, do one of the following:

■ On the Actions menu, click Agents/Plug-ins > Rollout Agents/Plug-ins.

■ On the Settings menu, click All Settings. In the left pane, click

Agents/Plug-ins.

2

In the left pane, click Altiris Agent.

3

Click Windows.

4

Click the Altiris Agent for Windows - Upgrade policy.

5

On the plug-in upgrade page, turn on the policy.

At the upper right of the page, click the colored circle, and then click On.

6

Click Save changes.

7

Repeat for the UNIX/Linux/Mac agent.

Fixed Issues in this Release

The following chapters list the new features of this release, things to know about
in this release, and previous issues that were fixed in this release.

IT Management Suite 7.0 MR2 Release Notes

Fixed Issues in this Release

8

Asset Management Solution

Build number 7.0.1359

The following are the issues that were fixed in the MR2 of Asset Management
Solution.

Table 1-1

Fixed issues in Asset Management Solution

Internal IDIssue

2015801Software Licenses list does not display a software product if the end

date of its license is in the past.

2035968Companies that have no name, are displayed as a slim line in the

companies report.

2054047When you try to add an existing line item from a purchase order that
has more than 20 line items, you get an error message “The Data could
not be loaded”.

1949840The Resource Link that is created for a Resource Type remains after
deleting the Resource Type, but clicking it gives errors.

1961763Some legacy software licensing reports fail to run.

2093031Edited Asset Status of a resource is not saved.

2076683When a computer is created manually and has the ownership set, and
then a computer checks in with basic inventory and full inventory,
and then both of these computers are merged, the Asset User Owner
association is lost when the clean ownership task is ran after the
merge.

2077152Ownership details dataclass is not updated correctly if the owners
(users) with same name are merged.

Deployment Solution

Build number 7.1.629

The following are the issues that were fixed in the MR2 of Deployment Solution.

Table 1-2

Fixed issues in Deployment Solution

Internal IDIssue

1833046When a Preboot Configurations policy is cloned, the name for the
clone is not properly displayed.

9IT Management Suite 7.0 MR2 Release Notes

Fixed Issues in this Release

Table 1-2

Fixed issues in Deployment Solution (continued)

Internal IDIssue

1885110Deployment Task Handler install policy does not check whether the
Site Servers have both Package Server Service and Task Server Service
installed.

1905379In the Sysprep Imaging Configuration dialog box, the text for the
item Modified is clipped.

1914466When selecting Sysprep Configuration files, localized text is not
displayed--it is English only.

1951071PECTAgent.ini refers to an incorrect port, which prevents image
creation.

1954244, 2046881PrebootConfigurations page and PXE Server Configuration page do
not have context sensitive help.

1967333In the Import OS Files dialog box, the Add Files option does not work
in German and in Italian.

2017328When the system restarts after the Prepare for Image capture task
has run, the time zone information dialog box appears and stops
responding.

2025056, 2080920PECTAgent fails to load.

2027332The Applied to filter of the Deployment Site Server Components -
Install policy targets any Site Server without Site Server Components
installed.

2027390When in a hierarchy, the Preboot Configuration policy page did not
store targets correctly.

2029214When Hierarchy is enabled, the PXE Preboot Configurations policy is
incorrectly replicated down-stream and can break down-stream
policies.

2036756Query for NSSERVERNAME token is incorrect.

2039921A Copy File task with the execute command that is scheduled to run
on a client computer, copies the file successfully but fails to execute.

2046881Some pages were not displaying online help when pressing F1.

2047965After running the Install Windows OS task with inventory data for
Win 2003 operating system, the client computer starts successfully
but fails to join the domain.

IT Management Suite 7.0 MR2 Release Notes

Fixed Issues in this Release

10

Table 1-2

Fixed issues in Deployment Solution (continued)

Internal IDIssue

2050017, 2062096Recreate Preboot Environment fails to call BootWiz.exe, after the

language package is applied to Deployment Solution.

2050930SbsNsSignal.ini file is blank or contains invalid data.

2055098Nic MAC Address token definition has incorrectly delimited SQL.

2056006When running a Prepare for Image Capture task, an error occurs:

Windows could not parse or process unattend answer file.

2059435On the Sysprep Imaging Configuration page, the details for the

Deploy.cab file are not properly displayed in Spanish.

2065709An error occurs if an image of a computer is uploaded twice to the

same Site Server.

2068395, 2069314Incorrect strings on the user interface.

2069397The DeployImage task that is set to use the Ghost Image and assigned

to more than one computer fails to run.

2074783The text for the link to upload the Deploy.cab file on the Prepare

for Image capture task page should be reworded.

2077308On the Deployment Portal page, menu texts contain localization

codes.

2087147When running a Capture Personality task on a client computer, “PC
Transplant evaluation license has expired” message is displayed and
the task fails.

2088934Computerswith Deployment Plug-in Installed report does not return
any results unless run as App Identity user.

2097144Installation of the Deployment Task Server Handler fails with return
code 1603 and further installation of Deployment Solution cannot
proceed.

2103640Task pages not localized for Portuguese.

2107463Deployment Agent plug-in sends multiple .NSE files to server during
a Basic Inventory post.

2111928Predefined computers don't match because the pectagent is not
returning the correct serial number thus preventing initial
deployments from working.

11IT Management Suite 7.0 MR2 Release Notes

Fixed Issues in this Release

Inventory Solution

Build number 7.0.1278

The following are the issues that were fixed in the MR2 of Inventory Solution 7.0
SP2.

Table 1-3

Fixed issues in Inventory Solution

Internal IDIssue

1926534Faulting application AeXNSAgent.exe, version 7.0.0.3599, faulting

module AMAgent.dll, version 7.0.1104.0, fault address 0x0004927b.

2027164Server inventory policy causes memory leak in AeXNSAgent.exe

when it collects the exchange user data class on exchange servers.

2062721It is not possible to include or exclude the X drive in an inventory

policy.

1882642Application Metering data is not collected for the applications that

have ‘[’ or ‘]’ characters in their version information.

2049562For some applications duplicate entries appear in

inv_installed_file_details data class.

1920379The ‘Email Notification’ sent by an application metering policy did

not contain client computer detail..

1946787 1890612
1926534

Application Metering conflicts with some 3rd Party Applications ­Applications Fail to Load

Patch Management Solution

Build number 7.0.4310

The following are the issues that were fixed in the MR2 of Patch Management
Solution 7.0 SP2.

Table 1-4

Fixed issues in Patch Management Solution

Internal IDIssue

1946790Arithmetical error occurs when running Patch Management for

Windows compliance reports

1971281Selecting software updates from a custom organizational view is

showing all updates not the ones in the view.

IT Management Suite 7.0 MR2 Release Notes

Fixed Issues in this Release

12

Table 1-4

Fixed issues in Patch Management Solution (continued)

Internal IDIssue

1994769The computers that have Software Update Plug-in upgraded are still
included in the All Windows Computers Requiring Software Update
Plug-in Upgrade filter.

2003221Patch Compliance reports do not display any data.

2004594In the Patch Remediation Center, if you right click and select 'View
Policies' or 'View Targeted Computers' , the secondary window opens
and shows 'No Results Returned'.

2029359Arithmetical error occurs when running the “Compliance by Bulletin”
report.

2068795Windows Compliance by Update: a sw update is showing 200%
compliant.

Software Management Solution

Build number 7.0.1866

The following are the issues that were fixed in the MR2 of Software Management
Solution 7.0 SP2.

Table 1-5

Fixed issues in Software Management Solution

Internal IDIssue

1735677Child package does not inherit the global settings that are defined in
the Managed Delivery Settings.

1853031A User does not have approved Software in the Software Portal if he
belongs to a child or separate trusted Domain Group.

1949829If more than 10 Software resources are added to a Managed Software
Delivery policy, it is not possible to remove the software resources
from this Managed Software Delivery policy.

1950767A Managed Software Delivery policy that is created with the wizard
does not install the software update.

1990125When you create a Quick Delivery task and edit its advanced settings,
the changes for Task can run option are not saved.

20088144Dependent Tasks in a Managed Software Delivery Policy do not inherit
the global settings that are defined in the Managed Delivery Settings.

13IT Management Suite 7.0 MR2 Release Notes

Fixed Issues in this Release

Table 1-5

Fixed issues in Software Management Solution (continued)

Internal IDIssue

2047231Using ‘{’ or ‘}’ characters in the download settings of a Software
Delivery task or policy, in the Location on destination computerbox,
gives an error message.

2051924Software Compliance Summary report times out on EOOC.

2052649The specified option Symantec Management Agent cache under

Destination download location is not saved for a ManagedSoftware
Delivery policy if in the global Managed Delivery Settings an

alternate download location is defined.

2054340Endless loop with spSWP_GetAllUserManagers results in the users
inability to edit software requests in the Manager Portal.

2055059Software Compliance Status report takes over 3 minutes to load on
EOOC.

2079738An error message on the Software Portal Plug-in Policy page is
displayed in information format.

IT Management Suite 7.0 MR2 Release Notes

Fixed Issues in this Release

14