• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 356
  • Last Modified:

How will new domain impact exchange server

I am upgrading our active directory from Windows Server 2003 R2 to Windows Server 2008 R2.  I feel we should just do a simple upgrade by adding the new server as an extra domain controller and demoting the older one.  However, our senior developer feels we should build a new active directory from the bottom up.  Although this does sound like a decent idea, we have an exchange server in place and I am unsure as to how doing that will impact the exchange server.  

What would be the best course of action?
0
JFrusci
Asked:
JFrusci
2 Solutions
 
Don S.Commented:
My experience leads me to try to use the existing domain and upgrade it rather than start over - unless it is very small (say a dozen or fewer comptuers/users) and/or it is named horribly wrong or has other major irreconcilable problems.  You will find the tools in 2008 and beyond help you clean up a lot of past transgressions.  Remember, starting over from scratch means rejoining all computers, redoing all file and object permissions, rebuilding all user and groups on all servers and computers.  Its a big deal.
0
 
Kamalasekar ParthasarathyMessaging SupportCommented:
Instead of going new one, you have to install additional domain controller in 2008 r2 and move all the fsmo roles.

This is the best way to do do the migration.
0
 
JFrusciAuthor Commented:
I know how to do the migration.  I've had to move FSMO roles in the past.  I am just unsure if I build a new active directory, how that will impact the exchange server.  
0
Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

 
skaraiCommented:
Question is do you want just a new AD or a new forest as well?  A new domain can be created in your existing forest no problem. You can then create trust relationships between them and allow use of the exchange server fro the new domain.
0
 
Don S.Commented:
If you leave the old domain in place and create a new one, you can establish trusts to get Exchange to work ok.  If the domain that exchange is in currently is to go away completely, then you will basically need to install a new instance of exchange into the new domain and migrate the mail to it.  - icky.
0
 
RadweldCommented:
I would not advise a new domain, the time and trouble moving resources doesn't make it a quick process. When ever I consult with customers looking to perform cross forest migrations were looking at least 20 days

You would have to build the domain
Configure trusts
Perform some kind of ad migration using ADMT
Manually export users in source and import a contact in target
Move mailboxes
Update users outlook profiles
And more.

This doest take into account gal sync and free busy between the two.

Unless your original domain is really bad, I would add the new dc move all roles onto it and demote the old one. You can then raise the fictional levels.
0
 
JFrusciAuthor Commented:
I have decided to keep the existing domain and just add to it.  The new DC will be server 2008 R2 and I will use those tools to clean up active directory.
0

Featured Post

Easily manage email signatures in Office 365

Managing email signatures in Office 365 can be a challenging task if you don't have the right tool. CodeTwo Email Signatures for Office 365 will help you implement a unified email signature look, no matter what email client is used by users. Test it for free!

Tackle projects and never again get stuck behind a technical roadblock.
Join Now