Purpose
This article is meant to provide some general troubleshooting tips for issues publishing data when using Shavlik SCUPdates.
Resolution
1) Verify that all pre-requisites have been satisfied (as per our guides).
2) Verify that the WSUS Self Signed Certificate is in the Trusted Root and Trusted Publisher’s location on the WSUS, SCUP, and SCCM machines (as per our guides). If the Certificate is not in place use a GPO, or manually copy the certificate to Trusted Root and Trusted Publishers. This certificate will need to be in place on all machines if WSUS, SCCM, and SCUP are on separate machines.
3) Check to see that the WSUS Self Signed Certificate is in place on the client machines. If the Certificate is not in place, use a GPO to copy the certificate to Trusted Root and Trusted Publishers.
4) Verify that 'Windows Update> Allowed Signed Content from Intranet' is enabled in the client machines' GPO, and that the GPO has been successfully applied.
5) The most common publishing issue is that the hash verification failed, which typically indicates that the update data does not match the vendor file. Ensure that you are using the most current data, and are not attempting to publish an outdated update. More information on this can be found here.
6) Any errors in the deployment process will be in the 'windowsupdate.log' file (located in the %windir% directory on the client machine). Any errors in publishing will be in the 'scup.log' file (located in the current user's %temp% directory).
Products
Shavlik SCUPdates