net time /set is this command persistant?

[Guest]

In other words.. Lets say i do a net time \\servername /set .. will this be persistant even once the computer reboots. I would like to have all the computers in my network sync to one specific machine even after reboots.

so basically 10 machines that synce to one \\servername.. and then I want that one server they are all syncing to to sync to a public server.

tia

 

[SaltPeter]

In other words.. Lets say i do a net time \\servername /set .. will this

be persistant even once the computer reboots. I would like to have all the
computers in my network sync to one specific machine even after reboots.

so basically 10 machines that synce to one \\servername.. and then I want

that one server they are all syncing to to sync to a public server.

tia

Whats the network architecture? Workgroup or domain?

Thats exactly how the W2K time service runs in a W2K domain. The "PDC
emulator" FSMO role is the time authority on a W2K domain with all clients
synchronizing of it. So perhaps, in your situation, if you aren't already
running a domain, you might consider switching from a workgroup to a domain.

 

[Guest]

Sorry, I should have stated. .Yes this is a domain.. But these 10 computers I am trying to keep semi seperate from the rest of the domain.. I have them in a vlan and would like to just have them all sync to one machine within the 10.. However, even with changing the registry on this one machine that I want to be the master timeclock.. It still keep setting it's time back to the rest of the domain's time..

I want 1 machine of a vlan 0f 10, on a domain of a 100, to keep its own time, and not to check in with the domain time of the other 90.. Then i want the other 9 machines in that vlan to sync up to the 1.. BTW all of these machines are 2k server except for the 1 i have set to be the master clock.. that one is just 2k pro.

tia

 

[SaltPeter]

Sorry, I should have stated. .Yes this is a domain.. But these 10

computers I am trying to keep semi seperate from the rest of the domain.. I
have them in a vlan and would like to just have them all sync to one machine
within the 10.. However, even with changing the registry on this one
machine that I want to be the master timeclock.. It still keep setting it's
time back to the rest of the domain's time..

I want 1 machine of a vlan 0f 10, on a domain of a 100, to keep its own

time, and not to check in with the domain time of the other 90.. Then i want
the other 9 machines in that vlan to sync up to the 1.. BTW all of these
machines are 2k server except for the 1 i have set to be the master clock..
that one is just 2k pro..

tia

Thanks for feedback, the time issue is a real sticky one when W2K is
involved. The best way i can explain the issue is by investigating how W2K
is able to support peer-to-peer domain controllers all having a writable
copy of the domain database. The key is that any change to a database is
timestamped, this is how the W2K architecture will detect replication
sequence numbers to be unique even if the numbers concur. Also, Kerberos
logins are timestamped since security tickets are time based.

Time is as important to W2K as a heartbeat. There is a possible workaround
if what you need is a few hours offset: Sites and alternate time zones. If
what you need is something more radical, you'll have to isolate the time
shifted network or users won't be able to login and replication will fail.

Note that if you are dealing with a language like SQL and you need to work
on a database using time selected entries, the language provides queries
with time specific parameters.

 

[Guest]

thx for the info saltpeter.

Yes sql is a life line on all these machines.. I am testing this theory in our test enviroment before I put it on production.. I am coming to the conclusion that I should not really mess with syncing the times at our datacenter.. I don't want to mess up anything with sql.

Also, I have been reading some problems when syncing time with 2k and security issues with kerberos.

I appreciate the help.

comb