Failed to download updates to the WUAgent datastore. Error = 0x800b0109.

This error has been shown on C:\Windows\SysWOW64\CCM\Logs\WUAHandler.log.



This issue happens when Adobe Flash Player 10.1.85.3 has been assigned by SCCM 2007 Software Update to target computer but the installation always failed.

The configuration is: SCUP 4.5 and SCCM 2007 are installed on same server, WSUS Self-Signed certificate created, issued and imported in Trusted Publishers and Trusted Root Certification Authorities in certificate store on Local Computer.

Solution for this is to import WSUS Self signed certificate to the local computer Trusted Publishers and Trusted Root Certification Authorities and to change this setting in GPO.
For that reason create a GPO which will import this certificate and enable Allow signed updates from an internet Microsoft update service location.






After this modification and GPO applying Adobe Flash Player has been installed successfully.

SCUP 4.5 Error: Publish: : Exception occured during publishing: Verification of file signature failed for file: \\SERVER\UpdateServicesPackage\.....

SCUP-System Center Updates Publisher 4.5 has been configured to download Third-party updates. Self assigned WSUS certificate is published, catalogs for downloading are configured but when publishing has been started there is an error:

"Publish: : Exception occured during publishing: Verification of file signature failed for file: \\server name\UpdateServicesPackages\bcc7176d-5168-4fcc-8ea1-6c4ddb4d2f69\2e66610e-8cf6-4518-a702-b0919cfae686_1.cab"

This error is located in UpdatePublisher.log Temp file on current user.

Solution for this issue is to copy the self-assigned WSUS Certificate to Trusted Publishers and Trusted Root Certification Authorities in certificate store on Local Computer.



After the certificates copy, third-party updates can be published and synchronized with SCCM Server.

Modifyig DELL BIOS Parameters using Task Sequences

Before to deploy OS on new DELL machine (Latitude, Precision) using Task Sequence in SCCM, BIOS can be configured with desired parameters.
This can be done using Dell Business Client Deployment Pack for SCCM .

This software can be downloaded from: http://content.dell.com/us/en/enterprise/d/solutions/dell-deployment-pack.aspx

After the installations of Dell Business Client Deployment Pack for SCCM on SCCM 2007 R2 Server or on computer where SCCM Console is installed, GUI Bare Metal Client Deploymens is integrated in SCCM Console.



There are two main modifications added in Task Sequence template; DiskPart clean and Set BIOS Config x86_64



To modify BIOS configuration before to install OS Set BIOS Config x86_64(ini file) can be used. Using Configuration file/Comand line parameters we can modify parameters, save them in customized INI file and deploy it with New Operating System Task Sequence.



In this case Wake On LAN is enabled into the ini file.

This BIOS setting will be applied on the machine before OS to be installed.

Modifying BIOS Parameters using Dell Client Configuration Utility

The BIOS Parameters can be modified and configured on DELL Desktops (Precision, OptiPlex & Latitude) using Dell Client Configuration Utility.

Dell Client Configuration Utility ver 3.0 can be downloaded here:

http://support.dell.com/support/downloads/download.aspx?releaseid=R204280&deviceid=19801&fileid=285029

After the installations there are possibilities to configure different BIOS settings. In my case I wanted Wakeup On LAN to be configured:


You can choose Aftter running: Restart computer, enter the value for minutes and click on Create BIOS Setting Package.

With this action an EXE file has been created. This file can be easily deployed using SCCM Server and BIOS Setting will be unified on all machines .

SCCM task sequence log file locations

The first step to troubleshoot SCCM OSD Task Sequence issues to is check out the log file – this is called smsts.log.

This can be found in one of several locations depending on the progress of the build and the architecture of the OS:

• Windows PE before HDD format: x:\windows\temp\smstslog\smsts.log
• Windows PE after HDD format: x:\smstslog\smsts.log and copied to c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
• Full version Windows before SCCM agent installed: c:\_SMSTaskSequence\Logs\Smstslog\smsts.log
• Full version Windows after SCCM agent installed: c:\windows\system32\ccm\logs\Smstslog\smsts.log
• Full version Windows (x64) after SCCM agent installed: c:\windows\sysWOW64\ccm\logs\Smstslog\smsts.log
• After Task Sequence has finished running: c:\windows\system32\ccm\logs\smsts.log
• After Task Sequence has finished running (x64): c:\windows\sysWOW64\ccm\logs\smsts.log