asked on

Exchange 2010 - Cannot find recipient update service ...

Hi,

I have Exchange 2010 installed on one machine in a single domain forest (not sure if I said that correctly -- it's two servers in the same AD domain) . The single Exchange 2010 server install is working fine.
I am installing a second Exchange 2010 server in the same domain to act as a backup and to use for DAGs.
I got past all the pre-reqs and am left with warning message under mailbox role prerequisites that says
" Cannot find recipient update service responsible for domain DC=XXXXXXX ...."

Can I push on through that warning or is there something I should take care of first?
Thanks,
Mike

Saoi

Hi,

I would make sure the health of your system is 100% before adding a new server. If you run the Exchange Best Practices Analyser on the first server, does it throw up any issues?

Is your Exchange 2010 an upgrade from Exchange 2003? If so, when you upgraded did you remove the RUS from the old server? That error is normally associated with upgrading, so there could be an artifact left from an upgade:

The Recipient Update Service is the next to remove from the Exchange Server 2003 server. Open the Exchange System Manager and in the Recipients Container select the Recipients Update Service (domain). Right click this Recipient Update Service and select “Delete”. To remove the Enterprise Recipient Update Service it’s not possible to use the Exchange System Manager. To remove this you have to use ADSIEdit.

Open ADSIEdit and open the Configuration Container in Active Directory. Navigate to the

“CN=Recipient Update Services,CN=Address Lists Container,CN=Inframan, CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=inframan,DC=local”

container. There you’ll find the Recipient Update Server (Enterprise) object. Right click this object and select “Delete”.

From http://www.simple-talk.com/sysadmin/exchange/upgrade-exchange-2003-to-exchange-2010---part-ii/

Sam

nachtmsk

ASKER

Hi Sam,

Yes, this was an upgrade from Exchange 2003. I did not remove the RUS from the old server. It's too late now as the old server is off line.
I'll run the health check as you suggested and see if that brings back anything.

Since I'm not able to remove the RUS from Ex2003 any longer, do I have another way to get past this error message?

Thanks,
Mike

ASKER CERTIFIED SOLUTION

Saoi

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

nachtmsk

ASKER

Hi,

I ran ADSIEdit on the 2008 domain controller (see attached screen shot).
There don't appear to be any records for CN=Recipient Update Services. Should I just delete the container/folder called CN=Recipient Update Services? I have a feeling that's not a good idea to delete that.

Thanks,
Mike

Screen-shot-2011-03-23-at-9.55.3.png

nachtmsk

ASKER

One more thing. I did find some references to my old Exchange 2003 server. See attached.
Should I delete these references?

Screen-shot-2011-03-23-at-9.59.5.png

SOLUTION

Saoi

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Saoi

Cross-over posting there - the references to your old Administrative Group are left there by your Exchange 2003 uninstall. You can safely remove the CN=EXCHANGE2003 and everything below it (that may well stop the warning for the Exchange 2010 install). You shouldleave the First Administrative Group in place.

Sam

nachtmsk

ASKER

Sam,
Thanks!
Removing that Exchange 2003 container fixed the issue, the warning message is gone.

One other related question - When I run Exchange Best Prac Analyzer, it shows the Exchange 2003 server still. It errors out when it tries to connect of course. I'm assuming there are other records that reference Exchange 2003 in ADSI Edit.
If I run ADSI Edit using "Default Naming Context" I see an Exchange 2003 record(See attached). I'm guessing this is why it's showing up in the BPA.
Safe to remove? Or should I just leave it -- it doesn't seem to be hurting anything.

Thanks again!
Mike

Screen-shot-2011-03-23-at-10.15..png

Saoi

Great, glad it's fixed the warning!

Under "default naming context" the reference to EXCHANGE2003 is the computer object in the "Computers" OU - it's best if you remove that via Active Directory Users and Computers console.

Did you re-run the ExBPA after removing the Exchange 2003 container? It should read the configuration directly from your active directory on your domain controller (which is what you are editing with ADSI Edit) but it's possible that there is some delay in updating what it sees if there's another DC it's looking at? Give it a few hours for replication to complete.

nachtmsk

ASKER

Thanks very much for the help!

Albert Widjaja

Hi All,

Does deleting the CN=Recipient Update Services container fix the issue with the following error message:

Cannot find the Recipient Update Service responsible for the domain.

I can't proceeed in patching the SP1 into SP3 because of this issue.