Re: Windows Time Service: What if the PDC-role is moved?



Behaviors depend on whether you have left things at default or not.

The is an SRV resource record in DNS for the domain that any
machine with access to that DNS zone may query (the PDC record).
Left at default settings a domain member will locate its timeserver
by use of query to DNS for this record.

If you client is not following the move of the PDC FSMO to a
different DC then a) the client is configured to use a specific
timeserver, b) DNS is not getting updated to reflect the PDC
move, or c) the wrong DNS server(s) is(are) being used
- or perhaps something else.

Also, in your post you mentioned configuring the new PDC
FSMO holding DC to use an external time source. One should
not be doing that unless the DC is in the forestroot domain.
Other domains' PDC FSMO holder will locate and use the PDC
FSMO of the forestroot domain if you leave things at install
defaults (so keeping the whole forest in sync).

Roger

"jeutix" <jeutix@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:F0DD3626-4CC9-413E-9BCB-E98FC9D33C49@xxxxxxxxxxxxxxxx
We've done this and configured the new server with an IP-address of a
Internet-time-server.

But if I execute "net time" on a client, then the old PDC is shown in the
result line.

But the old one doesn't have this config any longer, so I ask myself why
the
client still shows the older one?

--
Greetings
Udo
MCSE / CCA


"Florian Frommherz [MVP]" wrote:

Howdie!

jeutix schrieb:
I'read that normally the first DC in the domain which holds the
PDC-role is
also the authoritive time server. So this one should catch the time
from the
internet and serve it to the clients in the domain.

What is, if the PDC role is moved from the first DC in the domain to
another
DC? Will the first server be still the time server or will the new
server be
the one?

As of my knowledge, if you move the PDC-emulator-role to another DC, the
new PDC will be the authoritive time source for all other domain
controllers - and they will propagate the time to all authenticating
clients.

So if you move the PDC role be sure to have the new-to-be-PDC configured
to sync the time with a reliable source.

cheers,

Florian
--
Microsoft MVP - Windows Server - Group Policy.
eMail: prename [at] frickelsoft [dot] net.
blog: http://www.frickelsoft.net/blog.



.



Relevant Pages

  • Re: Internet Speed
    ... I think what we are trying to say is to use the DHCP from the SBS and NOT ... DNS and WINS point to the SBS. ... as the server IP address. ... it is recommend to configure all SBS client computers' IP and DNS ...
    (microsoft.public.windows.server.sbs)
  • Re: 70-294 next week
    ... to another DNS ... server for at least ... client, which then ... configuration on the client. ...
    (microsoft.public.cert.exam.mcse)
  • Re: Dual NIC vs Single NIC
    ... |> 135919 DNS Server Search Order Functionality in Windows ... Thank you for helping me to correct the misunderstand of DNS query ... Thank you again for your supplement about the client DNS cache issue. ... This newsgroup only focuses on SBS technical issues. ...
    (microsoft.public.windows.server.sbs)
  • Re: Dual NIC vs Single NIC
    ... I will again argue that turning off the client DNS cache (0 refresh ... 261968 Explanation of the Server List Management Feature in the Domain ... Internet when the SBS server is offline. ...
    (microsoft.public.windows.server.sbs)
  • RE: Dynamic Update of A&PTR Records - Best Practice?
    ... The DNS server does not support the DNS dynamic update protocol; ... For Windows Server 2003-based computers, the primary full computer name is ... When one of these events triggers a DNS update, the DHCP Client service, ...
    (microsoft.public.windows.server.dns)