I noticed that "Recipient Update Services" (RUS) is only configured to use 1 of my Domain Controllers. If that DC goes down, Exchange will not automatically connect to another DC in the domain(will it?). I see that in http://support.microsoft.com/default.aspx?scid=kb;en-us;319065
I can add and configure another Domain Controller here. WOULD IT HURT MY DOMAIN, MY AD REPLICATION, OR ANYTHING ELSE, if I configure my only 2 DC's to both be Recipient Update servers? I'm assuming that if one went down Exchange knows to continue using the next avaiable server and use it (so the domain stays fully operational) - is this correct? PLEASE ELABORATE AND/OR GIVE TECH REFERENCES ON THE WEB.
See info below for what I already have know. IS THERE ANYTHING ELSE I can do to make a single Exchange server more resilient in the event of a DC or DNS server being powered down/taken offline/crash? I'm currently reviewing MS's "Exchange 2003 Disaster Recovery Planning Guide." http://www.microsoft.com/downloads/details.aspx?FamilyId=784BBEA2-28DD-409A-8368-F9914E993B28&displaylang=en
Redundacy for Recipient Update Services in Exchange: How to Add a New Recipient Update Service
To add a new Recipient Update Service: 1. Click Start, point to Programs, point to Microsoft Exchange, and then click System Manager.
2. Expand the Recipients object, and then click the Recipient Update Services container.
3. Right-click Recipient Update Services, point to New, and then click Recipient Update Service.
4. Click Browse next to "Domain" to display a list of domains in your forest.
5. Click the domain that you want this Recipient Update Service to update, and then click OK.
6. Confirm that the domain that you selected is displayed in the New Object - Recipient Update Service dialog box, and then click Next.
7. Click Browse, click the Exchange server on which you want this instance of the Recipient Update Service to run, and then click OK.
8. Click Next.
9. Click Finish.
10. Right-click the new Recipient Update Service object that you created, click Properties, configure the Update interval setting, and then click OK.
Note When you are creating a Recipient Update Service, you cannot select the domain controller. You can only select the domain that you want the new Recipient Update Service to be associated with. After you have finished creating the Recipient Update Service, you can edit the properties of the Recipient Update Service and select the domain controller that you want.
Redundancy for DNS in Exchange 2003:
When I took down one of my DC's for maintenance the other day and my Exchange server stopped functioning correctly - couldn't resolve external DNS to send mail. I thought since the server NIC had two internal DNS servers listed (the one taken down plus another DC/DNS server) it would automatically forward all requests to the secondary DNS server listed in the NIC config.
I then found about the setting (in Exchange) that lets you tell Exchange directly) what DNS servers to use. See below
Directly setting DNS Servers in Exchange System Manager
1. Start Exchange System Manager.
2. Expand Your_Organization (where Your_Organization is the name of your Exchange organization).
3. Expand Servers, and then expand Your_Server (where Your_Server is the name of your server).
4. Expand Protocols, and then expand SMTP.
5. Right-click Your_SMTP_Virtual_Server (where Your_SMTP_Virtual_Server is the name of your SMTP virtual server), and then click Properties.
6. Click the Delivery tab, and then click Advanced.
7. Click Configure next to Configure external DNS Servers.
8. Click Add, type the IP address of your internal\external DNS servers, and then click OK