Domain time did not fall back -- Server 2008R2

Our Server 2008R2 Domain did not fall back over the weekend and the domain is now an hour ahead.  PCD emulator is not sync'd to an outside time server.  How can I get the domain back in time sync with out disrupting service or crashing the domain?
dustypenguinAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

dustypenguinAuthor Commented:
There are 3 other domain servers (2008R2) as well, FYI
0
Chris HInfrastructure ManagerCommented:
2008R2 should have the 2007 DST fix.  Was this upgraded from 2003?

The problem is, if everything is happy, that means that the 1 hour off is machine time correct.  If you move the clock, you're going to have domain issues.  I'd wait until after hours....

If you have to, set your time zone off one hour so the user sees the correct time.
0
dustypenguinAuthor Commented:
This is not an upgrade, so I am pretty sure the DST fix is not an issue.  

Strangely, when one opens the clock from the task bar, it says "Daylight Savings Time ended on Sunday, November 01, 2015 at 2:00 AM.  The clock went back 1 hour at that time.", but it obviously did not.
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Will SzymkowskiSenior Solution ArchitectCommented:
Have you tried to restart the Windows Time service on the PDC?

I would also be checking the Event Viewer as well to see if there is any reference to the time issue on your server.

Will.
0
diperspCommented:
Do you have the DC syncing to an external time source that could potentially be wrong?  Is your time zone also set correctly?

From a command line, you can run

w32tm /query /peers

to see if/who the DC is syncing to.  I'd recommend updating it to north-america.pool.ntp.org if you need a reliable time source.  

Here's what we run on DCs to sync them to an outside source reliably.  Once this DC is good, restart time services on all other machines.  As choward16980 said, I'd do this off-hours as the other DCs aren't going to be happy.  I'm wondering if shutting down the other DCs first wouldn't be a bad move then bring them back up once the time on the PDC is good.

From a command line -

1. net stop w32time
2. w32tm /unregister
3. w32tm /register
4. net start w32time
5. Re-check w32tm /query /peers - should be empty.
6. w32tm /config /manualpeerlist:"north-america.pool.ntp.org" /syncfromflags:manual /reliable:yes /update
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
compdigit44Commented:
THis is very odd, like other experts as stated this should not be an issue expecially with an upgrade.  Have you checked your event logs and/ or checked to see your time services to see if it is running
0
compdigit44Commented:
THe following article I found talks about the DST change and how is could affect AD authentication...

http://searchwindowsserver.techtarget.com/tip/Microsofts-daylight-saving-time-DST-patch-Does-it-matter-to-AD

In short it appears AD really relises on UTC time and the display time the user sees is a represention. SO if your UTC time zone is correct and you update the time on our PDC all other servers and workstations should sync up.. But right now we need to find out why your servers time did not change
0
diperspCommented:
Compdigit44 -

Just keep in mind that OTHER applications don't always utilize UTC only.  I had a time issue with a system and got it sorted out, but Exchange hub transport went crazy and we needed to restart it (Minor, but fyi.)  Same deal with Goldmine on the same server.
0
dustypenguinAuthor Commented:
So.  Without knowing what would happen by just going back an hour on the PDC emulator, I have been going back 3 minutes at a time (a normal file stamp error fudge, I have read) and letting everything sync back up.  This has been going well, even though this maybe a gorky solution.

The larger issue is indeed that the PDC was only syncing to "LOCL", and will change that to the ntp.org as suggested by dipersp, since we use ntp.org in our xenserver hosts.

Will let you know how it all goes ultimately.
0
dustypenguinAuthor Commented:
It's been stable now for a week, and things look ok.  
Synced to ntp.org timeservers.  
Adjusting the time back incrementally ultimately worked fine but was a pain.
Root cause, I believe was that the FSMO roles were transferred to this machine at some point and time services were not reconfigured for the authoritive time server role that the machine became.

Thanks for the help!
0
diperspCommented:
Just checking - any reason for the b grade?  Anything that could have been done better?
0
dustypenguinAuthor Commented:
I guess while we were hitting all around the fixes we never got to a definitive "when this happens do this" ... Nothing bad, just thought we were all incomplete.

Make sense?
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Windows OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.