17
Windows Deployment - Now and Into the Future Michael Niehaus @mniehaus http:// blogs.technet.com/ mniehaus #MMSMinnesota

Windows Deployment - Now and Into the Future Michael Niehaus @mniehaus s #MMSMinnesota

Embed Size (px)

Citation preview

Windows Deployment - Now and Into the Future

Michael Niehaus@mniehaushttp://blogs.technet.com/mniehaus

#MMSMinnesota

History of Windows Deployment

• 1995• Windows 95 was released, upgrade from Windows for Workgroups 3.11 using a stack of floppies• Ghost was created

• 1996• Windows NT 4.0 was released, looked just like Windows 95, installed from a bigger stack of

floppies – or you could use CDs and network installs• Sysprep was released to make SIDWalker obsolete

• 2000• Windows 2000 was released, looked just like Windows 95, installed from CDs• Active Directory and Group Policy started the demise of Netware

• 2001• Windows XP was released, prettier than Windows 95• VBScript, WMI, Windows Installer, MMC were introduced

• 2003• Business Desktop Deployment 1.0 was released, using PowerQuest imaging tools (later acquired

by Symantec)

History of Windows Deployment

• 2004• Windows XP SP2 was released, more secure and stable, “simple to deploy service pack”• SMS 2003 OS Deployment Feature Pack (first to use WIM file format) and Business Desktop Deployment 2.0

released• USMT 2.6 released, supported migration of data from multiple users

• 2005• Business Desktop Deployment 2.5 released, added support for 64-bit Oses

• 2006• Windows Vista released• WIM tools (ImageX, WIMGAPI) released for everyone to use, start of the decline of Ghost

• 2007• Configuration Manager 2007 released, with integrated OS deployment, task sequences• BDD 2007 released, leveraging task sequences• Microsoft Deployment released, adding server OS deployment

• 2009• Windows 7 released• USMT 4.0 released, adding support for hardlink migration

• 2010 through today• Incremental enhancements…

The Current “State of the Art”

• Image creation:• MDT 2013, creating WIM images

• Image deployment:• Use what you have:

• ConfigMgr 2012 R2 with MDT 2013, deploying captured WIM images• Otherwise, MDT 2013, deploying capturing WIM images

• Wipe and load for existing systems (refresh with data migration using hardlinks)• Dynamic deployment, including driver injection, app

installation, and configuration

So what about Windows 10?

• The logical “next OS” for those running Windows 7• Mainstream support ends January 13, 2015• Extended support ends January 14, 2020• “Gartner: Windows 7 Shops Should Start Planning Migration

Now”• http://mcpmag.com/articles/2014/08/13/windows-7-migration.aspx

• Compatibility is key• Hardware requirements are the same• Desktop and modern app compatibility will be excellent• Internet Explorer will continue to make investments in

enterprise compatibility features

Windows 10 Deployment Options

Traditional process• Capture data and settings• Deploy (custom) OS image• Inject drivers• Install apps• Restore data and settings

Still an option for all scenarios

Wipe-and-Load In-Place Provisioning

Let Windows do the work• Preserve all data, settings,

apps, drivers• Install (standard) OS image• Restore everything

Recommended for existing devices (Windows 7/8/8.1)

Configure new devices• Transform into an Enterprise

device• Remove extra items, add

organizational apps and config

New capability for new devices

Windows 10: Moving In-Place

Coming from Windows 7 or Windows 8?

Coming from Windows 8.1?

• Automated in-place upgrade• System Center and MDT support for managing

the workflow

• Automated servicing operation (an update)• Fastest deployment option

Simplified process, builds on prior experience

• Uses the standard Windows 10 image• Automatically preserves existing apps, settings,

and drivers• Fast and reliable, with automatic roll-back if issues

are encountered• Strong customer demand• Popular for Windows 8 to Windows 8.1• Piloting now with Windows 7 to Windows 8.1,

to learn• Working with ISVs for disk encryption

Demo

In-Place Upgrade(MDT, ConfigMgr, Windows Update)

Geeky Stuff

• New command line options for SETUP.EXE• Regain control after success or failure using /postoobe and /postrollback

switches• Control driver migration operations using /migratealldrivers and

/installdrivers• Copy log files to a location of your choosing using /copylogs• Inspect return codes from SETUP.EXE for a quick indication of what

happened

• Enabling upgrade from Windows 7 via Windows Update• WindowsTechnicalPreview.exe (a.k.a. KB2990214) enables installation via

Windows Update on Windows 7• Removing KB2990214 will remove the option

Geeky Stuff

• Sample task sequence for ConfigMgr 2012 R2:• http://

blogs.technet.com/b/configmgrteam/archive/2014/10/29/how-to-upgrade-to-win-10-using-the-task-sequence-in-sc-2012-r2-configmgr.aspx

• Sample task sequence for MDT 2013• Coming soon (although it’s fairly easy to recreate)

Provisioning, Not Reimaging

TAKE OFF-THE-SHELF HARDWARE

APPLY A PROVISIONING PACKAGE

DEVICE IS READY FOR PRODUCTIVE USE

Provisioning, Not Reimaging

Transform a device• Install apps and enterprise configuration• Enroll the device to be managed via MDM

Flexible methods• Automatically trigged from the cloud or connection

to a corporate network• Using media, USB tethering, or even e-mail

for manual distribution• Leverage NFC or QR codes

Demo

Provisioning Process

Geeky Stuff

• New tools for provisioning• Windows Imaging and Configuration Designer (ICD), delivered via the ADK,

for provisioning package creation• Command-line tool (ProvTool), part of Windows 10, for installing• Configure running devices, or deploy an image (and configuration) to a

new one

• Provisioning capabilities• Installation of language packs, updates, apps, certs• Configuration of wi-fi, VPN, e-mail, IE, WSUS, etc.• Enrollment in mobile device management

Traditional Deployment

Enhancements to existing tools Minimal changes to existing deployment processes

• New Assessment and Deployment Kit includes support for Windows 10, while continuing to support down to Windows 7

• Minor updates to System Center 2012 (through a hotfix or cumulative update) to add support

• Minor updates to Microsoft Deployment Toolkit 2013 to add support

• Will feel “natural” to IT Pros used to deploying Windows 7 and Windows 8.1

• Drop in a Windows 10 image, use it to create your new master image

• Capture a Windows 10 image, use it for wipe-and-load deployments

• Add apps to images!

Enterprise Preview Process

PREVIEW BUILDS AVAILABLE TO ALL ORGANIZATIONS• For evaluation and feedback, not for broad deployment

PERIODICALLY UPDATED THROUGH “FLIGHTING”• Enabling new features as they become available• Fixing and refining existing features and functions• Actively soliciting feedback

ROLLED OUT IN PHASES• Enabling new features as they become available• Fixing and refining existing features and functions• Actively soliciting feedback

WINDOWS

INSIDERS (slow)

WINDOWS INSIDERS

(fast)

INTERNAL (MICROSOFT)

Windows Deployment - Now and Into the Future

EvaluationsPlease provide session feedback by clicking the Eval button in the scheduler app. One lucky winner will get a free ticket to the next MMS!

Visit all of our sponsors in the expo area and online!

Platinum Sponsors:

Gold Sponsors:

MMS Minnesota 2014

Michael Niehaus@mniehaushttp://blogs.technet.com/mniehaus

#MMSMinnesota