Active Directory Domain Controllers are at the core of every organized Microsoft-oriented networking infrastructure, and Windows-based DNS Servers and DHCP Servers also make perfect sense on Server Core installations. Another technology, however, emerges more often at the center of these types of environments these days: certification authorities.
While you’d think Microsoft is luring organizations into using their cloud services as the main method for sharing files, most organizations have no need to share files beyond their organization’s borders or to access files in a web browser; as such, most organizations rely on file servers to share files among their employees. Today, I’ll show you how to transform a Server Core installation into a Dynamic Access Control-aware file server.
To make life easier as an admin, several network protocols have been introduced to help manage TCP/IP. One of these protocols is the Dynamic Host Configuration Protocol (DHCP).
In the previous article in this series, I showed you how to promote a Windows Server 2012-based Server Core installation to a Domain Controller. In this article, I’ll discuss configuring your Server Core installation to a Domain Name System (DNS) Server
In the first part of this series, I discussed the benefits of the available Server Roles in Server Coreinstallations of Windows Server 2012. Today, let’s get hands-on by configuring a Windows Server 2012 Server Core installation as a Domain Controller.
By Sander Berkouwer - Thu, May 23, 2013 - 0 comments 
