About the Notification Server 6.0 SP3 R14 Rollup
Created: 04 May 2012 | Updated: 08 Nov 2012 | 4 comments
In the Notification Server 6.0 SP3 R14 release, the following issues have been fixed:
|Issue||Article ID||Internal ID|
|Windows Server 2008 Package Servers take a long time to download packages.||N/A||2634897|
|Port scanner closes the 52028 listening port that the power management uses.
After the Microsoft PortQry 2 port scanner scans the 52028 listening port 6 times, the port closes.
|Med-V devices that run in NAT mode are unable to determine a proper package server.||N/A||2579471|
|Client Messages are processed in an endless loop.||N/A||2425360|
|Blue screens on HP 8440p laptops with the Altiris Agent R13 installed.
When you install new software on a HP 8440p laptop and shortly after that want to reboot this computer, the Altiris Agent attempts to write to the registry during shutdown, gets into a loop, and then might need to force the shutdown. When the computer starts next time, the corrupted registry causes the blue screen.
|Packages cannot be delivered to computers because the package delivery infrastructure is out-of-synch.||N/A||2223225|
|An SQL that checks whether all full control permissions are set correctly is very intensive and can take up to 30 minutes to complete on large customer databases, and may cause the Notification Server 6.0 SP3 R13 update to not complete successfully.||N/A||2078119|
|Resource merging is very slow.||N/A||2070370|
|Altiris Agent will randomly stop updating configuration until the Agent is restarted.||N/A||2065991|
|The Encrypt and Decrypt functions leak memory and do not clean up global memory under all circumstances.||N/A||2026822|
|Package Servers do not download files if only the timestamp differs from the snapshot.xml information.||TECH140644||1908728|
|A bug in Quicksoft SMTP component prevents Notification Server from using the Lotus Domino SMTP servers that require authentication.||N/A||1580410|
The Release Notes for Notification Server 6.0 SP3 R14 release are available at the following URL: http://www.symantec.com/docs/DOC5566