In the below example I'm calling a PowerShell script named UpdateExit.ps1 which is stored in the scripts folder of my deployment share.
If you rather want to run a PowerShell Script for your MDT Lite Touch boot image, you simply copy the LiteTouchPE.xml to the templates folder in your deployment share, and change it to run PowerShell. The two boot image settings options in the MDT deployment share.īoth XML templates have Exits section like this, which by default runs the UpdateExit.vbs script from the MDT installation directory: Ĭscript.exe "%INSTALLDIR%\Samples\UpdateExit.vbs" The two files are the LiteTouchPE.xml file, which is called for the boot image you define in the mandatory Lite Touch Boot Image Settings section, and the Generic.xml file which is called for the optional boot image that you can define in the Generic Boot Image Settings section (not so commonly used).
When you update a deployment share, the update process looks for an Exits section in two XML files in your deployment share templates folder. Lately I've been using it to add BITS and BranchCache to the boot image. But it has also been useful when patching boot images back in the old days when WinPE 1709 had a rather ugly driver bug, or to dynamically update the bootstrap.ini file, or to disable SMB1 to secure WinPE before SMB1 was disabled by default. The Exits feature was initially intended to do automation around WDS, like automatically replace the boot image in WDS every time you updated the deployment share. Note: This not the same as UserExits that you define in Bootstrap.ini and/or CustomSettings.ini. The feature was added back in MDT 2010, and was originally documented by Michael Niehaus ( here: MDT 2010 New Feature #17: Customizable boot image process. For the past decade or so, MDT Lite Touch have had a little know feature called Exits (or UpdateExit), which is called every time you do a full update of the deployment share.
0 kommentar(er)
