Error = 0x800703ee (Failed to Add Update Source for WUAgent) RESOLVED

Just recently, I’ve been wondering why I haven’t been prompted with any new Windows Updates from SCCM. I haven’t had too much time to look into this, but thought today is the day to get this sorted.

My colleagues on the other hand were ecstatic that they were receiving these updates. The ADR policy set for Windows 8.1 updates (critical and security updates ONLY) is to deploy 2 days after it’s release and wait a further 7 days until it is forced installed. We too have another ADR policy for Office 2013 updates. Same rule applies, 2 days deploy, 7 days install.

Having being well over that 7-9 day period, the boys are constantly prompted about a reboot (note – some of my colleagues reboot their PCs on an annually occurrence…….).

Identifying Problem

Firstly, when troubleshooting windows update issues on a PC this managed by SCCM, you will need to browse to the following directory;


This log file will more or less advise what the problem or at least, guide you in the right direction in terms of identifying update issues.

WSUS Error

Highlighted red, was the issue at hand – Failed to Add Update Source for WUAgent of type (2) and id {GUID string}. Error = 0x800703ee

After reviewing Matthew Hudson’s blog, even though the error message is different, the process that he advised worked for me.


Browse to the following directory;


You should see the Registry.pol file.

Rename It (i.e. Registry.pol.old).

WSUS Error 2

Once you’ve renamed said file, ensure you have the WUAHandler.log open.

Open up the Services (services.msc) window on the client PC and restart the SMSAgent service.

WSUS Error 6

Once reset, re-run the Software Update Scan Cycle under the Configuration Manager Actions Tab

WSUS Error 7

Once reset, you should see the WUAHandler.log file populate.

WSUS Error 3

Software Center should now display all missing updates.

WSUS Error 4

Hope this helps someone out there!

Good luck.

RESOLVED! SQL Server Configuration Manager – Cannot connect to WMI Provider Error

I’m back; it has been too long!

So I was stuck attempting to open the SQL Server Configuration Manager Application on my Configuration Manager Server.

Error Below;



This problem would have arose when we uninstalled an instance of SQL server; the WMI provider would have been removed during this process. From what I’ve researched, both the 32bit and 64bit instance of SQL Server share the same WMI configuration file.

Location – %programfiles(x86)% directory.


Open a CMD prompt as an Administrator.

Now browse to the following location, which would be the version of SQL you’re using on your SCCM server (or where the DB resides for your SCCM environment).

We’re using SQL 2012 so the directory below responds to our requirements;

cd “c:\Program Files (x86)\Microsoft SQL Server\110\Shared”


Now, once in the appropriate location, run the following command;

mofcomp sqlmgmproviderxpsp2up.mof


We’re now able to re-open the SQL Server Configuration Manager Window!


Hope this is helpful!

SCCM Application Deployment Error – 0x87D00607 Fix!

Down the other end of the office I could hear one of my colleagues complaining that an App deployment failed when installing from their SCCM’s Software Center Console on their workstation.

They received the following error message;

Generally, the first place to check is with your boundaries and boundary groups and to ensure that they’re setup correctly. Actually, reviewing your boundaries and boundary groups should be the first place to check when troubleshooting these errors.

The way we’ve configured the boundary groups within our environment(s) is through the use of Active Directory. Some choose to use IP subnets to define their boundaries, however we found that Active Directory would best suit our environment/setup. Resolution; Change the Deployment option under the Application deployment section.

I had ‘Do not download content’ selected from the dropdown menu. As soon as I changed it to ‘Download content from distribution point and run locally‘, I was able to install the application successfully.

We now have a quieter office thanks to this resolution! Good Luck!

Easy Way of Exporting from SCCM 2012

So there have been several requests internally who are NOW starting to leverage off the information that is readily available within SCCM.

Question; How do I export a list of devices from SCCM into Excel?

Solution; Easy! Ctrl A, Ctrl C, (select Excel spreadsheet), Ctrl V. Done.

Here’s the walk through guide –

As I need the list of Active PCs on the network, I have used the search functionality within devices. Note; this is just an example, as you can easily achieve this by using the Active/Inactive Collection under Device Collections.


Literally, use the Select All key combination (Ctrl + A) or Individual selection key combination (Ctrl + Left Mouse Click) and Copy the data (Ctrl + C).

(Select All)


(Individual Selection)


Now simply, head over to to your spreadsheet and paste the results (Ctrl + P)


As you can see, you should now have your ‘export’ performed successfully.


See the comparison below; requirement achieved.


Good luck!

Clearing Windows Temp Directory using SCCM’s Compliance Settings

In order to meet the objectives I’ve been assigned which are to perform Routine Infrastructure Tasks (i.e. Maintenance work) against ALL servers we manage, I have taken advantage of SCCM (and as well learning from an SCCM expert) to automate these mundane, lame and boring tasks!

The first step with anything is to map out what you want to achieve. Taking the time to plan out your steps from start to finish will allow you to stay focused and keep on track. What you don’t want to do is to lose the momentum you gain when working on a task/project. You also do not want to deviate away from the task at hand as well. Check out Steven Hosking’s blog on Logical Steps to Automate A Task.

What: Clear the Windows Temp directory

When: Once a Week

Why: Stop accumulating unnecessary data on the system drive.

How: SCCM Compliance Settings.

Within SCCM Compliance Settings we will use the ‘detection’ and ‘remediation’ method to achieve our task of cleaning the Windows Temp directory.

Under Assets and Compliance select Configuration Items. When selected right click in the clear space and select Create Configuration Item.


Fill in the below details as you see fit. In the example below, I have named it RITs – Clear Windows Temp Folder. As this task is targeted to the Windows devices, we will leave it as is. Use the Categories too, as you see fit. Select Next once completed.


As we are targeting servers only, we have selected the below. If however you’re managing ALL Windows devices, leave it as default (Select All). Select Next.


Select New…


Enter a Name and Description. From the drop down menus, select Script from the Settings Type and select String from Data Type. Let’s Add Script.. now under Discovery Script.


Now with the Discovery Script I have used the following to identify if there are any data within the Temp directory.


on error resume next
Set FSO = CreateObject(“Scripting.FileSystemObject”)
If fso.folderexists(“C:\Windows\Temp”) Then
If fso.getfolder.Count = 0 And fso.SubFolders.Count = 0 Then
wscript.echo “Compliant”
wscript.echo “Non-Compliant”
End If
wscript.echo “Compliant”
End if

You ask why have I used VBScript to achieve this detection method. Can I use PowerShell instead?

The reason why I have used VBscript over PowerShell in this instance is because of the multitude of servers we manage (also trial and error as I had PowerShell scripts to do ALL my tasks). Because it ranges from Windows Server 2003 to Windows Server 2012 R2, certain PowerShell commandlets may not work with older versions of PowerShell. VB on the other hand is compatible on the majority, if not all Windows servers.

Now with the Remediation Script I have left my PowerShell commands from the start. Reason being is that the Powershell commandlet is compatible across ALL PowerShell versions, therefore there was no reason to change.


Remove-Item C:\Windows\Temp\* -Force -Recurse
$ErrorActionPreference = “SilentlyContinue”

Once completed, you should see the below screenshot match your Settings.


Now Select the Compliance Tab. Once selected, select New…

When prompted with the Create Rule Window, fill in the Name and Description. Leave the Rule Type as default, Value. Set ‘The value returned by the specified script’ as Equal and ‘the following value:’ to Compliant.

Tick ‘Run the specified remediation script when this setting is noncompliant’.

Set ‘Noncompliance severity for reports;’ to Critical.

Once completed, hit OK.


You should now see the newly created Compliance Rule. Hit OK.


You should now see the Detection Method in the Specified settings for the operating system. Select Next >


As we have already created the Compliance Rule we can simply hit Next >


Under the Summary do a quick review before hitting Next > to process and create the Configuration Item.


You have now created the Compliance Item. Time to create the Compliance Baseline and deploy it to a Collection(s).



Now go back to Assets and Compliance and select Configuration Baselines. From here right click in the clear space and select Create Configuration Baseline.


Fill in the Compliance Baseline Name and Description details as you see fit.

In the Configuration Data field, select Add and then Configuration Item.


Search for the the created Compliance Item and select OK.


You should now see the Configuration Item now displaying in the Configuration Baseline data section. With any other tasks specific to clean-up/maintenance, I would include them as well into this Baseline. Once completed, select OK.


You should now see your recently created Compliance Baseline. Now it is time to deploy.


Right click on the Baseline and select Deploy.


By default, the Baseline should already be selected. Tick ‘Remediate noncompliant rules when supported’ and ‘Allow remediation outside the maintenance window’.

If you are taking advantage of SCOM (System Center Operations Manager) you can generate alerts depending on the compliance rate. We will leave this disabled.

In the Collections section, select the Collection you would like to deploy this baseline to. In our case, I will deploying it to our Test Deployment Group.

Now set a schedule as to when you would like this performed and hit OK.


You should now see the baseline marked as deployed.


Now lets browse to a server associated with that Collection and check to see if it has been deployed successfully.

Browse to a server that the Baseline has been deployed to and open the Configuration Manager Properties. Generally it would take several minutes to deploy or pick up (depending on the type of collections available) but you can accelerate the process by going into Actions and selecting Machine Policy & Evaluation Cycle.

Once it has been selected, wait about a minute, close and reopen the Configuration Manager Properties.


This time in Configuration Manager Properties, select Configurations and in here, you should now see the Baseline we created earlier. You should see the Last Evaluation status as N/A and Compliance State as Unknown…


On the server, bring up the Windows Temp directory and lay it side-by-side the Configuration Manager Properties window. Now select Evaluate.

Windows Temp Directory with Data


After a few seconds, you should see the data disappear within the Widows Temp directory.



Back in the Configuration Manager Properties window, you should see the following status.


You have no successfully completed/automate the task of clearing Windows Temp directory!

My Introduction to Microsoft’s System Center Suite – Configuration Manager.

Over the past year or so, I have been working with Microsoft’s System Center Configuration Manager. The role I have with our company (along with support, project work and other IT related tasks) is to perform Routine Infrastructure Tasks on a weekly basis. Prior to using and leveraging off Configuration Manager, I would have to go through each server (client & internal) and perform mundane, boring, manual tasks. Tasks such as clearing the temp directories, clearing the downloads directory under the Software Distribution folder, performing a backup of the System Info on each server. This is feasible if you’re working with a handful of servers; I was looking at close to 60-70 servers which would take up my entire day. This all changed when introduced to Microsoft’s System Center, Configuration Manager. The following posts will be on how I have used Configuration Manager to my advantage to allow me to automate, monitor and report on the mundane, boring and manual tasks. I will also describe how we’ve used Configuration Manager to patch and update our internal/client servers.