My goal is to provide redundancy. I did not set up the network this way--the last company was in the process of eliminating DC1 and moving to DC2 the year before I was hired (they had been with us a year and were changing things from the way the original
IT guy configured things). The two issues preventing me from eliminating DC1 is some old databases on DC1, and the fact that I want redundancy (in worst case scenarios, such as tombstone, I can replicate with DC1). DC1 is Windows Server 2003 32-bit
that is the Schema Master. DC2 that is Windows Server 2008 R2 64-bit that fulfillsall other FSMO roles. Right now, these servers are not providing redundancy--even though AD is replicating fine.
When DC2 is down, noone can log on (including thin clients--there is a separate terminal server, but DC2 has all of the licenses) even though AD replicates fine between DC1 and DC2.
When DC1 is down, noone can access Webmail& possibly other things, but can log in--even though that is on an exchange server. The user gets this error page in their browser:
| Outlook Web App didn't initialize. If the problem continues, please contact your helpdesk. | |
| The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers. | |
Request
Url: https://mail.my-fca.com:443/owa/auth/error.aspx?url=https://mail.my-fca.com/owa/&reason=0
User host address: 72.78.200.24
OWA version: 14.0.722.0
Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.
Call stack
Inner Exception
Exception type: Microsoft.Exchange.Data.Directory.NoSuitableServerFoundException
Exception message: The Microsoft Exchange Active Directory Topology service on server localhost did not return any suitable domain controllers.
Call stack