background image

 

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 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.  

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  

Summary of Contents for ALTIRIS IT MANAGEMENT SUITE 7.0 MR1 - S V1.0

Page 1: ...ated 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 comp...

Page 2: ...te 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 Sym...

Page 3: ...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 t...

Page 4: ...alled 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...

Page 5: ... 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 i...

Page 6: ...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 replace...

Page 7: ...sues 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 1...

Page 8: ...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 ...

Page 9: ... 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...

Page 10: ...f 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 incid...

Page 11: ...ier 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 ca...

Page 12: ...anagement 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 ...

Page 13: ...ware 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 201676...

Reviews: