Re: Using Exchange2003 when the PDC is offline

From: Dave Kearney [MSFT] (dkearney_at_online.microsoft.com)
Date: 11/30/04


Date: Mon, 29 Nov 2004 21:27:58 -0800

You should be able to survive for a while without your PDC emulator online.
That said, I'm assuming we're talking about Active Directory here. In that
case, you're going to be heavily dependant on DNS. I'd probably start by
checking your DNS resolution infrastructure. What server is your Exchange
server and clients configured to use as primary DNS? Is there a backup? In
the absence of DNS resolution, you're going to have big trouble.

That said, despite the work the Exchange team has done on improving its
ability to survive DC outages, there is still a possibility that you may
have service availability issues if the DC it has decided to associate
itself with unexpectedly dies. In that case, you might need to reboot the
Exchange server so that it will associate itself with an available DNS
server. Again, this will require successful DNS resolution.

-- 
-Dave
This posting is provided "AS IS" with no warranties, and confers no rights. 
Use of included script samples are subject to the terms specified at 
http://www.microsoft.com/info/cpyright.htm.
"Mark Walsh" <Mark Walsh@discussions.microsoft.com> wrote in message 
news:DF69B7D6-D18E-483D-9FF9-ABD6307C8E8B@microsoft.com...
> Our PDC went belly up with a RAID controller failure.  The full restore of
> the server from tape takes about 8 hours and is still underway.
>
> However, as soon as the PDC is taken off-line, for any reason, no one can
> connect to the Exchange server, which is also a BDC, using Outlook.  Plus,
> OWA also refuses to play while the PDC is off-line.  It just keeps coming 
> ups
> with authentication errors, as well as LDAP errors.  Once the PDC is back 
> on
> line, these errors go away and the exchange server will start working 
> again.
>
> Now I was of the understanding that a BDC could handle authentication if 
> the
> PDC was off-line.
>
> Or is it the case that having a single server fail, if it is the PDC, then
> all the rest of the servers are inaccessible.
>
> Is this normal behaviour?  Not being able to use the Exchange server 
> because
> the PDC is off-line.  Doesn't that also make us very vulnerable with all 
> our
> servers being at the mercy of a single server?  The SQL server is they 
> same,
> can't authenticate.  And it too is a BDC.  What have I done wrong?
>
> 


Relevant Pages

  • Re: NT4 to Server 2003 Migration
    ... based on everything you've said here, I would hire an experienced consultant, if only to assist you in the planning stage. ... I would not upgrade your current PDC to 2003. ... it's only 4-8 gig, not nearly large enough for 2003 server with SP1, and future service packs & upgrades. ... BDC 1 - RAS, Print Server, File Storage ...
    (microsoft.public.windows.server.migration)
  • Re: Windows Time Service: What if the PDC-role is moved?
    ... NTP - use the time source specified in the NtpServer Value ... I suggest using the w32tm command for modifying the time service parameters rather than directly modifying the registry entries. ... switch that takes priority and tells it to acquire NTP server info ... Doesn't he has to have the PDC DNS-name or IP-address in it? ...
    (microsoft.public.windows.group_policy)
  • Re: wrong time server
    ... It does not query what the local machine's time service is set to use with the domain hierarchy. ... It's rather useless trying to use it to find which server is the client's time service. ... All client desktops select an authenticating domain controller ) as their time source. ... The PDC of the current domain. ...
    (microsoft.public.windows.server.active_directory)
  • Re: NT to SBS 2003
    ... use the existing Exchange server hardware for SBS - this is an old AMD-K62 ... The PDC should be formatted and repartitioned as well, ...
    (microsoft.public.windows.server.sbs)
  • Re: NT to SBS 2003
    ... use the existing Exchange server hardware for SBS - this is an old AMD-K62 ... The PDC should be formatted and repartitioned as well, ...
    (microsoft.public.windows.server.sbs)

Loading