Follow these steps to setup a Domain Controller using Windows Server 2008. In this example, I am installing AD DS, DNS, and DHCP for the first time for a client. If this is not the first server in the forest, skip ahead to Add Server 2012 As A DC.
First answer key questions: Will they benefit? Is it practical? Who will support it? If a network has over 20 computers, it’s highly recommended. It’s also a good idea if you have multiple locations that need to access a single database.
Once that is complete, first thing to do is to rename the computer to something familiar like “DC01” or “Server”.
Set a static IP address.
Let’s get started… Start – Server Manager – Install Roles. Select AD DS, DNS, and DHCP select okay for each one.
Installing DHCP: If the DC is going to be a DHCP server, you need to disable DHCP on the router or look for a “forward to DC” setting.
Parent Domain= Domain Name
Primary – Static IP of the DC
Secondary – Router IP Address
Configure scope page – You can add DHCP ranges – 8 days for wired / 8 hours for wireless
Everything else is default, reboot the server.
NOTE: After researching this for a while, I have found that naming the domain is a common question. Best practice seems to be int.company.com or internal.company.com, but NOT .local on the end. This was used often and is highly debated.
- After reboot, go to “Server Manager” – Roles – Active Directory – Install and then run “DC Promo” if it does not do it automatically.
Functional Level- Needs to match the networks OS’s. If XP office, select 2003, if Windows 7, select Server 08r2 or whatever OS the server is. When installing AD, Windows creates a folder in the directory “C:\Windows\SYSVOL” which contains the bulk of AD info and is shared out automatically. After this, it will ask where to install the “Log, Database, and SYSVOL” folders. Keep it default unless it’s a large setup like in a forest where you would select different paths. Next it will ask for a password in case you need to restore AD to a previous time in Windows Restore – use the “Domain Administrator” password.
AD is now installed. Next step is to configure users. Key notes here is copying a user creates a new user with the same policies and groups attached to the user copied. MAKE A HABIT OF COPYING USER ACCOUNTS INSTEAD OF CREATING NEW ONES. Creating a group – Left column, select “Builtin” under your domain name – Right click New- Group – Create a group name – and Add users by going to users and selecting multiple users and adding them to the group. You can also select other groups and go to properties – Members – and add your custom group to theirs.
Now you can configure policies for the domain. Start – Group Policy Management – Creates new policies and configures them. There will be a section on this later on.
The domain is officially setup. The last thing to setup would be DHCP scopes depending on the network and make sure that DNS has started (make sure the “dns server” service is running) and also go to DNS and make sure it’s populating.
So we should then add the following icons to the task bar or desktop (your preference): Active Directory Users and Computers, Group Policy Management, DNS, DHCP, and Event Viewer. I like to open each one up and make sure the following:
DHCP – Your Domain Name – IPv4 – Server Options – Do you see a 003 Router record? Add your gateway IP if it’s not there. Do you see a 006 DNS server record? Add your new DC there along with any other replication DC’s. Do you see a 015 record there? If not, add your domain name there.
DNS – Server Name – Forward Lookup Zones – Domain Name – Do you see records?
Group Policy Management – Forest: Domain Name – Domains – DomainName – Default Domain Policy – Is is applied? Run gpupdate /force and rsop.msc to confirm. You should be good to go from here.
To Demote a Domain to A Workgroup:
For workstations: Just take the workstation off the domain and reboot. You do this by
sysdm.cpl– and “Change” to a workgroup.
On the Domain Controller , Run – dcpromo – Follow the prompts and remove the computer from the domain. You will still need to go to Server Manager and remove the role afterwards. Most likely will need to remove the DHCP and DNS roles as well. Note that the Small Business Server OS has to be on a domain but you can still authenticate with users on a workgroup through local account authentication.