Failed to validate content hash on ConfigMgr Distribution Points after Content Validation

sccm logo

We have recently had problems with our global distribution points in ConfigMgr after the monthly content validation has happened. On some of our distribution points (not all) we are getting and error stating:

“Failed to validate content hash”

With our monitoring on the Distribution Point Configuration Status looking like this (click the thumbnails for the larger images):

Failed to validate content hash on ConfigMgr Distribution Points after Content Validation 1

Failed to validate content hash on ConfigMgr Distribution Points after Content Validation 2

Failed to validate content hash on ConfigMgr Distribution Points after Content Validation 3

As you can see from the Asset Message screenshot, the actual error is:

“Failed to retrieve the package list on the distribution point, or the package list in content library doesn’t match the one in WMI.”

This is what the problem was in our situation – on the distribution points that had the error, the package ID was in the WMI but it was not actually on the server as a package, so there was a mismatch.

However, ConfigMgr does not make it easy for you as it does not tell you what the package is so that you cannot find it to redistribute it – the reason for this is that there actually is no package! It is probably an old package that has been previously deleted but remains in the WMI on the Distribution Point server.

So, how do you fix it?

The solution is very simple and you can use Powershell to fix it. You will need to download our Powershell fix package from below:

SCCM Distribution Point Validation Fix

First of all, you need to identify all your Distribution Point servers that have the issue, once you have this list, you can fix them one by one. Below is instructions on what to do on one server but you should repeat this on all your servers that have the issue.

Logon to your Distribution Point server and run Powershell as an administrator. You first need to ensure that you have unrestricted execution policy set, so to do this, run the following Powershell command:

Set-ExecutionPolicy Unrestricted

When you press enter, it will ask you to confirm, just press the “Y” key to complete this process.

Once this is complete, you can now run a Powershell script on your Distribution Point server to identify is there are any packages that are in the WMI on the server that are not actually on your Distribution Point.

The script you need to run is contained in the Powershell DP Fix pack that you downloaded earlier called:

“ContentValidationDPCheck.ps1”

When you run this, if there are any packages within the WMI that are not on the Distribution Point then it will list them for you and write them into an array for storage, then it will remove the WMI entries from the server – however it will ask you to confirm for each deletion. Below is a screenshot from one of our erroring Distribution Point servers with the list of packages in the WMI and the confirmation warnings:

Failed to validate content hash on ConfigMgr Distribution Points after Content Validation 4

Once this is complete, the next time the Content Validation is carried out on your Distribution Points, you should see that all errors have now gone.

COMMENTS

If you have any comments or questions, please feel free to ask using our comments system below.

Alternative Download Pages for Freeware Products

As you may be aware, we supply a number of custom designed and created freeware utilities. All of these are available from our website by click the Downloads button on the top menu bar. However, if you like to use alternative sites for your downloads, then we also have all of our products available to download from the list of sites below:

DOWNLOADS

cNet Download.com

SoftPedia

FreewareFiles

SourceForge

PAD FILES

All of the PAD files for our downloads can also be found here:

PAD Repository

COMMENTS

If you have any suggestions where we can add our freeware products or any other comments, please feel free to use our comments system below.

Windows Server 2012 R2 Core – Adding Roles and Features Error Fix

Windows Server 2012

If you have been trying to load any roles or features onto your Server 2012 R2 Core using Powershell, then you may find that you are the victim of this error message everytime you try to run your command: No matter was source you enter, it will not work. This frustrated us for days until … Read more

Java 7 Update 65 Released – MSI and Offline Installer

Java MSI

Java have now released update 65 of version 7 of their Java Client software.

The update is available as an offline installer and using our guide below, you can extract the MSI from it and use it for deployment by using Windows Updates to update current machines or add to your Configuration Manager Application Catalog or even deploy using Group Policy.

You can download the Offline Installer from the Java website using the link below:

Download

Download Java MSI Packs

Instructions

By following the guide below, you can extract the MSI installer to use in deployment and Windows Updates to automatically update machines using WSUS.

How to extract Java MSI File from the Offline Installer

Update

Update added 26th April 2015 – Please be aware that it seems that the MSI extraction does not always work with the newer versions of Java, so please see the guide below which shows you how to setup a silent install using the standard offline installer:

Java Silent Installation Guide

Comments

If you have any questions about this or wish to leave a comment, please use our comments system below and we will get back to you as soon as we can.

Powershell – Install Server Core GUI Features

powershell

If you have Windows Server 2012 R2 Core installed but you want to be able to use a Graphical User Interface (GUI) then you can use the following Powershell command to enable it:

 Install-WindowsFeature Server-Gui-Shell –Source d:sourcessxs  

NOTE: you should ensure that your source location is correct and up to date with your Windows Updates.

Once this is complete, you should reboot your server to fully enable the GUI.

Powershell – Get List of Windows Updates Installed

If you want to find the full list of Windows Updates that you have installed on your machine, you can use a Powershell command to find this information. This is particularly helpful for operating systems like Windows Server 2012 R2 Core.

COMMAND

Run this command in a Powershell environment on the machine you want to find the list of updates for:

 Get-WmiObject -Class "win32_quickfixengineering"  

This should now detail all the Windows Updates like this:

Powershell - Get List of Windows Updates Installed 6

COMMENTS

If you have any comments or questions, please feel free to use our comments system below.

Powershell Commands

Powershell Commands 7

Powershell is becoming more and more important these days and the possibilities with using it are endless. However, there are also a large amount of very basic easy to use commands that you should add to your knowledge collection.

We all pick up new Powershell commands that help us to do our jobs all the time so from today, we will be adding a Powershell section to our website and adding new commands to it when we come across them. This is more for our own reference than anything else but we thought that we may as well share with you too!
If you wish to also add any commands or Powershell scripts (PS1 files) to our site, please feel free to contact us either by using the comments system below or the Contact button on our menu bar. We will review them, check they work and add them and obviously credit you.

Join Server 2012 R2 Core to your Domain

Windows Server 2012

If you are using Server 2012 R2 Core and you wish to join it to the domain, then you can use this simple Powershell command to do it.

Add-Computer -DomainName YOURDOMAIN.COM -Credentials DOMAINUSERNAME -Restart

Note that the -Restart command at the end will automatically restart your server once it has completed the joining process.

Also be aware that you should change YOURDOMAIN.COM to the domain name that you are trying to join and also change DOMAINUSERNAME to domain admin credentials for the domain you are joining.

SCCM 2012 Client Stuck in Provisioning Mode

sccm logo

We recently have had issues with our Windows 7 operating system deployments seemingly not completing fully.

We were getting the following issues:

  • The ConfigMgr client was not fully installed – it was displaying the Site Mode as “Unknown”
  • The ConfigMgr client was not picking up a certificate – it was displaying as “None”
  • The _SMSTaskSequence folder remained on the largest partition and was not being deleted
  • Could not install anything from the Software Catalog
  • Could not remote onto the client
  • Tabs missing from the client control panel applet

The client control panel applet looked like this:

SCCM Client

After going through various logs and searching the internet, we found that the problem was that after the client install during the task sequence, after a reboot from WinPE into Windows, the client itself was getting stuck in provisioning mode – a bit like a evaluation mode for the client so when into the main windows operating system, it will not function correctly.

So, how can it be fixed?

The problem is two registry keys that need to be amended after the client installation during the task sequence. So, immediately after the client installation step in your task sequence, you should create two Run Command Line steps. In the first step, you should call it “Turn off provisioning mode” and for the command line enter the following:

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v ProvisioningMode /t REG_SZ /d false /f

So your first step should look like this:

SCCM - Turn off provisioning mode

For your second command line step, you should call it “Turn off System Task Excludes” and for the command line enter the following:

REG ADD HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\CCM\CcmExec /v SystemTaskExcludes /t REG_SZ /d "" /f

So your second step should look like this:

SCCM - Turn off task sequence schedules

Once you have made these additions then save your task sequence and try another deployment, you should now find that this works perfectly!

If you also have a machine that is affected by this problem and do not want to re-image the machine, you can simply make these changes in the registry manually in Windows, reboot the machine and you should then find that the client will work.

Comments

If you have any comments or questions, please feel free to use our comments section below.

Remove Windows XP End of Life Messages Utility

windows

On April 8th 2014, Microsoft ended all support for Windows XP. They then released a number of Windows Updates that displays annoying messages on your desktop telling you that your operating system is now at its end of life. This is the Windows message:

Remove Windows XP End of Life Messages Utility 8

The second is the Microsoft Security Essentials one:

Remove Windows XP End of Life Messages Utility 9

We have been asked a number of times about how to remove these and we have now created a new utility that will help you to do this.

DOWNLOAD

Download RemoveXP End of Life

CONSIDERATIONS

There is one problem with removing the Microsoft Security Essentials end of life message. If you have already installed Version 4.5.216.0 then you cannot remove this message. Also, eventually, your system will update to this version so the best thing to do is to uninstall MSE and install another free anti-virus like Avast or Avira.

If you have not yet installed Version 4.5.216.0 then this utility will work for you for the MSE part. The Windows end of life message should be able to be removed without issue using this utility.

You must have Dot Net 2.0 installed for this to work.

INSTRUCTIONS

Once you have downloaded the file you should run the executable file to start the utility. You will then be presented with a utility that looks like this:

Remove Windows XP End of Life Messages Utility 10

You should then click the buttons on the left hand side in relation to what you want to do. So, if you want to remove the Windows message, click the top button, if you want to remove the MSE message, click the bottom button.

Once you have done this, you should reboot your machine and you should now notice that the messages have not reappeared.

COMMENTS

If you have any questions or comments about this, please feel free to use our comments section below.

Adobe Flash Player 14.0.0.175 Released – MSI Download

Adobe Flash Player 14.0.0.175 Released - MSI Download 11Adobe have released another update to their Adobe Flash Player software, this time taking it up to version 14.0.0.145.

As always, you can download the executable file or get the MSI file so that you can load it into your Configuration Manager Software Catalog.

The update is also now available to import through System Center Update Publisher (SCUP) so you can inject it into your WSUS or Configuration Manager systems.

You can the download in all formats for all browsers for Windows and Mac directly from Adobe by clicking the download button below.

DOWNLOAD

Adobe Flash Player 14.0.0.175 Released - MSI Download 12

COMMENTS

If you have any comments or questions, please use our comments system below.