How To Installing Windows Server 2012 In Addition To Server Core

Managing too Configuring a Server Core Installation

The next sections encompass full general tasks associated amongst managing too configuring a Server Core organisation via the command prompt afterward the installation is complete. As an alternative, an administrator tin work the SCONFIG utility to configure full general settings.

Launching the Command Prompt inward a Server Core Installation

Remember, the Start bill of fare does non exist. Because of this, i of the near of import tasks an administrator must sympathise when managing a Server Core installation is how to launch a PowerShell console session. The next steps volition aid you:

1. Press Ctrl+Alt+Delete.
2. Select Start Task Manager.
3. On the Windows Task Manager screen, choose File, New Task (Run).
4. In the Create New Task dialog box, type powershell.exe, too and then click OK.

Changing the Server Core Administrator’s Password

After the initial password has been set, the syntax to alter the administrator password is equally follows:
Net user administrator *
After the command has been executed, y'all are prompted to type a password for the user. Enter the password too and then retype it for the confirmation process. It is a best practise to work a complex password when assigning passwords to the administrator concern human relationship too the default password policy on the server volition require complex passwords.

Changing the Server Core Machine Name

After the Server Core installation is complete, around other mutual chore is to alter the machine call of the server. By default, Windows automatically generates too assigns a server call starting amongst WIN too followed past times a string of characters. The syntax to alter the Server Core machine call follows:

netdom renamecomputer <CurrentComputerName> /newname:<NewComputerName>

When executing this command, supersede the <CurrentComputerName> declaration amongst the existing hostname (which tin last flora using the hostname command) too the <NewComputerName> declaration amongst the novel machine request the Server Core installation. Changing the server call from Win-123 to ABCDC2 is depicted inward the next example:

netdom renamecomputer Win-123 /newname:ABCDC2

The same role tin last performed using PowerShell amongst the next command:

Rename-computer –NewName ABCDC2

Assigning a Static IPV4 IP Address too DNS Settings

Another mutual Server Core administration chore is assigning an IP address, including the primary too secondary DNS settings. Before this chore tin last executed, y'all must run the next command to obtain too position the names of the network interfaces installed on the server. This includes capturing the unique ID associated amongst each network interface. To display a listing of network interfaces, including their respective unique IDs, run the next command:

netsh interface ipv4 present interfaces

NOTE

Netsh commands tin usually last abbreviated to brand typing easier i time the administrator is familiar amongst the command. For example, the preceding command tin also last executed past times running the following:

Netsh int ipv4 sh int

The adjacent pace is to brand a Federal Reserve notation of the network interface call too unique ID that y'all must change. The ID is located inward the leftmost column too is referred to equally Idx. This is depicted inward the output of the netsh interface ipv4 present interfaces command, equally displayed in

 Reviewing the Idx ID for a network interface.

NOTE

If y'all excogitation to alter the IP address settings on to a greater extent than than i interface, convey Federal Reserve notation of all the interface names too Idx unique IDs.

Now that y'all guide maintain captured the names too IDs, work the next syntax to alter the IP address for a desired interface:

netsh interface ipv4 laid address name="<ID>" source=static address=<StaticIP> mask=<SubnetMask> gateway=<DefaultGateway>

Replace the ID declaration amongst the network interface call or ID. In addition, come inward the static IP address, subnet mask, too default gateway inward subsequent arguments, equally follows:

netsh interface ipv4 laid address name="1" source=static advertising dress=192.168.115.10 mask=255.255.255.0 gateway=192.168.115.1.

The finally pace when configuring the network interface is to come inward a primary too secondary DNS entry for the interface. Do this past times using the next syntax:

netsh interface ipv4 add together dnsserver name="<ID>" address=<DNSIP> index=1

The same command is used too repeated when entering to a greater extent than than i DNS entry. However, increment the index each time. When finalized, run IP Config /all to verify the IP address settings.

The same role tin last performed using PowerShell amongst the next commands:

Get-NETIPInterface Set-NetIPAddress –InterfaceIndex 12 –IPv4Address 192.168.115.10 –PrefixLength 24 –DefaultGateway 192.168.115.1 Set-DNSClientServerAddress –InterfaceIndex 12 –ServerAddresses "DNSIP1","DNSIP2"

Adding the Server Core System to a Domain

The next script illustrates the basic syntax to add together a Server Core organisation to a Windows domain:

Netdom bring together <computername> /domain:<domain> /OU:<ou path> /userd:<domain>\<username> /passwordD:*

Input the domain call too the target OU. Supply the user concern human relationship too password for an concern human relationship that has permissions to add together computers to the domain.
The same role tin last performed using PowerShell amongst the next commands:

Add-Computer -domainname <domain> -OUPath "OU=OU,=Domain,DC=com"

Activating the Server Core System

Activating a Server Core organisation tin last achieved inward 2 slowly steps. First, y'all come inward a production key, too and then y'all activate the server. The syntax to come inward a production primal is equally follows:
slmgr.vbs –ipk<productkey>
After the production primal has been successfully entered, y'all activate the server past times typing inward the next command.
slmgr.vbs –ato

Using SCONFIG to Configure a Server Core Installation

As mentioned previously, Windows Server 2012 includes a utility to brand the initial configuration or a centre installation easier. The SCONFIG utility, which has been available since Windows Server 2008 R2, is really slowly to work too is usually the preferred configuration selection if scripting is non required.
The utility tin last executed past times running sconfig.exe inward the centre installation command prompt too presents the laid of options shown in

 SCONFIG utility

Server Core Roles too Feature Installations

The typical Windows server roles tin last configured on a Server Core installation. The next server roles are currently supported on a Server Core installation:

• Active Directory Certificate Services
• Active Directory Domain Services (AD DS)
• Active Directory Lightweight Directory Services (AD LDS)
• Active Directory Rights Management Server
• DHCP Server
• DNS Server
• File too Storage Services
• Hyper-V
• Print too Document Services
• Remote Access Server
• Remote Desktop Services (partial support)
  • Connection Broker
  • Licensing
  • Virtualization Host only
• Volume Activation Services
• Web Server (IIS)
• Windows Deployment Services
• Windows Software Update Services

The next are around of the features that are also supported on a Server Core installation:

• .NET Framework 4.5
• BITS Compact Server
• BitLocker Drive Encryption
• BranchCache
• Failover Clustering
• Group Policy Management
• IP Address Management (IPAM) Server
• Multipath I/O
• Network Load Balancing
• Remote Server Administration Tools (partial)
• Simple Network Management Protocol (SNMP)
• Telnet Client
• Windows PowerShell 2.0
• Windows Server Backup

NOTE

The next command lists all the potential server roles too associated features:
Dism /online /get-features /format:table

The OCSetup command-line computer program familiar from before versions is even so available (but deprecated) for setting upwards too configuring the server roles too features on a Server Core installation. You tin configure the OCSetup command-line options using the next syntax:

ocsetup.exe [/?] [/h] [/help] ingredient [/log:file] [/norestart] [/passive] [/quiet] [/unattendfile:file] [/uninstall] [/x: parameter]

Table 3.3 describes each of the options that are available when using the OCSetup command-line program.

Table 3.3. Available Command Options for OCSetup

Parameter	Description
/?, /h, /help	Explains all the options available for OCSetup
component	Represents the call of the ingredient y'all excogitation on installing, such equally DNS, DHCP, Web Server (IIS), too more
/log:file	Specifies the log file location if y'all create non wishing to convey payoff of the default location
/norestart	Does non reboot the estimator afterward the installation
/passive	Suppresses unnecessary vibrations too exclusively includes progress status
/quiet	Does non require user interaction
/unattendfile:file	Requires additional configurations
/uninstall	Removes server components
/x: parameter	Supplies additional configuration parameters

Using Powershell to Install a Server Role on a Server Core Installation

In add-on to OCSetup, Powershell tin last used to install roles too features, equally follows:

1. Run PowerShell past times executing powershell.exe inward the command prompt.
2. Run import-module servermanager to enable Server Manager features inside the PowerShell session.
3. Use Get-WindowsFeature to position installed too available roles too features.
4. Use Add-WindowsFeature to add together the required role or feature. Table 3.4 outlines an instance of mutual server role installations using Add-WindowsFeature.

Table 3.4. Server Role Installation Command Lines amongst PowerShell

Server Role	Command
DNS Server role	Add-WindowsFeature DNS
DHCP Server role	Add-WindowsFeature DHCP
File Server role	Add-WindowsFeature File-Services
Print Server role	Add-WindowsFeature Print-Server
Active Directory Lightweight Directory Server role	Add-WindowsFeature ADLDS
Windows Server Update Services role	Add-WindowsFeature UpdateServices
Web Server (IIS) role	Add-WindowsFeature Web-Server
Remote Access role	Add-WindowsFeature RemoteAccess
Hyper-V role	Add-WindowsFeature Hyper-V

The previous sections are a prelude to around of the mutual Server Core command-line arguments for installing too configuring elements on a Windows Server 2012 Server Core installation. For a total listing of command-line arguments, see the Microsoft website too send a search for Windows Server 2012 Server Core.

Installing the Active Directory Domain Services Role

Installation of AD DS is to a greater extent than complex too vital to the performance of the surround too so deserves to a greater extent than detailed attention. Installation of the role using Add-WindowsFeature AD-domain-services volition install the required binaries but non configure the server equally a domain controller.
In before versions, the recommended tool for that is the dcpromo utility. The job is that dcpromo ordinarily starts a sorcerer amongst a GUI that is non supported on Server Core. As a result, the dcpromo utility on server centre is a command-line utility that requires input past times supplying the performance parameters or past times using an response file.
The dcpromo utility tin convey to a greater extent than than xxx dissimilar performance parameters. Although this mightiness look similar a dizzying array of options, few command lines volition work all of them. Refer to the TechNet dcpromo command reference at http://technet.microsoft.com/en-us/library/cc732887(WS.10).aspx for a consummate listing too explanation of each parameter. You tin work this reference to create the right dcpromo command job or create an unattend file suitable for your centre domain controller.
As amongst many other aspects of the operating system, Windows Server 2012 provides PowerShell back upwards to perform that same function. Promoting a domain controller using PowerShell is really convenient too is based on the ADDSDeployment module, which includes the next commands:

• Install-ADDSForest
• Install-ADDSDomain
• Install-ADDSDomainController

These commands are available past times outset loading the appropriate module using Import-Module ADDSDeployment. Then, all that’s required is using the right command from to a higher house depending on whether the destination is to deploy a novel forest, add together a domain to an existing forest, or add together a domain controller to an existing domain. All the commands convey the required parameters, which y'all tin notice past times using the Get-Help cmdlet.
For example, work the next command to larn the syntax for the Install-ADDSForest cmdlet:
Get-Help Install-ADDSForest

Then, using the next syntax to install a novel Windows 2012 woods amongst a source domain called abc.com:

Install-ADDSForest –ForestMode "Win8" –DomainMode "Win8" –DomainName "abc.com" –DomainNetBIOSName "ABC" –DatabasePath "C:\Windows\NTDS" –LogPath "C:\Windows\NTDS" –SYSVOLPath "C:\Windows\SYSVOL" –InstallDNS:$true –CreateDNSDelegation:$false –RebootOnCompletion:$true –Force:$true

You volition last prompted for the rubber agency kick password, too the woods volition last created. The server reboots upon completion equally specified inward the command.