KNOWN ISSUE: HP Client Manager agent package replicates source paths causing inaccessible packages on child Notification Server
|Article:TECH41724|||||Created: 2009-03-25|||||Updated: 2011-02-09|||||Article URL http://www.symantec.com/docs/TECH41724|
|NOTE: If you are experiencing this particular known issue, we recommend that you Subscribe to receive email notification each time this article is updated. Subscribers will be the first to learn about any releases, status changes, workarounds or decisions made.|
In an environment configured with both parent and child Notification Servers, the HP Client Manager Agent package may become inaccessible when the path on the child Notification Server does not match the parent NS. This issue will result in problems for client machines that request the HP Client Manager agent install package.
HP Client Manager 7.0
If the parent Notification Server is installed to a different directory location than the child, the package source paths will fail to match up after the parent replicates package information to the child NS.
This is a documented known issue with the software. Symantec is currently investigating the problem and will research a possible fix for the issue.
Temporary Work Around:
- Modify the package source location manually on the Child NS. To achieve this, copy the package manually to the directory on the child Notification Server where the source indicates the agent should be located.
Logged in Littlebuggy (Altiris - Lindon, Plymouth) database
Article URL http://www.symantec.com/docs/TECH41724