1. Windows Server 2012 Administration
Introduction
Windows Server 2012 Administration
This course is intended for information technology (IT) professionals who have some knowledge and experience working with Windows operating systems.
We have two types of Windows Operating System available
Client Operating System ( Windows XP/Vista/Windows 7/Windows 8/Windows 10)
Server Operating System (Windows NT/2000/2003/2008/2012)
Client Operating System - It is used for end user purpose, to access services or applications required to perform their day to day job.
Server Operating System – It is used to provide services to the end user. It is more extensive as compared to client operating system. Like multiple users can login to the same server at the same time. It also provides services like Website hosting, Authentication, Database etc. The group of technician who work on Server operating system are identified as System Administrator.

2. Install and Manage Windows Server 2012
1: Deploying and Managing Windows Server 2012
Module 01
Presentation: 100 minutes
Lab: 75 minutes
After completing this module, students should be able to:
Describe Windows Server® 2012.
Install Windows Server 2012.
Perform post‑installation configuration of Windows Server 2012.
Describe the management tools available in Windows Server 2012.
Perform basic administrative tasks with Windows PowerShell®.
Required Materials
To teach this module, you need the Microsoft® Office PowerPoint® file 20410D_01.pptx.
Important: We recommend that you use Office PowerPoint 2007 or a newer version to display the slides for this course. If you use PowerPoint Viewer or an older version of Office PowerPoint, all the features of the slides might not display correctly.
Preparation Tasks
To prepare for this module:
Read all of the materials for this module.
Practice performing the lab exercises.
Work through the Module Review and Takeaways section, and determine how you will use this section to reinforce student learning and promote knowledge transfer to on‑the‑job performance.
Install and Manage Windows Server 2012
Post-Installation Configuration
Managing Server 2012 R2
Basics of Powershell

3. Introduction and Overview
1: Deploying and Managing Windows Server 2012
Introduction and Overview
4. Features

4. Common Editions Standard Datacenter Foundation Essentials Hyper-V
1: Deploying and Managing Windows Server 2012
Common Editions
Standard
Datacenter
Foundation
Essentials
Hyper-V
Storage Workgroup
Storage Standard
MultiPoint Standard
MultiPoint Premium
Supports All roles and features
Describe for students the type of environment in which they would deploy each edition, and why they should not use the Windows Server 2012 R2 Standard edition as a “one size fits all” solution. Ensure that they understand the difference between the standard and datacenter editions.
Specifically used for Virtualization, unlimited license
For small business, cannot be joined to domain, few roles, 15 users
Next edition for small business, 25 users. Available in two forms
Free for host OS, virtual machines licensed normally, no GUI - UI
Entry level unified storage appliance, limited to 50 users, Joins domain
Licensing different – 2 socket, 2 VM license, Supports few Roles & Features
For Educational Institutes – Sharing, 12 session, same system, Non-R2, Support few Roles
For Educational Institutes – Sharing, 22 sessions, same system, Non-R2, Support few Roles

5. Server Core It is more secure than GUI version
20410D
1: Deploying and Managing Windows Server 2012
Server Core
It is more secure than GUI version
Require less resource-(CPU/RAM) as no GUI
Still it can be converted to GUI
Default choice, while installing
sconfig.cmd
Can we remote Desktop to Server Core?
It can be managed command line or powershell
RSAT tool GUI experience
RSAT tool can be installed on client machine, to manage core server remotely.
gui/
Yes

6. 20410D
1: Deploying and Managing Windows Server 2012
Roles
Role services are software programs that provide the functionality of a role.
Server manager can identify servers with same roles (exp: Active Directory, DHCP)
Few roles have dependency as features
By default Roles selects required feature
Make sure you install dependent features.
Roles provide services to end user and managed by system administrator
Question : Name common roles you are aware of.
Question : Which role is frequently installed and which is less?
Question : Anything combination of roles installed together?

7. 20410D
1: Deploying and Managing Windows Server 2012
Features
Features are software programs that, although they are not directly parts of roles
Can support or augment the functionality of one or more role
Windows Server Backup or Failover clustering
DHCP, Telnet Client
Provide help to system to System administrator for specific work
Few roles also have dependency on features- Active Directory
Choose several features to point out and discuss. For example, point out that you need to install the Wireless LAN Service to use a wireless adapter with Windows Server Also point out that by default, no roles and features are installed. Mention the features that have been removed or deprecated.
Question
Which feature do you need to install to support NetBIOS name resolution for client computers running a Microsoft Windows NT® 4.0 operating system workstation?
Answer
You need to install the Windows Internet Name Service (WINS) server role to support NetBIOS name resolution.

8. Installation 1. Installation Sources
20410D
1: Deploying and Managing Windows Server 2012
Installation
1. Installation Sources
5. Installing Windows Server 2012 R2 Core and GUI
6. Upgrade to Windows Server 2012/R2
7. How to migrate servers – relate it to new installation or parallel installation

9. Installation Source (Physical/Virtual)
20410D
1: Deploying and Managing Windows Server 2012
Installation Source (Physical/Virtual)
Nowdays, most of the build process is done on Virtual Machines, and ISO is the most commonly used. Still for a physical server installation, USB is sometimes not recommended in organizations because of it’s RAM nature.
Network install not only includes .WIM file, it also supports .VHD and .VHDX.
ISO
Disk Drive
USB
WDS/MDT/SCCM

10. Types of Installation

11. Upgrading Windows Server
It sound very simple to do.
There can be unforeseen complications.
It retains all the complicated settings and configurations while just making the operating system newer.
Rollback options will generally require re-installing the original configuration.
This requires consistent backups, and the expertise to restore them immediately if things go wrong.
Clients need to carefully research the available upgrade options.  For example, cross-architecture upgrades are not supported. Which means businesses can’t move directly from 32-bit Windows Server 2003 systems to 64-bit Windows Server systems. Customers in this situation cannot upgrade and must do a fresh install.
Best For: Environments where the budget is tight; places with complicated in-house applications and cross-server installs and configurations that might be difficult to recreate with new hardware.

12. Install New Servers Also known as the Parallel Environment method
With the Install New Servers Approach, a company will purchase new servers to host the upgraded operating system.
IT organizations will often use this opportunity to increase the power of existing server hardware.
Typically, the business will install a clean operating system on the new servers and then transfer the roles, applications and workloads off of existing servers, shutting down server as their responsibilities are offloaded.
While it is conceivable, a company could replace every server one-for-one, most enterprises will take advantage of virtualization to consolidate servers on more powerful hardware when possible.
Best For: Data companies looking to get clean installation of operating system, or looking to consolidate servers. Most cautious approach.

13. Partial New Servers
Just because the operating system is a decade old doesn't mean all of the servers are.
In many cases, some of data center hardware is still sufficient and there is no need to replace it all.
In that case, the IT organization may choose to bring in a limited amount of new hardware, and continue using existing servers where it makes sense.
Using the same methodology as above, functions are replicated from existing servers to the new hardware. Old hardware that will no longer be used is retired as workloads are transferred. With this method, there is an additional step of upgrading the existing hardware to Windows Server 2012.
Best For: Environments with plenty of existing hardware with sufficient capability to run Server 2012, companies looking to consolidate server hardware.

14. Migrating Server Roles & Features to 2012
20410D
Migrating Server Roles & Features to 2012
1: Deploying and Managing Windows Server 2012
Migration documentation and tools ease the process of migrating server roles, features, operating system settings, and data from an existing server that is running Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Server 2012, or Windows Server R2 to a computer that is running Windows Server 2012 R2. By using migration guides using below link
Not all Roles can be migrated. The link is the best place if you are looking for migration of Roles and Features.

15. Minimum Requirement Component Minimum Requirement Recommended Maximum
Processor
1.4GHZ 64-bit
2GHZ or faster dual core
Not applicable
Memory
512MB RAM
2GB RAM or greater
32GB RAM Standard Edition4TB RAM Datacenter Edition
Disk space
32GB
40GB Full installation or 10GB Server Core installation

16. Installing Windows Server 2012
Please refer to Windows Server 2012 Installation steps from the document.

17. Post-Install Windows Server 2012 Full (GUI) Network Settings
1: Deploying and Managing Windows Server 2012
Post-Install
Windows Server 2012 Full (GUI)
Network Settings
Joining Server to domain
Windows Updates and Time Zone
Activating Windows Server 2012
Firewall Setting
Windows Server 2012 Core
Demonstration: Using DISM to Add Windows Features

18. Server Manager Console
20410D
1: Deploying and Managing Windows Server 2012
Server Manager Console
One you login to Windows Server 2012 R2 after installation, you will see the Server manager console.
It is used to perform, most of the post installation tasks
Slide 4 of 8: Windows Firewall status

19. Post-Installation You can use Server Manager perform below activities
20410D
1: Deploying and Managing Windows Server 2012
Post-Installation
You can use Server Manager perform below activities
Network Setting
Computer rename
Domain /Workgroup
Windows Firewall
Remote Desktop
Windows Updates
Time Zone configured

20. 20410D
1: Deploying and Managing Windows Server 2012
Network Setting
Slide 3 of 8: Domain or Workgroup
Once you Install the operating system, below actions required
Assign IP address to the server, it must be static.. If this server is not test/lab server
Assign DNS setting after consulting with Active Directory administrator
By default you must put nearby domain controller ip as Primary DNS
DNS configuration is also required to Join server to domain
If IPV6 is not used in environment, uncheck it from Network adapter properties

21. Domain Join From Server Manager, locate Domain Click on “Workgroup”
1: Deploying and Managing Windows Server 2012
Domain Join
From Server Manager, locate Domain
Click on “Workgroup”
If you want to rename computer name, that can he done here
Now click the checkbox – Domain
Type the Domain name
Click OK
It will prompt for credentials
Type domain credential, have permission to join computers
Click ok
It will prompt for a restart, click Restart now
Slide 5 of 8: Remote Desktop

22. Windows Update and Time Zone
1: Deploying and Managing Windows Server 2012
Windows Update and Time Zone
In Server Manager, at the right top side you will find details about Windows Update.
Click to change settings
In most scenarios, it is managed by WSUS Server
Slide 7 of 8: Shows these three together: Last installed updates, Windows Update, Last checked for updates

23. Activating Windows Server 2012
1: Deploying and Managing Windows Server 2012
Activating Windows Server 2012
Discuss the traditional activation process. Ask students about the last time they performed a telephone activation. Ask them if they have ever had any problems with activation, and if so, how they resolved the problem. Ask if they use any automatic activation technologies in their environment.
From Server Manager, you can also active Windows Server Manager
Type the Product key
Mostly, KMS server is used to handle such Product activation

24. Windows Firewall
Post Installation, there is a confusion among System Administrator, whether to keep Windows Firewall should be On or Off. We will discuss it here.
First thing is the it should remain On
As per Microsoft also, it must be on
Keeping it off increases security risks
You must set the Firewall rules
Rules must be created for each port/application
Inbound or Ourbound
Generally, in a corporate environment this configuration is done by group policy

25. Configure Windows Firewall
Please follow the document to configure Windows Firewall in Windows Server 2012 R2

26. 20410D
1: Deploying and Managing Windows Server 2012
Post Install (Core)
Now you are very much aware of Server Manager, below is the command line tool used in Windows Server Core 2012 for Post Installation Configuration.
Path to this C:\Widowds\System32\Sconfig.cmd
Discuss the functionality of sconfig.cmd.
Sconfig is a menu‑driven command‑line tool that presents menu options in a numerical format. Administrators can run commands and perform configurations based on the numbered menu options.
This tool simplifies the process of performing common basic administrative tasks on Server Core, which was a problem for many administrators with the Server Core version that was available with Windows Server 2008 because you needed to know the correct commands.

27. Using DISM to Add Windows Features
1: Deploying and Managing Windows Server 2012
In this demonstration, you see how to use the DISM command-line utility to:
View a list of all Windows features and their current state
DISM /online /get-features
Gather information about the Windows Server Backup feature
(DISM /online /get- featureinfo/featurename:WindowsServerBackup)
Enable the Windows Server Backup feature
DISM /online /enable-feature /featurename:WindowsServerBackup
Emphasize that the feature names are case-sensitive when you use the DISM utility.
Preparation Steps
For this demonstration, start the 20410D-LON-DC1 virtual machine.
Sign in as Adatum\Administrator with the password Pa$$w0rd.
Demonstration Steps
View a list of all Windows features and their current state
1. In Server Manager click the Tools menu, and then click Windows Server Backup.
In the details pane, notice that Windows Server Backup is not installed on the computer.
2. Close the wbadmin-[Windows Server Backup(Local)] window.
Gather information about the Windows Server Backup feature
Right-click the Windows PowerShell icon on the taskbar, and then click Run as Administrator.
Type the following command, and then press Enter:
DISM /online /get-features
3. Type the following command, and then press Enter:
DISM /online /get-featureinfo /featurename:WindowsServerBackup
Enable the Windows Server Backup feature
DISM /online /enable-feature /featurename:WindowsServerBackup
Note: The feature name is case-sensitive.
In Server Manager, click the Tools menu, and then click Windows Server Backup.
In the details pane, notice that Windows Server Backup is now available.
3. Close all open windows.

28. Managing Windows Server 2012
1: Deploying and Managing Windows Server 2012
Managing Windows Server 2012
Administrative Tools and Remote Server Administration Tools
Demonstration: Performing Remote Management
Briefly present the lesson content.

29. Remote Server Administration
Let’s take a scenario, where you have multiple server running different roles. Now to manage each role, you have to Remote Desktop to each server, is it feasible?
Managing Server Roles from the Client Machine
You can install RSAT (Remote Server Administration Tool)
You can install RSAT on your client machine (Windows 7/8/10)
You can open respective role console and connect
Managing Server Roles from a Windows Server 2012 R2
In Windows Server 2012 R2, you must use Administrative tool
You can open the respective role console and connect

30. Server Manager
You already know about Server manager now, once the post installation activity is done, still you need this Server Manager to lots of tasks. Listing few tasks can be done using Server Manager –
Add or Remove Roles & Features
Manage multiple server from single Server
View Events
Launch Windows PowerShell sessions
Configure Server Management Tasks

31. Installing Roles and Features
Please follow the instructions from the document to Install Roles and Features in Windows Server 2012 R2

32. What to do after Roles Installation
Review Role based event to ensure the installed Role is working fine
Run BPA for the role
Best Practices Analyzer (BPA) is a server management tool that is available in Windows Server® 2012 R2, Windows Server 2012, and Windows Server 2008 R2. BPA can help administrators reduce best practice violations by scanning roles that are installed on managed servers that are running Windows Server 2012 or Windows Server 2008 R2, and reporting best practice violations to the administrator.
Here is the method to run BPA using PowerShell

33. 20410D
1: Deploying and Managing Windows Server 2012
Configuring Services
All roles rely on some services to remain operational.
So, after you have the Role Installed, you must set the Recovery setting for the particular services
It will reduce chances of a service failure
Make sure, you don’t set Restart your computer setting, without getting it documented.
Discuss configuring service recovery, and why you should avoid having the service keep restarting.
Remind students to be careful with the option to restart the computer, because a service that keeps failing might trigger a cycle of restarting.
Discuss the benefits of managed service accounts over traditional service accounts. Ask students which method they currently use to manage service accounts.
The slide shows the properties of the DNS Server service, which is accessible from the Services console.
Question
What is the advantage of a managed service account compared to a traditional domain‑based service account?
Answer
The advantage of a managed service account is that you do not have to manage passwords for it.

34. Configure Remote Management
System Administrators commonly use Remote Desktop for remote management of Servers. Let’s discuss what all methods, can be used.
Remote Desktop – you must enable Remote Desktop on each server, while this setting is again managed by group policy in a corporate IT Infrastructure.
RSAT or Features for remote management – We have already discussed in much detail. Please follow the instruction from document to manage roles.
Windows PowerShell - A basic introduction to Powershell

35. Remote Desktop

36. Installing RSAT Tools in Server 2012

46. PowerShell Basics Introduction to PowerShell Variables1
Introduction to PowerShell 2
Variables 3
Loops and Conditions

47. We will discuss about below topics in coming slides.
Introduction of PowerShell.
Installation of PowerShell
Interface and ISE
Cmdlets
Scripting

48. Introduction
Windows PowerShell is a command-line shell and scripting environment that brings the .NET Framework to command-line users and script writers.
Windows PowerShell is not a scripting language. PowerShell is an engine designed to execute commands that perform administrative tasks.
PowerShell provides a foundation upon which Microsoft’s GUI-based administrative tools can rest

49. Installation
Windows PowerShell is pre-installed by default in Windows Server 2008 R2 and Windows .
Windows PowerShell requires the Microsoft .NET Framework 2.0 with Service Pack 1.
The Windows PowerShell ISE requires the Microsoft .NET Framework 3.5 with Service Pack 1

50. PowerShell Versions Versions Operating Systems 1
Windows XP Sp2, Windows 2003, Windows Vista 2
Windows 7, Windows Server 2008 R2, Windows Xp Sp3 3
Windows 8,Windows Server 2012, Windows 7 with SP1, Windows Server 2008 SP1, Windows Server 2008 R2 SP1 4
Windows 8.1, Windows Server 2012 R2, Windows 7 SP1, Windows Server 2008 R2 SP1, Windows Server 2012

51. PowerShell Environment

52. PowerShell ISE
The Windows PowerShell Integrated Scripting Environment (ISE) is a host application that enables you to write, run, and test scripts and modules in a friendly environment. Features in the Windows PowerShell ISE include:
A Command Pane
An Output Pane.
A Script Pane to create, edit, debug, and run, functions, scripts and modules.
Multiple PowerShell tabs.

53. PowerShell ISE

54. cmdlets
A cmdlet (pronounced "command-let") is a single-feature command that manipulates objects in Windows PowerShell. You can recognize cmdlets by their name format -- a verb and noun separated by a dash (-), such as Get-Help, Get-Process, and Start-Service.

55. Scripting
In Windows PowerShell, script files have a .ps1 file name extension. To run a script, type the name of the script at the command prompt. The file name extension is optional.
For example:
c:\test\testscript.ps1
-or-
c:\test\testscript

56. Using PowerShell
The first topic of interest might be the Help system itself. To display information about the Help system in Windows PowerShell, type:
get-help
Then, you might be interested in learning about a few of the basic cmdlets, such as Get-Help, Get-Command, Get-Process, Get-Service, and Get-Eventlog.

57. Get-Help and Get-Command

58. Get-Process and Get-Service

59. Get-EventLog

60. Get-Date

61. Import a Module

62. Formatting Command Outputs
In Windows PowerShell, the only cmdlets that format output are the format cmdlets:
Format-List
Format-Custom
Format-Table
Format-Wide

63. Format-list and Format-Table

64. Format-Custom

65. Using Aliases To find all of the aliases in your session, type:
get-alias
To find the aliases for a cmdlet, type:
get-alias | where-object {$_.definition -eq "<cmdlet-name>"}

66. Execution policy
The default execution policy, Restricted, is the most secure of the execution policies. It does not permit any scripts to run.

67. Advantages and Disadvantages
Advantages Object-Oriented
.NET Objects and Forms supported
More Functions compared to cmd.exe and VBScript. More Extensible via cmdlets, plugins.
Background Jobs
Ease of administration
Disadvantages
Remoting creates openings for an attacker to exploit
WinRM requires a Web server to run on the server

68. Summary In this module, you have learned about:
Introduction of PowerShell.
Installation of PowerShell
Interface and ISE
Cmdlets
Scripting

69. Review Questions What are the advantages of PowerShell?
Which Server operating systems, PowerShell is enabled by default.
What are the different panes available in PowerShell ISE

70. Variables
In PowerShell, variables can contain text strings, integers, and even objects (complete with properties and methods). Special variables exist, which are pre-defined within PowerShell. We have worked with one of these variables ($_) in a prior tutorial.
Special Variable Examples
$_ – Contains the current pipeline object, used in script blocks, filters, and the where statement.
$Args – Contains an array of the parameters passed to a function.
$Error – Contains objects for which an error occurred while being processed in a cmdlet.
$Home – Specifies the user’s home directory.
$PsHome – The directory where the Windows PowerShell is installed.

71. Variables (contd.).
In PowerShell, ALL variable names must start with the “$” character. Once data is assigned to a PowerShell variable, it’s automatically declared. The “=” operator is used to assign data to a variable. Here is a simple example of creating a variable in PowerShell:
$strComputer = “Computer1″<enter>
There is a “Set-Variable” cmdlet that can also be used:
Set-Variable -Name strUser -Value “John Doe”<enter>
Listing Variables
PowerShell keeps a record of all variables, which is accessible via a virtual drive called variable:. Here is how you see all currently defined variables:
Dir variable:

72. Thank you