I set all my non DC servers to have no specific SNTP server using the following command (which can be run remotely in a script)
*NET TIME \\RemoteComputer /SETSNTP:""* When you query for those systems, they should return the following: *>net time \\%computername% /querysntp* This computer is not currently configured to use a specific SNTP server. -ASB: http://XeeSM.com/AndrewBaker Providing Competitive Advantage through Effective IT Leadership On Tue, Sep 22, 2009 at 10:57 AM, <richardmccl...@aspca.org> wrote: > > Thanks! Now that we've confirmed I have only a vague idea of what I'm > doing here... > > What is the difference in having a PDC-Emulator having its parameter set > for NT5D5 (as is mine) and NTP? What do the flags do here? > > Finally (and hopefully!), when going back to fix what I've been breaking > for several months... > > Once the PDC-Emulator is syncing with the external source properly, how > should the WTime32 parameters be set in all the other servers (including the > other local DCs as well as "member servers" so they will: > 1. Sync with the PDC-Emulator and this sytem only? > 2. Not themselves try to act as local time servers? > > If the PDC-Emulator happens to go down, does one then try to establish that > FSMO role to one of the other DCs (to keep time sync services available)? > > Thanks y'all for your patience! > -- > Richard D. McClary > Systems Administrator, Information Technology Group > > *ASPCA®* > 1717 S. Philo Rd, Ste 36 > Urbana, IL 61802 > > richardmccl...@aspca.org > > P: 217-337-9761 > C: 217-417-1182 > F: 217-337-9761 > *www.aspca.org* <http://www.aspca.org/> > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
