SCCM - TSMBootstrap.exe issue in PE section of TS on Nutanix UEFI only

Question

Hi all,
SCCM 2002 with ADK 2004.

Task sequences are working across (almost) all workstations and servers for deploying Windows 10 and Server 2019.

We have some nutanix-based hyper-visors for VDI.... they work fine when the BIOS type is set to legacy/MBR, but crash Windows PE prior to the GUI when the BIOS type is set to UEFI.

Nutanix has advised that there is an issue with ADK 2004 and UEFI in the long-term servicing branch we are using -and we cannot move to the short-term branch due to environment restrictions. The recommendation is to use an earlier version of ADK/PE - and this is where the fun starts.

After creating a 1903 PE, importing the nutanix drivers and importing it into SCCM, the VM (with UEFI) now boots into the PE GUI - but immediately reboots. Pressing F8 so we can have a look at the logs shows that

All the config files, such as Winpeshl.ini, Winpeshl.log, Wpeinit.log etc are consistent between the not working and working PE's
The network and disk drivers are working correctly (ipconfig and diskpart to check)
It seems that the issue (according to smsts.log) is TSMBootstrap.exe.

While i cannot post the full logs - i can paraphrase them - and you will see this in any smsts.log at start start of the PE phase

Executing command line X:\sms\bin\x64\tsmbootstrap.exe /env:WinPE /configpath X:\sms\data
The command completed successfully

At this point, on a successful instance, you will see the TSMBootstrap section start.... in this example, im simply get
"Execution complete"..

It looks like tsmbootstrap.exe is crashing, or not running properly.... but there is no way to tell how or why its crashing. Im having difficulty finding the full list of command line switches for tsmbootstrap.exe - hoping that there might be a logging option for it.

Can anyone assist with a logging option for tsmbootstrap.exe or perhaps any suggestions as to why it would fail to run.

Answer 1

Hey.... you kinda of missed the point of the question there. (and by kinda, i mean completely)

Anyway - in case anyone else runs into this
When your creating your 1903 boot wim - inject optionsal components using
Dism /image:C:\winpe\mount /Add-Package /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-HTA.cab"
Dism /image:C:\winpe\mount /Add-Package /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-DismCmdlets.cab"
Dism /image:C:\winpe\mount /Add-Package /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-Dot3Svc.cab"
Dism /image:C:\winpe\mount /Add-Package /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-NetFx.cab"
Dism /image:C:\winpe\mount /Add-Package /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-PowerShell.cab"
Dism /image:C:\winpe\mount /Add-Package /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-Scripting.cab"
Dism /image:C:\winpe\mount /Add-Package /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-SecureBootCmdlets.cab"
Dism /image:C:\winpe\mount /Add-Package /PackagePath:"C:\Program Files (x86)\Windows Kits\10\Assessment and Deployment Kit\Windows Preinstallation Environment\amd64\WinPE_OCs\WinPE-WMI.cab"

then import into sccm and it will work.

While the required compoenents are listed as there if you use the SCCM redist to inject them - there appears to be some compat issue when 2004 is the ADK on your site server.

Answer 2

Hi,

Please try to restart the task sequence wizard in WINPE.

TsBootShell.exe

To find it you might need to go to the root of your WinPE drive and type:

DIR TsBootShell.exe /s

It will normally be found in

X:\sms\bin\X64