Wednesday, November 28, 2012 6:53 PM
I'm planning an SBS 2003 to 2008 R2 Standard\Exchange 2010 migration for a client per this protocol. My research seems to indicate that at the end of the process the source SBS box must have Exchange uninstalled, DCPROMO'd down, and removed from the domain. The client now wants to keep the old SBS server online due to a proprietary app that they cannot migrate to the new system. So my question is simple, is it possible to keep the demoted server as a member server, or even a domain controller? Now that I think about it, I believe that demoting the server starts hourly reboots, so I guess my question is actually whether the source SBS server can remain in the domain as a domain controller.
TIA for any assistance
- Edited by Michael Salm Wednesday, November 28, 2012 6:58 PM
Thursday, November 29, 2012 8:47 AMModerator
You cannot remove Flexible Single Master Operations (FSMO)roles from the SBS 2003 Server and use it as a member server. The FSMO roles, the Global Catalog, and the Operations Master role must remain on the SBS machine. While the software will not stop you from moving these roles off to another domain controller, once you do, the server will shut itself down every hour or so until you either put the transferred roles back or you remove the SBS machine from the domain altogether. This product is mainly intended for use in a single-location environment. Once you expand to any sort of multi-location environment, you will run up against these limitations.
For more information, please also refer to the following Microsoft TechNet blog:
On Site: Is Small Business Server Right For You?
TechNet Community Support
- Marked As Answer by Arthur_LiMicrosoft Contingent Staff, Moderator Monday, December 03, 2012 4:45 AM
Thursday, November 29, 2012 3:11 PMThanks Arthur.