Applications, Configuration Manager 2012, Deployment, Error

App Install Failed 80004005 – SCCM OSD Standalone Media

Issue:

I created a standalone media of a fully functioning network build task sequence. A number of applications would not install from the stand alone media.

The SMSTS.log showed the following:
App install failed.
Install application action failed: ‘Office_2016_ProPlus_16.0.4266.1001_P1’. Error Code 0x80004005

No MSI log file was created, so the installer didn’t even begin.

Solution:

In the task sequence the application had the Retry this step if computer unexpectedly restarts option enabled. Disable this setting and the stand alone media worked correctly.

#DuncanToTheRescue

Advertisements
Applications, Deployment, Drivers, MDT

Install HP Softpaq Silently without Extraction or Reboot

Quick little note for me to remember the silent install command for the HP Softpaq. No need to extract and search the %Temp% location for the MSI files. Use the the following command to install the Softpaq silently without reboot:

setup.exe /S /v"/qn /norestart"
Applications, Configuration Manager 2012, Deployment, Error, Task Sequence

Re: Install Application Step fails in Task Sequence

Great blog post about a similar issue we were having in production.

Instances where application will not install after a reboot. Even when the logs say they installed correctly. We found this was more likely to happen on devices with SSD compared to SATA drives.

Looks like a know bug, but nothing a sleep command can solve: http://www.bctechnet.com/install-application-step-fails-in-task-sequence/

Administration, Applications, Configuration Manager 2012, Deployment, Drivers, Hardware, System Center, Task Sequence, WMI

Configuration Manager OSD Task Sequence WMI Queries

During your OSD Task Sequence you may want to determine whether the machine is a laptop or not, install software to a specific machine name format, or install drivers to only specific models of laptops.  For this you can use the WMI Query Condition within the Tasks of your Task Sequence.  A great tool to look up what can be queried from of WMI is WMICodeCreator and is provided by Microsoft.

Examples:

Laptop Hardware: Select * FROM Win32_Battery WHERE Chemistry > 3

Computer Model:  Select * FROM Win32_ComputerSystem WHERE Model like ‘%latitude%5400%’

Computer Name:  Select * FROM Win32_ComputerSystem WHERE Name like ‘CH%’ or Name like ‘AR%’