> On the other hand, as for people saying they have to go through > the Windows desktops one by one to update them - I'm not a > Windows expert but I heard the the really good Windows admins > are able to do such stuff over the network through central servers.
[Guy] It's not about being good. It's about working with your head instead of working with your legs: http://guy.netguru.co.il/archives/8-Summer-clock-in-Israel-for-2005.html And I hope some day I'll have the time to finish this one (http://guy.netguru.co.il/uploads/w32tm.html ), so I won't have to explain each time that "net time" should NOT be used on W2K and up in AD environment(this is to-be-deprecated mechanism which uses legacy RPC calls). The right way to sync the clock is by triggering the W32TM service update via: "w32tm /configure /update /syncfromflags:DOMHIER" will configure the client to use AD domain hierarchy as it's SNTP source. "w32tm /resync" will trigger an immediate clock resync via SNTP. And you do NOT need to update the timezone on the DCs as long as the UTC on the DC is correct: the clock synchronization uses UTC and does not care about timezones. Heck, my PDC Emulator (acts as SNTP hierarchy root in AD environment) is in Palo Alto and the client machines still do not show the time of the shiny California. Guy ================================================================To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
