IT Consultant Everyday Notes

Just some problems/solutions storage

Category Archives: Updates

SCCM 2012: CU2 installation failed

Microsoft published CU2 for SCCM 2012 recently. I faced installation issues trying to get it installed. In GUI installer it failed on the second step (update installation).

In logs (c:\windows\TEMP\configmgr2012-rtm-co2-kb2780664-emu.msi.log”) I found:

MSI (s) (B8:F4) [10:17:12:708]: Note: 1: 1708
MSI (s) (B8:F4) [10:17:12:708]: Note: 1: 2205 2:  3: Error
MSI (s) (B8:F4) [10:17:12:708]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1708
MSI (s) (B8:F4) [10:17:12:708]: Note: 1: 2205 2:  3: Error
MSI (s) (B8:F4) [10:17:12:708]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (B8:F4) [10:17:12:708]: Product: Cumulative Update 2 for Configuration Manager RTM (KB2780664) — Installation failed.

I copied an extracted .msi file to a separate folder and tried to run it from there. This time I had clearer errors:

1. WDS is running and need to be stopped

2. There is no enough space on drive C: (even though requisites check passed just fine!)



1. I manually stopped WDS

2. I freed 200MB of space on C:\ (error asked for 74MB and I had them free on c: so I decided to free more just to be on safe side)

After that I restarted GUI installer and it finished without errors.

SCCM: Updates cannot be deployed due to WSUS improvements

Recently Microsoft published a WSUS update to support Windows 8 and Server 2012.  A lot of updates must be re-downloaded after that, otherwise they cannot be deployed.

Here is the way to fix it:

SCCM 2007: Apply hotfix described in

SCCM 2012: How to remove an Update installed via offline service

When you use Offline image servicing in SCCM you can add updates, but there is no clear way to remove them (for example if update is obsolete). You can do it manually using DISM. Step-by-step is here

SCCM 2012: Clients cannot install deployed update packs. Error 0x87D00692

Issue: SCCM Clients cannot install deployed updates.

Resolution: Check your deployment status either in console, or using SCCM report  (Software Updates – E Troubleshooting/Troubleshooting 2 – Deployment errors)


The cause of failure is “GPO conflict”. Domain GPO overwrites SCCM Client settings and points the machine to corporate WSUS server. That is why Client cannot use SUP for update evaluation. It is necessary to either set GPO settings for Intranet Windows Update Server to “Not Configured” and let SCCM client configure local policy properly or put SUP FQDN and port instead of WSUS into GPO. If you are in migration and not ready to repoint all machines to SCCM  you can configure GPO to repoint the settings to SCCM for SCCM clients only using WMI filter (see more here )