User guide

User Guide NetXtreme II
September 2013
Broadcom Corporation
Document INGSRVT78-CDUM100-R Detailed Procedures Page 115
Perform HTTP Configuration on the Server
To use the BACS GUI, you must configure the HTTP protocol, as follows:
NOTE: The default HTTP port is 5985 for WinRM 2.0.
1. Click Start (or press the Windows logo key) and select Run.
2. Enter gpedit.msc to open the local Group Policy editor.
3. Under Computer Configuration, open the Administrative Templates folder and then open the Windows
Components folder.
4. Select Windows Remote Management (WinRM).
5. Under Windows Remote Management (WinRM), select WinRm Client.
6. Under WinRM Client, double-click Trusted Hosts.
7. In the TrustedHostsList, enter the host names of the clients. If all clients are trusted then enter an asterisk (*) only.
8. Select WinRM Service.
9. Enable Allow Basic Authentication.
10. Enable Allow unencrypted traffic.
11. Close the Group Policy wIndow.
12. From the command prompt, run the following command to configure WinRM with default settings:
winrm qc or winrm quickconfig
13. When the tool displaysMake these changes[y/n]?“, enter “y”.
14. Enter one of the following commands to check whether an HTTP listener is created:
winrm enumerate winrm/confg/listener
or
winrm e winrm/config/Listener
15. Enter the following command from the command prompt to test locally.
winrm id
Perform HTTPS Configuration on the Server (to use HTTPS rather than HTTP)
This step consists of two distinct processes: generating a self-signed certificate, if certificate does not exist, and importing it
to a Windows server. If one does not already exist, you must configure a self-signed certificate on the Windows server to
enable HTTPS/SSL communication with the BACS GUI on the Windows or Linux client. The Windows and Linux client also
must be configured with the self-signed certificate. See Perform HTTPS Configuration (if you plan to use HTTPS) to
configure Windows and Configure HTTPS on Linux Client to configure Linux client.
NOTE: The self-signed certificate can be created on any Windows or Linux server. The server does not require
BACS to be installed. The self-signed certificate generated on any Windows/Linux server should be copied on the
local drive of client.
1. Click Start (or press the Windows logo key) and select Run.
2. Enter gpedit.msc to open the local Group Policy editor.
3. Under Computer Configuration, open the Administrative Templates folder and then open the Windows
Components folder.