Hello, I am having a problem installing a piece of software via a task sequence. If I try to deploy this same exact program with Software Distribution, it works fine; but when I assign the package/program as a step in the TS it fails. Unfortuantely, in the smsts.log, it shows the program sucess (so no troubleshooting there - when it terminates it returns error code 0, so SCCM thinks it worked even though it didn't). When watching the TS progress bar, i see the install step appear briefly for about 2-3 seconds, then it moves on. What is different about deploying a piece of software from OSD vs. software distribution that might cause this problem? Any specific ideas? Thanks for the help!

Hello, I had a similar issue witha softwareinstallerthat was trying to install an unsigned driver. Driver policy for unsigned drivers was active for normal software distribution functinality. In TS phase, these settings are still default (if default settings are set in the image) and prompt is presented for installation. gr, Kurt

HiI had also issues with that.Just pay attention that your software packages do not require a user environment.

Hi, Remember that installating software within a task-sequence behaves diffently as you would install it when booted in the OS. Nico already mentioned that you have to be aware of the fact that no user environment is available, but also no GPO processing has taken place for example. Also some variables are different in a TS compared to when the OS is operational. My suggestion would be to try to make your software installation log every step into a log file, that logfile could be used to troubleshoot why your software installation didn't work out. The best way to troubleshoot software installation within a TS is to troubleshoot in the command prompt available during the task sequence (you have to enable command prompt support though). Just execute every step of your script/ or call the installation itself from the command line. I think this comes as close as possible to the situation when you are running within a TS. Good luck ! Kenneth

I'm experiencing that the softwaretask sequence downloads the source,kicks off the installation and then it stays therewaiting for I don't know what...If I add the source of the package to my %deployroot% and I run the package via a "command line" task the package installs correctly.Of course I don't want to add each failing software to my deployroot. But it proves that it's nothing with the package source but really something with the Task Sequence vs SCCM client??Any help would be very appreciated!!Nico

Thanks for the replies. I validated that it does not need a regular user to be logged in to work. I tried to execute the .exe (without the silent switch) from the command prompt in the TS. It launched the wizard and ran setup interactively and worked fine. Then I tried to run setup as setup.exe -s -f2C:\Windows\Temp\InstallLog.log from the command line in the task sequence and it worked perfectly (silent + logging). For some wierd reason, when I turn on logging on the .exe (InstallSheild), all of a sudden the Task Sequence can install the software. If logging is off (default), it fails. This is not the case in Windows, there, setup.exe -s works fine (.iss file has already been configured). I guess that will work (don't need to log in production, but if it makes it works I guess that is okay). Anyone have any idea why this makes it work? Thanks!

Have you checked this setting: http://technet.microsoft.com/en-us/library/bb680380(TechNet.10).aspx "Allow this program to be installed from the Install Software task sequence without being advertised"

Hi TorstenTnx for your replyYes indeed, even with that option checked no success

I know this is an old thread but I experienced the same problem as bcher - specifying the logging directory also fixed the issue for me. To answer the last question "Anyone have any idea why this makes it work?" I think it may be due to the fact the by default the installer trys to write the logfile to the same directory as the installation files. Perhaps it crashes because it can't access the UNC path of the ConfigMgr Package Share properly and write the logfile to that directory? Specifying a local directory i.e. %systemroot%\temp for the log file results in success.William Eriepa | New Zealand

Hi all, i have absolutely the same situation, software are successfully distributed and installing using Software Distribution, but failed with Task Sequence. I'm trying to install several applications in msi. Could anyone make some screens, or write, where should i put logging to have them installed with TS. Thanks in advance.