Jon

Windows 10 Deployment Scenarios Overview

3 posts in this topic

#1 ·  Posted (edited)

With the imminent public release of Windows 10 I have been readying my test environments to be able to deploy and test Windows 10. This is a quick overview of the main deployment scenarios supported and some links to the
software you will need. Also I’ve included some links to a selection of videos from the MS Ignite conference that I found the most useful for someone new to Windows 10 deployment.
 
Deployment Scenarios
 
The main deployment scenarios are:
  • Wipe and Load
  • In-place Upgrade
  • Provisioning
 
Wipe and Load
This is the traditional process and follows these general stages:
  • Wipe device
  • Deploy customised OS image
  • Inject drivers
  • Install applications
Optionally this can include steps to capture and restore user data and/or settings if present on the device (usually laptops). Wipe and Load can be done with both MDT and ConfigMgr.
 
Pros
  • Device will be in a known new state
  • Removes any remnants of old installations, updates and obsolete applications. Over months and years performance and disk space can be adversely affected
  • Can use a custom image that could be pre-updated, or contain applications that rarely change - this can drastically improve deployment times
Cons
  • Can have a longer deployment time due to re-installation of all applications post-deployment
  • Must have driver packages available for all machine variants
  • Creating scripts to capture and restore user data can be time-consuming
 
In-place Upgrade
This is a newer scenario available for clients running Windows 7/8/8.1. Windows setup does most of the work for you:
  • Save existing user data, settings, applications and drivers
  • Deploy original Windows 10 image
  • Restore everything
This is a new scenario introduced with Windows 8.1 and Windows 10 and it will be interesting to see how it works in anger. In the Microsoft presentations I’ve seen this is being advertised as the preferred method for upgrading from Windows 7 and 8. I personally prefer a wipe-and-load so that I know everything is clean. Also, new OS deployment is often used as an good opportunity to upgrade major software like Microsoft Office which makes some of the in-place upgrade benefits redundant.
One scenario I think may benefit is the ability to get a Windows client from an OEM and easily upgrade it to Windows 10 while keeping all the drivers it has. Getting the driver packages for new machines was a burden for some smaller companies.
 
Pros
  • Preserves all data: user data, setting, applications and drivers and therefore is potentially less risky
  • Don’t always require new drivers if existing drivers are compatible
  • Often a shorter deployment time
  • Requires less preparation
Cons
  • Cannot use a customised image, the original Windows 10 media must be used
  • If a machine had obsolete installations and settings these will remain
 
Provisioning 
This is another new Enterprise-focused scenario designed to help with the situations where a company wants to ship a new Windows 10 machine directly from the OEM to a user and then have enterprise software and policies applied to that machine to bring it into compliance.
This is controlled by a provisioning package (.ppkg) that is obtained and executed on the target machine and can perform the following operations:
  • Change Windows 10 version from Pro to Enterprise and add in Enterprise features, updates and language packs
  • Retains drivers and applications
  • Install or remove Modern UI applications 
  • Enrol into a domain or management solution
Provisioning packages are created with the new Windows Image and Configuration Designer (Windows ICD) tool.
 
Pros
  • Can change Windows from Pro to Enterprise - this previously required a wipe-and-load
  • Enables Bring Your Own Device (BYOD) scenarios
Cons 
  • The available policies are a small - but useful - subset of those available in Group Policy
  • Yet another tool to go into the toolkit along with WinPE, WIMs, MDT, ConfigMgr. Many organisations already struggle with the best way to deploy and now we have a choice of bespoke vs MDT vs ConfigMgr vs MDM vs Windows ICD
  • For remote installations, you need a delivery mechanism and the .ppkg files involved may be large
  • The only applications that can be installed are Modern UI applications. PowerShell scripts and Win32 applications are in the long-term plan.
 
Deployment Tools and Kits
Here are links to the toolkits you need for MDT and ConfigMgr to deploy Windows 10. Many are in beta or RC stage - I’ll update the links when the final versions are publicly available.
 
Videos
Here are a selection of videos from the MS Ignite conference in May 2015 that I found the most useful:
 
Edited by Jon
1 person likes this

Share this post


Link to post
Share on other sites



Thanks for the post, Jon. I am working at a client's right now in which upgrade discussions have already begun. Thankfully I believe it'll coincide with a hardware refresh, so the number of machines we actually upgrade will be small. And I don't think they'll be ready to even plan a rollout until 2016, but the requests are already piling up for testing resources, both physical and virtual.

1 person likes this

√-1 2^3 ∑ π, and it was delicious!

Share this post


Link to post
Share on other sites

Hi 

My first post 

from so many days i am trying to make a best image of Windows 10 for our organisation but there are lot of problems i am facing with it

at first i tried audit mode after sysprep cortana cant be click and no where to enable back it. and we got lots of issues on that audit mode so i am making the fresh image with all silent installers using batch file but still there are some softwares need to install manually so i came here today

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Similar Content

    • BBs19
      By BBs19
      Features:
      Create modern looking borderless and resizable GUIs with control buttons (Close,Maximize/Restore,Minimize, Fullscreen, Menu) True borderless, resizeable GUI with full support for aerosnap etc. Many color schemes/themes included. See MetroThemes.au3 for more details. 3 type of Windows 8/10 style buttons. Modern checkboxes, radios, toggles and progressbar. All buttons, checkboxes etc. have hover effects! Windows 10 style modern MsgBox. Windows 10/Android style menu that slides in from left. Windows 10 style right click menu  
      Credits: @UEZ, for the function to create buttons with text using GDIPlus. @binhnx for his SSCtrlHover UDF
       
      Changelog:
      Download UDF with example:
       
       
    • keelaji
      By keelaji
      Hello,
      first of all i searched in the forum but i didn't found any solution to my problem.
      I am using windows 10.
      I made a script that is supposed to change the title to the active window, resize it to the smallest size possible (should be around 800 x 600) and move to (0, 0).
      I can change the title but i fail to do the other 2 tasks.
      i use wingettitle [active] copied from the F1 help tool (and this works), i i put the title in a variable and than i use
      winsettitle ($variable, "one") (this works too)
      winmove ("one", 0, 0, 800, 600) (doesn't do anything)
      i also tried
      local $x = winget ( "one")
      msgbox (0, "", $x) (i get a completely white box so i suppose winget can't have any data about my window ??)
      any suggestion ?
    • spuuunit
      By spuuunit
      I have a script that autostart with Windows, and sometimes some of my code is skipped. My script takes long pauses, so it's not that the script "goes too fast". This is my script for now:
      TraySetIcon("C:\Portables\AutoIt\_\icon.ico") AutoItSetOption("WinTitleMatchMode", 2) Run("C:\Portables\Key Manager\keymanager.exe") WinActivate("ATNSOFT Key Manager v") WinWaitActive("ATNSOFT Key Manager v") WinMove("ATNSOFT Key Manager v", "", 650, 200, 600, 800) Sleep(500) $pos = MouseGetPos() MouseClick("left", 1220, 210, 1, 100) MouseMove($pos[0], $pos[1], 100) Run("C:\Portables\foobar2000\foobar2000.exe") $version = 298 For $i = 0 To 99 Step 1 $path = "C:\Users\spunit\AppData\Local\Discord\app-0.0." & $version + $i & "\Discord.exe" If FileExists($path) Then Run($path) ExitLoop EndIf Next Run("C:\Portables\Firefox\FirefoxPortable.exe") Sleep(10000) WinMove("- Mozilla Firefox", "", 205, 0, 1214, 1047) Sleep(100) MouseClick("left", 1300, 15, 1, 10) Sleep(100) MouseClick("left", 1130, 275, 1, 10) Sleep(100) MouseClick("left", 930, 105, 1, 10) Sleep(100) Send("#{m}") Sometimes it skips to click and move mouse right after Key Manager starts. Almost always it skips everything after the last run.

      This type of script were never an issue with Windows 7... Any thoughts?
    • VIP
      By VIP
      I can not do anything with any user in the "Local Users Group"
      I tried from my account but I could not change my password (ie set new password)!
      But I was able to activate the Administrator account and I logged into the Administrator account and still could not do anything with my account! But I can set the password and disable the Administrator account from my account or Administrator.
      Any ideas? (Ignore the click on the Sign-in option in the Change Accout settings.)
       

    • dreivilo47
      By dreivilo47
      When I want to test Example 1 of Function _IECreate (AutoIt Help File), I see that function _IECreate doesn't work in Windows 10.
      Syntax Check (Ctrl+F5) gives no errors.
       
      Example 1:
      ; Create a browser window and navigate to a website #include <IE.au3> Local $oIE = _IECreate("www.autoitscript.com")  
      The error I receive with F5 (Tools, Go) in SciTE: