Changing Time Zones and Clock Settings on a Report Server

A report server always uses the local time of the computer on which it is installed. You cannot configure it to use a different time zone. If a client application points to a report server in a different time zone, the report server time zone is used to execute a scheduled operation. In Report Manager, the time zone is indicated on each scheduling page so that you know exactly when a scheduled operation will occur.

If you change the time zone on a computer hosting a report server, you must restart Microsoft Internet Information Services (IIS) in order for the time zone change to take effect.

Timestamp values of existing generated reports that are not refreshed (for example, report history snapshots) are synchronized to the new time zone setting. If you generated a report history snapshot at 9:00 A.M., and then reset the time zone ahead one time zone, the timestamp on the generated snapshot will change from 9:00 A.M. to 10:00 A.M.

Schedules retain existing settings, except that they are mapped to the new time zone. For example, if a schedule runs at 2:00 A.M. Pacific Standard Time and you change the time zone to East Australia Standard Time, the schedule runs at 2:00 A.M. East Australia Standard Time.

Property timestamp values (for example, the time at which a folder or linked report item is created) are not synchronized to a new time zone setting. If you create an item on June 25 at 9:00 A.M., and then reset the time zone or clock, the timestamp remains June 25 at 9:00 A.M.

Changing the computer clock has no effect on existing timestamp values (for example, if you move the clock forward an hour, the timestamps of report history snapshots do not change). There may be a delay of 10 seconds before the Scheduling and Delivery Processor uses the new setting. The actual delay may vary if you modified polling interval settings in the configuration files.

Community Additions