One thing most forget is that the Windows Domain Controllers also need to be configured properly for time synchronization. It’s easy to forget as it takes quite a few months, sometimes even years for the time difference to be noticeable by humans. Software usually tends to act up once the time difference is big enough and it breaks all kinds of stuff. For example in a vCD environment where the vCloud Director cells are on linux and use the ntpd daemon and the vCenter Servers usually reside on a Windows server which gets it’s time from the Domain Controller (VMware KB: 2058394). To set up the time on a domain controller, you first should locate the PDC Emulator to start things off. All Domain Controllers get their time from the PDC and the clients (workstations and other servers) get their time from the DC’s.To get the Primary domain controller, type the following command in cmd: “netdom query PDC“
- Log into your PDC Server and open the command prompt.
- Stop the W32Time service: net stop w32time
- Configure the external time source(s), type: w32tm /config /syncfromflags:manual /manualpeerlist:”0.pool.ntp.org,1.pool.ntp.org,2.pool.ntp.org”
- Make your PDC a reliable time source for the clients. Type:w32tm /config /reliable:yes
- Start the w32time service: net start w32time
- The windows time service should begin synchronizing the time. You can check the external NTP servers in the time configuration by typing: w32tm /query /configuration
- Check the Event Viewer for any errors.
Once this is done, it will take a while for the time to sync throughout the rest of the domain. Windows syncs time during netlogon process and periodically after it’s started.