We have an OSD task sequence that runs absolutely fine and builds a PC and joins it to the domain. I have now added a couple of install software steps to the end of the task sequence but when the TS tries to run the first one it just hangs and doesn't progress any further. Looking at the smsts.log it just repeatedly says "waiting for job status notification" but never moves on. The software install steps are individual packages within SCCM that run absolutely fine when a PC is added to their relevant collections, but they will just not run as part of the task sequence. The program command lines are standard setup.vbs files that run to install the software. Can anyone offer any suggestions as to how to get the software to install as part of the OSD? Regards Pamela.

this probably means that the application has popped up a window waiting for user input, probably like a 'click next or ok to continue' or some other error, however as it's running in the local system context you don't see it, try installing the software using psexec as system context on a virtual machine to see that it installs correctly before adding it to the task sequence, which application is it hanging on and how long did you wait (perhaps it will continue after the 90 minutes time out) Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady

Thank you for the reply. The applications install fine outside of a task sequence and are configured to run silently and with no user interaction. When a PC is added to a collection where the package is advertised, it installs with no pop up boxes or prompts. We have waited for about 1 hour, but there is no progression of the application. It is a custom in house application that we have been using for some time with no problems and when run outside of the task sequence it only takes a couple of mintes to silently install.

you can add some msgbox in your vbscript to find out on which exact line the script "waits"...

test installing the app using psexec -s cmd.exe (this starts the command prompt in SYSTEM context) then run the app installer, do you see any errors ? Step by Step ConfigMgr 2007 Guides | Step by Step ConfigMgr 2012 Guides | I'm on Twitter > ncbrady