Hi jonathonz,
I never test with this settings, but I suspect that it is not the cause of the problem.
If you are publishing the update from the Wsus server itself, check :
If you have installed the Microsoft kb2661254 read this : kb2661254
I never test with this settings, but I suspect that it is not the cause of the problem.
If you are publishing the update from the Wsus server itself, check :
- If you are using a selfsign certificate, it should be present in :
* (Local Computer)\Wsus certificate folder.
* (Local Computer)\Trusted Publisher.
* (Local Computer)\Trusted Root Certification Authority.
- If you are using your own signing-code certificate, it should be present in :
* (Local Computer)\Wsus certificate folder.
* (Local Computer)\Trusted Publisher.
* And the Certificate of the authority who have made this certificate should be in the (Local Computer)\Trusted Roor Certification Authority.
If you are publishing the update from a computer, check : - If you are using a selfsign certificate, it should be present in :
* (Local Computer)\Trusted Publisher.
* (Local Computer)\Trusted Root Certification Authority.
- If you are using your own signing-code certificate, it should be present in :
* (Local Computer)\Trusted Publisher.
* And the Certificate of the authority who have made this certificate should be in the (Local Computer)\Trusted Roor Certification Authority.
In both case, the machine should be reboot so that this can take effect.If you have installed the Microsoft kb2661254 read this : kb2661254