Time Servers

[TwistedHelixis]

Hello, I have just been asked to update our primary schools servers with 3 IP addresses for time synchronization.

 

We have 2 Hyper-V Host servers (Not Domain Joined), 2 virtual DC's and a virtual Data server.

 

Am I correct in thinking I should set our DC as the main Time sync server and the other servers can use that for the time.

 

What about the 2 Hosts that are not Domain Joined.

 

Just so you know I do not have Time sync ticked in the Hyper-V settings.

 

Thanks in advance for you time.

[Michael]

You'd set all three to be time servers, so they sync accordingly.

 

Setting your DC as a time server means all other DCs, member servers and workstations will all sync their time from it. The two standalone servers won't, so set them both individually.

[rrrrr]

Setting virtual dc's as the time server for a domain can cause things to go slowly out of sync.

 

DC as time server > hyper-v host gets time from virtual dc > hyper-v host updates virtual dc time through vm services > repeat.

 

This process adds a second here and there to original time and slowly things get out of sync.

 

I have a diagram on how i set ours up to avoid this. Can supply if needed

[TwistedHelixis]

DC as time server > hyper-v host gets time from virtual dc > hyper-v host updates virtual dc time through vm services > repeat.

 

I have un-ticked the option to sync time between the host and its vm's in the integration services list.

[rrrrr]

I have un-ticked the option to sync time between the host and its vm's in the integration services list.

 

Double check on dc that it isn't still getting from host. Mine was, even after disabling integration services.

 

Think command to check is

w32tm /query /status

[TwistedHelixis]

Think command to check is

w32tm /query /status

 

Thanks, command worked. All good, it's looking at our old DC for time.

[TwistedHelixis]

Been looking online for the code to actually set the ip addresses and think this is it.

 

w32tm /config /manualpeerlist:”01.01.01.01 02.02.02.02 03.03.03.03” /syncfromflags:manual /reliable:yes /update

 

Does that look correct? last thing I want to do is kill our server while doing something trivial like setting the time.

 

Cheers

[TwistedHelixis]

w32tm /config /manualpeerlist:”01.01.01.01 02.02.02.02 03.03.03.03” /syncfromflags:manual /reliable:yes /update

 

Just tested this out on a laptop and it does work but when I do w32tm /query /status it only lists the last ip range out of the 3 I have entered, so there must be something wrong with my code - w32tm /config /manualpeerlist:”01.01.01.01 02.02.02.02 03.03.03.03” /syncfromflags:manual /reliable:yes /update

 

I read you should have spaces between the ip addresses but wonder if that is correct

[TwistedHelixis]

Well it works with or without commas, just needed to use this command w32tm /query /configuration to do a full list.

 

Thanks

[twin--turbo]

I gave up on relying on virtual servers as the master time reference. We were seeing all sorts of odd time related issues.

 

but we have all sorts wanting time,

 

Windows,

Oracle,

Linux,

Switches,

Routers,

SANS,

NAS,

Etc..

 

 

We put in two old HP DL360 G5's running NTPD on Ubuntu and Time has been rock solid for 2 years.

 

TT