Hello,
For awhile know we have been receiving the "The certificate is invalid" when used the WSUS Package Publisher tool, but we have been ignoring it because our certificates worked deploying MSI packages through the "WSUS Package Publisher" tool. We just thought the tool didn't like using our in-house created certificates that we have been using for the past few years.
The new version of the WSUS Package Publisher displays this same error, but now it won't let us publish any new MSIs. Is there anyway to figure out why the tool doesn't like our in-house certificates even though they work deploying MSI files?
Note 1: The "Certificate Path" information shows that the publishing certificate and the trusted CA are OK.
Note 2: The CA certificate is installed in the "Trusted Root Certificate Authority" folder.
Note 3: The publishing certificate is installed the "WSUS" and "Trusted Publishers" folder.
For awhile know we have been receiving the "The certificate is invalid" when used the WSUS Package Publisher tool, but we have been ignoring it because our certificates worked deploying MSI packages through the "WSUS Package Publisher" tool. We just thought the tool didn't like using our in-house created certificates that we have been using for the past few years.
The new version of the WSUS Package Publisher displays this same error, but now it won't let us publish any new MSIs. Is there anyway to figure out why the tool doesn't like our in-house certificates even though they work deploying MSI files?
Note 1: The "Certificate Path" information shows that the publishing certificate and the trusted CA are OK.
Note 2: The CA certificate is installed in the "Trusted Root Certificate Authority" folder.
Note 3: The publishing certificate is installed the "WSUS" and "Trusted Publishers" folder.