Server clock not synchronized with primary DC clock

Installed new Hyper-V 2012R2 VM on Hyper-V host. All went well, joined it to domain, installed SQL 2014 configured it. However, when I go to any computer on the domain to attempt to map a drive to this server I get the error message "The server's clock is not synchronized with the primary domain controller's clock".
The other 6 servers in the domain are having no issues, The primary DC is a Windows 2003R2 server

Henry StarcherConsultantAsked:
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.

Henry StarcherConsultantAuthor Commented:
Will do this in an hour when I return to office

Rodney BarnhardtServer AdministratorCommented:
You may want to verify that the Hyper-V server is configured to communicate with the time servers. I have a micro tutorial on setting the NTP server

The VM's could also be set to sync with the host in the event that is where the time difference is. If it is your VM's that are off, then check them for this setting.
You can use the W32tm.exe tool to configure Windows Time service (W32time) settings. You can also use W32tm.exe to diagnose problems with the time service. W32tm.exe is the preferred command-line tool for configuring, monitoring, or troubleshooting the Windows Time service.

To configure the server to automatically sync with the domain time we can use the following command at the cmd prompt.

w32tm /config /syncfromflags:DOMHERE /update
net stop w32time
net start w32time

Open in new window

Jason CrawfordTransport NinjaCommented:
I configure my PDC to sync with several NTP pools, then set all other non-PDCs to follow the domain hierarchy:  

From the PDC:

net stop w32time
w32tm /configure /syncfromflags:manual /manualpeerlist:",0x1,0x1,0x1,0x1"
net start w32time
w32tm /configure /reliable:yes /update
w32tm /resync

From all other DCs:

w32tm /config /syncfromflags:domhier /update


You can check the registry entries if the domain controller is using NTP (should be on PDC) or NT5DS (on non-PDC):
Find the value of Type under HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W32Time\Parameters

You can also check for time advertisement on the PDC by running this command:

w32tm.exe /resync /rediscover /no_wait

Tthen check for Event ID 139.  To check the source time server: w32tm /query /status

Don't stop here in a virtualized environment.  You have to check the VM host settings as well since the host time will affect the guest (at least it does in VMware).  I'm not familiar with the exact location of this settings for Hyper-V, but this is what The Google came back with:

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
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 Server 2012

From novice to tech pro — start learning today.