Install Software with TS - The operating system reported error 50

            If you ever go to build a machine but it craps out when trying to install applications/software, first open up the Advertsiment Status logs and check the messages which have been produced by the advertisement.

If you come across the following error:
The task sequence execution engine failed executing the action (Applicaiton Name) in the group (Install Software) with the error code 50
Action output: . The operating system reported error 50: The request is not supported.

 

 

Then chances are something gone awry in your task sequence. More speicifically, the odds are you've got a reboot positioned just before the application/software/driver installation begins. The important thing to note here is that the Reboot must be set to restart "The currently installed default operating system" other wise it will try and run the TS boot image again which obviously won't really like trying to install drivers/software/applications. In short, be sure any reboot which forms part of the Task Sequence has the below option selected:

 

 

Task Sequence Fails after SCCM Client Hotfix Install (KB977384)

Introudcing KB977384 into a Task Sequence causes it to Fail on the Software Installaiton Stage

The hotfix in question (KB977384), will upgrade your sccm client to version 4.00.6487.2157. It's a SCCM 2007 R3 Update.

Problem:

If you wrap this hotfix up into a package and then advertise it out to your clients, chances are it'll work fine. If you try and add the Hotfix package into a Task Sequence, however, you may notice that any software which is set to install after the hotfix has installed will fail and bomb out the Task Sequence. 

If you check the SMSTS.log you will most likely see the following:

• The sms client service is not running
• Install Software failed hr=0x80040215
• Failed to run the action: Install <software package>
• Unknown error (Error: 80040215; Source: Unknown)

Furthermore, if you open up the advertisment status of the Task Sequence, you might see the following appear:

Solution:
Basically, don't add the Hotfix into the Task Sequence as a package. Either add it to the Setup Windows and ConfigMgr step as a PATCH command under the INstallation Properties (see http://ccmexec.com/2010/12/installing-the-sccm-hotfixes-on-the-clients/ for a solid guide on how to do this)
Alertnatively, you could just advertise the package out to a collection which contains all the machines which need their sccm client upgrading. Obviously this is a lot less elegant but it could help to mop up any stragglers which are lurking in your environment.