Today I set about installing Windows Server 2012 in a virtual test environment. Further down the road I plan to look at publishing remote applications, but for now let’s begin with installing Active Directory.
This is a basic outline of the post-installation steps that I will follow:
- Change the machine name
- Set a static IP address
- Install Windows Updates
- Install Active Directory Domain Services
- Promote server to Domain Controller
1. Change the machine name
From the desktop press Ctrl + X and then click System on the pop-up menu. Under Computer name, domain and workgroup settings click Change Settings.
In the System Properties window click the Change button and then change the Computer name. Click OK to exit.
2. Set a Static IP Address
From the Start Screen click Control Panel and then click Network and Sharing Center and then click the link for your Ethernet connection.
In the Ethernet Status window click the Properties button. Scroll down and select Internet Protocol Version 4 (TCP/IPv4) and then click the Properties button.
Set your static IP address, Subnet mask, Default gateway and Preferred DNS server.
My settings are provided just so that you have a screenshot. I am using a NAT network provided by VMware Player.
3. Check for Windows Updates
From the Start Screen click Control Panel and then click Windows Update. If necessary turn updates on and then Check for updates and install them.
4. Installing Active Directory Domain Services (ADDS)
From the Server Manager Dashboard click Add roles and features.
Review the Before you begin screen for any actions that are required prior to installing roles, role services or features, and then click Next.
Select Role-based or feature-based installation and then click Next.
Select your server from the server pool and then click Next.
Select Active Directory Domain Services from the list.
Review the role services and features to be installed and click the Add Features button.
You will be returned to the Server Roles page of the Add Roles and Features Wizard, click Next to proceed.
On the Features page of the Wizard the Group Policy Management feature is automatically selected, click Next.
Review the AD DS page and then click Next. If you do not have a DNS server on your network you will be prompted to install DNS later.
The Confirmation page gives the option to Export configuration settings and to Restart the destination server automatically if required. Configure as required and then click Install.
The previously selected roles and features will now be installed. Click Close to exit the wizard.
5. Promote Windows Server 2012 to a Domain Controller
An Alert notification will appear on the Server Manager Dashboard prompting you to Promote this server to a domain controller.
Review the domain deployment options. I will Add a new forest called Pricklytech.local. Click Next.
Select the Forest functional level (FFL) and the Domain functional level (DFL) from the two drop-down menus – they should be set to the highest level that your environment supports (to enable as many AD features as possible). The FFL, for example, can be set to Server 2003, 2008, 2008 R2 or 2012.
Next specify domain controller capabilities. I have Domain Name System (DNS) server selected as I do not yet have a DNS server in this particular test environment. You will also notice that Global Catalog is checked and greyed out – because this is the first domain controller in a new forest.
Type and confirm the Directory Services Restore Mode (DSRM) password. DSRM is a safe mode boot option that is used to repair / recover Active Directory.
Review the DNS delegation alert. In my environment no action is required – so after closing the alert I clicked Next.
The NetBIOS domain name is supplied – click Next.
The default paths for the AD DS database, log files, and SYSVOL are displayed. Click Next.
Review your selections. You can export a Powershell script to automate additional installations by clicking the View script button. Click Next.
A prerequisite check is run. If All prerequisite checks passed successfully click Install to continue.
Once the server is successfully promoted it was automatically rebooted.