User manual SYMANTEC ALTIRIS IT MANAGEMENT SUITE 7.0 MR1 RELEASE NOTES V1.0

[. . . ] 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. [. . . ] Table 1-6 Things to know 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 Things to know in Inventory Solution Internal ID 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. In the left pane, click Agents/Plug-ins > Discovery and Inventory > Windows. 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. Starting with Step 2, repeat for the UNIX/Linux/Mac Inventory plug-in. 1712682 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. The following are the issues that were fixed in the MR1 of Inventory Solution 7. 0 SP2. Table 1-7 Issue The count of the not reporting computers on the How current is my computer Inventory?Some filter parameters that are present on the Add or Remove Programs Search report page are not used in the report SQL query. The restricted user does not have read permissions in security scoping environment. In the Computer Name field a new drop-down has been introduced that lets you narrow down your search. 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. Devices Inventoried By Type Web part only displays the devices that were discovered within last 30 days. The inventory policy that is specified to scan one single file, does not report information about this file, although it exists on the computer. When the Inventory runs, the InvProvider. dll causes the Altiris Agent to stop 1972344 1972759 1982646 Fixed issues in Inventory Solution Internal ID 2013677 1929752 1938978 1961602 responding. Inventory policy data class selections are not saved when you use Internet Explorer 8 in Native Mode. Custom data class selections are removed when a custom schedule is added or edited on the Collect Delta Hardware Inventory policy. [. . . ] Table 1-14 Issue On the Subtasks page, the text Return Incident On Completion at the option is unclear. On the Advanced Incident form, the submitter of the incident is set as the Primary Contact for the ticket. When an incident is created from an incoming email and the sender is not a ServiceDesk user, the incident's contact is set to guest@logicbase. com. However, because this guest user is not added as the primary contact, the support technician must add a primary contact to the incident. [. . . ]