Create the Secondary Active Directory server (Optional)

The Lab Management Installer automatically creates the configuration files (the host files for the Active Directory server) for you. After it completes this task, follow these steps to create the Secondary Active Directory server.

1. Before you create the Secondary Active Directory server, you must prepare the Primary Active Directory server for its addition. In the steady-state operation of a Lab Management Domain, the Dynamic DNS Update feature is turned off. However, when you are adding a new Domain Controller, you need to turn off the feature temporarily using these steps:
   1. Log in to the Primary Directory server as the Administrator user.
   2. Click Start.
   3. Select Run.
   4. Enter cmd.exe and click OK.
   5. From the command window, type the following command:
      • dnscmd/Config Lab Management Domain Name/AllowUpdate 1
      Command output:

               C:\>dnscmd/Config cubit.example.com/AllowUpdate 1
               Registry property AllowUpdate successfully reset.
               Command completed successfully.

2. Create a VMware virtual image for the Secondary Active Directory server on the physical node where the server is hosted using the following two commands: In the steady-state operation of a Lab Management Domain, the Dynamic DNS Update feature is turned off. However, when you are adding a new Domain Controller, you need to turn off the feature temporarily using these steps:
   1. From the command window, type the following command:
      • sudo vmcreate -n <fully-qualified Domain Name of the Secondary Directory server>
      Command output:

              $ sudo vmcreate -F -n ad.cubit.example.com
              Unregister guest node: ad.cubit.example.com
              Fetching prebuilt virtual disk images from manager node
              URL =
              "http://mgr/public/os/Microsoft/2k3stdR2/i386/Windows2k3stdR2_
              dc/4/Windows_2k3stdR2.vmdk"
              Register guest node: ad.cubit.example.com
              $

   2. From the command window, type the following command:
      • sudo vmctl start <fully-qualified Domain Name of the Secondary Directory server>
      Command output:

              $ sudo vmctl start ad2.cubit.example.com
              Start ad2.cubit.example.com: OK
              $

      Note: Monitor the progress of this task to make sure that the Secondary Active Directory server configures successfully.
3. Launch the VMware Server Console application from your desktop to connect to the VMware server running on the physical node to monitor the progress of the Secondary Active Directory server set-up process.
4. Once the installation process is complete, review the log files located at C:\runonce.log to verify that all steps have completed successfully.
5. After confirming that the Secondary Active Directory server has successfully joined the Lab Management Domain, disable the Dynamic DNS Update feature in the DNS server running on the Primary Active Directory server. Use the following commands:
   1. Log in to the Primary Directory server as the Administrator user.
   2. Click Start.
   3. Select Run.
   4. Enter cmd.exe and click OK.
   5. From the command window, type the following command:
      • dnscmd/Config Lab Management Domain Name/AllowUpdate 0
      Command output:

          C:\>dnscmd/Config cubit.example.com/AllowUpdate 0
          Registry property AllowUpdate successfully reset.
          Command completed successfully.