Re: NTP question



Thank you, Meinolf.


"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message news:ff16fb66c35f8cb08166a82c112@xxxxxxxxxxxxxxxxxxxxxxx
Hello Steven,

That's correct.

If you have configured some policy settings, set them to "Not defined" and check on the client with gpresult /v that it is removed correctly. On the client either wait for automatic refresh of the policy up to 90 minutes, reboot or run gpupdate /force on it. If the old settings still appear, you have to change the policy to the opposite, if you configure an "Enabled" change it to "Disabled" and so on, run the client update and after the change is done set it to "Not defined".

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Basically, it's like this:

w32tm /config /manualpeerlist:times.windows.com/syncfromflags:manual
/reliable:yes /update

Understood.

Do I need to make any changes in Group Policy or revert it back to
default with no configuration settings?

Steven

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66c33f8cb080e381e56b2@xxxxxxxxxxxxxxxxxxxxxxx

Hello Steven,

No, domain time sync runs automatically by design.

In this command line you have "PEERS":
w32tm /config /manualpeerlist:peers /syncfromflags:manual
/reliable:yes
/update
For PEERS choose an external time server, either with the name or ip
address according to this link, where you can find time servers:
http://www.pool.ntp.org/

If you configure them with the command above, one or more, the
PDCEmulator will sync with them.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Forgive me, while I'm sort of confused here.

So we run the command on the Primary, but how would it know where to
look.

Also, the setting under Group Policy, where Windows Time Service,
does that need to be configure?

Steven

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb66c1e98cb076c72708f4a@xxxxxxxxxxxxxxxxxxxxxxx

Hello Steven,

This command has to run on the DC which has the PDCEmulator role
and that's it. Domain time synchronisation occurs as described
before.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
Hi,

So do you run this command ( w32tm /config /manualpeerlist:peers
/syncfromflags:manual /reliable:yes /update ) from the command
prompt?

and then specify the time source in Group Policy Management, via
by Hostname or IP?

Steven

"Meinolf Weber" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb6698168caf936fb1a4f34@xxxxxxxxxxxxxxxxxxxxxxx

Hello steve,

In a domain the "master" time server is the DC with the
PDCEmulator role, all other DC's sync with that one and all
member servers and workstations sync with one available DC.
That's the way in a domain, so you have to configure the
PDCEmulator to sync with the Cisco switch.

w32tm /config /manualpeerlist:peers /syncfromflags:manual
/reliable:yes /update

With "peers" you can set the time source, either DNS name
(time.windows.com) or an ip address from a reliable time source.

Here you can find also some of them:
http://www.pool.ntp.org/
Best regards
Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties,
and
confers no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
Hello Meinolf,

The computers are on a domain

Hello steve,

Only workstations on the switch or do you have a domain or
workgroup server?

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no
warranties,
and
confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!!
http://www.blakjak.demon.co.uk/mul_crss.htm
Is there anything on a local machines policy that would block
it from getting info on a NTP server? We have our Cisco
switch that serves as a time server, some clients have the
correct time, some do not.......... so I'm looking into why
some do not have the correct local time




.



Relevant Pages

  • Re: Machine policy when user logged onto local machine
    ... you log into the domain or local machine. ... then it sounds like domain policy has never propagated to the ... > Interesting point about effective settings. ... > had just been rebooting the client to force it to take the new policy. ...
    (microsoft.public.win2000.security)
  • Re: GPO causing client security logs to fill?
    ... Possibly delete the Default Domoan Controller Policy (As it did not ... settings as applied by the wizard cannot be trusted or that is why ... with client logon failures. ... So basically, the Account lockout threshold, account lockout ...
    (microsoft.public.windows.server.sbs)
  • Re: NTP question
    ... If you have configured some policy settings, set them to "Not defined" and check on the client with gpresult /v that it is removed correctly. ... If the old settings still appear, you have to change the policy to the opposite, if you configure an "Enabled" change it to "Disabled" and so on, run the client update and after the change is done set it to "Not defined". ... For PEERS choose an external time server, either with the name or ip ...
    (microsoft.public.windows.server.general)
  • Re: Password policy
    ... So you are saying that I should use the Default Domain Policy GP; ... as you can get "Computer Configuration" and "User Configuration" settings to ... replicate to all domain computers. ... The GP is now replicating to client domain computers ...
    (microsoft.public.win2000.security)
  • RE: Windows Update Server question/problem
    ... Windows Update settings on clients thru SBS group policy. ... SBS have Windows Update group policy for all client ...
    (microsoft.public.windows.server.sbs)