Skip to main content

Windows server 2016/2019/2022 sync with NTP server

 Steps to follow:


1.Check Existing config - w32tm /query /status

C:\Users\Administrator>w32tm /query /status

Leap Indicator: 0(no warning)

Stratum: 1 (primary reference - syncd by radio clock)

Precision: -23 (119.209ns per tick)

Root Delay: 0.0000000s

Root Dispersion: 10.0000000s

ReferenceId: (source name:  "")

Last Successful Sync Time: 11/11/2022 

Source: Local CMOS Clock


2.Stop Windows Time service - net stop w32time

C:\Users\Administrator>net stop w32time

The Windows Time service is stopping.

The Windows Time service was stopped successfully.


3.Sync with NTP server - w32tm /config /manualpeerlist:<NTP Server NAPE/IP> /syncfromflags:MANUAL

C:\Users\Administrator>w32tm /config /manualpeerlist:ntp.test.net /syncfromflags:MANUAL

The command completed successfully.

4.Start the windows Time service -  net start w32time

C:\Users\Administrator>net start w32time

The Windows Time service is starting.

The Windows Time service was started successfully.


5.Resync the new time - w32tm /resync

C:\Users\Administrator>w32tm /resync

Sending resync command to local computer

The computer did not resync because no time data was available.







Comments

Post a Comment

Popular posts from this blog

Deploy OVF fails Issues detected with selected template. Details: VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19].

 Error: While deploy using OVF file ,getting error as : Issues detected with selected template. Details: - -1:-1:VALUE_ILLEGAL: No supported hardware versions among [virtualbox-2.2]; supported: [vmx-04, vmx-07, vmx-08, vmx-09, vmx-10, vmx-11, vmx-12, vmx-13, vmx-14, vmx-15, vmx-16, vmx-17, vmx-18, vmx-19]. Solution: Open .OVF file and edit       <Info>Virtual hardware requirements for a virtual machine</Info>       <System>         <vssd:ElementName>Virtual Hardware Family</vssd:ElementName>         <vssd:InstanceID>0</vssd:InstanceID>         <vssd:VirtualSystemIdentifier>zabbix_appliance-6.2.7</vssd:VirtualSystemIdentifier>         <vssd:VirtualSystemType> virtualbox-2.2 </vssd:VirtualSystemType>       </System> to  vmx-19       <Info>Virtual hardware requireme...
Post a Comment
Read more

Change ESXi acceptane level of VIBs to community Supported

-When you install VIB bundles you may see issue like:               'Could not find a trusted signer: self signed certificate  For resolving this issue, we have to convert the ESXi to community supported acceptance level. -To do that: if  ESXI is a VM :      Edit settings ->boot option ->disable secure boot. if Physical ESXi:      Edit  UEFI Now ssh to ESXi: - Move the ESX machine to community-support esxcli software acceptance set --level=CommunitySupported - Install the bundle with no-sign-check esxcli software vib install -d  VMware_bootbank_vmware-fdm_7.0.1-16478307.vib --no-sig-check -  Set back PartnerSupported esxcli software acceptance set --level=PartnerSupported
Post a Comment
Read more