<?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: How to Configure Multiple Domains in Exchange 2003 for Hosting</title>
	<atom:link href="http://itknowledgeexchange.techtarget.com/itanswers/how-to-configure-multiple-domains-in-exchange-2003-for-hosting/feed/" rel="self" type="application/rss+xml" />
	<link>http://itknowledgeexchange.techtarget.com/itanswers/how-to-configure-multiple-domains-in-exchange-2003-for-hosting/</link>
	<description></description>
	<lastBuildDate>Wed, 19 Jun 2013 15:16:59 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: adtechjo</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-to-configure-multiple-domains-in-exchange-2003-for-hosting/#comment-37782</link>
		<dc:creator>adtechjo</dc:creator>
		<pubDate>Wed, 13 Dec 2006 14:49:07 +0000</pubDate>
		<guid isPermaLink="false">#comment-37782</guid>
		<description><![CDATA[It is not clear what your administration wants. If they actually want two different domains that recquires that members do not have access to the other domain resources then you need to set up new domain controller separate of the other. Of course you can then install a separate exchange server. You can use System Manager to control and manage both by giving spcific trust to administrator in both domains.
If you need to separate the emails only, set a domain as company.loc whereby all users are listed. Then in the exchange setup two different connectors each responsible to receive that specific domain (@company1.com) and (@company2.com). You need to setup two policies each with the different email domain. When applied, you reset each user email as primary email domain to that specific respective one

Clear out what the administration wants really!! good luck]]></description>
		<content:encoded><![CDATA[<p>It is not clear what your administration wants. If they actually want two different domains that recquires that members do not have access to the other domain resources then you need to set up new domain controller separate of the other. Of course you can then install a separate exchange server. You can use System Manager to control and manage both by giving spcific trust to administrator in both domains.<br />
If you need to separate the emails only, set a domain as company.loc whereby all users are listed. Then in the exchange setup two different connectors each responsible to receive that specific domain (@company1.com) and (@company2.com). You need to setup two policies each with the different email domain. When applied, you reset each user email as primary email domain to that specific respective one</p>
<p>Clear out what the administration wants really!! good luck</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: pdmeat</title>
		<link>http://itknowledgeexchange.techtarget.com/itanswers/how-to-configure-multiple-domains-in-exchange-2003-for-hosting/#comment-37783</link>
		<dc:creator>pdmeat</dc:creator>
		<pubDate>Wed, 13 Dec 2006 10:04:57 +0000</pubDate>
		<guid isPermaLink="false">#comment-37783</guid>
		<description><![CDATA[I&#039;ve not actually done this myself but exchange supports multiple domains in a single forest and you can only have one exchange org per forest. 

If all you wanted to do is to control a person&#039;s account so that the default send &quot;from&quot; address is &quot;acquired_co.com&quot; instead of &quot;native_co.com&quot;, you should just create a second (or third, etc) recipient update service so that when new users are created in that domain they get the other default sender address domain. Another option is to just go into each acquired_co user account and uncheck the box for the RUS to automatically update their addresses and just manually change the default SMTP address yourself.

You can still use one SMTP server (native_co.com) for sending and receiving mail as long as you point the internet MX for acquired_co.com to an A record that is a SMTP server for native_co.com.

It&#039;s up to you and your boss if you want to host the acquired_co.com users on another server possibly in another exchange administrative group.

Email disclaimers and/or content scanning will require a little thought too, if you use those services.]]></description>
		<content:encoded><![CDATA[<p>I&#8217;ve not actually done this myself but exchange supports multiple domains in a single forest and you can only have one exchange org per forest. </p>
<p>If all you wanted to do is to control a person&#8217;s account so that the default send &#8220;from&#8221; address is &#8220;acquired_co.com&#8221; instead of &#8220;native_co.com&#8221;, you should just create a second (or third, etc) recipient update service so that when new users are created in that domain they get the other default sender address domain. Another option is to just go into each acquired_co user account and uncheck the box for the RUS to automatically update their addresses and just manually change the default SMTP address yourself.</p>
<p>You can still use one SMTP server (native_co.com) for sending and receiving mail as long as you point the internet MX for acquired_co.com to an A record that is a SMTP server for native_co.com.</p>
<p>It&#8217;s up to you and your boss if you want to host the acquired_co.com users on another server possibly in another exchange administrative group.</p>
<p>Email disclaimers and/or content scanning will require a little thought too, if you use those services.</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.012 seconds using memcached
Object Caching 282/285 objects using memcached

Served from: itknowledgeexchange.techtarget.com @ 2013-06-19 15:18:29 -->