phiadmin
asked on
SCUP 2011 fails at publishing updates
I'm attempting to set up SCUP 2011 on a 2012 Datacenter edition virtual machine with SCCM 2012 SP1 and WSUS 6.2.9200.16384 previously installed.
As a test, I'm attempting to deploy the latest Java update MSI following the steps in this link: http://www.techygeekshome.co.uk/2013/04/java-client-updates-deployment-using.html
It's failing when publishing full content. Publishing Metadata works.
During the SCUP setup, I'd imported our domain cert (2048bit from GoDaddy), and set that cert up in Trusted Root Certs, Trusted Publishers, & WSUS, and enabled GPO to accept it. I have not installed the WSUS 3.0 SP2 hotfix, as it appers to not be needed/compatible (error when attempting to install it
I'm getting the following series of errors in the SCUP.log. I don't understand why some times are timestamped with a date of 1/1/1601 (see bold), and have unchecked the setting in SCUP options - add timestamp when signing updates. (neither way works.)
2014-01-07 19:03:17.785 UTC Info Scup2011.4 CabUtilities.CheckCertific ateSignatu re File cert verification failed for \\WSUS\UpdateServicesPacka ges\1ab59b f5-2009-45 fe-9938-56 dce1ea8533 \45a2154d- 2e2f-4ce4- bbe6-25950 e25a185_1. cab with 2148204816 Updates Publisher 1/7/2014 11:03:17 AM 4 (0x0004)
--
2014-01-07 19:03:17.786 UTC Error Scup2011.4 Publisher.GetLocalFileDeta ils VerifyAndPublishPackage(): Failed to Verify Signature for file: \\WSUS\UpdateServicesPacka ges\1ab59b f5-2009-45 fe-9938-56 dce1ea8533 \45a2154d- 2e2f-4ce4- bbe6-25950 e25a185_1. cab 1/1/1601 12:00:00 AM 1186801212 (0x46BD263C)
--
2014-01-07 19:03:17.787 UTC Error Scup2011.4 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file: \\WSUS\UpdateServicesPacka ges\1ab59b f5-2009-45 fe-9938-56 dce1ea8533 \45a2154d- 2e2f-4ce4- bbe6-25950 e25a185_1. cab 1/1/1601 12:00:00 AM 1186801212 (0x46BD263C)
---
PublishItem: InvalidException occurred during publishing: Verification of file signature failed for file: \\WSUS\UpdateServicesPacka ges\1ab59b f5-2009-45 fe-9938-56 dce1ea8533 \45a2154d- 2e2f-4ce4- bbe6-25950 e25a185_1. cab Updates Publisher 1/7/2014 11:03:17 AM 4 (0x0004)
---
Publish: A fatal error occurred during publishing :Signature verification exception during publish, verify the WSUS certificates and advanced timestamp setting are properly configured. Updates Publisher 1/7/2014 11:03:17 AM 4 (0x0004)
Everything I've googled seems to point to certificate issues or installing the hotfix, but I don't see how that could be the problem.
As a test, I'm attempting to deploy the latest Java update MSI following the steps in this link: http://www.techygeekshome.co.uk/2013/04/java-client-updates-deployment-using.html
It's failing when publishing full content. Publishing Metadata works.
During the SCUP setup, I'd imported our domain cert (2048bit from GoDaddy), and set that cert up in Trusted Root Certs, Trusted Publishers, & WSUS, and enabled GPO to accept it. I have not installed the WSUS 3.0 SP2 hotfix, as it appers to not be needed/compatible (error when attempting to install it
I'm getting the following series of errors in the SCUP.log. I don't understand why some times are timestamped with a date of 1/1/1601 (see bold), and have unchecked the setting in SCUP options - add timestamp when signing updates. (neither way works.)
2014-01-07 19:03:17.785 UTC Info Scup2011.4 CabUtilities.CheckCertific
--
2014-01-07 19:03:17.786 UTC Error Scup2011.4 Publisher.GetLocalFileDeta
--
2014-01-07 19:03:17.787 UTC Error Scup2011.4 Publisher.PublishPackage PublishPackage(): Operation Failed with Error: Verification of file signature failed for file: \\WSUS\UpdateServicesPacka
---
PublishItem: InvalidException occurred during publishing: Verification of file signature failed for file: \\WSUS\UpdateServicesPacka
---
Publish: A fatal error occurred during publishing :Signature verification exception during publish, verify the WSUS certificates and advanced timestamp setting are properly configured. Updates Publisher 1/7/2014 11:03:17 AM 4 (0x0004)
Everything I've googled seems to point to certificate issues or installing the hotfix, but I don't see how that could be the problem.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.