6.4

Use the following command to congure TrustedHosts:
winrm.cmd
N Computers in the TrustedHosts list might not be authenticated. For more information, run the
following command:
winrm help config
You can also run the following command to set the remote host as a trusted host on the client:
winrm set winrm/config/client'@{TrustedHosts="10.0.5.35"}'
What to do next
Once you have enabled the protocol, skip to “Congure a Firewall,” on page 33.
Enable HTTPS Protocol for PowerShell Remoting
If you have not already enabled PowerShell Remoting and want to use the HTTPS protocol, follow these
steps.
If you want to enable the HTTP protocol instead of the HTTP protocol, see “Enable HTTP Protocol for
PowerShell Remoting,” on page 29. However, it is recommended to implement HTTPS for encrypting the
trac between the client and remote server.
These are the steps for enabling the HTTPS protocol:
Procedure
1 “Acquire an SSL Certicate,” on page 30
2 “Create a Self-Signed SSL Certicate Using the IIS Manager,” on page 31
3 “Create a Self-Signed SSL Certicate Using Makecert.exe,” on page 31
4 “Create a Self-Signed SSL Certicate Using OpenSSL,” on page 31
5 “Import the SSL Certicate on the Remote Machine,” on page 32
6 “Congure a WinRM HTTPS Listener,” on page 33
Acquire an SSL Certificate
To set up PowerShell remoting to use the HTTPS protocol, deploy an SSL certicate to the remote server.
To acquire an SSL certicate, rst generate a self-signed certicate. There are two purposes for using SSL
certicates with PowerShell remoting:
n
Encrypting trac between client and server
n
Verifying server identity (CN check)
The following are the methods to generate a self-signed SSL certicate:
“Create a Self-Signed SSL Certicate Using the IIS Manager,” on page 31
“Create a Self-Signed SSL Certicate Using Makecert.exe,” on page 31
“Create a Self-Signed SSL Certicate Using OpenSSL,” on page 31
In all these methods, replace HOSTNAME with either the remote server host name or the IP address to be used
to connect to that server; for example, srv1.mycompany.com or 32.53.2.87.
VMware vRealize Operations for Published Applications Installation and Administration
30 VMware, Inc.