1. Windows Server 2012
Darmawan Suandi
Technical Evangelist, Developer and Platform Evangelist Group
Microsoft Indonesia
dsuandi@microsoft.com

2. Agenda
 Server Manager
 Minimal Shell
 Power Shell 3.0
 Storage Spaces
 IIS 8.0 – CPU Throttling

3. Management and Infrastructure
Windows Server 2012 User Interface Changes

4. Server Manager
Why redesigned? How does it benefit admins?

5. Why Server Manager Redesigned?

6. Modern UI Style and the Local Server
Experience
• By default, Server Manager
starts when logging on to
server
• Administrative Tools available
from the Tools Menu

7. Server Manager
DEMO

8. Window Server 2012 User
Interface Changes
Why should I care?

9. Why should I care?
The challenges…
• Lowering the attack footprint of the server to the smallest size possible while
keeping it fully patched is a primary responsibility of administrators
• Many administrators are uncomfortable with only a minimal command-line
interface (Server Core)
The Windows Server 2012 solution… multiple interface options
• Allows administrators to use the same familiar graphical tools to administer
the server without using remote management tools
• Removes the overhead of the other operating system elements not needed to
perform that task
• Does not require a re-installation to modify the level of GUI on a server;
modified in the same manner as any other role or feature
• Allows for a single server deployment image

10. User Interface Changes
Windows Server 2012 allows you to have three levels of User
Interface:
• Server Core
• Traditional server core with command line only interface
• Minimal Installation Shell (“MinShell”)
• Server Core plus select UI elements such as MMC support
and Server Manager
• Full Shell
• Full Windows desktop, which can also include the Desktop
Experience

11. MinShell
DEMO

12. Windows PowerShell
What is it?

13. What is Windows PowerShell?
PowerShell is a distributed automation engine with a scripting language and
interactive shell(s).
• Focuses on the business
• Makes change safe through automation
• Bridges the gap between Operators and Developers
PowerShell 3.0 is available for the following
Operating Systems:
• Built-in:
• Windows Server 2012
• Windows 8 (built-in)
• Downloadable for:
• Windows 7 SP1
• Windows Server 2008 SP2
• Windows Server 2008 R2 SP1

14. Windows PowerShell
Why should I care?

15. Why should I care?
The challenge…
• Reduce errors during configuration changes
• Reduce the skill set required for authoring automation of complex solutions
• Locate and import the numerous PowerShell modules into each session
• Reduce the syntax learning curve, especially for people new to PowerShell
• Bridge the gap between Operators and Developers
The Windows Powershell 3.0 solution….
• Allows for use of tested scripts, reducing the number of errors that impact
production environments
• Improves efficiency due to the dramatic increase number of built-in cmdlets
• Includes new features designed to speed understanding and correct usage of
syntax (Show-Command)
• Makes excellent progress toward bridging the gap between Operators and
Developers

16. Windows PowerShell
Technical Overview

17. What’s New for IT Professionals
in PowerShell 3.0?
Easier to Automate
• ~2,430 built-in cmdlets (compared with ~ 230 in Windows Server 2008/R2)
• Skill level required to successfully automate complex solutions is reduced
• Language and utility cmdlets are simplified to reduce steps and syntax
• Improved authoring tools
• PowerShell ISE supports rich Intellisense, snippets, 3rd party extensibility, and
a Show-Command window
Windows Workflow Foundation integration
• Operators can use any available Workflow designers to create workflows
Scheduled Jobs
• Seamless integration with Task Scheduler
Robust Networking
• PowerShell Remoting enabled by default
• Disconnected session support

18. Windows PowerShell
DEMO

19. Storage Spaces
Overview

20. What is Storage Spaces & Thin
Provisioning?
Storage Spaces
• New in Windows Server 2012
• Provides an in-box storage virtualization that can use low-cost commodity storage devices
• Aggregates unallocated space on physical disks installed in or connected to servers through
a “pooling” model
• Can provide a cost-effective platform for business critical storage across a variety of
scenarios
Thin Provisioning
• “Just-in-Time” allocations of storage with the ability to reclaim storage (“Trim”)
• Integrated with Storage Spaces

21. Why should I care?
The features of Storage Spaces are designed to meet a variety of challenges in
support of highly-available storage
Storage pools
• Can be mapped to combinations of hard disks as well as solid-state drives
(SSDs)
• Can be expanded dynamically by simply adding additional drives, thereby
seamlessly scaling to cope with unceasing data growth
Multitenancy
• Administration of storage pools can be controlled through access control lists
(ACLs) and delegated on a per-pool basis
• Can be fully integrated with Active Directory Domain Services
Resilient storage
• Storage Spaces support two optional resiliency modes (mirroring and parity)
• Per-pool support for disks that are reserved for replacing failed disks (hot
spares), background scrubbing, and intelligent error correction allow
continuous service availability despite storage component failures

22. Why should I care? (cont.)
Continuous Availability
• Failover clustering integration delivers continuously available service
deployments
• One or more pools can be clustered across multiple nodes within a single
cluster. Storage spaces can then be instantiated on individual nodes, and the
storage will seamlessly fail over to a different node when necessary (in response
to failure conditions or due to load balancing)
• Integration with CSVs permits scale-out access to data
Optimal storage use through thin provisioning
• To allow businesses to easily share storage capacity among multiple unrelated
data sets and thereby maximize capacity use
• Trim support permits capacity reclamation when possible
Operational simplicity
• Easily managed through the File Services role in Server Manager
• Fully remoteable and scriptable management through the Windows Storage
Management API, WMI, and Windows PowerShell
• Designed to be compatible with existing backup-restore and cloning tools, as
well as snapshotting infrastructures

23. Storage Spaces
Technical Overview

24. Storage Spaces Requirements
• Windows Server 2012 Drive Stand-Alone Clustered File
• Serial ATA (SATA) or Serial Attached SCSI (SAS) Type File Servers Servers
connected disks (in an optional just-a-bunch-of- SATA Supported
disks [JBOD] enclosure) SCSI Supported
• Multinode clustered shared-storage deployments iSCSI Supported Supported
• Two or more servers running Windows Server SAS Supported Supported
2012 USB Supported
• Requirements as specified for failover
clustering and Windows CSV
• SAS connected JBODs that comply with
Windows Certification requirements
• The criterion for determining which drives are eligible to be part of a Pool are:
• Minimum drive size is 10 GB
• Drive is empty, i.e. no partition data exists on the drive
• Drive is not assigned to any other pool
• The Primordial Pool will consist of Physical Disks that are not assigned to
any existing Storage Pool

25. Storage Spaces
DEMO

26. Web Application Deployment
with IIS 8.0
Why should I care?

27. Why should I care?
The challenges The IIS 8.0 solutions
Managing a large number of dedicated IP addresses for each SNI uses the host name to identify the network endpoint so
secure site multiple dedicated IP addresses are no longer needed
Taking full advantage of emerging high-performance NUMA-Aware Scalability can help you take advantage of
hardware systems emerging, high-performance server hardware systems for
greater efficiency, scalability and manageability
Managing resources across application pools IIS CPU Throttling is used to establish the maximum CPU
consumption allowed per application pool
Management of SSL certificates is time consuming and SSL certificate management is greatly simplified - no
costly certificates to import to each server; there is now support
for a centralized certificate store
Improving the speed of first connections to a web Application Initialization helps to speed up the initialization
application of websites
Protecting web sites from DoS and brute force attacks IP Address filtering can be dynamically filtered; FTP Logon
Attempt Restriction provides protection from brute-force
attacks
Supporting multiple types of applications on the same Open Web Platform provides for support and management
server of .NET 3.5, .NET 4.5 and open source applications

28. Application Initialization
• x Example modifications in applicationHost.config
Application pool configuration entry:
<add name=".NET v4.5" managedRuntimeVersion="v4.0" />
Application configuration entry:
<application path="/appinit" applicationPool=".NET v4.5">
Example modifications to application level web.config
<applicationInitialization skipManagedModules="true" >
<add initializationPage="/default.aspx" />
</applicationInitialization>

29. IIS CPU Throttling
Sandboxing sites
and applications

30. IIS CPU Throttling
DEMO

31. 3
1

33. Server Core •
•
•
.Net Framework 4.5
Active Directory (AD)
Active Directory Lightweight Directory
Services (ADLDS)
• Active Directory Certificate Services (ADCS)
Microsoft promotes Server Core as • DHCP Server
the primary server deployment • DNS Server
• File Services
option • BITS Server
• BranchCache
• Server Core now supports more • Hyper-V
roles and services, including .Net • Internet Information Services (IIS)
Framework 4.5 and SQL Server • Printing Services
• Streaming Media Services
2012 • iSCSI
• Firewall-friendly remote • Load Balancing
management (WinRM) and • MPIO
Windows PowerShell are • qWave
• Telnet
enabled and installed by default • Unix Migration
• Added the ability to easily move • SQL Server 2012
between Server Core and
MinShell

34. MinShell
Minimal User Experience
option
• Server Core with GUI tools
• Server Manager and
cmd.exe launch by default
when server is booted
•Allows other GUI tools to
be loaded
• Enabled through Add Roles
and Features wizard, or with
PowerShell

35. Enabling/Disabling MinShell
Install-WindowsFeature
Server-Gui-Mgmt-Infra
Install-WindowsFeature
Server-Gui-Shell
Install-WindowsFeature
Desktop-Experience
Uninstall-WindowsFeature
Server-GUI-Shell
Uninstall-WindowsFeature
Server-GUI-Shell -remove

36. Interface Feature Sets
Server Core MinServer Server W/GUI Desktop Experience
Command Prompt Available Available Available Available
Windows PowerShell Available Available Available Available
Server Manager Not Available Available Available Available
MMC Not Available Available Available Available
Control Panel Not Available Not Available Available Available
Control Panel Applets Not Available Some Available Available Available
Windows Explorer Not Available Not Available Available Available
Taskbar Not Available Not Available Available Available
Notification Area Not Available Not Available Available Available
Internet Explorer Not Available Not Available Available Available
Help Not Available Not Available Available Available
Themes Not Available Not Available Not Available Available
Metro Start Screen Not Available Not Available Not Available Available
Metro Apps Not Available Not Available Not Available Available
Media Player Not Available Not Available Not Available Available