Install Windows Server 2012 R2
Install Windows Server 2012 R2
Server Core:
• Is a more secure, less resource-intensive
installation option
• Can be converted to full graphical shell version of
Windows Server 2012
• Is the default installation option for Windows
Server 2012
• Is managed locally using sconfig.cmd
Roles
• Roles are made up of role services components that
provide additional functionality associated with the
role
• In Server Manager 2012, console servers with a similar
role are grouped together
• Role deployment also includes the configuration of
dependencies
What Are the Windows Server 2012 Features?
Features:
• Are components that support the server such as
Windows Server Backup or Failover clustering
• Usually do not provide a service directly to clients
on the network
Keep in mind the following points:
• Roles can have features as dependencies
• Features on Demand are features that need to be
installed using a mounted image as a source
Lesson 2: Installing Windows Server 2012
• Installation Methods
• Installation Types
• Choosing Whether to Upgrade or Migrate
• Hardware Requirements for Windows Server 2012 R2
• Installing Windows Server 2012
• Migrating Server Roles
Installation Methods
In-place upgrade
Advantages: Disadvantages:
• Generally straightforward process • More difficult to troubleshoot
that takes less time and planning installation failures caused by existing
than a migration strategy applications or server roles
• All server roles, features, data, and • Existing problems and configuration
application settings are maintained issues might be brought into the new
operating system
Migration
Advantages: Disadvantages:
• Easier to troubleshoot installation • Requires all applications to be
failures reinstalled and configured
• Existing configuration or application • Requires planning of migration of
issues are not carried forward to the server roles
new operating system • Requires migration of data
• You can easily move to updated • Requires the purchase of new
versions of applications hardware
Hardware Requirements for Windows Server 2012 R2
Information necessary
for a domain join:
• Domain name
• Account with
permission to join
the computer to the
domain
Activating Windows Server 2012
Configuring a Server Core Installation
Demonstration: Using DISM to Add Windows
Features
Administrative tools:
• Active Directory Administrative Center
• Active Directory Users and Computers
• DNS console
• Event Viewer
• Group Policy Management Console
• IIS Manager
• Performance Monitor
• Resource Monitor
• Task Scheduler
• Can be used to manage non-domain joined systems
Demonstration: Using Server Manager
Windows PowerShell
Cmdlet Syntax:
• Get-Help -Noun
NounName
• Get-Help -Verb
VerbName
• Help CmdltName
• Get-Command
Common Cmdlets for Server Administration
System Administration
Details
cmdlets
Service Cmdlets Use the Service noun
Event Log Cmdlets Use the Eventlog noun
Process Cmdlets Use the Process noun
ServerManager module Allows the WindowsFeature
noun
Windows PowerShell Allows cmdlets or scripts to be
Remote Management run on remote computers
Demonstration: Using Windows PowerShell
PS V1, V2, V3
PS V4
Third-party
languages and
tools
Pull Model Server Local Configuration
Contains DSC data and Store
modules
Configuration Files
Parser and
PS V1, V2, V3 Dispatcher
Imperative Providers
PS V4
Third-party
languages and
tools Push Model Configuration
Staging Area
Contains DSC data
Lab: Deploying and Managing Windows Server 2012
Logon Information
Virtual machines 20410D-LON-DC1
20410D-LON-SVR3
20410D-LON-CORE
User name Adatum\Administrator
Password Pa$$w0rd
• Review Questions
• Common Issues and Troubleshooting Tips
• Tools