Net Time command - survive a reboot?? 1

[pndscm]

I have searched and found several posts as to setting the NTP on a Win2003 server using the Net Time command. When I Google for setting a time server in Win2003, I find a lot of Registry edits. Which is better, the Registry edits or Net Time? Does the Net Time command survive a reboot of the server?

 

[unclerico]

your domain controller that holds the PDC Emulator role should be configured as the authoritative time server for your domain. Setting it up is rather easy (this will make all of those registry changes you mention):

w32tm /config /update /manualpeerlist:<timeserver_name_or_ip>,0x1 /syncfromflags:manual /reliable:yes

<timeserver_name_or_ip> is the NTP source, whether it's time.nist.gov, or time.windows.com, or a hardware device internal to your network. The ,0x1 is added on if you are using host names as opposed to IP addresses for your NTP source. You may need to stop and start your Windows Time service for this to take effect. Also, be sure that UDP port 123 is open on your firewall if you are using an external source. You can verify that it is functioning by either looking in your System log of your event viewer for W32Time entries or you can run the following command:

w32tm /monitor

I hate all Uppercase... I don't want my groups to seem angry at me all the time! =)
- ColdFlame (vbscript forum)

 

[pndscm]

That sounds like it will take care of my problem. The Win2003 is running my voicemail system (Cisco Unity) and it is the Domain controller for the Domain. Since you say this will make the Registry edits for me, it will survive a reboot also. Great!!! Thank you very much!!