Decommissioning Exchange 2003 server - Roles designation?

We have recently migrated mailboxes from an Exchange 2003 server to Exchange 2007, and are in the process of decommissioning the Exchange 2003 server from the organization, following MS KB: 

However, we also have another Exchange 2003 server in the organization (in the First Administrative Group), in a child domain.

Therefore we have 2 Exchange Administrative Groups:
First Administrative Group – Server: EXCH2007
Exchange Administrative Group (FYDIBOHF23SPDLT) – Servers: EXCH2003_1, and EXCH2003_2

The Exchange 2003 server being decommissioned (EXCH2003_1) holds key roles:
OAB generation, routing group master, Recipient Policy, however is in the same administrative group (First Administrative Group) as EXCH2003_2.

In previous Exchange migrations I’ve been involved with, I’ve moved these roles over to the new Exchange 2007 server, as per caution in MS KB, (‘you must use caution when you remove this server from the administrative group that it belongs to’),

My concern is that if these roles are moved to a server in a different site / child domain to our new Exchange 2007 server, that this might cause problems?

I assume that these roles (Schedule+ Free Busy folder, RUS, Org Forms, Routing Group Master) must be rehomed to the remaining Exchange 2003 server (EXCH2003_2), rather than the Exchange 2007 server. Can you confirm that I am correct in this assumption?

With reference to RUS, our current settings are:

RUS Parent domain - EXCH2003_1
RUS Child domain - EXCH2003_2
RUS (Enterprise configuration) - EXCH2003_1

RUS is no longer used in Exchange 2007 / 2010, however assuming we want to keep EXCH2003_2, what are the settings for RUS? Is the RUS service (for parent domain and enterprise) required to be transferred to EXCH2007 or to EXCH2003_2, in order for RUS to continue functioning in the child domain (i.e. on EXCH2003_2)?

We currently have mail routed through EXCH2003_1. When EXCH2003_1 is decommissioned, mail will be routed through EXCH2007. Current RGCs are between EXCH2003_1 and EXCH2007. What action do we need to take with regards to connectors?
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

SriHarsha KTechnical Services SpecialistCommented:
Can you please make few things more clear..
- Are you planing to decommissioon your entire 2003 Exchange Enviranment ??
BethanieAuthor Commented:
Thanks for your reply.
As posted, 'The Exchange 2003 server being decommissioned is (EXCH2003_1)'.
To clarify, we are not currenlty planning do decommission the second Exchange 2003 server. This is precisely my concern, in that Exchange services are able to function correctly on the remaining Exchnage 2003 server (EXCH2003_2) when roles are transferred from EXCH2003_1.
SriHarsha KTechnical Services SpecialistCommented:

"Schedule+ Free Busy folder" can be co-existed on both the servers.
"RUS" as this is no more in exchange 2007,it will be present on the exchange 2003 server which is still exixting.
As RUS was already present on both the exchange 2003 servers.

"Routing Group Master" - For better reasons you can make the exchange 2007 server the routing Group Master and point the MXRecords to the Exchange 2007 as this is the latest server for you and route the emails from exchange 2007 server to the exchange 2003 server.

If you already have org. forms , just replicate the forlder to Exchange 2007 server and you have your forms ready to go.
You can not create new org forms library in Exchange 2007, but if you have them available in earlier version you can replicate them to Exchange 2007. Dont know if you can use interorg for replicating them across Exchange organizations.
More info

Refer these 2 articles before proceding,sorry there is good amount to read ;)
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

BethanieAuthor Commented:
Thanks for your reply. I have indeed read the 2 articles on the subject, and great as they are, they don’t actually answer these questions.
So can you confirm that it’s possible / correct / safe to designate the new Exchange 2007 server for following?
Recipient Update Service (you say that it’s already present on remaining Exchange 2003 server EXCH2003_2)
Offline Address List
Routing group master
Also can you confirm that we need to create new routing group connectors between EXCH2007and remaining Exchange 2003 server (EXCH2003_2)
Many thanks for your help.
SriHarsha KTechnical Services SpecialistCommented:
Sorry for the delay..

As RUS is already present on your existing 2003 Server,there is no need to designate to the new Exchange 2007 server.
Yes you have a create a new RGC between Exch2007 and Exch2003_@.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
BethanieAuthor Commented:
Many thanks for your help
SriHarsha KTechnical Services SpecialistCommented:
You are welcome. :)
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.