This blog is about script errors that occur when you use ADK for Windows 11 version 22H2 with MDT. Today I was testing the installation of Windows 11 and ran into some problems.
- Windows PE snap-in error
- Deployment Share update error
- Windows PE Script error
Windows PE snap-in error
First, there is no 32-bit support. This causes an error in the current version of MDT when opening the Windows PE tab. This error occurs because a path is called that is not present in this ADK version.
Deployment Share update error
The second problem I ran into was also related to the lack of 32-bit support. When updating the deployment share, I got this error message.
This was fairly quickly fixed by adjusting the properties of the deployment share. Under platforms supported, uncheck x86. After this modification, the error message was gone.
Windows PE Script error
The last problem I ran into was when booting a new machine with PXE. After Windows PE started up, a “Script Error” appeared on the screen. It showed a generic error message “An error has occurred in the script on this page.”. The error message was easily bypassed by closing it, but it appeared on every page. In addition, the pages did not seem to load properly.
After a brief internet search, I found the error message on MDT’s known issues page. The problem is caused by replacing the default scripting engine (IE). To solve this problem, the Unattend_PE_x64.xml must be modified. On the MDT server, go to the following location “C:\Program Files\Microsoft Deployment Toolkit\Templates\unattend_PE_x64.xml” and edit the file. Always backup before editing the file to be on the safe side. Replace the rules in the xml with the rules named in the known issues article.
<RunSynchronousCommand wcm:action="add"> <Description>Lite Touch PE</Description> <Order>1</Order> <Path>reg.exe add "HKLM\Software\Microsoft\Internet Explorer\Main" /t REG_DWORD /v JscriptReplacement /d 0 /f</Path> </RunSynchronousCommand> <RunSynchronousCommand wcm:action="add"> <Description>Lite Touch PE</Description> <Order>2</Order> <Path>wscript.exe X:\Deploy\Scripts\LiteTouch.wsf</Path> </RunSynchronousCommand>
Then you have to completely re-generate the boot image. This ensures that the changes are incorporated into the new boot image.
Replace the boot image in Windows Deployment Services with the boot image you just generated. The script problem is now gone and all screens load correctly.
Thanks for reading this article, I hope you have benefited from it.