Module 5: Server Management & Automation with Windows Server 2012 R2

1. Module 5: Server Management & Automation with Windows Server 2012 R2 Rick Claus Microsoft Sr. Technical Evangelist Corey Hynes Lead Technical Architect, holSystems

2. Jump Start Target Agenda Server Management & Automation with Windows Server 2012 R2

3. Talk with our Experts in Chat tool. #WS2012JS Hands-On Labs DOWNLOAD Windows Server 2012 R2 Preview DOWNLOAD System Center 2012 R2 Preview http://technet.microsoft.com/evalcenter

4. Agenda • Windows Server 2012 R2 Preview is a great operating system for many servers and the devices that connect them—whether physical or virtual, on-premises or off-premises. • Windows Server 2012 R2 Preview is a cloud-optimized operating system that provides customers with a standards-based, simplify your routine task platform. • This platform enables efficient and productive multiserver manageability and automation capabilities. • Introduction • Standards-based management • Simplify your routine tasks • Deployment • Multiserver management • Ecosystem and extensibility

5. Scenario summary Ecosystem and extensibility Simplify your routine tasks Multiserver management Deployment options Standards-based management

6. Standards-based management Simplifies the management of a diverse ecosystem Standard APIs Windows Management Framework Standard protocols Standard models

7. Managing a diverse ecosystem STANDARDS-BASED MANAGEMENT “The NxM Problem” IT Pro Tool Developer Solution Provider Number of devices to manage Methods to manage each device Disk Storage Operating system Devices Managed objects

8. Windows Management Framework STANDARDS-BASED MANAGEMENT Maximize the value of using the Windows Management Framework IT Pro Tool Developer Solution Provider Windows Management Framework Disk Storage Operating system Devices Managed objects

9. Standard models, protocols, and APIs STANDARDS-BASED MANAGEMENT Maximize the value of using the Windows Management Framework IT Pro ToolDeveloper Solution Provider Standard APIs: MI Client, Windows PowerShell, Open Data Protocol (OData) Windows Management Framework Standard protocols: WS-Management, REST, HTTP, PSRP Standard models: Common Information Model (CIM) schema, Storage Management Initiative Specification (SMI-S) Disk Storage Operating system Devices Managed objects

10. Approach for Windows Server 2012 R2 Preview STANDARDS-BASED MANAGEMENT Non-Windows REST clients Management OData Service Dispatching Layer CIM Model Dispatching File PowerShell Generic CIM Module Service Module CIM client CIM servers CIM client WS-Man Protocol Handler

11. OpenManagment Infrastructure STANDARDS-BASED MANAGEMENT • New WMI provider API (MI) with extended Windows PowerShell semantics. • Open Management Infrastructure (OMI) for Linux and UNIX with the same MI provider API. • Full implementation of WS-Man on Windows and Linux/UNIX. • New MI client with integrated Windows PowerShell layer. Windows Linux/UNIX Windows PowerShell MI provider Classic provider MI provider MI client API Microsoft .NET MI API Native MI API Windows Management Infrastructure Open Management Infrastructure Any device WS-Man protocolhandler WS-Man protocol handler WS-Man protocol handler WS-Man protocol handler WS-Management

12. One Management Infrastructure STANDARDS-BASED MANAGEMENT Open source Windows Management Infrastructure server implemented by Microsoft. • Includes Windows Server Management protocol stack. • Interacts with MI client and Windows PowerShell outofthebox. Portable • Uses the same MI provider interface as Windows Management Infrastructure. • Can share provider development tools with Windows Management Infrastructure. Scalable Small footprint

13. Approach for Windows Server 2012 R2 Preview STANDARDS-BASED MANAGEMENT Simplify and lower the cost of: • Instrumenting services and devices for Windows—through Windows Management Infrastructure (WMI) providers. • Developing PowerShell cmdlets in native code, as CIM providers. • Standards-based way to access and manage storage. • SMI-S service in the box for easier storage discovery. Use SMI-S to manage external storage arrays: Use OMI to manage network switches: • Standards-based way to access and manage network switch. • OMI in the box for configuring network switch.

14. Switch managementStandards based automation Easily deploy and operate network switches in standards approach Switch x CIM • PowerShell scripts for common switch management tasks. • SCVMM imports and validates port configuration from switch. • Logo Program: Server Certification for switch endors implementing CIM Schema. • Define mechanisms to auto generate PowerShell cmdlets for vendor extensions. Windows (PowerShell) Switch y CIM WS-Man SCVMM Non-Windows Switch z CIM

15. Out-of-band hardware managementStandards based automation Manage hardware in standards approach BMC x SMA S H • Support multiple industry standards, schemas and protocols. • PowerShell Cmdlets and WMI provider shipping in box to provide a common abstraction layer. • Test scripts for validating hardware implementation. SMASH (WS-Man) BMC y I P M I PCSV IPMI (RMCP+) Windows (PowerShell) PCSV (WS-Man) BMC z PCSV

16. Simplify your routine task • Ease of use Windows PowerShell Real world scenario More intuitive Provides greater flexibility, reducing the cost and complexity of management in a diverse datacenter ecosystem. Greater resiliency

17. SIMPLIFY YOUR ROUTINE TASK Windows PowerShell 4.0 Key features • Ease of use • Integrated Scripting Environment: IntelliSense, Code Snippets. • PowerShell web access. • Real world scenario • Domain join. • System Center integration. • Extensive coverage • Rich management through more than 3000+ cmdlets. • Greater resiliency • Robust session connectivity. • Job scheduling. • Windows PowerShell workflow.

18. SIMPLIFY YOUR ROUTINE TASK Ease of use IntelliSense • Run Windows PowerShell ISE to execute commands and write, test, and debug scripts in a single Windows-based graphic user interface with multiline editing, tab completion, syntax coloring, and selective execution. • Context-sensitive command completion for cmdlet and script names, parameter names and enumerated values, and property and method names. • Show-Command pane for finding and running cmdlets in a dialog box.

19. SIMPLIFY YOUR ROUTINE TASK Ease of use Simplified Scripting • Syntax simplification: Windows PowerShell 4.0 includes simplified, consistent syntax across all cmdlets. • Simplified scripting through Windows PowerShell ISE: • Built-in code snippets include templates for functions, parameters, and statements. • Users do not need to remember the syntax. Snippets add reusable text to scripts and commands.

20. SIMPLIFY YOUR ROUTINE TASK Extensive coverage Windows PowerShell 4.0 • For example • New modules for: • AppBackgroundTask • Defender • NetEventPacketCapture • PSDesiredStateConfiguration • SyncShare • WDS • WebApplicationProxy • WindowsSearch • Others • Comprehensive management with more than 3000+ cmdlets in 100+ modules. • Many new modules that allow the use of Windows PowerShell 4.0 to manage all aspects of the datacenter.

21. Internet SIMPLIFY YOUR ROUTINE TASK Greater resiliency Windows PowerShellWeb Access • Manage computers running Windows by using Windows PowerShell within a browser. • Broad support for popular browsers. • Built for tablets and mobile devices. Server 1 Server 2 Windows PowerShell Web Access Gateway DMZ Web-based Console User Server 3 Corporate Network

22. Internet SIMPLIFY YOUR ROUTINE TASK Greater resiliency 03 Robust session connectivity Server 1 • User connects via the browser through the PowerShell Web Access Gateway to run a script on Server 1. • User loses connection to the internet. • User reconnects to internet at a later point in time and reconnects to the Windows PowerShell session which is still in a connected state and still running. Script Windows PowerShell Web Access Gateway Corporate Resource DMZ Web-based Console User

23. SIMPLIFY YOUR ROUTINE TASK Greater resiliency 03 Job scheduling Improve management automation. Schedule jobs for executionat a later time, according to a particular schedule.

24. SIMPLIFY YOUR ROUTINE TASK Greater resiliency 03 Jobs execute based on triggers Job scheduling Improve management automation. • Weekly • Once • Daily Schedule jobs for executionat a later time, according to a particular schedule. • At startup • At logon

25. SIMPLIFY YOUR ROUTINE TASK Greater resiliency 03 Jobs example Jobs execute based on triggers # Create a job trigger based on the desired schedule and register the job $trigger = New-JobTrigger -Daily -At 4am Register-ScheduledJob -Name MyScheduledJob -ScriptBlock { Get-Process } -Trigger $trigger Get-ScheduledJob # Once the trigger has fired and the job has run, you can work with it the same way you do regular background jobs Import-Module PSScheduledJob $j = Get-Job -Name MyScheduledJob Receive-Job $j • Weekly • Once • Daily • At startup • At logon

26. SIMPLIFY YOUR ROUTINE TASK Greater resiliency 03 Windows PowerShell Workflow A set of long-running activities (in sequence or in parallel) that perform complex management tasks, such as multi-machine application provisioning. Authored using a Windows PowerShell script or the Visual Studio Workflow Designer (XAML). Workflows survive system interruptions (reboots, network problems): suspend-job/ resume-job, persist state and metadata.

27. SIMPLIFY YOUR ROUTINE TASK Real world scenarios • Join-Domain through Workflow workflow Join-Domain {     param(         [Parameter(Mandatory)]         [string]$DomainName,         [Parameter(Mandatory)]         [PSCredential]$DomainCredential         )     Get-CimInstance -ClassName win32_computersystem     Add-Computer -Credential $DomainCredential -DomainName $DomainName -LocalCredential $PSCredential     Restart-Computer -Force -Wait     Get-CimInstance -ClassName win32_computersystem } # Usage Join-Domain -PSComputerName <list of machines> -PSCredential <local admin credential> -DomainName <domain name> -DomainCredential <credential that can join machine to domain>

28. New Modules in Windows Server 2012 R2 Preview16 new AppBackgroundTask Defender DFSR NetEventPacketCapture NetNat PcsvDevice PSDesiredStateConfiguration SoftwareInventoryLogging StartScreen SyncShare TLS WDS WebApplicationProxy WindowsSearch WssCmdlets WssSetupCmdlets

29. New Cmdlets in Windows Server 2012 R2 Preview652 new 223 WssCmdlets 60 ADFS 58 IpamServer 42 DFSR 36 RemoteAccess 33 WDS 26 NetEventPacketCapture 18 DhcpServer 18 Storage 14 SyncShare 14 Hyper-V 13 PSDesiredStateConfiguration 13 NetNat 13 VpnClient 10 WebApplicationProxy 10 SoftwareInventoryLogging 8 Dism 7 SmbShare 5 PcsvDevice 5 WssSetupCmdlets 4 TLS 3 StartScreen 3 NetTCPIP 3 IscsiTarget 2 WindowsSearch 2 TrustedPlatformModule 2 PrintManagement 1 SmbWitness 1 NetWNV 1 AdcsAdministration 1 Deduplication 1 NetSecurity 1 FailoverClusters 1 DnsServer

30. New Parameters in Windows Server 2012 R2 Preview3,603 new 619 IpamServer 384 WssCmdlets 351 RemoteAccess 315 ADFS 285 WDS 190 DFSR 170 NetEventPacketCapture 166 Hyper-V 157 Storage 124 DhcpServer 117 VpnClient 99 SyncShare 82 NetNat 79 Dism 74 PcsvDevice 67 WebApplicationProxy 42 SoftwareInventoryLogging 40 NetTcpIP 39 SmbShare 37 PSDesiredStateConfiguration 19 NetWNV 19 IscsiTarget 15 DnsServer 14 WssSetupCmdlets 13 PrintManagement 12 NetSecurity 11 FailoverClusters 11 Deduplication 10 TLS 8 StartScreen 6 PSScheduledJob 5 AppX 4 WindowsSearch 3 ClusterAwareUpdating 2 PowerShellWebAccess 2 AdcsAdministration 2 BitsTransfer 2 TrustedPlatformModule 2 Microsoft.PowerShell.Management 2 SmbWitness 1 SMISConfig 1 Microsoft.PowerShell.Utility 1 NetQos 1 FileServerResourceManager

31. Deployment Server Core Minishell Full GUI Real world scenario • Deployment options Deployment method Windows Deployment Services Server Manager Desired state configuration

32. DEPLOYMENT Deployment Deployment options • Server Core • The default deployment option. • RSAT for remote GUI management. • PowerShell support achieves critical mass with 3000+ cmdlets. • More roles and features available. • Server with a GUI • Equivalent of full Server in Windows Server 2008 R2. • Provided for backwards compatibility.

33. DEPLOYMENT Deployment Configuration levels Server with a GUI • Classic “Full Server” • Full Metro-style GUI shell. • Install Desktop Experience to run Metro-style apps. • Full Server without Server Graphical Shell • No Explorer, Internet Explorer or associated files. • MMC, Server Manager, and a subset of Control Panel applets are still installed. • Provides many of the benefits of Server Core for those applications or users that haven’t yet made the transition. • Server Core • Can move between Server Core and Full Server by simply installing or uninstalling components. Minimal Server Interface Server Core

34. Local Shell Capabilities

35. DEPLOYMENT Deploying with Server manager Server manager deployment • Select installation type: role or feature-based. • Select destination server: server pool or VHD. • Select server roles. • Select features. • Confirm selection and install.

36. DEPLOYMENT Deploying with WDS Server manager deployment Plan, manage, diagnose Boot with PXE Get into WinPE • Powershell cmdlet. • Update images. • Monitor status. • Remotely manage WDS. First boot and OOBE Inject drivers Apply full OS image

37. DEPLOYMENT Desired State Configuration DSC • Components of your data center have the correct configuration. • PowerShell language extensions and providers which enable declarative, repeatable deployment. • Define the exact configuration of target nodes (computers or devices) and prevent “configuration drift.”

38. DEPLOYMENT Desired State Configuration “Make it so” phase Declarative configuration is reified through imperative providers. • Staging phase • Fully declarative configuration representation using DMTF standard MOF instances. • Configuration is calculated for all nodes. Authoring phase May include imperative as well as declarative code. 3rd party languages and tools Local DSC cache Configuration staging area (Contains DSC data) PS V1, V2, V3 Agent of consistency PS V4*** Imperative providers • *** When authoring in PowerShell, on top of PSV3 imperative features, PSV4 adds: • Declarative syntax extensions. • Schema validation (early-binding). • Providers implement changes: • Monotonic. • Imperative. • Repeatable.

39. Managing multiple service • Dashboard with overall view of server environment. • Easily and quickly see which servers have issues. Glance-able Actionable • Fix issues from Server Manager, no need to open other tools. • Works over multiple servers. • Start and stop services. • Add roles. Relevant • Server Manager dashboard customizable. • Create custom groups based on your needs.

40. MULTI SERVER MANAGEMENT Server Manager Glance-able dashboard • Overall view. • Quickly see issues. • Lists Physical and Virtual Machines.

41. MULTI SERVER MANAGEMENT Server Manager Actionable functions • Contextual menu of Server Management functions. • Fix issues from within Server Manager. • Ability to stop and start services on one or multiple machines. • Add roles remotely. • Add roles to offline VHDs.

42. MULTI SERVER MANAGEMENT Server Manager Relevant functions • Provides access to all the relevant functions and roles on server with one click, in one tool. • Applicable on menus at all levels within Server Manager.

43. MULTI SERVER MANAGEMENT Server Manager Server roles • Manage servers individually or as a group. • Selecting server role lists all servers with that role.

44. MULTI SERVER MANAGEMENT Server Manager Server groups • Group servers based on role, location, or other criteria. • Easy to monitor and manage groups of servers. • Servers can be in added to multiple groups.

45. MULTI SERVER MANAGEMENT Server Manager Host groups • BPA—Best Practice Analyzer. • Filters available: • Severity • Category • Server

46. MULTI SERVER MANAGEMENT Server Manager Single server • When single server selected displays only events, services, and BPA entries relevant to that server.

47. Ecosystem and extensibility • Provides a standard set of tools to deploy and administer servers across the datacenter. Standardized automation across the datacenter. • Interoperates with environments that are not based on Windows. Extension of the development and operations story. • Enables developers and operations to use the same interfaces.

48. Automation across the datacenter ECOSYSTEM AND EXTENSIBILITY There is no management interoperability without a standard interface and protocol. • Lack of standards results in proprietary agents, protocols, and clients. • Complicates deployment and maintenance. • Consumes additional resources. • Increases the security exposure.

49. Managing heterogeneous environment ECOSYSTEM AND EXTENSIBILITY Multiple industry standards makes admins hard to manage and automate. Application • Application management: .NET, Java, 3rd party management tool. • Operating System management: WMI, vendor-specific management tool. • Compute management: DCMI/IPMI, SMASH/CIM, vendor-specific management tool. • Network management: SNMP, vendor-specific management tool. • Storage management: SMI-S, vendor-specific management tool. Operating system Compute Network Storage

50. Eco system in Standards based ECOSYSTEM AND EXTENSIBILITY WS-Man for standard communication and management with Common Information Model. Windows Application Operating system Compute WS-MAN Others Network Storage