Altiris™ Credential Manager, Connection Profiles and Pluggable Protocols Architecture 7.0 SP2 from Symantec Release Notes

Article:DOC1775  |  Created: 2009-03-10  |  Updated: 2009-03-10  |  Article URL
Article Type


PPA build number 7.0.6453

Credential Manager build number 7.0.2617

Connection Profiles and the Pluggable Protocols Architecture store the information that is required to communicate with computers and other network devices using standard network monitoring protocols. The Pluggable Protocols Architecture unifies the configuration of protocols across the Symantec Management Platform. Connection Profiles is a feature of the Symantec Management Platform that is leveraged by other solutions and components in the Symantec Management Platform. It provides the ability to update and add protocols without requiring a wholesale upgrade of all dependent solutions. These protocols can include SNMP, WMI, WSMAN, as well as several others.

Credential Manager provides a secure storage location for user names and passwords. The types of credentials that are stored are defined by the installed management solutions. Access to credentials is controlled using the built-in role-based security of the Symantec Management Platform. When a credential is created, only the creator is granted access. If other users need to perform management operations requiring a credential, they must be assigned rights.

This component is part of the Symantec Management Platform 7.0 SP2. For release notes, see knowledgebase article 46035.

This document contains the following topics:

Back to top

Fixed Issues in this Release

The following are previous issues that were fixed in this release. If additional information about an issue is available, click the Article ID link.

Issue Article ID Internal ID
Unable to create \ edit credentials profiles while editing the "Connection Profile"

Deleting Alert from "Alert category page" reflects the changes on that page but it does not delete that alert from Alert tree

AMT: When "Secure mode" is checked, doesn't give an error if user does not enter values for dependent enabled fields(On state)

PPA 7.0.6099: unable to connect to CM on NS with custom site, port, and HTTPS

PPA: Exception in WSMAN plug-in prevents establishment of WMI Session

Kerberos user with long name AMT connection problem in RTSM

Sample EC Credential requires Administrator in permissions list

AMT plug-in should generate NS message when CIRA session is opened or closed

Suggestion to add information about the current AMT "Power Saving" mode to AMT information pages

Alerts under Alert Mangement Settings cause Unknown Error

We should not cause the SIM install to crash if there is a problem with the CM install

A support for AMT 5.1 should be added to plug-in

Cannot add Alert to Category

SNMP retry count does not work

CIRA connection cannot be established when DNS record for resource removed

All traps sent to NSConsole is "Unrecognized Alert"

Alert count in Alert details mismatch from Alerts count in Event Console

Event Console uninstallation through cmd does not remove EC references from menu tab


Back to top

Known Issues in this Release

The following are known issues for this release. If additional information about an issue is available, click the Article ID link.

Issue Article ID Internal ID
Credential Manager    
Credential selector drop-down does not show newly added Credentials (using the Add button) on Connection Profile page

48032 1298
Steps to enable server certificate authentication in Credential Manager

To enable server certificate authentication in Credential Manager, you need to create the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Altiris\CredentialManager\SSL. Then add the value VerifyServerCertificate (DWORD) and set it to 1. By default, or in the absence of the above mentioned key, Credential Manager will work without server certificate authentication.

Pluggable Protocols Architecture    
MIB Import links are not shown clearly

MIB Import does not check for valid files

47953 1241
MIB Import confirmation dialog does not appear

47954 1242
MIB Import does not check for existing MIB

47955 1245
Retry and Timeout values may not be used during connection

Each protocol allows you to specify its own timeout and retry value. However, these values are typically only used during the execution of commands by the protocols, but not when attempting to connect to a target computer using these protocols. If a solution only attempts to connect to targets to determine availability, but does not execute any commands over the protocols used to connect, it should not be expected by the user that failed connection attempts would be retried, unless such attempts are controlled at the solution level.


Back to top

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices