Re: pdc emulator crash questions

Scott,

You might want to consider making both Domain Controllers a Global Catalog 
Server....that way you have two.  Unless you have specifically made your 
environment not require a GC you absolutely need one.  And you will find 
that Exchange really needs one.  So, make the second DC a GC and things will 
be happier.

And, as Danny stated, you really need to tread lightly when it comes to 
seizing FSMO roles.  If you do that then the DC that held the seized role 
can never be reintroduced into the environment.

-- 
Cary W. Shultz
Roanoke, VA  24012

"Scott O" <pats1776@xxxxxxxxxx> wrote in message 
news:11u1d406hkhltd5@xxxxxxxxxxxxxxxxxxxxx
> So here is my setup:  Windows 2000 Domain, single site, single domain, 
> single location.
>
> - 2 domain controllers (one of them holds all the FSMO roles, both are DNS 
> & DHCP servers)
> - 1 Exchange Server
>
> Essentially, the DC that holds the FSMO roles crashed yesterday, and when 
> it did, it made Outlook clients on XP boxes start freezing up, takes 
> forever to login to boxes, etc.  I have seen this before when I've had to 
> reboot it before.  Eventually, everything seems to even out and clients 
> stop freezing up, etc. as Exchange, etc. must start using the other DC. 
> My only guess for the intial piece is that it is something to do with the 
> PDC emulator role, does that sound like where the sluggish clients, etc. 
> would stem from?
>
> Is there a quicker way to essentially make everything happy again?  I know 
> things like DNS lookups on the clients may stay with that slight delay, as 
> the primary DC is listed as their first DNS server.
>
> Another thing is that I know I can seize the PDC emulator and 
> Infrastructure master roles without ill effects unlike the other FSMO 
> roles, but will this help at all if the DC is only down for 5 or 6 hours?
>
> Any other thoughts on this?
>
> Thanks,
>
> Scot
> 


.

Relevant Pages

  • Re: Linux - SAMBA/OpenLDAP/Plone/OpenExchange
    ... There is a drastic difference between Windows environment ... adminstration and Unix (Linux mimics Unix, but its close enough to be ... appropriate configuration file to the new server, ... but what I have done in MS world is make my clients ...
    (alt.os.linux)
  • RE: Newbie SBS questions
    ... that we'll need to run on the server. ... The best coarse of action with legacy ... environment before running in the production environment. ... need to disable SMB signing on the clients. ...
    (microsoft.public.windows.server.sbs)
  • Re: Pros & Cons of sharing a front end MDB (Client workstation vs. Server)
    ... Our environment uses Win XP SP2 for clients, ... Common sense tells me that if I have the Front End in the server then ... But it *seems* that in a shared environment it is better to have each ... install the Front End on each client's workstation? ...
    (comp.databases.ms-access)
  • Pros & Cons of sharing a front end MDB (Client workstation vs. Server)
    ... Our environment uses Win XP SP2 for clients, ... Common sense tells me that if I have the Front End in the server then ... But it *seems* that in a shared environment it is better to have each ... I have the Front End living on client's workstations as opposed to ...
    (comp.databases.ms-access)
  • Pros & Cons of sharing a front end MDB (Client workstation vs. Server)
    ... Our environment uses Win XP SP2 for clients, ... Common sense tells me that if I have the Front End in the server then ... But it *seems* that in a shared environment it is better to have each ... I have the Front End living on client's workstations as opposed to ...
    (comp.databases)