OSD - Create Variable to control creation of DisableCMDRequest.TAG in Setup Windows & ConfigMgr Step
During OSD, specifically the Setup Windows & Configuration Manager Step, the step creates the file DisableCMDRequest.TAG right before rebooting from WinPE into the Full OS
This disables the F10 prompt during the Windows Setup.
Could you allow us to change this behavior via TS variable?
Example: SMTSTDisableCMDRequest = False
[Bonus] Then also automatically set the it to false if TSDebugMode = True
This would be helpful for troubleshooting Windows Errors during Setup before the TS kicks back in after setup. (SetupComplete.cmd runs)
Gary Blok
shared this idea
![SetupWinCM03[1].png 926 KB](/assets/223255177/SetupWinCM03%5B1%5D.png){kind=link}
Thanks for your suggestion. Updating status to noted – see https://docs.microsoft.com/en-us/mem/configmgr/core/understand/find-help#send-a-suggestion for an explanation of each value.
Can you elaborate with some examples of why this would be needed?
We already have the task sequence debugger and comprehensive logging. https://docs.microsoft.com/en-us/mem/configmgr/osd/deploy-use/debug-task-sequence
Also, Windows developed SetupDiag which can be run from the task sequence or used on setup.exe completion https://docs.microsoft.com/en-us/windows/deployment/upgrade/setupdiag
1 comment
-
Gary Blok
commented
This came up because during OSD, it can hang after the first reboot at times. You see a Black Screen and spinning wheel... and nothing else ever happens. F8 doesn't work and Shift-F10 is disabled.
I've seen this happen due to drivers or bad unattend files. I'd like the ability to troubleshoot live.TS Debugger is great and I use it all the time, however at this point in the process, it's not running and isn't an option.
I also use setupdiag in my Upgrade Task Sequences, but that isn't applicable at this point either.