The running startup script takes too long?

[Charisma]

Hi,
I define a new policy and make a time.bat file and type in
it the
net time \\servername /set
command for all my domain in computer configuration in
windows setting startup script,
1- but it does't work all time
some users compliant that their computer's clock time is
wrong.Ofcource on the server that I synch others with it
all the time in error log's file there is w32time error.
Then I have a default domain policy that creates by AD
instalation and another one that I created.
2-When clients start up their computers It takes too long
in Running startup scripts phase?
Server OS is w2k server service pack 3
Clients OS is w2k pro service pack 3
Thank you so much.

 

[Matjaz Ladava [MVP]]

You don't need that in Windows 2000 AD domain, because Windows 2000/XP/2003
clients will automatically synchronize clock with server. See
http://support.microsoft.com/default.aspx?scid=kb;EN-US;216734 on how to
setup authoritative time server in domain.

--
Regards

Matjaz Ladava, MCSE, MCSA, MCT, MVP
Microsoft MVP - Active Directory
(e-mail address removed), (e-mail address removed)
http://ladava.com

 

[Charisma]

Again Hi,
Really I read that article that you wrote for me but
1- is it necessary to use an external time server?
2- If I set an external time server the w32time error was
fixed?(because every they I have this error in my PDC
operation master DC's event log)
2- If I set an external time server and suddenly our
internet service was stop for days what's happen for PDC
operation master DC's time?
3- After I set an external time server for PDC operation
master DC,what happen for other DCs and clients's computer?
4- In "net time /setsntp:server list" command what's
server list?
5- That article says for second step run one of the
following commands(that you know and I don't type it),
we must type one of them for other DC's and all clients?
Oh my god this is too long,so sorry about my questions (
So much thanks.

 

[Matjaz Ladava [MVP]]

1. No it can be any NTP server, but generally it is better to rely on one
reliable time server
2. What error ? You must pass NTP traffic out of your firewall for PDC to
synchronize with external time server. If the time server or internet is not
available, the time still comes from PDC master, but it relies on its
internal clock. The important thing here is, that the clients and servers
have the same time.
3. They will synchronize time with your time server (servers with PDC,
clients will also use other servers). Windows Time Service does that.
4. server list is a list of NTP servers. For example net time /setsntp:
time.windows.com will set external time source to time.windows.com. you can
specify more servers (separated by blank) for redundancy
5. the net time /setsntp.... is set only on root domain PDC master and you
don't have to do anything on other servers/clients

--
Regards

Matjaz Ladava, MCSE, MCSA, MCT, MVP
Microsoft MVP - Active Directory
(e-mail address removed), (e-mail address removed)
http://ladava.com