How to introduce 2012 standard server into SBS 2003 network
We have a SBS 2003 R2 Windows Server that hosts domain and other resources. As 2003 is to be phased out, we got a 2012 R2 Standard Edition Server, and we need to introduce it into the network.
So, how to do it?
The idea is that 2012 will become a AD controller, and 2003 will be phased out and left working as a backup server. However, I am not sure what can I expect from SBS, as I know it has series of limitations.
Thanks in advance! :-)
So, how to do it?
The idea is that 2012 will become a AD controller, and 2003 will be phased out and left working as a backup server. However, I am not sure what can I expect from SBS, as I know it has series of limitations.
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.
I'm afraid I have to take issue with some of Sandeshdubey comments. Specifically, his statement: "To introduce Windows Server 2012 DC in existing domain you need to first migrate Exchange 2003" is incorrect. Before you introduce Exchange 2013 to a 2003 network you need to do migrate to Excchange 2007 or 2010 - NOT Server 2012.
First, there are few significant limitations for SBS. Specifically:
1. No Trusts
2. MUST hold FSMO Roles
3. No Terminal Services
4. REALLY should use the wizards for everything.
The above restrictions do not prevent you from adding other servers OR other DCs.
Things you cannot do in adding the 2012 DC:
1. You cannot raise the domain or forest functional levels of AD.
You should also make sure EVERYTHING is FULLY patched.
As for keep the SBS server, you COULD do that provided you didn't transfer the FSMO roles from it and left it as a DC. But, I would consider that very unwise considering that support is ending for it next month if it hasn't ended already. You need to migrate off it completely for security purposes.
Keep in mind, AD is NOT a PDC/BDC model - that ended with NT4 15 years ago. There is no consequence (beyond the outdated issue and being unable to raise the Domain Functional and Forest Functional levels leaving the FSMO roles on the SBS server so as not to violate it's licensing. PROVIDED you are fully patched (there was a bug for DCs mixing 2003 and 2012 (R2?) but that should have been fixed.
First, there are few significant limitations for SBS. Specifically:
1. No Trusts
2. MUST hold FSMO Roles
3. No Terminal Services
4. REALLY should use the wizards for everything.
The above restrictions do not prevent you from adding other servers OR other DCs.
Things you cannot do in adding the 2012 DC:
1. You cannot raise the domain or forest functional levels of AD.
You should also make sure EVERYTHING is FULLY patched.
As for keep the SBS server, you COULD do that provided you didn't transfer the FSMO roles from it and left it as a DC. But, I would consider that very unwise considering that support is ending for it next month if it hasn't ended already. You need to migrate off it completely for security purposes.
Keep in mind, AD is NOT a PDC/BDC model - that ended with NT4 15 years ago. There is no consequence (beyond the outdated issue and being unable to raise the Domain Functional and Forest Functional levels leaving the FSMO roles on the SBS server so as not to violate it's licensing. PROVIDED you are fully patched (there was a bug for DCs mixing 2003 and 2012 (R2?) but that should have been fixed.
ASKER
Thanks a lot Lee, this is a helpful comment! :-)
ASKER
Thanks!