Add WinRM Connection Credentials
You can set up a WinRM connection and then use it as a Deployment Type in an Environment's Service Infrastructure.
In this topic:
- Before You Begin
- Step 1: Set Up the WinRM Connection
- Step 2: Name
- Step 3: Auth Scheme
- Step 4: Domain
- Step 5: User Name
- Step 6: Select Encrypted Password
- Step 7: Use SSL
- Step 8: Skip Cert Check
- Step 9: WinRM Port
- Step 10: Update the Infrastructure Definition
Before You Begin
Step 1: Set Up the WinRM Connection
In Secrets Management, under Execution Credentials, click WinRM Connection.
The WinRM Connection Attributes dialog appears.
Step 2: Display Name
Name to identify the connection. You will use this name to identify this connection when setting up the Connection Attributes in the environment Service Infrastructure.
Step 3: Auth Scheme
Specifies the mechanism used to authenticate the credentials used in this connection. Select NTLM.
Step 4: Domain
The Active Directory domain name where the user account in the credentials is registered. This can be left blank when using a local user.
Step 5: User Name
The user account credentials for this connection. The user must belong to the same Active Directory domain as the Windows instances that this connection uses. These are the same user account credentials you would use to log into the VM using a remote connection such as Microsoft Remote Desktop.
In cases when Domain is blank (local user), you can put ./ before the user name. The ./ prefix is equivalent to
Step 6: Select Encrypted Password
Make sure you use a Harness Encrypted Text secret to save the password and refer it using this option. Either select an existing secret from the drop down list or create a new one by clicking + Create Encrypted Text.
For more information on creating Encrypted Text, see Harness Encrypted Text secret.
Step 7: Use SSL
Enables an HTTPS connection instead of an HTTP connection. SSL is recommended.
Step 8: Skip Cert Check
When connected over HTTPS (Use SSL in enabled), the client does not validate server certificate.
Step 9: WinRM Port
Specifies the network port on the remote computer to use.
To connect to a remote computer, the remote computer must be listening on the port that the connection uses. The default ports are 5985, which is the WinRM port for HTTP, and 5986, which is the WinRM port for HTTPS.
To determine what ports WinRM is listening on, use the command:
winrm e winrm/config/listener
Step 10: Update the Infrastructure Definition
In Infrastructure Definition, the Infrastructure Definition dialog will look like this: