acconsultant
asked on
SBS 2000 Migration to Windows 2003 AD - REMOVE SBS
Network currently has SBS 2000 as the core server for AD. Previous IT team had implemented Exchange 2007 one of the servers on the network. Current objective is to move away from SBS all together but keep all AD information along with Exchange 2007 site. We've called Microsoft on this case and they had recommended us to either utilize the Transition Pack or just to purchase the licensing for Windows 20003 and decomission the SBS server (after seizing all FSMO roles from the SBS server). Question is:
* If we just seize all the FSMO roles from the SBS server, what are the precautions or gotchas that we should be looking for?
* If the Transition Pack has no technical values (besides software cost savings), should we even consider that solution?
All in all, the software cost factor is not an issue for us. Our bottom line to get away cleanly from SBS but retain our current AD and Exchange infrastructure. Please help if you have the migration experience. Thanks in advance.
* If we just seize all the FSMO roles from the SBS server, what are the precautions or gotchas that we should be looking for?
* If the Transition Pack has no technical values (besides software cost savings), should we even consider that solution?
All in all, the software cost factor is not an issue for us. Our bottom line to get away cleanly from SBS but retain our current AD and Exchange infrastructure. Please help if you have the migration experience. Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Thanks for the comments on this topic guys. I've already gone through the documents you had posted. I guess the core of my questions are:
1. Technically, how does the Transition Pack help with migrating away from SBS infrastructure.
2. If we were to seize the roles on another 2003 DC and turn off the SBS server, what harms or effects would that have on AD?
1. Technically, how does the Transition Pack help with migrating away from SBS infrastructure.
2. If we were to seize the roles on another 2003 DC and turn off the SBS server, what harms or effects would that have on AD?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Seizing the roles or transferring the roles planned steps in our project, but how can you "decommission" the SBS server? I thought you can't DCPROMO an SBS server?
Decommission. Not Demote.
Decommission means remove, retire, deactivate or shut down :)
http://dictionary.reference.com/browse/decommission
So basically throw it into the bin.......no just kidding. You can reformat the hard disk and use it for other purpose.
Decommission means remove, retire, deactivate or shut down :)
http://dictionary.reference.com/browse/decommission
So basically throw it into the bin.......no just kidding. You can reformat the hard disk and use it for other purpose.
ASKER
I accepted your answer but a "DECOMMISSION" leaves the rogue DC on AD thus creates NTDS replication errors in system logs. Anyhow, we turned off the SBS and performed a metadata clean up for the SBS.
However, I must admit I was unfamiliar with the transition pack. I read up on it a bit for this post and in theory this would seem like the easier solution. Just install and the SBS limitation is released, giving you the situation you wanted.
I'm not sure if this works as easy in practice though, as I haven't ever tried it. But given the situation I think I'd opt for that this time.
Good luck in your decision.