The System Center 2012 Configuration Manager Administration Console does not reflect changes in time zone until it is closed and reopened

Applies to: Microsoft System Center 2012 Configuration ManagerMicrosoft System Center 2012 R2 Configuration Manager

Symptoms


Consider the following scenario in Microsoft System Center 2012 Configuration Manager:
  • You work in the Administration Console that is connected to a site server. This site server is configured for the (GMT-5:00) Eastern Time (US & Canada) time zone.
  • You change the time zone of the primary site server to (GMT-8:00) Pacific Time (US & Canada).
  • You do not close and reopen the Administration Console, and then you deploy an Application or Package to a collection of users or devices.

In this scenario, the default value of the current time for the Schedule when this deployment will become available field and for the Schedule when this deployment will expire field are set to a time that is three hours later than expected. This time is the current time at the initial time zone setting. This behavior may cause your software deployment to occur later than you expected.

Workaround


To work around this behavior, close and reopen the Administration Console. You must do this any time that the site server time zone is changed. Or, select a specific date and time for the software distribution event to occur instead of the default schedule.