Improve company productivity with a Business Account.Sign Up

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1032
  • Last Modified:

Exchange 2003: Change Recipient Update Service Domain Controller

We have a single forest/single domain and are in the process of decommisioning a 2003 domain controller that both the Exchange 2003 Enterprise and Domain Recipient Update Services are pointing to.  We would like to repoint the Recipient Update Services to a 2008 R2 domain controller.  Is there anything to keep an eye out for or any gotchas when performing this change?  Thanks.
0
bsohn417
Asked:
bsohn417
Advertise Here
  • 5
  • 2
  • 2
  • +1
2 Solutions
 
AmitIT ArchitectCommented:
Just browse and change it to new DC. Make sure DC is up and running when you are doing this change. Rest is simple.
0
 
Stelian StanNetwork AdministratorCommented:
Make sure you have a good backup before doing this. There are no gotchas but you have to be very careful because you have to do this using ADSi Edit: http://social.technet.microsoft.com/Forums/en-US/exchangesvradminlegacy/thread/23782bd7-9a92-452b-b327-41809bbc4dbf
0
 
AmitIT ArchitectCommented:
clonyxlro: It can be done via ESM itself. I don't think ADSIEdit is required here.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

Learn More
 
bsohn417Author Commented:
The DC RUS is currently pointing to and the DC it will be changed to are both up and running.
0
 
AmitIT ArchitectCommented:
Just change it, nothing to worry.
0
 
Stelian StanNetwork AdministratorCommented:
That's correct.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
I second Amit to simply change the DC for RUS from the ESM and not get into ADSIEDIT until its no otherway

Hopw you have moved the FSMO roles and ensured that your exchange can work with Windows 2008 server ??
Did you check event 2080 on the Exchange Box and also it appears in the DSAccess tab

- Rancy
0
 
AmitIT ArchitectCommented:
Good Call Rancy regarding FSMO. Also make sure 2008 DC is also a GC.
0
 
bsohn417Author Commented:
We haven't moved the FSMO roles yet but are planning to before decommisioning the DC.  FSMOs are not relevant for changing the DC the RUS's are pointing to, right?  All the DCs in the forest are GCs.
0
 
AmitIT ArchitectCommented:
Yes that is correct, FSMO roles has no relation with RU's.
0
 
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Yes FSMO roles dont have a call with RUS but just ensuring we try to cover the point and as said if RUS is repointed and all is working i guess the Post can be resolved and if you have other doubts you can call another post :)

- Rancy
"Happy New Year"
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Get 10% Off Your First Squarespace Website

Ready to showcase your work, publish content or promote your business online? With Squarespace’s award-winning templates and 24/7 customer service, getting started is simple. Head to Squarespace.com and use offer code ‘EXPERTS’ to get 10% off your first purchase.

Start Now
  • 5
  • 2
  • 2
  • +1
Advertise Here
Tackle projects and never again get stuck behind a technical roadblock.
Join Now