Download
1 / 9
90 likes | 100 Views
Server Management and Automation Windows Server 2012 R2. Won Huh Product Marketing Manager. Deployment. Server Core Minishell Full GUI. Real world scenario. Deployment options. Deployment method. Server Manager. Desired state c onfiguration. DEPLOYMENT. Deployment.
E N D
Server Management and AutomationWindows Server 2012 R2 Won Huh Product Marketing Manager
Deployment Server Core Minishell Full GUI Real world scenario • Deployment options Deployment method Server Manager Desired state configuration
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.
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
DEPLOYMENT Deployment Server with a GUI Minimal Server Interface R2 supports the compression for SxS storage. Windows Server 2012: from Nov. 2012 to Jul. 2013 Windows Server 2008 R2 SP1: Nov. 2008 to Jul. 2013 In-depth Analysis: How the 42 patches above for Windows Server 2012 Core deployment affected Hyper-V availability Server Core Only updates that should be applied is 2 while running Hyper-V role only. The two updates for Kernel are against Denial of Service vulnerability. And it can be mitigated if Hyper-V management network is segregated. Windows Server 2012 Hyper-V availability is not impacted by Security Updates if there is a risk-based update policy in place. *Client-like: It’s vulnerability that is exposed when a user who locally logged on browses or executes malicious programs. That’s usually not going to happen on Parent-partition of Hyper-V.
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.
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.”
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.
