We have about 120 computers in Western Australia, that updated on the 19th of October to daylight savings time. Now Western Australia does not use daylight savings, therefore everybody's clock went forward an hour incorrectly. This has thrown everybody's calendar out of whack. Meetings are all wrong, and nobody's is correct.
So far what I have done to try and correct the problem is to roll out a registry change using a gpo startup script, to disable auto time zone updates. This has now been applied, but everybody is still set to 1 hour ahead unless I physically log in as admin. I know that even if all the times go back 1 hour, any appointments made after the 19th will still be wrong. The problem I'm having is how do I set everybody's clock back 1 hour, without going to 3 different sites and 120 different computers to change the time on each machine? And how do I then know that the calenders have the correct time? I have updated all the domain controllers, and server time, but for some reason this has not pushed it out to the clients?
The other problem is that I have updated 10 or so desktops, to test the calendars out, and none of them have the same time for the same appointment, some updated to the correct time, others stayed the same. Is there a fix for this? All clients are using XP and Office 2007. All our servers are using server 2008.
