Exchange 2010 Migration from Exchange 2007 - Can I dedicate a hub-transport role to a specific server during migration?

I have an extremely large, crowded Exchange 2007 server running all (3) Exchange roles (CAS, Hub-Transport, Mailbox).  I am migrating to a distributed Exchange 2010 environment with multiple Mailbox servers, and dedicated servers for each of CAS / Hub-Transport.

At our first migration attempt of a batch of 10 users, the server had big issues after the move with email delivery.  Delays of inbound email to users on the original Exchange 2007 server, delays of outbound email from users on the original Exchange 2007 server, BUT the users migrated to the new Exchange 2010 system experienced NO issues at all.

Inbound email from the firewall still arrives at the original Exchange 2007 Hub Transport server and that has not changed...so it does not make sense that after the migration all users still on the 2007 system were having delay issues and users on the Exchange 2010 server were NOT.  I did notice that the pre-submission queue database was quite large at the time (3+GB).  A reboot of the Exchange 2007 server eventually solved all of these delay issues, restarting individual Exchange services did not (Transport service, info store, IIS in general).

What I wanted to do to prevent this was to create a dedicated Exchange 2007 Hub-Transport server (as a VM) and bridgehead that to be the server that does the moving of messages to the Exchange 2010 systems.  How can I do this?  I feel like this would alleviate the load and let us migrate the balance of the users (almost 1000 users in total) without affecting the existing services of the already overloaded server.

Does anyone have any insight as to how this can be completed?
LVL 5
jkeegan123Asked:
Who is Participating?
 
Simon Butler (Sembee)Connect With a Mentor ConsultantCommented:
I am pretty sure that it cannot be done as there isn't that level of control in the system.
The only thing you can do is specify the source server on the send connectors.

I would also point out that the model you have on Exchange 2007 is now the preferred design for Exchange 2010. Lots of servers all holding the three roles. I don't think I have split the roles in any design I have done in the last 18 months. The I/O requirements on Exchange 2010 have dropped considerably.

I would have all email delivered to the highest version of Exchange in the system (so preferably Exchange 2010 SP3) and let Exchange process the email, taking immediate advantage of improvements in transport handling that Exchange 2010 provides.

Simon.
0
 
jkeegan123Author Commented:
I've requested that this question be deleted for the following reason:

No acceptable answer
0
 
Simon Butler (Sembee)ConsultantCommented:
I object to the question being deleted.
There was no feedback from the OP, and as clearly stated, "You cannot do that" is an acceptable answer.
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.

 
jkeegan123Author Commented:
Sorry Sembee, I didn't want to accept your answer as correct because of the comment of holding all 3 roles on all of your recent implementations.  While this is certainly a configuration that will WORK, for security reasons, I think it's best to have a front facing server (i.e. CAS in DMZ) NOT holding any mailbox / public folder data.  

As for "you can't do that" ... we are still working on the best way to do this.  We have 1500+ mailboxes waiting to migrate, and when we do, the load of messages transferring form some of the LARGER mailboxes (20GB+) causes significant delays in the inbound delivery queues...I can dedicate transport servers to specific connectors, and nail a specific connector to a namespace, but can't quite get one together that would be JUST doing transfers for moved mailboxes....when you initiate a mailbox move, it basically just creates a mailbox on the target server and mails everything there.
0
 
Simon Butler (Sembee)ConsultantCommented:
CAS in DMZ is not supported. Putting any role of Exchange 2007 or higher other than EDGE in a perimeter network is not supported.
Splitting the roles out does NOTHING for security.

Simon.
0
 
jkeegan123Author Commented:
Answer to question is:  NOT POSSIBLE, so this answer is technically correct.
0
 
Simon Butler (Sembee)ConsultantCommented:
Not possible is a correct answer, and does not justify a C grade.
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.

All Courses

From novice to tech pro — start learning today.