>I'm sorry I wasn't specific enough...I'm not talking
>the other server permanently going down. I'm talking
>about for the several hours it would take to rebuild it
>from backups or replace failed hardware. Also we're
>talking about 50-75 mailboxes/users, so is the
>degredation still an issue? This is a small network, so
>when you say, "anywhere on the network", there are 2
>servers total...one of which is currently a Global
>server...It sounds to me as though you are suggesting
>the benifits of having both servers be GC Servers would
>probably outweigh the performance issue?
>>Is this your ONLY Global Catalog server anywhere on the
>>If it is, and it goes down, you're going to have worse
>>problems then Exchange not working. It may still allow
>>to login (in a single domain configuration), but you're
>>going to have problems.
>>Yes, there is a downside to having Exchange run on a
>>Global Catalog server. Performance will suffer, but it
>>be done... but not a 'best practice'.
>>>I have a single domain configuration where there are 2
>>>Windows 2000 Servers. ServerA is an Active Directory
>>>Domain Controller and holds all FSMO roles as well as
>>>Global Catalog. ServerB is also a DC, which is running
>>>If ServerA goes offline, will ServerB (exchange server)
>>>able to function in the absence of a Global Catalog
>>>Server? If the answer is no...then is there any
>>>to also making ServerB a Global Catalog Server?
>>>The goal is to make sure the Exchange server can
>>>independently (being the only server running).