RE: setting up domain name aliases
- From: "Mulnick, Al" <Al.Mulnick@xxxxxxxxxx>
- To: "'[ExchangeList]'" <exchangelist@xxxxxxxxxxxxx>
- Date: Wed, 5 Nov 2003 15:18:26 -0500
The delay in replication within Exchange is not the only latency you're
waiting for. The DS2MB process has to run after the Active Directory has
replicated the changes and there is also some store caching times that have
to be accounted for.
Sounds like you found the culprit however.
Al
-----Original Message-----
From: A. Michael Salim [mailto:msalim@xxxxxxxxxxxx]
Sent: Wednesday, November 05, 2003 3:12 PM
To: [ExchangeList]
Subject: [exchangelist] RE: setting up domain name aliases
http://www.MSExchange.org/
Hi,
> After implementing, how long did you wait?
Just a few minutes. It now seems to have "magically started working", after
about 2-3 hours. I did not think that AD propogation delays could take that
long.
> When you set up the recipient policy, did you set the server as
> responsible for the domain or are you sharing it?
not sharing, set it as "server is responsible". I also have many other
unrelated domains on the sae Exchange 2003 server (as a hosted ASP
environment, each has their own independent setup).
best regards
Mike
------------------------------------------------------
List Archives: http://www.webelists.com/cgi/lyris.pl?enter=exchangelist
Exchange Newsletters: http://www.msexchange.org/pages/newsletter.asp
Exchange FAQ: http://www.msexchange.org/pages/larticle.asp?type=FAQ
------------------------------------------------------
Other Internet Software Marketing Sites:
Leading Network Software Directory: http://www.serverfiles.com
No.1 ISA Server Resource Site: http://www.isaserver.org Windows Security
Resource Site: http://www.windowsecurity.com/ Network Security Library:
http://www.secinf.net/ Windows 2000/NT Fax Solutions:
http://www.ntfaxfaq.com
------------------------------------------------------
Other related posts:
