Alright, I was surely hoping not to have to post, but I've been through all of the troubleshooting that I can find.
I am trying to publish my first update, and am getting the following message:
Invalid Operation Exception: The package could not be published.
Verification of file signature failed for file: \\SERVER\UpdateServicesPackages\c5479764-26ae-41ca-bcc1-4a22b5ca13f2\616c241d-4d14-48c7-b3f1-5f816b118dfa_1.cab
So... I've been poking around for tips, and can say this.
The certificate is a brand new 2048-bit certificate.
The WSUS Publishers Self-Signed certificate is available on the WSUS server in the WSUS store with the private key.
The WSUS Publishers Self-Signed certificate is installed on the WSUS server and our test client (including where I am running LUP) in the Trusted Publishers and and Trusted Root Certification Authorities stores. The status indicates the certificate is valid.
I looked through the Troubleshooting LUP wiki page, and everything appears to be fine with the certificate and distribution.
I was able to keep the CAB file from being deleted, and was able to verify that is indeed signed with my brand-spanking new signing certificate. The serial and thumbprint match.
Joel, it's been a while since I've had to troubleshoot the certs side of things. Do you have the Group/Local policies in place? I forget if the server will reject it or not. Also, to be clear, you used LUP to create the certificate right? If you used the MMC snapin to import it that won't work ... it has to be created or imported via LUP.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi, and sorry for my english.
I'm too having this problem, but with a CA certificate.
After I'm created in center certification this certificate with the 2048 bits key, in IIS 7.0 on wsus server. I exported it's in the LUP and after to GPO in container "Trusted Publishers"'. It was 1st time error with my publish. I add this CA certificate to the «Trusted Root Certificates Authorites» and had 2nd time error.I dont think that program errors, but don't know what doing. Can u help me?
I can add that this problem is saved in "Wsus Package Publisher"... and :-)
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Alright, I was surely hoping not to have to post, but I've been through all of the troubleshooting that I can find.
I am trying to publish my first update, and am getting the following message:
So... I've been poking around for tips, and can say this.
I was able to keep the CAB file from being deleted, and was able to verify that is indeed signed with my brand-spanking new signing certificate. The serial and thumbprint match.
Any other advice?
Joel
Joel, it's been a while since I've had to troubleshoot the certs side of things. Do you have the Group/Local policies in place? I forget if the server will reject it or not. Also, to be clear, you used LUP to create the certificate right? If you used the MMC snapin to import it that won't work ... it has to be created or imported via LUP.
Hi, and sorry for my english.
I'm too having this problem, but with a CA certificate.
After I'm created in center certification this certificate with the 2048 bits key, in IIS 7.0 on wsus server. I exported it's in the LUP and after to GPO in container "Trusted Publishers"'. It was 1st time error with my publish. I add this CA certificate to the «Trusted Root Certificates Authorites» and had 2nd time error.I dont think that program errors, but don't know what doing. Can u help me?
I can add that this problem is saved in "Wsus Package Publisher"... and :-)