Windows 10 Deployment with Microsoft Deployment Toolkit
rovabu
3,163 views
132 slides
Nov 21, 2015
Slide 1 of 132
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
About This Presentation
Windows 10 Deployment with Microsoft Deployment Toolkit
Size: 20.51 MB
Language: en
Added: Nov 21, 2015
Slides: 132 pages
Slide Content
Windows 10 Deployment with Microsoft Deployment Toolkit Roel van Bueren ([email protected])
Roel van Bueren ROVABU Software BV
Roel van Bueren
Setup Commander
Setup Commander
Setup Commander
Slideshare
Twitter
MDT 2013 Update 1 and the ADK for Windows 10
MDT 2013 Update 1
Microsoft Deployment Toolkit (MDT) 2013 Update 1 Overview
MDT 2013 Update 1
MDT 2013 Update 1
Microsoft Deployment Toolkit (MDT) 2013 Update 1 Overview
Windows Automated Installation Kit Windows Automated Installation Kit (Windows AIK or WAIK) is a collection of tools and technologies produced by Microsoft designed to help deploy Microsoft Windows operating system images to target computers or to a VHD (Virtual Hard Disk). The WAIK is a required component of the Microsoft Deployment Toolkit .
ADK and WAIK history WAIK = Windows Automated Installation Kit WAIK 1.0 – Windows Vista WAIK 1.1 – Windows Vista SP1 WAIK 2.0 – Windows 7 WAIK 3.0 – Windows 7 SP1 ADK for Windows 8 ADK for Windows 8.1 ADK for Windows 10
Windows Assessment and Deployment Kit (ADK) Overview
Deployment Scenario’s
Windows 7, 8(.1) to Windows 10 Deployment Scenario’s: Wipe and load Inplace upgrade
MDT 2013 Update 1 Windows 10 is adding in a new deployment scenario, the inplace upgrade scenario, which at this point in time has been tested by millions of Windows Insiders around the globe .
MDT 2013 Update 1 Windows 10 is adding in a new deployment scenario, the inplace upgrade scenario, which at this point in time has been tested by millions of Windows Insiders around the globe.
MDT 2013 Update 1
Wipe and Load or Upgrade http://www.setupcommander.com
Windows 8.1 Upgrade
Wipe-and-load or Upgrade?
Inplace upgrade For a start, the inplace upgrade is quite interesting in the way it technically doesn’t require any new infrastructure, no new ADK, no new boot images etc.
Inplace upgrade I t’s simply running setup.exe with some command line switches, and you can upgrade from Windows 7, Windows 8, and Windows 8.1. This scenario also makes sure all apps and data are still there when the machine is upgraded
Inplace upgrade
Inplace upgrade You can’t use an reference image that already have applications in it, you have to use the Microsoft media. There are restrictions for 3rd party antivirus and disk encryptions, that typically have to be uninstalled No upgrade from x86 to x64 (and vice versa )
Inplace upgrade Reference images If you are using the traditional scenarios, you can create reference images with MDT 2013 Update 1, but they can’t be used for the inplace upgrade scenarios (bare metal, computer refresh, and computer replace). You also cannot deploy your Windows 7 SP1 reference image , upgrade it to Windows 10, and then run sysprep. Sysprep is not supported on an upgraded machine.
Inplace upgrade No upgrade from from MBR to UEFI some of the security features in Windows 10 do require UEFI No upgrade for: Windows to Go Boot from VHD, dual-boot / multi-boot systems .
Wipe and Load or Upgrade http://www.setupcommander.com
http://www.setupcommander.com
http://www.setupcommander.com
http://www.setupcommander.com
http://www.setupcommander.com
http://www.setupcommander.com
http://www.setupcommander.com
Still on Windows XP?
Windows XP to Windows 10 Deployment Scenario’s: Wipe-and-load
Windows XP to Windows 10 Deployment Scenario’s: Wipe-and-load
Wipe-and-load
CustomSettings.ini
Applications
Applications
Applications
Applications
Applications
Applications
Applications
Drivers
Drivers
Drivers
Drivers
ENGL Driver Manager
Drivers
Packages
Packages
Packages
Packages
Packages
Packages
Packages
Universal Windows Platform (UWP) apps (Windows store apps) versus Windows desktop apps
The Death of the Windows Desktop
The Death of the Windows Desktop
The Death of the Windows Desktop “Every time I mention the possibility that Microsoft might kill off the Windows desktop , I get pushback from IT admins, power users, developers, and anyone else who currently relies on complex desktop applications and can't imagine such a future. Folks, it's time to face reality. It isn't a question of whether this will ever happen. It's just a question of when” .
There's one glaring flaw in Microsoft's Windows 10 strategy
There's one glaring flaw in Microsoft's Windows 10 strategy Building real stuff for real PC users Microsoft limits the API platform to build Universal Windows Apps, Wardell says, such that every app runs in what programmers call a "sandbox," meaning that it can't "touch" other apps .
Windows Apps
Windows Apps
Windows Apps
Windows Apps
Get-AppXPackage
Get-AppXPackage
Remove-AppXPackage Removes an app package (.appx) from a user account.
Remove-AppXPackage Get-AppxPackage -AllUsers | Remove-AppxPackage Just uninstalling an app for all users does not prevent the app from being installed for new user accounts on the system
Get-AppXProvisionPackage Gets information about app packages (.appx) in an image that will be installed for each new user
Get-AppXProvisionPackage
Remove-ProvisionedAppXPackage Removes an app package (.appx) from a Windows image.
Deployment Image Servicing and Management Tool (DISM.exe) DISM enumerates, uninstalls, configures and updates features and packages in Windows images The Commands that are available depend on the image being serviced and whether the image is offline or running (online)
Remove-ProvisionedAppXPackage
Remove-ProvisionedAppXPackage
Remove-ProvisionedAppXPackage
Remove-ProvisionedAppXPackage
Remove-ProvisionedAppxPackage
Remove-ProvisionedAppxPackage
App-V 5
App-V 5
App-V 5
App-V 5
App-V 5
Start Menu
Export-StartLayout
Export-StartLayout
Export-StartLayout
Export-StartLayout
Export-StartLayout
LayoutModification.xml Import-StartLayout -LayoutPath C:\Temp\LayoutModification.xml -MountPath $env:SystemDrive \ Copy LayoutModification.xml to C :\Users\Default\AppData\Local\Microsoft\Windows\Shell
LayoutModification.xml
LayoutModification.xml
LayoutModification.xml
LayoutModification.xml
LayoutModification.xml Pro: No need of an Active directory No need to maintain a reference image VM Solution of choice for OS Deployment Start menu can be captured from every where Changing the start menu every five minutes is now fast and painless
LayoutModification.xml Cons Unsupported (sort of) with Import-StartLayout cmdlet, but supported with the copy process !!… don’t ask…