TechMentor 2012

Deploying Windows Server 2012: From Bare Metal, Server Core, Minimal Server Interface, and More Harold WongBlogs.technet.com/haroldwong@haroldwong

Agenda

Deployment methods and what’s new in Windows Deployment Services (WDS)Windows Server 2012 Installation OptionsMinimal Server InterfaceMinimizing disk space using Features on Demand

High Touch – Image Based Setup

Essentially the same as Windows Server 2008 R2 Setup

Existing scripts and deployment tools that you have for Windows Server 2008 R2 will work with Windows Server 2012Provides a single unified process with which all customers can install WindowsSpeed improvements

IBS Setup optionsUpgrade: Keep files, settings, and applicationsCustom: Install only

Lite Touch

Microsoft Deployment Toolkit (MDT) 2012Step 1: Obtain the Required Software

http://go.microsoft.com/fwlink/?LinkId=76620

Step 2: Prepare the MDT EnvironmentStep 3: Configure MDT to Create the Reference ComputerStep 4: Deploy Windows Server 2012 and Capture an Image of the Reference ServerStep 5: Configure MDT to Deploy Windows Server 2012 to the Target ServerStep 6: Deploy the Captured Image of the Reference Server to the Target Server

Windows Deployment Services (WDS)

End-to-end solution for clean installations over the network using PXE bootWhy use WDS?

Reliable – in use since 2006Proven – by external and internal customersScalable – can deploy over 300 machines at a timePowerful – flexible and extensibleSimple – improved manageability

Standalone Mode

Standalone serverNew server configuration optionDecoupled from Active Directory

Local data storeWorks with management tools

MMC GUI snap-in and WDSUtil command line tool

MMC Improvements

Device management now in the MMCClient Unattend file generatorNew server properties options

Max TFTP block sizeUDP port policy

Image priorityExpected Deployment Results wizard

See the results of your choices before you deployPresents the deployment options for a certain device Included in the MMC and also available from the command line

Diagnose Your Deployments

Server trace log updatesETW-based logsSupport for /trace parameterSetuperr.log/Setupact.log still available

Performance countersProvides better understanding of what the server is “doing”Added many for Windows 8 – now over 50

x86 UEFI and IPv6 PXE Support

UEFI 2.3.1 supportPXE extended to x86 UEFI architectureSeparate settings for BIOS and UEFI

IPv6 support for PXEUEFI requires firmware support in UNDI and UEFI version (2.3.1 or later) Requires stateful DHCPv6IPv6 is also supported in TFTP, multicast, WDS client, and setup.exe

TFTP Download Enhancements

Dynamically determined variable-size transmission windowTripled performance on Gb networks from ~8 MB to ~20-30 MB per secondAccommodates clients with “small” NIC buffers

Shared UDP port allocationImproves scalability - Uses 16 ports by defaultAdds performance counters

Shared client bufferDetects clients downloading the same fileUses shared in-memory buffer of the file for all clientsReduces memory use and improves performanceAdds performance counters

In-place WIM Multicast Apply

What it doesEliminates download of the WIM before applying to the local diskAllows the WIM to be decompressed on-the-fly as received over the network

Why it’s goodFaster process that uses a smaller disk footprint

What’s needed to use it?Minimum of 2 GB RAM

VHDX Apply

What it doesApplies VHDX file directly to disk using sector-based deploymentMultiple-partition deployment for OS & recovery partition in single imageMust use VHDX format, not VHD

WDS does not create the VHDXAvailable for

WDSMCast.exe and WDSClient.exe

Windows Server 2012 Deployment Options

Server CoreThe default deployment optionRSAT for remote GUI managementPowerShell support achieves critical mass with 2300+ cmdletsMore roles and features available

Server with a GUIEquivalent of full Server in Windows Server 2008 R2Provided for backwards compatibility

Windows Server 2012 Configuration Levels

Server with a GUI

Minimal Server Interface

Server Core

NEW 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• NEW Can move between Server Core and

Full Server by simply installing or uninstalling components

Classic “Full Server”• Full Metro-style GUI shell• Install Desktop Experience to run Metro-

style apps

Transitioning between Server Core and Server

Server ManagerRemote only to go from Server Core to Server

PowerShell

Transitioning with Server Manager: PS cmdlets

Full Server to Server Core

Server Core to Full Server

POWERSHELL

Uninstall-WindowsFeature Server-Gui-Mgmt-Infra -Restart

POWERSHELL

Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell -Restart

NEW Can install multiple features with one command by separating with commas

Single reboot required to restart all services

TechMentor 2012

demo

Transitioning between Server Core and Server with a GUI

Minimal Server Interface

It’s a Server with a GUI…

…but without Windows Explorer and Internet Explorer

Provides some of the benefits of Server Core for those products or admins that can’t fully make the transition to Server Core

Enables administrators and developers to begin shifting to support headless servers

Remove dependencies on Shell and Internet Explorer

Enable full remote management

Higher availability

Converting to and from Server Graphical Shell

Server ManagerUninstall Server Graphical Shell:

Install Server Graphical Shell:

Server Core to Minimal Server Interface

POWERSHELL

Uninstall-WindowsFeature Server-Gui-Shell -Restart

POWERSHELL

Install-WindowsFeature Server-Gui-Shell -Restart

POWERSHELL

Install-WindowsFeature Server-Gui-Mgmt-Infra -Restart

Limitations of the Minimal Server Interface (1/2)

Common Dialog box is functional (except networking)

Any UI with dependencies on items implemented as Shell Namespace Extensions will fail

Certain CPLs are namespace extensions, e.g. Networking

Internet Explorer is not available when Server Graphical Shell is uninstalled

Links in UI won’t workHelp isn’t available – calls to HTML Help API will return NULL!

Limitations of the Minimal Server Interface (2/2)

Some file associations and protocol handlers brokenhttp://file://*.chm

Some DLL files not installedCheck for dependencies or delay loads might fail!

DUMPBIN (Windows SDK)Dependency Walker (http://www.dependencywalker.com, freeware)

Test your applications on the Minimal Server Interface!

Detecting the state of Server Graphical Shell

Using the RegistryHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Server\ServerLevels

WMIWin32_ServerFeature class can be used to determine installed roles and features

http://msdn.microsoft.com/en-us/windows/cc280268Server-Gui-Shell has an ID of 99Server-Gui-Mgmt-Infra has an ID of 478

Server Core Minimal Server Interface

Server Graphical Shell

ServerCore = 1 Set Set Set

ServerGuiMgmt = 1

Not Set Set Set

ServerGuiShell = 1

Not Set Not Set Set

Local Shell CapabilitiesServer Core Minimal Server

InterfaceServer with a GUI Desktop

Experience

Command Prompt a a a a

PowerShell/.NET a a a a

Server Manager x a a a

MMC x a a a

Control Panel x x a a

CPL Applets x Some a a

Explorer Shell x x a a

Taskbar x x a a

System Tray x x a a

Internet Explorer x x a a

Help x x a a

Themes x x x a

Start screen (Metro)

x x a a

Metro-style apps x x x a

Media Player x x x a

TechMentor 2012

demo

Minimal Server Interface

Reducing on Disk Footprint

All Roles and Features are copied to the Windows Side by Side store (\windows\winsxs) during Setup

Uses disk space to store roles and features that may never be installed

Windows Server 2012 now has Features on DemandAllows an administrator to remove unneeded roles and featuresFiles for removed roles and features are deleted from the Side by Side storeCan be used to minimize VHD footprint

Server Core Installation Option

Server Core installation option is created using Features on Demand

Unsupported Roles and Features are removed from \windows\winsxs to maintain minimal footprintShow as Removed in PowerShell

Show as Payload Removed in Dism.exe

Removing Roles and Features

Files for <FeatureName> will be deleted from the \windows\winsxs folder

Must use PowerShell, remove is not available in Server Manager

POWERSHELL

Uninstall-WindowsFeature <FeatureName> -Remove

Sources for Removed Roles and Features

Reinstallation SourcesWindows Update

If server has Internet access, it can use WU

Use the WIM directlyMount WIM

Can mount the install WIM

Running Server’s \windows\winsxs folderLocation can be specified via Group Policy:

Computer Configuration > Administrative Templates > System > “Specify settings for optional component installation and component repair”

Mounting the WIM

Create a folder to mount the WIM in:

Determine the index of Server with a GUI:

Mount the WIM:

Install role or feature:

CMD

mkdir c:\mountdir

CMD

dism /mount-wim /WimFile:<drive>:\sources\install.wim /Index:<#_from_step_2> /MountDir:c:\mountdir /readonly

CMD

Dism /get-wiminfo /wimfile:<drive>:sources\install.wim

POWERSHELL with mounted WIM

Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source c:\mountdir\windows\winsxs

Using the WIM Directly

Determine the index of Server with a GUI:

Install role or feature specifying a source of WIM:<path>:<#_from_step_1>

CMD

Dism /get-wiminfo /wimfile:<drive>:sources\install.wim

POWERSHELL

Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source wim:<drive>:\sources\install.wim:4

Reinstalling Roles and Features

Server ManagerPowerShell

POWERSHELL

Install-WindowsFeature <FeatureName> -Source <Source>

Server Core Installation Option to Server

If Server Core was installed using Setup converting to Server requires a source

With a mounted WIM

Using the WIM directly

POWERSHELL with mounted WIM

Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source c:\mountdir\windows\winsxs

POWERSHELL

Install-WindowsFeature Server-Gui-Mgmt-Infra,Server-Gui-Shell –Restart –Source wim:d:\sources\install.wim:4

TechMentor 2012

demo

Reducing Disk Footprint with Features on Demand

.NET 3.5 and Features on Demand

Not included in the Windows Server 2012 imageApplication Compatibility shim will prompt to install if running an application that requires .NET 3.5Installation sources

Windows UpdateInstall media \sources\sxs

Whitepaper on .NET 3.5 in Windows Server 2012http://msdn.microsoft.com/library/windows/hardware/hh975396

Key Resources

Download Windows Server 2012 RC Bits …http://aka.ms/hwws2012

Download System Center 2012…http://aka.ms/hwsc2012

Free Training on Microsoft Virtual Academy … http://aka.ms/virtualacademy

Find me on Twitter … @haroldwong

Check out my Blog … http://blogs.technet.com/haroldwong

© 2012 Microsoft Corporation. All rights reserved. Microsoft, Windows, Windows Vista and other product names are or may be registered trademarks and/or trademarks in the U.S. and/or other countries.The information herein is for informational purposes only and represents the current view of Microsoft Corporation as of the date of this presentation. Because Microsoft must respond to changing market conditions, it should not be interpreted to

be a commitment on the part of Microsoft, and Microsoft cannot guarantee the accuracy of any information provided after the date of this presentation. MICROSOFT MAKES NO WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, AS TO THE INFORMATION IN THIS

PRESENTATION.