Server 2012 R2 – Post installation checklist 15 September 2015 by Stefan Dingemanse 1 Comment Check out this post to see a checklist which can be used after installing WIndows Server 2012 R2. Get your server build request form template. Modify this server build request form template and add it to your website in seconds. No coding required! Add multiple recipients, use file uploads, add third-party apps, and much more with 123FormBuilder. Experience the power of online forms!
-->Applies To: Windows Server 2016, Windows Server 2012 R2, Windows Server 2012
The forest owner is responsible for creating a domain design for the forest. Creating a domain design involves examining the replication requirements and the existing capacity of your network infrastructure and then building a domain structure that enables Active Directory Domain Services (AD DS) to function in the most efficient way. Domains are used to partition the directory so that the information in the directory can be distributed and managed efficiently throughout the enterprise. The goal for your domain design is to maximize the efficiency of the Active Directory replication topology while ensuring that replication does not use too much available network bandwidth and does not interfere with the daily operation of your network.
![Windows Server Build Checklist Template Windows Server Build Checklist Template](/uploads/1/2/5/8/125865960/526758853.gif)
In this section
we've found that using some different lists for different steps helps keep it manageable:
1. Planning - do naming convention,ip address, vlan, location - all that fun stuff here
2. OS - choose from seperate checklists for Windows/Linux/VMware etc. Have things like your logging clients/management setup here, as well as anything else you do to every server of that OS
3. Documentation - write up how-tos for whatever is setup on the server, make sure the previous checklists are actually completed
One other note: GPOs shouldn't need to be touched for each server, as long as the computer object is in the right security groups and OU, you should be able to leave it alone. You can do RDP security, disabling guest and windows updates through GPO as well - the fewer manual steps the better!