<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Exchange Issues</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/exchange-issues/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-issues/</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 19:19:38 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: dlevine</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/exchange-issues/#comment-46695</link>
		<dc:creator>dlevine</dc:creator>
		<pubDate>Mon, 16 Oct 2006 00:27:36 +0000</pubDate>
		<guid isPermaLink="false">#comment-46695</guid>
		<description><![CDATA[Steve is right on how to handle incoming email for the new domain name... but just to be sure...

Make sure that you add the new domain name to a policy in the Exchange System Manager&#039;s Recipient Policies container. This can be your default policy, or you can create a new one.

Make sure that whoever is hosting your public DNS adds an MX record for the new domain and points it at your exchange server&#039;s public IP (or hopefully your SMTP relay host&#039;s IP address!)

As for the second part... Active Directory does not have Primary Domain Controllers and Backup Domain Controllers. It is a multi-master topology - so all domain controllers have a read/write copy of the directory database. You do however have FSMO roles... one of which is the PDC emulator.

Anyway - it sounds to me like you have a pretty small network - so I would not worry about installing Exchange on a second system.... especially if your system is another DC. 

Having 2 systems configured as domain controllers is good for any sized network. Make sure that each DC is running DNS &amp; WINS, and make sure they are both Global Catalog Servers. It is also not a bad idea to have both running DHCP - but *make sure* that you split your scope up so that you do not have any overlap! This is handy if you have one of your 2 server systems go down - you will still have all of your basic infrastructure functioning as it should. 

Now - for Exhcange redundancy... if you have the money for the licensing costs and hardware costs, a 2nd installation of Exchange with DoubleTake is great. However, for a small network, I might suggest that you stick with the single install and just make sure that you have your backup and restore process well documented. If you have a couple of old workstation systems, you could even set them up as a test network and practive your recovery process there. In addition to making you more prepared for an actual event, you will also be testing the integrity of your backup media which is more valuable than you know... 

Put together a basic DR kit. Instructions on how to do the entire restore process, all required software media, all required lic keys, all required information, like domain names, org names, etc., unattended answer files, phone numbers to people who can help, etc...

If you want to use something like Ghost to enhance your backup routines, that is great - just make sure that you do not install the Ghost client on any servers with hardware or software RAID configs... (trust me). Taking a monthly backup image of a system can be very useful in speeding up recovery times.

Now - when you use the *Exchange version* of AD Users and Computers... are you running that from the 2nd Domain Controller or from your Workstation? (You did install the Exhcange Management Tools on your workstation, right?)

Best of luck...
---
David Levine]]></description>
		<content:encoded><![CDATA[<p>Steve is right on how to handle incoming email for the new domain name&#8230; but just to be sure&#8230;</p>
<p>Make sure that you add the new domain name to a policy in the Exchange System Manager&#8217;s Recipient Policies container. This can be your default policy, or you can create a new one.</p>
<p>Make sure that whoever is hosting your public DNS adds an MX record for the new domain and points it at your exchange server&#8217;s public IP (or hopefully your SMTP relay host&#8217;s IP address!)</p>
<p>As for the second part&#8230; Active Directory does not have Primary Domain Controllers and Backup Domain Controllers. It is a multi-master topology &#8211; so all domain controllers have a read/write copy of the directory database. You do however have FSMO roles&#8230; one of which is the PDC emulator.</p>
<p>Anyway &#8211; it sounds to me like you have a pretty small network &#8211; so I would not worry about installing Exchange on a second system&#8230;. especially if your system is another DC. </p>
<p>Having 2 systems configured as domain controllers is good for any sized network. Make sure that each DC is running DNS &amp; WINS, and make sure they are both Global Catalog Servers. It is also not a bad idea to have both running DHCP &#8211; but *make sure* that you split your scope up so that you do not have any overlap! This is handy if you have one of your 2 server systems go down &#8211; you will still have all of your basic infrastructure functioning as it should. </p>
<p>Now &#8211; for Exhcange redundancy&#8230; if you have the money for the licensing costs and hardware costs, a 2nd installation of Exchange with DoubleTake is great. However, for a small network, I might suggest that you stick with the single install and just make sure that you have your backup and restore process well documented. If you have a couple of old workstation systems, you could even set them up as a test network and practive your recovery process there. In addition to making you more prepared for an actual event, you will also be testing the integrity of your backup media which is more valuable than you know&#8230; </p>
<p>Put together a basic DR kit. Instructions on how to do the entire restore process, all required software media, all required lic keys, all required information, like domain names, org names, etc., unattended answer files, phone numbers to people who can help, etc&#8230;</p>
<p>If you want to use something like Ghost to enhance your backup routines, that is great &#8211; just make sure that you do not install the Ghost client on any servers with hardware or software RAID configs&#8230; (trust me). Taking a monthly backup image of a system can be very useful in speeding up recovery times.</p>
<p>Now &#8211; when you use the *Exchange version* of AD Users and Computers&#8230; are you running that from the 2nd Domain Controller or from your Workstation? (You did install the Exhcange Management Tools on your workstation, right?)</p>
<p>Best of luck&#8230;<br />
&#8212;<br />
David Levine</p>
]]></content:encoded>
	</item>
</channel>
</rss>

<!-- Performance optimized by W3 Total Cache. Learn more: http://www.w3-edge.com/wordpress-plugins/

Page Caching using memcached
Database Caching 6/9 queries in 0.014 seconds using memcached
Object Caching 268/271 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-06-19 21:51:48 -->