Setup A Domain Controller With Windows 2012 Server Core

11/5/2019 Setup a Domain Controller with Windows 2012 Server Core
PETRI NEWSLETTER SIGN-UP
OFFICE 365 INSIDER

Here at Petri.com, we get IT — and so can you. Subscribe today to stay informed and
knowledgeable regarding the latest on IT.
Email
Subscribe
SEE ALL PETRI NEWSLETTERS
Setup a Domain Controller with Windows 2012 Server

Core
Posted on May 15, 2013 by John O'Neill Sr. in Active Directory with 2
Comments
Share Post Tweet Share
Server Core, introduced with Windows Server 2008, is a lean and mean
installation option for Windows Server 2012. It is a GUI-free, or
“headless,” operating system. Eliminating the GUI on the server o ers
many advantages; in fact, Microsoft believes in Server Core so strongly
that it is the default installation option in Windows Server 2012.
WE USE COOKIES TO IMPROVE YOUR BROWSING EXPERIENCE.
Find out more about our cookie policy here.
https://www.petri.com/setup-domain-controller-windows-2012-server-core 1/12
One of the best uses for Server Core in Windows Server 2012 is as an
Active Directory Domain Controller. Why? For starters, Server Core
minimizes the Windows components installed. Fewer components
mean fewer security patches and Windows updates. It also means a
lower attack surface making the server easier to protect from malware.
Less running processes and services reduce the opportunity for system
crashes and hangs.
Preparing a DC Using Windows 2012 Server Core
Now it’s time to go from just wanting a Server Core DC to actually

having one. Before we get too far along, we better start by making sure
our bases are covered and that all prerequisites have been met. It
should go without saying Windows Server 2012 Server Core must
already be installed. Next, we need to make sure network settings have
been correctly con gured. We’ll begin by assigning a static IP address.
Logon using an account with administrative privileges on the Server

Core system.
At the Windows Server 2012 Server Core Command Prompt, type

scon g.cmd and press Enter to start the Server Con guration Tool.
SECTIONS
Type 8 and press Enter to select Network Settings from the menu.
Type the Index# for the network adapter to change from the
displayed list.
Type 1 and press Enter to select the menu option to Set Network
Adapter Address.
Type S and press Enter to select the option for a Static IP.
Type the IPv4 static IP address and press Enter.
TypeTOthe
WE USE COOKIES subnetYOUR
IMPROVE mask for the network
BROWSING and then press Enter.
EXPERIENCE.
Find out moreType

aboutthe
ourdefault
cookie policy here. for the network and then press Enter.
gateway
The settings will be applied and the Network Settings menu will be
redisplayed.
Down the road, this server will query the existing domain controllers in
the domain. It’s essential this works without any hiccups so set a DNS
Server address while still in the Network Settings menu.
Type 2 and press Enter to Set DNS Servers.
Enter the IP address of the preferred, or primary, DNS server for

the domain. Press Enter.
Click OK when prompted that the Primary DNS Server has been set.
If a secondary DNS server exists for the domain, enter its IP address
when prompted for an alternate DNS server. If no secondary DNS
server exists, leave blank. Press Enter.
Click OK when prompted that the Alternate DNS Server has been
set. The Network Settings menu will be redisplayed.
Windows Server 2012 Server Core
Type 4 and press Enter to exit the Network Settings menu.
Type 15 and press Enter to exit the Server Con guration Tool.
Domain Controller Setup with PowerShell
I bet a number of you are anticipating my usual “Do this in one step
with PowerShell” approach. Well, I have no intention of disappointing
anyone, so here we go!
At the Windows Server 2012 Server Core Command Prompt, type

PowerShell and press Enter to begin a PowerShell session.
Get the name of the installed network adapter by typing Get-

NetAdapter at the PowerShell prompt and then pressing Enter.
Pay attention to the name displayed for the adapter you intend to
modify. Petri insider’s tip: In a fresh Server Core installation with
one network adapter installed, the name will be Ethernet by default.
Type the
WE USE COOKIES TOfollowing
IMPROVE cmdlet, and replace
YOUR BROWSING the IPAddress parameter with
EXPERIENCE.
the static
Find out more IP to
about our assign
cookie thishere.
policy server. The InterfaceAlias parameter is the
name of the adapter found using the Get-NetAdapter cmdlet. Also, be

sure to set the DefaultGateway parameter appropriately for the
network.
PowerShell
1 New-NetIPAddress -IPAddress 10.0.10.142 -InterfaceAlias "Ethernet" -Def
Armed with the interface name retrieved earlier using the Get-
NetAdapter cmdlet, it’s time to set the DNS servers using the Set-
DNSClientServerAddress cmdlet. The IPs entered for the
ServerAddresses parameter are the primary and secondary DNS
servers.
PowerShell
1 Set-DnsClientServerAddress -InterfaceAlias "Ethernet" -ServerAddresses
Okay, technically that’s two cmdlets, but come on – it’s still way faster
than the non-PowerShell way!
There’s no sense in slowing down now. Without exiting the PowerShell

session, install the Active Directory Services Role using the following
cmdlet:
PowerShell
1 Install-WindowsFeature AD-Domain-Services –IncludeManagementTools
This is a great time to mention a few things about an error you

may see: “WARNING: Windows automatic updating is not enabled. To
ensure that your newly-installed role or feature is automatically
updated, turn on Windows Update.”
First, don’t worry – this has zero impact on the installation of the AD
Services Role. If this is the only error you see, rest assured everything
installed just ne.
Second, since this server will ultimately be joined to a domain and if

Windows Update is enabled in the domain’s Group Policy settings
there’s nothing to worry about. Once joined to the domain, the server
will automatically turn on Windows Update.
Third, if you absolutely will not sleep well knowing that Windows
Update is turned o even for a moment, don’t break out in a sweat just
yet: It can be enabled manually. Since I prefer that all IT admins be calm
and well rested as they read my Petri articles, here’s the process.
Type scon g.cmd and press Enter to start the Server Con guration
Tool.
Type 5 and press Enter to select Windows Update Settings from

the menu.
Type A and press Enter to change the Windows Update to

Automatic. Click OK.
Type 15 and press Enter to exit the Server Con guration Tool and
return to the PowerShell prompt.
Almost done! It’s now time to move forward with promoting the server
to function as a domain controller. In this scenario, the domain tree
where this DC will live is called awssol.com. Keep in mind that we’re
adding this DC to an existing domain and con guring this server as an
additional DNS server for the domain.
Type Install-ADDSDomainController -DomainName awssol.com

-InstallDNS:$True –Credential (Get-Credential) and click Enter. Of
course, remember to replace awssol.com with your domain name.
The cmdlet will prompt for credentials. This needs to be an account

with Domain Admin privileges in the domain where the DC is being
created.
Windows PowerShell Credential Request
Next, it will ask for a SafeModeAdministratorPassword. This is the

Directory Services Restore Mode Password used primarily for disaster-
recovery scenarios. Type in the password you’d like to set and then
press Enter. If you’re a fan of simple passwords, you’re out of luck: A
non-blank password that meets the password complexity rules of the
domain is required. You’ll need to con rm the password by entering it
twice.
The system will prompt you to con rm that the server will be
con TO
WE USE COOKIES gured as a DC
IMPROVE and
YOUR rebooted.EXPERIENCE.
BROWSING Type A and press Enter to
con rm everything and get this train rolling.
There are a couple warnings you’ll probably be presented with as the

promotion does its job.
The rst warning lets you know that Windows Server 2012 has defaults
for certain security settings that can a ect very old OSes on the
network such as Windows NT 4.0. The second warns that a DNS Server
delegation can’t be created. Since we’re installing DNS on this server as
part of the DC promotion process, both of these errors are safe to
ignore. Unless of course you are still running Windows NT 4.0 systems
on the network (in which case, what are you thinking? Get those servers
upgraded!)
I’m a big fan of Windows Server 2012 Server Core Active Directory
Domain Controllers and of Server Core in general, and I’ll have more
Server Core related articles here on Petri in the future. In the
meantime, why not turn all your AD DCs into Server Core machines?
Tagged with Domain Controller, PowerShell, Server Con guration

Tool, and Windows Server Core
MEMBER LOGIN:
Username/Email
Password
Keep me signed in
Forgot password?
Sign In
BECOME A PETRI MEMBER:
Don't have a login but want to join the conversation? Sign up for a Petri Account
Register
0 Comments Sort by Votes | Date
There are no comments yet.
About the Contributor
During his 20+ years in the IT industry, John has enjoyed the opportunity to work as a
consultant, architect, executive, speaker, and author. He’s been involved in multi-national
networking, messaging, and communications projects as well as nding solutions for small
mom and pop shops allowing them to use technology to increase business opportunity and
decrease operational complexity.
John has authored material for both Thomson-Reuters’ Aspatore Books and Exec Blueprints
publications. He regularly contributes technology articles to the Petri.co.il online community in
addition to developing exciting training courses for the best IT training company in the world,
TrainSignal.
John often speaks at IT events around the nation. Recently he has been a featured presenter on
innovative technology solutions for the enterprise at conferences such as TechMentor,
Live!360, the NEOSA CIO Summit, and the Northeast Ohio Technology Summit. When he’s not
presenting at a conference, John can often be found leading informative webinars.
John is proud to be the North East Ohio Software Association’s CIO of the Year Award recipient
in 2012.
Follow John O'Neill Sr.

Sponsors
PETRI NEWSLETTER SIGN-UP
OFFICE 365 INSIDER

Here at Petri.com, we get IT — and so can you. Subscribe today to stay informed and knowledgeable
regarding the latest on IT.
Email
Subscribe
SEE ALL PETRI NEWSLETTERS

Sponsors
Pass PMP Exam Easy

100% Real Exam Questions,
Accurate & Veri ed Answers. 30
Days Updates.
© 2019 BWW Media Group | Terms and Conditions

Setup A Domain Controller With Windows 2012 Server Core

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Setup A Domain Controller With Windows 2012 Server Core

Uploaded by

Copyright:

Available Formats

11/5/2019 Setup a Domain Controller with Windows 2012 Server Core

PETRI NEWSLETTER SIGN-UP

OFFICE 365 INSIDER

SEE ALL PETRI NEWSLETTERS