/build/static/layout/Breadcrumb_cap_w.png

Setup.exe hangs if TSProgressUI.exe not the active window

Does anyone else experience hangs with InstallShield Setup.exe -S -SMS packages when run through MDT.

I identified that the TSProgressUI.exe requires itself to be the active window. The install works fine as long as you regularly ensure that the active window is TSProgressUI.exe! This is the Task Sequence Progress UI for MDT 2008. Does anyone know why this happens or have a fix other than continuously make TSProgressUI.exe the focus or kill it?

0 Comments   [ + ] Show comments

Answers (7)

Posted by: anonymous_9363 15 years ago
Red Belt
0
In all probability, the installer is running in non-silent mode and, during what is perceived as a hang, is displaying a dialog box, waiting for a non-existent user to click 'OK' or 'Yes'. Or it may just be an idiot package which, even when run silently, STILL pops up a dialog...

Either way, a log is required.
Posted by: aogilmor 15 years ago
9th Degree Black Belt
0
probably installshield is crap and you have to repackage or somehow extract the msi if one exists and use that with a transform.
Posted by: MSIPackager 15 years ago
3rd Degree Black Belt
0
In all probability, the installer is running in non-silent mode and, during what is perceived as a hang, is displaying a dialog box, waiting for a non-existent user to click 'OK' or 'Yes'. Or it may just be an idiot package which, even when run silently, STILL pops up a dialog...

You can prove this by setting it to install when a user is logged on and checking the "allow users to interact with this program" box in the SMS program properties.

Regards,
Rob.
Posted by: bkruiser 15 years ago
Orange Belt
0
Thanks MSIPackager, Yes we have done this. It works when a user is logged in.
Posted by: anonymous_9363 15 years ago
Red Belt
0
It works when a user is logged inWhat does that mean? That there IS a dialog popping up during the install? If so, I don't think you have a choice other than re-packaging it.
Posted by: jmcfadyen 15 years ago
5th Degree Black Belt
0
if you are chaining ISScript etc with SMS you may need to check for IDriver.exe or ISSetup.exe and kill it prior to running successive MSI's.

often these processes don't die and you need an external kill script or similar to stop them prior to running more MSI's . (another IS item of brilliance.)
Posted by: bkruiser 14 years ago
Orange Belt
0
I have identified that the TSProgressUI.exe requires itself to be the active window. The install works fine as long as you regularly ensure that the active window is TSProgressUI.exe! This is the Task Sequence Progress UI for MDT 2008.

I have found this http://social.technet.microsoft.com/Forums/en-US/configmgrosd/thread/86de7e89-6070-44e0-9c98-a74a2e22c404/ discussion where people get around the issue
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ