How to remove Small Business Server 2003 from domain using new server 2008 domain controller
My main goal here is to remove / retire the aging Small Business Server 2003 from the domain. The server 2008 file server will take over the PDC, DNS and other master roles. (Once the SBS is removed, I will reinstall as a 2008 DC.)
Here is what we have in the domain:
Small Business Server (SBS) 2003 Std - currently only function is Domain Controller and DNS
Server 2008 Std - Exchange 2007
Server 2008 Std - File Server, Domain Controller, DNS, Schema Master, Global Catalog
Server 2003 R2 Std - Terminal Server
Current issues: The 2008 file server is a domain controller, but is not properly replicating sysvol and netlogon.
I have tried moving the FSMO roles to the 2008 file server / DC, but it will not operate without the SBS. Cannot figure out why.
I have considered creating a new domain with the 2008 DC and then joining the Exchange and terminal servers, but I understand that I would have to reinstall Exchange and possibly the terminal server.
Any recommendations?
dcdiag-mtn-file-for-web.txt
Here is what we have in the domain:
Small Business Server (SBS) 2003 Std - currently only function is Domain Controller and DNS
Server 2008 Std - Exchange 2007
Server 2008 Std - File Server, Domain Controller, DNS, Schema Master, Global Catalog
Server 2003 R2 Std - Terminal Server
Current issues: The 2008 file server is a domain controller, but is not properly replicating sysvol and netlogon.
I have tried moving the FSMO roles to the 2008 file server / DC, but it will not operate without the SBS. Cannot figure out why.
I have considered creating a new domain with the 2008 DC and then joining the Exchange and terminal servers, but I understand that I would have to reinstall Exchange and possibly the terminal server.
Any recommendations?
dcdiag-mtn-file-for-web.txt
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
All SBS installations have various licensing limits by default, no matter what version of SBS you are running or the type of license you have. To correctly remove these and start moving FSMO roles around, you must purchase the transition pack to change the SBS back to a normal domain controller. You will not be able to start doing things like moving FSMO roles while the SBS is still an SBS - because the SBS is NOT a normal server, and won't be until after the transition pack is run.
If Exchange is not on a DC then you can safely move the FSMO roles back to the SBS, and you must in order to stop unwanted, random shutdowns of the SBS in the future.
Your first step is to sort out the FSMO roles and demote the 2008 DC, then run the transition pack, then you can reinstall the 2008 DC and start migrating as per the procedure I posted above.
-tigermatt
If Exchange is not on a DC then you can safely move the FSMO roles back to the SBS, and you must in order to stop unwanted, random shutdowns of the SBS in the future.
Your first step is to sort out the FSMO roles and demote the 2008 DC, then run the transition pack, then you can reinstall the 2008 DC and start migrating as per the procedure I posted above.
-tigermatt
ASKER
Okay, I ordered the transition pack yesterday for overnight delivery. Once it arrives (hopefully soon) I will perform the above procedures. (I have already transferred all roles except Schema Master back to SBS.) Thanks for your help and I'll let you know how it goes.
:-)
ASKER
So I followed tigermatt's procedures, except for a couple of notes:
- There was an existing error with the sysvol replication on newly transitioned small business server that had to be addressed before promoting the other server.
- I waited 2 days before demoting the transitioned small business server to make sure everything was working properly still and allow replication.
- Demoting the transitioned small business server gave an error, so I forced the dcpromo. It did not remove the server from DNS, so I had to manually go in and remove all entries pointing to the old server in DNS.
The old small business server is completely out of the picture and everything is functioning just fine.
Thanks, tigermatt!
- There was an existing error with the sysvol replication on newly transitioned small business server that had to be addressed before promoting the other server.
- I waited 2 days before demoting the transitioned small business server to make sure everything was working properly still and allow replication.
- Demoting the transitioned small business server gave an error, so I forced the dcpromo. It did not remove the server from DNS, so I had to manually go in and remove all entries pointing to the old server in DNS.
The old small business server is completely out of the picture and everything is functioning just fine.
Thanks, tigermatt!
ASKER
Thanks, tigermatt. You gave the complete solution that Microsoft could not due to their narrow areas of expertise. In fact, I spoke with four Microsoft engineers on this issue and they never mentioned the transition pack.
You're welcome, glad it's sorted :-)
ASKER
The current issue is that the new 2008 DC will not replicate the sysvol/netlogon and properly act as a PDC. (the dcdiag is attached to the original posting) Is this due to not running the transition pack? I just think that we may go through the transition pack and still be stuck with this same issue.
Does the transition pack just change the 75 user limit and the FSMO role restrictions? We use business licensing instead of OEM licensing. I don't know that Microsoft has an option for business licensing for the transition pack but am looking into it.