Status times for Caches display differently when connected to DRA servers in different time zones.
DRA does not display the correct FACR and IACR times in the Status.
Directory and Resource Administrator 7.x
Directory and Resource Administrator 8.0
Directory and Resource Administrator 8.0 SP1
DRA offsets the time settings in different time zones to the local time on the machine of the logged on user.
Directory and Resource Administrator (DRA) resolves to Greenwich Mean Time (GMT) to calculate time and corrects for a local time zone offset. DRA uses GMT for calculating time, but it then offsets it with the local time of the machine for the logged on user. Local time for the machine is obtained from the domain controllers (time server) in the site where the machine resides. See the following example:
DRA is installed on two servers. One in Houston (Central Time) and one in New York (Eastern Time). Both have their Full Account Cache Refresh (FACR) intervals set to Daily at 3:00 AM, both of which have completed successfully. If I physically log on to the DRA server in Houston and connect to the Houston DRA server, I will see that the FACR completed successfully at 3:10 AM. If I then change my focus and connect to the New York DRA server while still physically logged on to the Houston DRA server and check the FACR on the New York server, I will see that it too completed successfully, but at 4:09 AM. If I were to physically connect to the New York DRA server and check the FACR statistics however, I will see that it completed at 3:09 AM. The Houston DRA server adjusts the time displayed for the New York DRA server's FACR to the local time of the logged on user in Houston. Thus, it will adjust the time by the one hour difference between the Eastern and Central time zones. This is by design.