Re: AD, Win 2000, and new 2007 Daylight savings time
- From: "Joe Richards [MVP]" <humorexpress@xxxxxxxxxxx>
- Date: Tue, 23 Jan 2007 23:20:22 -0500
You need to do it on every machine that you locally want displaying the proper time. If the machine displays the incorrect time, that isn't really an issue as long as you are aware of it but in most normal cases that will confuse the crap out of people.
As mentioned, replication and other core functions don't care what the TZ/DST settings are. It is all about displaying the things properly for users. A user will never notice that a DC doesn't have the patch as it will have no impact on users. An Exchange server that runs server side scripts could have an issue though if the scripts work in localtime instead of UTC (that would be the norm for scripts - working in localtime).
joe
--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net
---O'Reilly Active Directory Third Edition now available---
http://www.joeware.net/win/ad3e.htm
Nick wrote:
We have a windows 2003 DC and that is set up with authoritative time server.We have around 400 Win 2k clients. Will we need to patch our clients are will the time be ok Since we are using authoritative time server manage the time. The only place we will need to patch on the DC. Do I have this correct or do we need to patch all member servers and clients?.
"Joe Richards [MVP]" wrote:
OK you are living under a huge misunderstanding of how time works in the computers.
When DST changes, the machine time does not change. Only what is displayed for local system time. All back end time on clients and servers is handled via UTC and then the local machine translates that into a value for humans to view locally based on their local TZ and DST settings. It isn't like DST will flip and then DCs will start handing out a new time... The time they will hand out one second before and one second after the change will be 2 seconds apart, not an hour and 2 seconds. If they didn't, you couldn't run machines across time zones at all, it would all blow apart.
--
Joe Richards Microsoft MVP Windows Server Directory Services
Author of O'Reilly Active Directory Third Edition
www.joeware.net
---O'Reilly Active Directory Third Edition now available---
http://www.joeware.net/win/ad3e.htm
Sean wrote:We've got about 300 W2K Pro, and 350 WXP Pro computers in a domain
(functional level 2k3). We're worried about what will happen to the
300 Win 2000 machines when daylight savings time is changed this year.
We're running WSUS so all the XP machines have the patch Microsoft
released, but we're afraid we'll have to manually change all the 2000
machines (Using Windows Time Zone Editor). My question is, is there
any reason to change each 2000 client? I mean w32time's type is set to
NT5DS (which means it should use the domain hierarchy). When the DC's
change their time for daylight savings, won't w32time pick up the
change and run with it? I'm worried we'll end up with clients that
can't authenticate because of an hour difference in time...
Any suggestions would be appreciated!
- References:
- AD, Win 2000, and new 2007 Daylight savings time
- From: Sean
- Re: AD, Win 2000, and new 2007 Daylight savings time
- From: Joe Richards [MVP]
- AD, Win 2000, and new 2007 Daylight savings time
- Prev by Date: Re: Crashed Controller, Recreated, Logon Problems
- Next by Date: Re: DCDiag Errors
- Previous by thread: Re: AD, Win 2000, and new 2007 Daylight savings time
- Next by thread: upgrading ad schema windows 2003 R2
- Index(es):
Relevant Pages
|
