Home - Blogs - Orchestrator (Opalis) - Orchestrator and SMA and the change to Daylight Savings Time
Donnerstag, den 19. März 2015 um 08:55 Uhr

Orchestrator and SMA and the change to Daylight Savings Time

Artikel bewerten
(0 Bewertungen)

Erstellt am Donnerstag, 19. März 2015 Geschrieben von Stefan Horz

At the end of this month, Sunday, March 29th, at 2:00 AM the clocks get changed to one hour forward in Germany and other European countries. How does this affect Schedules in Orchestrator or Service Management Automation (SMA)?

In "classic" Orchestrator the Schedules depend on the time of the Runbook Server(s) set in Windows. So if a Runbook is executed the "Monitor Date/Time" or "Check Schedule" Activities will check the time set in Windows of the executing Runbook Server, the times between 2:00 AM and 3:00 AM on March 29 will not happen

For example if you have the time 2:30 in the field "At" in your "MonitorDate/Time" Activity "Monitor Date/Time" will not trigger on Sunday, March 29. If time is shifted 1 hour back on Sunday October 25 it will trigger twice with a gap of on hour …

In Service Management Automation (SMA) there’s a known issue that Jobs are running an hour earlier than expected after the change to Daylight Savings Time. This will be fixed in further releases. Until now you will need to delete the schedule and create a new one and re-link to the runbooks as a workaround (https://technet.microsoft.com/en-us/library/dn554314.aspx?f=255&MSPPError=-2147217396#DSTIssue).

Read more

Kommentar hinterlassen