Altiris™ Connection Profiles and Pluggable Protocols Architecture 7.0 SP1 from Symantec Release Notes

Article:DOC1743  |  Created: 2009-01-23  |  Updated: 2009-01-23  |  Article URL
Article Type


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. 

Fixes in this release of Connection Profiles and the Pluggable Protocols Architecture

The following issues are fixed in this release:

Fixed Issue Article ID Internal ID
The check boxes in the "Access permissions to protocols settings" window are supposed to be radio buttons
Manage Connection Profiles page toolbar symbols are not greyed-out when they are disabled by user permissions

Known Issues in this release of Connection Profiles and the Pluggable Protocols Architecture

The following are unresolved issues in this release.

Known Issue Article ID Internal ID
If the same resource is discovered by two different discoveries with two different Connection Profiles, then the resource is associated with the Connection Profile that is run last 

If a resource is applicable to two different Connection Profile discovery ranges and both discoveries are run, then the data that is stored that associates a protocol with the resource switches between both Connection Profiles.

The protocol of the discovery that is run last is the protocol that is associated with the resource in the Connection Profile data store. Because the resource is discovered with separate Connection Profiles, both protocols are not associated with the resource as might be expected.

For example:

In the event that a device supports both SNMP and WMI, if you first run a Network Discovery task with the SNMP Connection Profile enabled, any solutions that utilize PPA to query this device (for example agentless Inventory or the Event Console) would be successful in communicating with this resource using the SNMP protocol.
However, if  you or someone else then runs a Network Discovery task against this same resource with the WMI Connection Profile enabled, then the data store on the resource gets updated, and the device will only respond to PPA using WMI.  At this point, solutions attempting to communicate with this resource using PPA will fail when using the SNMP protocol, even though SNMP is still a valid protocol on that device.  SNMP is no longer a valid protocol in the PPA data store.

To avoid problems that could result from this behavior, we recommend that you make sure that all of the possible protocols that could work on a given resource are contained within a single Connection Profile, as opposed to splitting up the different protocols between multiple Connection Profiles and multiple discoveries. 

You must use the Credentials Management page to create new credentials 

There is not a facility to create new credentials from within the Connection Profile user interface. To create new credentials, you must go to the Credentials Management page.

You cannot set security permissions when you are first creating a new Connection Profile 

Security permissions cannot be set while creating a Connection Profile. To set security permissions, you must edit the Connection Profile.

You may need to specify login information when accessing Connection Profiles 

You may need to specify your login information while accessing the Connection Profile user interface. If this occurs, the login name must be specified in the following format: '[domain]\[login]'

It takes a long time to display the details of hundreds of Connection Profiles 

If there are hundreds of Connection Profiles, the Manage Connection Profiles page takes a considerable amount of time to display the details of a selected Connection Profile.

A Kerberos user with a long name in the format of username@domainname causes an AMT connection problem in Real-Time System Manager 

This problem is only reproducible in the username@domainname format. To work around this issue, use the domainname\username

The Monitor Solution Remote Monitoring Server Agent hangs on processing PAL metrics when password is about to expire

If a password comes within 14 days of expiration, PPA cannot connect to Monitor Solution's Remote Monitoring Server through WMI, and the Remote Monitoring Server Agent hangs.
Changing the password resolves the issue.

Uninstalling the imported MIBs is not possible

To remove imported traps, you must navigate to Settings > All Settings > Monitoring and Alerting > Protocol Management > Alert Management Settings and manually delete the traps from the various categories.

You must then delete the entry on the file system under the Notifications Server install directory. Open MibImportTask\Mibs\Uploaded, and delete the MIB file.

Cloning Connection Profiles requires write permissions  

Ensure that users have both Write permission as well as Clone permission before cloning any Connection Profiles.
If a user has clone permissions but not write permissions, then an exception error is thrown when attempting to clone a Connection Profile.

“Unknown or unspecified error” occurs when editing SNMP Trap Definitions

If you attempt to edit an SNMP trap definition located under the Unknown or under the Security category at the following location:
All Settings > Monitoring and Alerting > Protocol Management > Alert Management Settings
Then you will receive a Notification Server error.

This issue effects all but one of the trap definitions that are displayed under the Unknown folder. It does not effect the "unknown" trap definition.
This issue effects the following three traps definitions displayed under the Security folder:

    • authenticationFailureTrap
    • pcdot1xPortStatusAuthorized_V2
    • pcdot1xPortStatusUnAuthorized_V2
Saving a Connection Profile that contains an expired credential in a protocol throws an error   

If your save a Connection Profile that contains an expired credential that is selected for any of the protocols within it, an error page with exception details is displayed.

Alerts under Alert Management Settings cause an Unknown Error
User not able to save Alert Management Settings
Calendar not functioning if past date is chosen
Default Connection Profile security window does not close
CP Overflow after port input

Legacy ID


Article URL

Terms of use for this information are found in Legal Notices