Professional Documents
Culture Documents
Module 07:
Deploy using on-premises
based tools
• Apps that run on Win7/8.x will typically work on Windows 10 and later
• Test compatibility – do not assume.
• Mitigate within Windows 10/11
‒ Modify the app
‒ Updates from developer
‒ Upgrade if available
‒ Permission to resource
‒ Run virtualized
‒ Compatibility mode
‒ Explore alternative apps
Client Hyper-V
Components of Deployment
Workbench
Operating system (OS images)
Applications
Drivers
Packages
Task sequences
• Gather
• Format and Partition
• Inject Drivers
• Apply Operating System
• Windows Update
© Copyright Microsoft Corporation. All rights reserved.
Setup the Microsoft Deployment Toolkit for client deployment
Can MDT can be part of your overall deployment strategy?
Do you need to deploy applications after the device has been built?
Automated deployments that require some Deployment is completely automated The user can interact during the deployment,
user intervention without any user intervention giving them certain choices for configuration
LTI deployments using MDT require minimal Can be more difficult to implement than Unlike ZTI, where every setting must be
infrastructure and are less complex than zero- LTI/UDI deployments and require defined, UDI allows the end user to decide
touch deployments Configuration Manager certain options
Bootstrap.ini
Bootstrap.ini is copied from the Control folder to the boot image, so
the boot image needs to be updated every time you change that file
Add only a minimal set of rules to Bootstrap.ini, such as which
deployment server and share to connect to (the DEPLOYROOT value)
CustomSettings.ini
Put the other rules in CustomSettings.ini because that file is updated
immediately when you select OK
• Boot images
‒ The Windows Preinstallation Environment (Windows PE) images that are used to start a
Windows deployment
‒ Start boot images from a CD or DVD, an ISO file, a USB device, or over the network using a
Pre-Boot Execution Environment (PXE) server
‒ Use x64 platform