One thing you will note at this stage of the SBS 2011 essentials is that it’s not yet a member of the domain or a domain controller.

This is normal and the next step is to build a config file to join the server to to the domain and promote it as a domain controller.

Promote the Destination Server to a Domain Controller in the existing Windows SBS 2011 Essentials forest
You must promote the Destination Server to domain controller within 6 days of installing Windows SBS 2011 Essentials .
Use the DCPromo tool to promote the Destination Server as described in this section.
 To promote the Destination Server to a Domain Controller
1.    Open a Command Prompt window, type the following command, and press ENTER.
COPY C:\Windows\System32\ntds.dit c:\Windows\System32\sbsntds.dit

NTDS.dit is the guts of the database for active directory.  Because the server is not yet a DC and we’re in the “500” account in workgroup mode, there’s no need to launch UAC here.


2.    Create an answer file on the administrator’s desktop, as follows:
a.    Click Start, click All Programs, click Accessories, and then click Notepad.
b.    Copy the following content and paste it into the file. Do not put any other content into the file.
Leave the rest of the file blank.
c.    Click File, click Save, and type dc-cfg.ini for the file name. Save the file on the desktop.
3.    Open a Command Prompt window as an administrator. See To open a Command Prompt window as an Administrator.
4.    Type the following command, and press ENTER.
DCPROMO /unattend:”C:\Users\Administrator\Desktop\dc-cfg.ini”

After the tool runs, the process status appears.

When it gets done you’ll need to reboot the server.

The KB the final window references is;en-us;942564 and is just warning you that NT4 machines won’t natively connect.

Now reboot and you’ll see the server is now joined to your SBS 2003 domain.
If DCPromo does not succeed because of an incorrect entry in the answer file, the tool may erase the passwords from the dc-cfg.ini file. If this occurs, add the passwords back into the file before running the tool again.
5.    Restart the Destination Server. Since the computer now resides in the OU of the domain controller, the server requires a few minutes while different Group Policies are applied to it.
6.    Log on to the Destination Server as the domain administrator, using the same username and password you use on the Source Server.
7.    To verify that the server is a domain controller, click Start, click Administrative Tools, and then click Active Directory Users and Computers.
8.    Select the Domain Controllers node. The Source Server appears as the Global Catalog, and the Destination Server appears as the Domain Controller.

Note you can do .lan or any .whatever you used on the original SBS network.


Comments are closed.