haribo48 Posted July 20, 2016 Report post Posted July 20, 2016 Hi Everyone, We use task sequences to deploy software applications to machines such as applications that require multiple steps and conditions such as uninstalling previous versions of software based on conditions, reboots and installing new applications. For this topic OSD doesn't play a part as the task sequnce is ran within windows. Since updating SCCM 2012 config manager to 1511 application task sequences that previously worked via direct deployment to either a machine collection or the application catalog (via a powershell script). Since the update the task sequence always fails the first time it is sent to or requested by a client computer, if you wait for the automatic retry or manually re-run the task sequence from software center it always works fine. Appreciate any advice or help? Cheers Quote Share this post Link to post Share on other sites More sharing options...
tregelen Posted July 21, 2016 Report post Posted July 21, 2016 Are you able to get away from TS at all? You could always use the PS App Deploy Toolkit (http://psappdeploytoolkit.com/) to handle the steps, as for the restarts you could use the prerequisites abilities with the Applications. As for why the TS aren't working what are the logs saying? Quote Share this post Link to post Share on other sites More sharing options...
haribo48 Posted August 3, 2016 Report post Posted August 3, 2016 Thanks Treglen for the reply, I'll have a look at PS App Deploy toolkit see what it offers. Thats the thing the software install TS do work, just the first time a machine is added to the device collection and gets the deployment it fails immediately - no content is downloaded and no smsts.log file is created. It appears it doesn't even try to run. If i wait for the default re-run or manually re-run the deployment the TS works 100% of the time, content begins to download and the TS executes. Quote Share this post Link to post Share on other sites More sharing options...
tregelen Posted August 22, 2016 Report post Posted August 22, 2016 It could be one of those weird things that are the reasons why MS doesn't recommend software installs with TS. Sorry I couldn't help any more. Quote Share this post Link to post Share on other sites More sharing options...