KNOWN ISSUE: In the NS log shows 'Force an update of collection....' multiple times per second
|Article:TECH185414|||||Created: 2012-03-30|||||Updated: 2013-04-23|||||Article URL http://www.symantec.com/docs/TECH185414|
|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.|
A customer reported seeing “Force an Update of collection…” message occurring about every second in their NS logs.
If a client performs a client configuration update during the time that a resource membership update schedule is running and is supposed to get the "Inventory Agent Plug-in", these messages will be generated for 10 specific filters (collections) . So it 50 computers in the Inventory Plug-in Install target send configuration updates while resource membership update is running each of these computers will force an update for each of the 10 collections.
These messages don’t occur if a resource membership update isn’t running.
Steps to Duplicate:
1. Disable the Inventory Agent Plug-In policy.
2. Clean the SMP Agent off of a client and repush the agent to it.
3. Allow the agent to update with its client settings.
4. Perform a Delta Membership resource update
5. Enable the Inventory Agent Plug-In policy.
6. Start a Full Membership resource update.
7. Force a configuration update on the client with the Full Membership resource update running
8. Watch the logs.
Symantec Management Platform 7.1 SP1, SP2
Known Issue. After analysing the issue we observed that this is not just happening for *Inventory agent plug-in* policy but also for other plug-in policies which uses 'Altiris.Agent.Unix.Policy.UnixAgentInstall' e.g. Software management plug-in policy. Though this happens for these plug-in policies, this membership update is not forced by any of them. This is done by the code 'Altiris.Agent.Unix.Policy.UnixAgentInstall.OnBuildClientConfigXml2()'.
This issue has been reported to Symantec Development team. A fix for this issue should be added in the next SMP release.
There is a pointfix available for SMP 7.1 SP2. Please contact Support to obtain a copy of it.
NB! It must stay enabled to guarantee plug-ins delivery to the new clients.
How to Uninstall
- Make sure that Backup folder exist in the same location as PFinstaller.EXE.
- Run as administrator PFinstaller.EXE, click ‘Uninstall’ button
Article URL http://www.symantec.com/docs/TECH185414