6.5

Enabling HTTP or HTTPS Protocols
for PowerShell Remoting 6
This chapter describes how to enable either HTTP or HTTPS protocols for PowerShell remoting.
N Many users have PowerShell remoting already congured in the Citrix environment, with HTTP or
HTTPS protocols already enabled. If this is the case for you, you can skip this chapter.
This chapter includes the following topics:
n
“Enable HTTP Protocol for PowerShell Remoting,” on page 29
n
“Enable HTTPS Protocol for PowerShell Remoting,” on page 30
n
“Congure a Firewall,” on page 33
n
“Update the etc/host le for DNS Resolution,” on page 33
n
“Install the Certicate on the Client,” on page 33
n
“Test the Connection from the Client Machine,” on page 34
n
“Use makecert for SSL Certication,” on page 34
Enable HTTP Protocol for PowerShell Remoting
If you have not already enabled PowerShell Remoting and want to use the HTTP protocol, follow these
steps.
If you plan to use the HTTPS protocol instead, skip this section and see “Enable HTTPS Protocol for
PowerShell Remoting,” on page 30.
Procedure
u
To use HTTP for PowerShell remoting, run the following command on the host:
winrm quickconfig
Port 5985 is opened to listen to incoming connection. Sometimes, the connection from the remote PowerShell
does not work because of the following error:
Connecting to remote server failed with the following error message : The WinRM client cannot
process the request.
If the authentication scheme is dierent from Kerberos or if the client computer is not connected to a
domain, you must use HTTPS transport. Or, add the destination machine to the TrustedHosts conguration
seing.
VMware, Inc.
29