Fails with code '-1' when Task Sequence step has timeout set

Damon
New Member

Posts: 3

Fails with code '-1' when Task Sequence step has timeout set Aug 22, 2018 19:19:21 GMT

Quote

Post by Damon on Aug 22, 2018 19:19:21 GMT

I have a need to use the "Time-out" option in a Configuration Manager Task Sequence 'Run Command Line' step which runs UI++ while in Windows. What I really need is for the Pre-Flight check to have a timeout, but that's not an option.

The problem I'm having is when the "Time-out" checkbox in the task sequence 'Run Command Line' step is not checked, UI++ runs as expected. When it is checked (with any valid timeout value defined), the step instantly fails with error code '-1'. No further information in smsts.log or status messages. It doesn't write to UI++.log either.

Here's my (sanitized) commandline*:

ServiceUI%PROCESSOR_ARCHITECTURE%.exe -process:tsprogressui.exe %_SMSTSMDataPath%\SMS10000\UI++\UI++%PROCESSOR_ARCHITECTURE%.exe /disabletsvareditor /config:http://<CM-Server>/<WebFolder>/UI-PlusPlus-UserCancel.xml

* UI++.exe files renamed so I can dynamically reference them using the built-in %PROCESSOR_ARCHITECTURE% variable.

I'm using UI++ version 2.10.4.0 and Configuration Manager v1802

Thanks for any suggestions you might have.

Last Edit: Aug 22, 2018 21:40:56 GMT by Damon

Damon
New Member

Posts: 3

Fails with code '-1' when Task Sequence step has timeout set Aug 22, 2018 23:10:13 GMT Stuart likes this

Quote

Post by Damon on Aug 22, 2018 23:10:13 GMT

I found a workaround - I run this 'Run Command Line' step immediately before I run UI++

cmd /c START /B powershell.exe -ExecutionPolicy Bypass -Command "& { Start-Sleep -Seconds 3900 ; Get-Process | Where-Object Name -like 'UI++*' | Stop-Process -Force }"

The timeout for my Info action is 3600 - gives a user 1 hour to see it, then it does Pre-Flight checks. If one of those fails, the user has 5 minutes to look at it. If they're not there for any of it, the powershell script kills UI++, generating an error and stopping the task sequence. Should prevent a user coming back to a preflight check error screen, but still generate an error I can see in ConfigMgr monitoring.

Jason Administrator Posts: 485	Fails with code '-1' when Task Sequence step has timeout set Aug 31, 2018 17:59:05 GMT Quote Select Post Deselect Post Link to Post Member Give Gift Back to Top Post by Jason on Aug 31, 2018 17:59:05 GMT Adding a timeout to additional GUI actions, like the pre-flight, is on my to-do list. Nice work-around though.

Fails with code '-1' when Task Sequence step has timeout set

Post by Damon on Aug 22, 2018 19:19:21 GMT

Post by Damon on Aug 22, 2018 23:10:13 GMT

Post by Jason on Aug 31, 2018 17:59:05 GMT