Symantec ALTIRIS IT MANAGEMENT SUITE 7.0 MR1 - S V1.0 Owner's manual

IT Management Suite 7.0 MR1
Release Notes
This document contains the following topics:
Introduction
Installation and Upgrade
New Features, Things to Know, and 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 the IT 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 MR1 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 version if you run the Symantec Installation Manager.
In the Symantec Installation Manager, on the Product Updates page, you see all available MRs for all the
components of IT Management Suite. 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 MR1 is not supported.
Upgrading the Symantec Management Agent
on managed computers
After installing MR1, 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.

New Features, Things to Know, and
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:
Asset Management Solution
Barcode Solution
Deployment Solution
Inventory Solution
Out-of-Band Management Component
Patch Management Solution
Power Scheme Task component
Real-Time System Manager
ServiceDesk
Software Management Solution
Asset Management Solution
Build number 7.0.1343
The following are the issues that were fixed in the MR1 of Asset Management Solution.
Table 1-1 Fixed issues in Asset Management Solution
Issue
Internal ID
When you add a new schedule for the Assets that have attached devices with
different owners task, on the New Schedule dialog box, the string Data is not
localized.
1931617
The bulk editing of the Covered Hardware is missing on the Lease Schedule page.
1955473
In the Symantec Management Console, in the Manage menu, the Asset Manager
cannot see the Software menu item.
1960563
Legacy Software License reports are broken.
1961763
It is possible to save User or Cost Center without filling out required fields.
1970128
The compliance report does not reflect that a software has been uninstalled.
1970395
Errors with the migrated foreign key attributes of a custom data class.
1971304
Update Network Resource Location does not update the
1990854

ResourceAssociationHistoryDelta table and Inv_Audit table.
The Asset Summary print page does not display the data properly.
2008551
Adding associated assets to a configuration item, causes high memory usage
(memory leak) with a large count of resources.
2021871
On the Software Licensing page, on the Legacy Licenses Requiring Migration
Web part, the Software Catalog Data Provider link needs to be removed.
2051531
Barcode Solution
Build number 7.0.1080
The following are things to know about in this release.
Table 1-2 Things to know in Barcode Solution
Things to know
Internal ID
If you want to install MR1 on a computer that has Barcode 7.0 or SP1 installed, you
need to back up the default profile before you install MR1. This is needed because
MR1 overwrites the default profile during installation.
To back up the default profile:
1. In the Symantec Management Console, on the Home menu, click Service
and Asset Management > Barcode.
2. In the left pane, under Barcode Solution, expand the Synchronization
Profiles folder.
3. Right-click Default and click Export.
4. Specify the location on your computer and click Save.
To restore (import) the default profile after installation:
1. In the Symantec Management Console, on the Home menu, click Service
and Asset Management > Barcode.
2. In the left pane, under Barcode Solution, right-click Synchronization
Profiles and click Import.
3. Select the file and click Open.
Successful tests are performed to confirm that Socket CHS Series 7 (CHS 7M2)
works with the Handheld Application.

The following are the issues that were fixed in the MR1 of Barcode Solution.
Table 1-3 Fixed issues in Barcode Solution
Issue
Internal ID
In the Symantec Management Console, the expiry notifications are not displayed
to the user upon the license Expiration. User has to look into the Altiris Log on an
operation failure and discover that the license has expired.
2025860
On the License View page, in the Device Licenses list, the reclaimed licenses are
still shown with the status 'Reclaim Pending'.
2025860
Delete functionality on Device licenses does not release the licenses in real time.
You have to wait for a few minutes before the licenses are reclaimed.
2025860
License Usage does not show total license count and number of the licenses that
are in use.
2025860
Deployment Solution
Build number 7.1.607
The following are things to know about in this release.
Table 1-4 Things to know in Deployment Solution
Things to know
Internal ID
During initial install of Deployment Solution 7.1 the PXE services are installed but
not started. After the install, it is up to the administrator to go into services, start
the service, and change its properties from “Manual” to “Automatic” every time
the computer reboots. However, after you upgrade to MR1, that service is
stopped and its property is set back to “Manual”, which means that all customers
with existing Deployment Solution 7.1 PXE environments that are started need to
go back into services and set the PXE service to “Automatic”.
Warning messages appear in the Log Viewer, while performing an upgrade from
Deployment Solution 7.1.598 to Deployment Solution 7.1.603. However, the
upgrade is completed successfully.
2048065
The following are the issues that were fixed in the MR1 of Deployment Solution.
Table 1-5 Fixed issues in Deployment Solution
Issue
Internal ID
On the create new Deploy Image task page, the Browse button of the Sysprep
Configuration option opens NSCap folder instead of Deployment folder.
1677907

In the advanced options dialog box of the Deploy Image task, on the File
Preservation tab, the Add button does not work.
1873031
On the Sysprep Imaging Configuration page, when you upload a Deploy.cab file,
the hard-coded string Copying data... is displayed.
1906175
The Capture Personality dialog box that is opened from the Actions menu, does
not allow user to edit the Select template field.
1907151
In the Add OS License Key dialog box that is opened from the create new Prepare
for Image capture task page, the texts in the Operating System drop-down list
are truncated.
1913822
On the Sysprep Imaging Configuration page, the Modified text is truncated.
1917078
On the Sysprep Imaging Configuration page, when you upload a Deploy.cab file,
the string Copying data... is not displayed.
1920425
After you run Deploy Image task using rdeploy on the Windows 7 Ultimate (32
Bit: without reserved partition) computer, the computer fails to join domain.
1945582
Windows Vista Scripted OS Install task uses “altiris” as the default password,
Scripted OS Install task of all other Windows versions uses “password” as the
default password.
1954197
The Preboot Configuration policy page lists Solaris pre-boot as Linux.
1991513
When the Deployment Portal page is opened remotely (not on Notification
Server ), then in some cases it fails to load.
1993672
The tokens that are normally used in an answer file are not replaced with the
data from the database during imaging.
1997061
The Deployment Portal page does not show any data in the Computers window.
2000272
Inventory Solution
Build number 7.0.1255
The following are things to know about in this release.
Table 1-6 Things to know in Inventory Solution
Things to know
Internal ID
After installing Inventory Solution, you must upgrade the Inventory plug-in on all
managed computers.
For the upgraded Inventory plug-in to work properly, you must have the
Symantec Management Agent, version 7436 installed on managed computers.
Version 7436 of the Symantec Management Agent is available from Symantec
Management Platform 7.0 SP4 Hotfix1, which was automatically installed with
Inventory Solution MR1 if it was not previously installed. After installing the SMP

Hotfix1, you must upgrade the Symantec Management Agent on managed
computers.
See Upgrading the Symantec Management Agent on managed computers
To upgrade the Inventory plug-in on managed computers, do the following
1. In the Symantec Management Console, on the Settings menu, click All
Settings.
2. In the left pane, click Agents/Plug-ins > Discovery and Inventory > Windows.
3. Click the Inventory Plug-in for Windows Upgrade policy
4. 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.
5. Click Save changes.
6. Starting with Step 2, repeat for the UNIX/Linux/Mac Inventory plug-in.
The schedule for ‘Weekly Software Catalog Inventory’ that runs by default every
Wednesday at 2:40 A.M. on the Software Catalog Data Provider Inventory page
does no longer run by default as its entry is removed from the Windows Task
Scheduler. To run the Software Catalog Data Provider Inventory task, you must
create a new schedule.
1712682
The following are the issues that were fixed in the MR1 of Inventory Solution 7.0 SP2.
Table 1-7 Fixed issues in Inventory Solution
Issue
Internal ID
The count of the not reporting computers on the How current is my computer
Inventory? Web part is different from the count on the drill-down .
2013677
Some filter parameters that are present on the Add or Remove Programs Search
report page are not used in the report SQL query.
1929752
The restricted user does not have read permissions in security scoping
environment.
1938978
Audit Software Search report times out on a larger database.
In the Computer Name field a new drop-down has been introduced that lets you
narrow down your search. The option "--Any--" is no longer defaulted. However,
if you select the option "--Any--" in the Computer Name drop-down list and
"%.exe" as a file name, then the possibility of timing out still exists.
1961602
Devices Inventoried By Type Web part only displays the devices that were
discovered within last 30 days.
1972344
The inventory policy that is specified to scan one single file, does not report
information about this file, although it exists on the computer.
1972759
When the Inventory runs, the InvProvider.dll causes the Altiris Agent to stop
1982646

responding. for more information, see the knowledge base article 52072.
Inventory policy data class selections are not saved when you use Internet
Explorer 8 in Native Mode.
1989408
Custom data class selections are removed when a custom schedule is added or
edited on the Collect Delta Hardware Inventory policy.
1990956
When the Application Metering plug-in is installed on a client computer using the
'out-of-the-box' installation task, and then the same installation task runs again
on that client computer, the AMAgent.dll becomes unregistered.
1993505
It is possible to edit only first 16 attributes of the Custom data class .
2008718
Out-of-Band Management Component
Build number 7.0.1541
The new features of this release are as follows:
Out-of-Band Management Component installs Intel SCS 5.3
Intel SCS 5.3 resolves issues with wireless Intel AMT 6.0 computers.
The following are things to know about in this release.
Table 1-8 Things to know in Out-of-Band Management Component
Things to know
Internal ID
Out-of-Band Management Component MR1 includes an update for OOB Site
Service. To upgrade OOB Site Service, you must enable Out of Band Site Service
Agent - Upgrade policy.
The following are the issues that were fixed in the MR1 of Out-of-Band Management Component 7.0
SP3.
Table 1-9 Fixed issues in Out-of-Band Management Component
Issue
Internal ID
"Unable to lookup the name of the account associated with the specified SID"
error is displayed after the upgrade.
Cannot assign wireless profile and update power policy to Intel AMT 6.0 notebook
computers.
Errors in log when configuring Intel AMT 6.0 notebook computers.

Patch Management Solution
Build number 7.0.4219
The following are things to know about in this release.
Table 1-10 Things to know in Patch Management Solution
Things to know
Internal ID
Patch Management for Windows updated plug-in version to 7.0.4210. To update
the plug-in, enable the Software Update plug-in Upgrade policy in the Symantec
Management Console.
The following are the issues that were fixed in the MR1 of Patch Management Solution 7.0 SP2.
Table 1-11 Fixed issues in Patch Management Solution
Issue
Internal ID
The new versions of pmimport.cab file are not downloaded when Only download
if modified check box is checked. For more information, see the knowledge base
article 51625.
1968542
Downloading Red Hat errata fails if proxy is used.
1975814
Processor load on the SQL server is 100% when Policy Refresh is in progress with
260+ enabled policies.
1985801
The Patch Management Import task fails to load the PMImport file.
1989163
Upgrading to Patch Management Solution 7.0 SP2 causes custom targets in the
Software Update policies to revert to the default Resource Target without
disabling the policy.
1992267
Not all the policies that are replicated from a parent Notification Server to its
children, reach child Notification Server. Moreover, the policies that reach child
Notification Server cannot be distributed to its client computers.
2061388
Power Scheme Task component
Build number 7.0.1302
The following are the issues that were fixed in the MR1 of Power Scheme Task component.
Table 1-12 Fixed issues in Power Scheme Task component
Issue
Internal ID
The Power Scheme Settings report shows the computer as out of compliance only
2011040

if it has all the report settings out of compliance. When only one report setting is
out of compliance, the computer is not reported.
The Power Scheme Settings report shows incorrectly all the current power
settings in case at least one report setting is set to Any.
2011040
Performance issues while running reports.
Real-Time System Manager
Build number 7.0.1820
The new features of this release are as follows:
Support for the Intel AMT 6.0 KVM feature
Keyboard, Video and Mouse (KVM) capability enables remote control of an Intel AMT system
using a remote keyboard and mouse and viewing the managed system’s screen output at a
remote monitor. You can use the Remote Control page in the Real-Time view to start a remote
control session.
The following are the issues that were fixed in the MR1 of Real-Time System Manager 7.0 SP2.
Table 1-13 Fixed issues in Real-Time System Manager
Issue
Internal ID
Sometimes applying event filters on Broadcom DASH client can fail.
ServiceDesk
Build number 7.0.1360
The new features of this release are as follows:
Incident close codes are stored as editable application properties.
ServiceDesk contains a set of predefined close codes that are used when an incident is resolved.
Previously, application close codes were stored in the SD.IncidentManagementProcess project.
Now they are stored as application properties, which you can edit more easily.
Incidents that were postponed can be reopened before the postponement date.
When you postpone an incident by scheduling it for a later date, it is placed on hold and cannot
be worked until the postponement date arrives. A new action on the incident's Process View
page lets you reopen a postponed incident before that date. The Remove From Hold option
appears only on the incidents that have been postponed.

ServiceDesk permissions can be copied from one group to another group.
The ability to copy permissions between existing groups is useful when you import an Active
Directory group that is not mapped to a ServiceDesk group. In that case, the imported group is
created without any permissions and you must assign the permissions yourself. Copying the
permissions from another group eliminates the need to assign the permissions manually.
Additional information is included in the incidents that are migrated from Helpdesk Solution
6.x.
When you migrate incidents from Helpdesk Solution 6.x, the following data is now also
imported: ticket number, full history, and contacts.
Changes have been made to the advanced incident form.
The advanced incident form has been changed to provide simpler user selection and additional
user information.
The incident category lists are sorted alphabetically.
On the Create Incident page (advanced), the Incident Response page, and at the Reclassify
action, the drop-down lists for the incident type (category) and classifications are sorted
alphabetically for easier scanning of the entries.
It is possible to select specific Organization Units to import during the initial Active Directory
synchronization.
The following are the issues that were fixed in ServiceDesk.
Table 1-14 Fixed issues in ServiceDesk
Issue
Internal ID
On the Subtasks page, the text Return Incident On Completion at the option is
unclear.
1859545
Blacklisting the sender of an incident email causes errors.
1859551
On the Advanced Incident form, the submitter of the incident is set as the
Primary Contact for the ticket.
1951092
When an incident is created from an incoming email and the sender is not a
ServiceDesk user, the incident’s contact is set to [email protected]om. However,
because this guest user is not added as the primary contact, the support
technician must add a primary contact to the incident.
1949845
When ServiceDesk starts the pcAnywhere remote control window, the
pcAnywhere console buttons do not work.
1960615
Equipment Search from pcAnywhere smart task does not return correct results.
2025965
Know Issues in the Incident Management. For more information, see the
knowledge base article 51634.
An email notification is not sent out to the customer when a ticket is created
using Advanced Form. For more information, see the knowledge base article
51606.
1976168

End-users can see the comments that are marked as private.
Licensing is not properly measured based on user's IP address.
"Remote control via NS" in the Manage Equipment action does not work
properly.
Software Management Solution
Build number 7.0.1831
The following are things to know about in this release.
Table 1-15 Things to know in Software Management Solution
Things to know
Internal ID
To install Software Virtualization Workspace Agent 6.1 on a Windows 2000
computer the following updates are required:
Update Rollup Pack 1 (available from Microsoft).
Copy msvcp60.dll to system32 folder (the file can be found in the XP SP3,
dated 4/13/2008 5:12 P.M.; 404 KB).
Software Management Solution Agent for Windows is updated to version
7.0.1831. To update the plug-in, enable the Software Management Solution
Agent for Windows - Upgrade policy in the Symantec Management Console.
The following are the issues that were fixed in the MR1 of Software Management Solution 7.0 SP2.
Table 1-16 Fixed issues in Software Management Solution
Issue
Internal ID
Old version of Software Virtualization Agent is shipped in Software Management
Solution 7.0 SP2.
1872523
Software Compliance reports don't show any results for items greater than seven
days.
1937220
On the Managed Delivery Settings page, on the Run tab, it is not possible to
select the option Allow user to interact with installing software when the option
Task can run is set to Whether or not the user is logged on.
Note, that to make this fix function properly, you must upgrade the Symantec
Management Agent to the version 7.0 SP4 HF1.
1947177
Software Virtualization Agent 2.1 is not compatible with Windows 7 and Windows
2008 R2.
1967335
When you click on the Software Management Solution Agent installation policy,
1974801

the following error message is displayed: "No package could be found for the
selected Agent installation policy".
Changing or saving a Managed Software Delivery policy that is saved in a
subfolder under the Managed Software Delivery folder moves the policy back to
the root folder.
1998692
The check box for a dependency in a Managed Software Delivery policy does not
save properly if the box is unchecked.
2010118
On the Managed Delivery Settings page, on the Run tab, the value 1 hour for the
option Allow user to defer action up to is not correctly saved.
2012066
On the Managed Delivery Settings page, on the Run tab, the time measure units
drop-down list for the option Terminate after is not grayed out when the value 0
is selected.
2016764
On the Managed Delivery Settings page, on the Run tab, the value 25 hours for
the option Terminate after is not correctly saved.
2016774