FriendsOfMDT / PSD

PowerShell Deployment
MIT License
505 stars 78 forks source link

Adding debug parameter breaks deployment #61

Closed yckbrd closed 1 year ago

yckbrd commented 2 years ago

The current documentation says in order to enable debug mode one has to add the parameter to the PSDStart.ps1 execution command in PSD:\Templates\LiteTouchPE.xml. However, there is no such command in that file. So I added the parameter to the command in PSD:\Templates\Unattend_PE_x64.xml and PSD:\Templates\Unattend_PE_x86.xml.

But changing <Path>powershell.exe -noprofile -windowstyle hidden -file X:\Deploy\Scripts\PSDStart.ps1</Path> to <Path>powershell.exe -noprofile -windowstyle hidden -file X:\Deploy\Scripts\PSDStart.ps1 -Debug</Path> causes the deployment to stop and the monitor output remains the following indefinitely:

image

yckbrd commented 2 years ago

Causing the issue seems to be the -windowstyle hidden parameter, which seems obvious now after finding out... Since the window is hidden the query at the beginning of PSDStart.ps1 whether to stay in debug mode or quit it doesn't receive an answer because we cannot make any inputs. My workaround for now is to change the parameter to -windowstyle minimized. Or, if you're lazy and don't want to press y everytime comment out the query until we find a robust solution. <#if($Global:PSDDebug -eq $false) { if($DeBug -eq $true) { $Result = Read-Host -Prompt "Press y and Enter to continue in debug mode, any other key to exit from debug..." if($Result -eq "y") { $DeBug = $True } else { $DeBug = $False } } }#>

GeoSimos commented 1 year ago

Thank you for the feedback, will check it with the team and try to reproduce, until then you can add the parameter in the BootStrap.ini file as such:

Priority=Default

Properties=PSDPrestartMode,PSDDebug

[Default]

PSDDebug=YES

GeoSimos commented 1 year ago

We're updating the documentation the aforementioned change.