KB16678: If MicroStrategy Intelligence Server and Desktop 9.2.x - 9.3.x are running on different machines with different time zones when scheduling reports, what time will the schedule use?

A Strategy Intelligence Server 9.x machine and Strategy Desktop 9.2.x - 9.3.x machine are located in different timezones or are not synchronized. If a schedule is created in the Strategy Desktop 9.x machine, it will use the Strategy Desktop 9.2.x - 9.3.x machine time as the time to run the schedule.
 
To test with Strategy Tutorial data, follow the steps below:
 

1. Change the Strategy Desktop 9.2.x - 9.3.x machine time to be one hour ahead of the Strategy Intelligence Server 9.2.x - 9.3.x machine time. Make sure that no time synchronization is being done between the Strategy Intelligence Server 9.2.x - 9.3.x machine and the Strategy Desktop 9.2.x - 9.3.x machine.
2. Create a three tier connection to the Strategy Intelligence Server 9.x in the Strategy Desktop 9.2.x - 9.3.x machine.
3. Log in as the administrator.
4. Create a schedule to run every day at exactly 12:00a.m.
5. Schedule a report to run at the previously created schedule.
6. Check the Next Update column for that schedule in the Schedule Monitor in the Strategy Desktop 9.2.x - 9.3.x machine and notice the Next Update time is 12:00a.m.
7. Check the Next Update column for that schedule in the Schedule Monitor in the Strategy Intelligence Server machine using Strategy Desktop 9.2.x - 9.3.x and notice the Next Update time is 11:00p.m. of the previous day.

Basically, this means that the schedule will use the time of the machine where it was created. Administrators must add the timezone to the naming convention so that other administrators and users can be aware about the actual time when this schedules will run.