question

MohammadQamrulHuda-0112 avatar image
0 Votes"
MohammadQamrulHuda-0112 asked DSPatrick commented

Time is not fixed After restart the Active Directory Windows Server 2012 R2

After restart the Active Directory Windows Server 2012 R2, Time is not fixed in this Server with AD members Computers. after restart, always approximate one hour time back, but date is not change. I have checked, others VM not change the time, which not member of the AD.

AD is Virtual machine in VMware 6.5 platform. My Host Server is HP ProLiant DL380p.


Pls. help me for resolving this problem.
Thanks,
Qamrul

windows-serverwindows-active-directoryazure-ad-domain-serviceswindows-server-management
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

1 Answer

DSPatrick avatar image
0 Votes"
DSPatrick answered DSPatrick commented

I'd check that time sync is turned off in guest integration services.

Some general info
- All domain members should use NT5DS domain time.
- Desktops and member servers sync with any domain controller.
- Domain controllers sync with PDC emulator (one per domain)
- PDC emulator in child domain can sync with any domain controller in parent domain.
- PDC emulator in parent domain syncs with either a hardware clock or possibly an external source.
https://blogs.technet.microsoft.com/nepapfe/2013/03/01/its-simple-time-configuration-in-active-directory/

on all members (not PDCe)

w32tm /unregister
net stop w32time
w32tm /register
net start w32time
w32tm /config /syncfromflags:domhier /update
net stop w32time
net start w32time
then check
w32tm /query /source
w32tm /query /configuration

--please don't forget to upvote and Accept as answer if the reply is helpful--








· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Just checking if there's any progress or updates?

--please don't forget to upvote and Accept as answer if the reply is helpful--



0 Votes 0 ·

It is solved after adjusting the local host CMOS time.

0 Votes 0 ·
Show more comments