After daylight savings time (DST) changes occur, any maintenance windows configured to run using server time will be offset by an hour on targeted agent computers. For example, a maintenance windows configured to use server time starting at 12:00am may reflect on an agent computer starting at 11:00pm after DST changes occur, therefore allowing the agent to execute policies on hour earlier than the configured time.
The scheduling of maintenance windows is stored in the database using a time zone value according to the local date/time configuration on the SMP server; however, after DST changes the time zone offset is not updated within the database.
This issue is currently under review by Symantec development teams. There are two workarounds to this issue, both of which involve re-saving the maintenance windows after the change in DST. Once the maintenance windows are saved in the database with the updated time zone offset, targeted agents will receive the changes after a new configuration policy is received from the SMP server.
Option 1: Manually open each maintenance window within the console and click "Save changes" after the change in DST has occurred on the SMP server. It is not necessary to modify any configuration within the maintenance window but by clicking on "Save changes" the database will be updated with the correct time zone value.
Option 2: Use the attached script to resave all maintenance windows on the SMP server after the change in DST has occurred. The script can be manually executed through a command prompt or can be scheduled using the Windows Task Scheduler.
To manually run the script:
When executing Install.cmd, the item GUID for the maintenance windows will be displayed as well as the schedule as it was originally configured in the database and the schedule after the maintenance windows was resaved. This information repeats for each maintenance window within the currently attached database.
To schedule the execution of the script through the Windows Task Scheduler:
Date: 03/1/2013 12:01:28 PM
Tick Count: 91079608
Host Name: SERVER
Process: NScript (5104)
Thread ID: 29
Description: EventLogging thread has started.
Symantec Management Platform 7.1 SP2