Coexistance with Exchange 2003 and 2010 Error with RUS during mailbox role install
We have a single forest with three domains, domainA.org, domainB.local and mynewdomain.local. DomainA.org was the first domain of the forest and has Exchange 2003 Standard DomainB.local was the first child domain of the forest and has Exchange 2003 Enterprise We're now adding mynewdomain.local with CAS role on a node and MBX role on a node. During the mailbox role installation today I receive this: Mailbox Role Prerequisites Warning: Cannot find the Recipient Update Service responsible for 'DC=mynewdomain,DC=local. New and existing users may not be properly Exchange-enabled. I thought I read RUS was no longer part of 2010... Do I need to go into 2003's configuration and set up a policy for mynewdomain.local or can this warning be safely ignored?
March 23rd, 2012 11:02am

In our Recipient Update Services of 2003, there is already present: Recipient Update Service (DomainB) DomainB Recipient Update Service (Enterprise Configuration) DomainA Recipient Update Service (DomainA) DomainA This indicates RUS is set up correctly, no? I still have not been able to determine if that message returned in the mailbox pre-req can be safely ignored?
Free Windows Admin Tool Kit Click here and download it now
March 26th, 2012 9:28am

If the ones in DomainA & DomainB are working it can be ignored. Did you have a 3rd domain, maybe for testing, at some point? If so it's possible it didn't get decommissioned correctly. I've installed 2010 multiple times with this warning and haven't had any issues. In most of those cases there was a root domain that never had 2003 in it, but it still caused this warning to come up.Microsoft Infrastructure Architect, MCSE: M, MCTIP, Microsoft Exchange MVP http://info.izzy.org | http://jasonsherry.org | Twitter: @JasonSherry
March 26th, 2012 7:35pm

Hi, Please refer to the article below, we need to run Setup /PrepareLegacyExchangePermissions in each domain that has a domain Recipient Update Service. Setup Cannot Find the Recipient Update Service When Preparing Legacy Exchange Permissions http://technet.microsoft.com/en-us/library/bb676693(v=exchg.80).aspx Note: If you have run Setup /PrepareLegacyExchangePermissions in each domain and have verified that the Recipient Update Services are functioning correctly, you can safely ignore this warning. Xiu Zhang TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
March 27th, 2012 3:00am

To my knowledge, there has never been a 3rd domain for testing or otherwise. I pushed on past the warning and installed the 2010 mailbox role anyway. When I went through the 'new mailbox' on an existing user wizard, those accounts do not get stamped with the correct primary SMTP address. In 2010, tried to create an Exchange Address Policy for 'mynewdomain.local' in 2010 and received: Error: You can't specify the recipient container because legacy servers are detected. So I created a Recipient Policy in our 2003 environment for 'mynewdomain.local' and now adding new mailboxes to users in 'mynewdomain.local' do get the correct primary SMTP. Is there a way to find out what I may be doing wrong to require a Recipient Update Policy in our 2003 environment in order for our 2010 environment to stamp primary SMTP addressing correctly?
March 27th, 2012 9:35am

Hi, I recommend you to have a health scan(ExBPA) of the current organization. E-mail Address Policy is built on LDAP queries in Exchange 2003. When we have Exchange 2010 installed, we need to upgrade the E-Mail Address Policies and Address Lists to use OPATH filters. If you want to create custom email address policy, then please try to use recipientfilter from EMS. Email Address Policy and OPATH filters http://blogs.technet.com/b/evand/archive/2006/09/14/email-address-policy-and-opath-filters.aspxXiu Zhang TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
March 28th, 2012 2:11am

Any update?Xiu Zhang TechNet Community Support
April 2nd, 2012 2:07am

In 2010's Exchange Management Console, I tried to create an Exchange Address Policy for 'mynewdomain.local' and received: Error: You can't specify the recipient container because legacy servers are detected.
Free Windows Admin Tool Kit Click here and download it now
April 10th, 2012 11:00am

Hi, Please try to update the address policy via Update-EmailAddressPolicy cmdlet. Upgrade the Default E-Mail Address Policy from LDAP Filters to OPATH Filters http://technet.microsoft.com/en-us/library/dd351283.aspxXiu Zhang TechNet Community Support
April 10th, 2012 11:28pm

Hi, Please try to update the address policy via Update-EmailAddressPolicy cmdlet. Upgrade the Default E-Mail Address Policy from LDAP Filters to OPATH Filters http://technet.microsoft.com/en-us/library/dd351283.aspx Xiu Zhang TechNet Community Support Doesn't this Update-EmailAddressPolicy need a policy first? I'm actually still trying to create a new Email Address Policy in 2010 without involving 2003. Is that not the right procedure?
Free Windows Admin Tool Kit Click here and download it now
April 11th, 2012 8:31am

Hi, It will update the default emailaddresspolicy in Exchange 2003 to Exchange 2010.Xiu Zhang TechNet Community Support
April 11th, 2012 10:55pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics