Certificate for server authentication, install and activate HTTPS listener. Without certificate on each participating PC there is no encrypted WinRM. The certificate infrastructure is absolutely the last from the following list of conditions required for, each must fulfill it:
- CN is the same as host name,
- issued for server authentication,
- valid, so neither revoked nor expired
- not self-signed.
Unless the PC is not already there is a certificate, it can usually via a browser certificate server via the URL. So that traffic is encrypted, it must run over the HTTPS protocol. The default port for this is 443, Windows 7 uses port WinRM 5986th After installing the certificate on to the listener via HTTPS :
winrm quickconfig -transport:https
Is something wrong with the certificate, we learn it here by error message, the message is not a complete lack of certification and inadequate properties differs between.
winrm enumerate winrm/config/listener
one can verify that the HTTPS listener is used. The ports used, valid authentication settings and other parameters of a PC configured.
Bookmarks