KNOWN ISSUE: Problem to control time of installation for all plug-ins when you use schedules
|Article:TECH176442|||||Created: 2011-12-07|||||Updated: 2011-12-09|||||Article URL http://www.symantec.com/docs/TECH176442|
|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.|
Some policies that use scheduled time zone are incorrectly handled on client side if the server and the client time are set to different time zones, or time.
If scheduled resource membership updates are performed on a server with its clock set to a future time, then new resources are not added. They are not added until the next resource membership update are performed. If you then set the clock on the server back to current time a new problem arises. The next resource membership update can't be performed because the current time is less than the previous updating time.
For example, agent rollout policies based on SWD rely on the Task Scheduler. The rollout policy page uses the policy scheduling control which provides more capabilities than the Task Scheduler supports. Among other things, the Task Scheduler does not support the use of timezones.
Step to reproduce (one example case):
1.Install on client Symantec Management Agent
2.Open NS console->Actions->Rollout Agents/PlugIns->Software->Software Management Solution(Patch management solution) folder.
3.Open Rollout policy page and add schedule time at 13:00 and time zone equal server time. Untick checkbox to install plugin ASAP and save changes.
4. Update configuration on client side and open received policy XML file.
The schedule time zone(server, utc, agent) is incorrectly handled on client side in case different time used for server and client.
ITMS 7.1 SP1, SP2
Known Issue. The schedule time zone(server, utc, agent) is incorrectly handled on client side in case different time used for server and client.
This issue has been reported to Symantec Development team. This issue should be addressed in a later release.
Article URL http://www.symantec.com/docs/TECH176442