Article ID: 2012889 - View products that this article applies to.
When deploying Windows Vista, Windows 2008, Windows 7, Windows 2008 R2, or newer Windows OS using an Configuration Manager 2007 OSD Task Sequence, the Task Sequence fails during the "Setup windows and ConfigMgr" task. Examining the SMSTS.log file shows the following errors:
The execution of the group (Setup Operating System) has failed and the execution has been aborted. An action failed.
This issue may be caused be a driver not being signed. In certain cases, when installing Windows Vista, Windows 2008, or newer Windows OSes, the drivers must be signed in order for them to install, such as in the case of Boot Critical drivers. If Windows Setup cannot install certain type of drivers, such as Boot Critical drivers, Windows Setup will fail, causing the Task Sequence to fail.
There are two solutions to the problem:
1. Ensure that the driver which is causing Windows Setup to fail at is properly signed.
Note If the driver is an OEM driver and not showing as being properly signed, try downloading the latest driver from the OEM manufacturer and/or contacting the OEM manufacturer.
2. Remove the affected driver from the driver package that is being applied either via the "Apply Driver Package" or "Auto Apply Drivers" task. The driver can then be installed when the Task Sequence is in the full Windows OS via an "Install Software" task.
To determine if the driver is properly signed or not, examine the setupact.log and determine what driver Windows Setup is failing at. The driver that is failing to install will be indicated by the INF file specified in the line
PnPIBS: Installing driver C:\_SMSTaskSequence\drivers\<#>\<driver>.inf ...
which is right before the line:
"Windows Setup could not install one or more boot-critical drivers. To install Windows, make sure that the drivers are valid, and restart the installation.]".
To determine what driver the INF file belongs to and if the driver is signed:
It can also be determined if the driver is signed or not by navigating to the "Operating System Deployment" --> "Drivers" node, locating the driver using the steps above, and then clicking on the driver in the right hand pane. When clicking on the driver, an information pane should appear after a second or two. Under the "General" tab, there should be a field labeled "Digital Signer". If the value of this field is "Unsigned", then the driver is NOT signed. If the value of the field has a name of a digital publisher next to it (usually "Microsoft Windows Hardware Compatibility Publisher"), then the driver is signed.
For the driver to be properly signed there should be a corresponding .CAT file for the .INF file in the driver source files. If there is a corresponding .CAT file, this is an indication that the driver MAY be signed, but not a guarantee that the driver IS properly signed. If there is no corresponding .CAT file, the driver is definitely NOT signed.
To determine where the driver source files are located:
If there is a corresponding .CAT file for the .INF file and the driver is showing as not being signed in the Configuration Manager 2007 Admin Console, try deleting the driver from the console and reimporting it back into the console. If the driver is still not showing as being properly signed, try downloading the latest driver from the OEM manufacturer and/or contacting the OEM manufacturer.
(http://go.microsoft.com/fwlink/?LinkId=151500)for other considerations.
Article ID: 2012889 - Last Review: July 19, 2011 - Revision: 5.0