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

Complete SBS 2003 Migration to standalone Server 2008 and Exchange 2010

I took over a network where the SBS 2003 was not fully migrated. The old SBS box still has Exchange running (Exchange 2010 has all the mbx migratedas well as FSMO roles (Schema, PDC, Infrastructure). What are the proper steps to complete the migration. Plus their userdomain is: domain.local and userdnsdomain domain1.local

thank you
0
piotrmikula108
Asked:
piotrmikula108
  • 3
  • 2
1 Solution
 
KaffiendCommented:
Or, look for demazter's guide - he wrote a detailed guide here on EE for exactly your scenario - SBS2003 to Exchange 2010/Windows2008

Look under "articles"
0
 
piotrmikula108Author Commented:
Thank you Kaffiend.

Side question, we're having problems with that SBS box (keeps crashing) if the server died and was not recoverable what happens with migrating the remaining FSMO roles and uninstaling Exchange from the box to cleanly complete the migration? Can the roles be recreated on the primary DC or this is not as simple?
0
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.

 
KaffiendCommented:
Your SBS box *might* be doing exactly what it is supposed to do.

Once FSMO roles have moved to another server, one will have 21 days before it (the SBS box) shuts itself off automatically every hour.

Check your Win 2008 box to see if it thinks it is the FSMO role(s) holder.
0
 
piotrmikula108Author Commented:
well it's not doing this every hour, maybe once a day
the 2008 box only holds 2 roles
0
 
KaffiendCommented:
Assuming that replication has been working between SBS and your new server, then you should be able to seize FSMO roles (if necessary) without any adverse effects.

It would be nice to be able to cleanly uninstall Exchange 2003, but if the SBS server dies completely tomorrow, it really won't hurt too much.  Look for and delete the Routing Group Connectors (using EMS).


Oh, and as if that wasn't enough, you will *still* have to contend with the 21-days thing sooner or later (at the latest, in 20 days, since you've already moved some FSMO roles).   :-(

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

Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

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