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

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

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.
Answered 03/05/2009 by: VBScab
Red Belt

Please log in to comment
0
probably installshield is crap and you have to repackage or somehow extract the msi if one exists and use that with a transform.
Answered 03/11/2009 by: aogilmor
Ninth Degree Black Belt

Please log in to comment
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.
Answered 03/12/2009 by: MSIPackager
Third Degree Black Belt

Please log in to comment
0
Thanks MSIPackager, Yes we have done this. It works when a user is logged in.
Answered 03/12/2009 by: bkruiser
Orange Belt

Please log in to comment
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.
Answered 03/13/2009 by: VBScab
Red Belt

Please log in to comment
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.)
Answered 03/15/2009 by: jmcfadyen
Fifth Degree Black Belt

Please log in to comment
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
Answered 03/25/2009 by: bkruiser
Orange Belt

Please log in to comment
Answer this question or Comment on this question for clarity