This function will retrieves C: drive volume information’s for one or more remote Computers.


Fix- Error -Unable to compile Sql CE script file during SCCM client install or upgrade (80004005)

IF you get the below error.

File C:\WINDOWS\ccmsetup\{CA4329EC-A4F5-4E5E-A9FE-EFAAE88B0D67}\client.msi installation failed. Error text: ExitCode: 1603
Action: CcmCompileSqlCEScripts.
Setup was unable to compile Sql CE script file C:\WINDOWS\CCM\StateMessageStore.sqlce.
The error code is 80004005.

Steps to Resolve the issue :

1- Uninstall the SCCM client . (C:\Windows\ccmsetup>ccmsetup.exe /uninstall)

2- Then move the following files to a backup folder. These are the old client Sql CE database files. They are located in the client install folder %windir%\CCM\ or in the SMS_CCM folder).

  • CcmStore.sdf
  • CertEnrollmentStore.sdf
  • ComplRelayStore.sdf
  • InventoryStore.sdf
  • UserAffinityStore.sdf

OR you can take a backup and empty the CCM Folder

3- Install the SCCM client again.

This will resolve the issue

FIX- Rebuild the WMI On Windows Servers

Needs to follow the below Steps to resolve the WMI Issues.

1. Change startup type to Window Management Instrumentation (WMI) Service to disabled
2.  Stop the WMI Service; you may need to stop IP Helper Service first or other dependent services before it allows you to stop WMI Service
3.  Rename the repository folder: C:\WINDOWS\system32\wbem\Repository to Repository.old
4.  Open a CMD Prompt with elevated privileges
5.  CD windows\system32\wbem
6.  for /f %s in (‘dir /b /s *.dll’) do regsvr32 /s %s
7.  Set the WMI Service type back to Automatic and start WMI Service
8.  cd /d c:\ ((go to the root of the c drive, this is important))
9.  for /f %s in (‘dir /s /b *.mof *.mfl’) do mofcomp %s
10.  Reboot the server

Recover the WMI

Follow the Below Steps to

1. Stop WMI and kill any WmiPrvse.exe processes.
2. Start up WMI
3. cd C:\Windows\System32\wbem\AutoRecover
4. Run this command: for /f %s in (‘dir /b *.mof *.mfl’) do mofcomp %s


Batch File  for same activity.

Copy the below lines and create the batch file and run on problem server.

@echo off
sc config winmgmt start= disabled
net stop winmgmt /y
cd %windir%system32wbem
for /f %s in (‘dir /b /s *.dll’) do regsvr32 /s %s
wmiprvse /regserver
winmgmt /regserver
sc config winmgmt start= auto
net start winmgmt
cd \
for /f %s in (‘dir /s /b *.mof *.mfl’) do mofcomp %s

MS Patch Installation Failure: Solution

If you face MS Patch Installation Failure with below error codes, then try the below steps to resolve the issue.

Error logs:


Application Logs : The Cryptographic Services service failed to initialize the Catalog Database. The ESENT error was: -1011. (Event ID 257)


Log Name: Application
Source: Microsoft-Windows-CAPI2
Date: 24/05/2017 04:44:09
Event ID: 257
Task Category: None
Level: Error
Keywords: Classic
User: N/A
The Cryptographic Services service failed to initialize the Catalog Database. The ESENT error was: -1011.
Event Xml:
<Event xmlns=””&gt;
<Provider Name=”Microsoft-Windows-CAPI2″ Guid=”{5bbca4a8-b209-48dc-a8c7-b23d3e5216fb}” EventSourceName=”Microsoft-Windows-CAPI2″ />
<EventID Qualifiers=”0″>257</EventID>
<TimeCreated SystemTime=”2017-05-24T03:44:09.287530700Z” />
<Correlation />
<Execution ProcessID=”480″ ThreadID=”4604″ />
<Security />


System Logs: Installation Failure: Windows failed to install the following update with error 0x8000ffff: Security Update for Windows (KB********). (Event ID 20)


Log Name: System
Source: Microsoft-Windows-WindowsUpdateClient
Date: 24/05/2017 04:42:37
Event ID: 20
Task Category: Windows Update Agent
Level: Error
Keywords: Failure,Installation
Installation Failure: Windows failed to install the following update with error 0x8000ffff: Security Update for Windows (KB4012212).
Event Xml:
<Event xmlns=””&gt;
<Provider Name=”Microsoft-Windows-WindowsUpdateClient” Guid=”{945A8954-C147-4ACD-923F-40C45405A658}” />
<TimeCreated SystemTime=”2017-05-24T03:42:37.881470200Z” />
<Correlation />
<Execution ProcessID=”980″ ThreadID=”2088″ />
<Security UserID=”S-1-5-18″ />
<Data Name=”errorCode”>0x8000ffff</Data>
<Data Name=”updateTitle”>Security Update for Windows (KB4012212)</Data>
<Data Name=”updateGuid”>{3CED8332-5A43-4CB1-AED9-4ABDDB4BA3CA}</Data>
<Data Name=”updateRevisionNumber”>501</Data>


Steps to resolve the issue:

  1. Removed any tmp*.cat files in the

“%systemroot%\System32\catroot\{F750E6C3-38EE-11D1-85E5-00C04FC295EE}” folder.

  1. At the command prompt run below command

net stop cryptsvc

  1. rename %systemroot%\System32\Catroot2 oldcatroot2
  1. At the command prompt run below command

net start cryptsvc

5. Try to install the MS patch again.


How to install SUP with WSUS: Step-by-Step

This guide will help you set up your own WSUS server on Windows Server 2012 R2 and Sync with SCCM 2012.

Windows Server Update Services (WSUS) is a free patch management tool by Microsoft. It allows System Admins to centrally push Microsoft product updates to computers that are running Windows on their network

Steps 1 – Once Server Manager is open, select Add roles and features.


Step 2 – In the Add Roles and Features Wizard, click next on the Before You Begin page. You can optionally select to Skip this page by default for the future.


Step 3 – Select Role-based or feature-based installation. Click Next…

Step 4 – Select your server from the server pool. If you’re not using Hyper-V, you will see only one server.

Step 5 – In the Server Roles list, scroll down and select Windows Server Update Services

Step 6 – A window will pop up showing you the features that are required for WSUS which will be enabled. Click Add Features


Step 7 – You will get the below screen, Click Next…


Step 8 – On Role Services page please select Database (It will use the SQL DB). Click Next…


Step 9 – This page will allow you to set the destination directory for the downloaded updates. Tick the checkbox for Store updates in the following location.

Enter the path here. It can either be a local or a remote path. Keep in mind that WSUS will take up considerable amount of storage as time goes on. It is not unusual to find update folders of sizes greater than 50 GB.

Choose your destination accordingly. Click Next…


Step 10 – Provide the database server name and check the connection, should be successfully connected to server. Click Next…


Step 11 – You need to add the Web Server Role (IIS), Click Next…


Step 12 – Select the Required IIS role servers. Click Next…


Step 13 – On the Confirmation screen, check the Restart the destination server automatically if required option if you wish to do so, otherwise you can leave it unchecked. Click Install…


Installation will start ….


Step 14 – Need to click on Launch Post-Installation tasks


Step 15 – You will the below screen and Windows Server Update Service status will be: Configuration successfully completed. Click Close


Note: WSUS configuration is not required from WSUS server, as that configuration will be taken care by SCCM while we install the SUP.  (Do not follow the Wizard from WSUS Server)


Installing SUP On remote Server

In this section we will see the steps how to deploy the software update point on Remote server using SCCM 2012 R2.

Step 1 – To start with, install the Software Update Point role first. Launch the Configuration Manager Console, click on Administration, expand Overview, click Site Configuration, click on Sites. Right click on Primary Site  àConfiguration Site Components  à Software Update Point


Step 2 – Select server where you want to install the Software Update Point


Step 3 – Click Next… with default setting.

Step 4 – Click Next… with default setting.

Step 5 – At Site Role Selection, Select Software Update Point.


Step 6 – When you install WSUS, you can specify whether to use the default Internet Information Services (IIS) website or create a new custom WSUS website. WSUS configures port 8530 for HTTP and port 8531 for HTTPS. You must specify these port settings when you create the software update point for the site.


Click Next … with default setting.

Step 7 – At Synchronization Source, Select Synchronize from Microsoft Update (As this the first server and we don’t have any upstream server)


Step 8 – At this step please update the Synchronization Schedule as per your requirement.


Step 9 – For Supersedence Rules, select immediately expire a superseded software update. Click Next.


Step 10 – Select Critical Updates, Definition Updates and Security Updates. Note that you can do this after installation of SUP. Click Next.


Step 11- Choose the products that you want to synchronize. Click Next…

Step 12 – Choose the desired language, click next.

Step 13 – The Software Update Point role has been installed. Click Close.

Step 14 – Go to Primary Site Server If you are running with WSUS v 6.2 or later then we needs to install the “Windows Server Update Services Tools” Features on your primary site server.






After this installation, in the configuration manager console, click Software Library, expand Overview, click Software Updates, click All Software Updates and at the top ribbon click Synchronize Software Updates.

Now all update will available at \Software Library\Overview\Software Updates\All Software Updates


Now you need to create Software Update Group and deploy to the required collections.