This article will explain how to setup Windows Server 2008 Domain Controller on a VPC. Steps remain the same for physical machine. Follow the steps below to setup domain controller:
- Logged into machine as local administrator.
- Run dcpromo command on Windows command prompt. System will start checking whether the binaries are already installed. It may be possible, if you have run dcpromo command previously.
- The Active Directory Domain Services Installation Wizard will start as shown in the figure below. You can either enable advanced mode installation checked or leave it unchecked. In my case, I have enabled advanced mode installation. Click Next to proceed.
- Operating system compatibility announcement will be displayed. Please read the message and Click Next to proceed.
- The next screen will allow you to choose Deployment Configuration, i.e. create a new domain or Add this machine to existing domain controllers. In my case, I have chosen “Create a new domain in a new forest”. Click Next to proceed.
- Enter Fully Qualified Domain Name (FQDN) of your forest. In my case, I have entered litwareinc.com for my VPC. Click Next to proceed.
- As I have selected advanced mode installation in step 2 above, Domain NetBIOS Name screen will appear. Otherwise installation will skip this screen. Enter NetBIOS name of the domain in next and Click Next to proceed.
- The next screen will allow you to select Forest functional level; I have chosen Windows Server 2003, which will allow me to add WIN2003 or later version of domain controller to my domain. Click Next to proceed.
- In the previous step, as I have selected Windows Server 2003 as my forest functional level, that domain functional level screen appears at this stage. I have again selected Windows Server 2003 as my domain functional level and click Next to proceed.
Note: I have chosen Windows Server 2008 in the previous step then installer will automatically skip this step.
- In the Additional Domain Controller Options screen, you will be asked to select Domain Name Service (DNS) to install as part of your domain controller installation. If you want to make this Domain Controller to server as DNS server as well, then check DNS Server checkbox. In my case, I have checked DNS Server checkbox and clicked Next to proceed.
- Please make sure that you have assigned a static IP to your domain controller otherwise you see the screen shot below. Assign static IP and click NO to proceed.
- If the wizard cannot create a delegation for the DNS server, it displays a message to indicate that you can create the delegation manually. Click YES to proceed.
- Now you will have the location where the domain controller database, log files and SYSVOL are stored on the server.
- This screen will allow you to specify windows paths to store database information, log files and SYSVOL. SYSVOL stores Group Policy objects and scripts. Leave the default path settings and click Next to proceed.
- In the Directory Services Restore Mode Administrator Password (DSRM) screen, enter the Directory Services Restore Mode Administrator Password.
Note: The Directory Services Restore Mode Administrator password is different from the Domain Administrator Password. Assign a password for the Administrator account that will be used, when this domain controller is started in Directory Services Restore Mode. Always use strong password for Directory Service Restore Mode Administrator account.
- The next screen will display settings that you have selected during installation wizard. These settings can exported to an answer file for use with other unattended operations. Click Next to proceed.
- Now DNS installation will start. See the screen shot below.
- Now Group Policy Management Console will start. Wait for Group Policy Management Console operation to finish.
- Configuring DNS Server configuration console will start, once Group Policy Management Console will complete. See the screen shot below.
- Setting up this server or VPC to host Domain Controller is completed. Click Finish.
- Click on Restart Now to restart your server or VPC for the changes to take effect.
- Once server will reboot, this server will become a domain controller.
Please provide your comments about this article.
Category: Installation and Configuration
Published: 04/05/2009 13:28
