To collect session latency metrics and establish a MS SQL Server relationship, users must install a signed certificate and set up WinRM HTTPS on each VDA and DDC (XenDesktop Delivery Controller) as outlined in the following sub-topics.
Create a signed certificate for the system to be monitored
Note the following requirements for the certificate:
The certificate can be self-signed or signed by an authority.
If self-signed, VMware Aria Operations must be told to ignore SSL verification.
The certificate must include the private key for the system.
If creating the certificate manually, the PFX format (which includes both a certificate and private key) is required by Windows.
Install the certificate on the target system
Open mmc.
Add Snap-in Certificates:
Select File > Add Snap-in.
Select Certificates.
Select Computer Account.
Select Local computer.
Click OK.
Expand the certificates tree:
Select Personal/Certificates (or just Personal if /Certificates does not exist).
Right-click inside the directory and select:
All tasks > Import.
Locate your certificate, then click OK.
Install certificate authority certificate (Optional)
If the certificate installed above was signed by an authority, you will need to install a trusted authority certificate, provided by your authority.
Under the Certificates (Local Computer) snap-in, select Trusted Root Certificates/Certificates.
Right-click and select All tasks > Import to import a certificate.
Navigate to your certificate authority's provided certificate, then click OK.
Any system connecting to the target system with WinRM HTTPS will also need your root certificate authority’s certificate.
Enable WinRM
Launch the Command Prompt as an Administrator (NOTE: Do not use PowerShell).
Execute the following command:
winrm quickconfigImportant:This will enable HTTP listening by default (using port 5985). The HTTP listener can be removed later.
Find your certificate thumbprint:
Open the mmc snap-in and find your personal certificate.
Double-click the certificate. On the details tab, find Certificate Thumbprint.
Create the HTTPS listener:
Execute the following command:
winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname="<YOUR_DNS_NAME>"; CertificateThumbprint="<COPIED_CERTIFICATE_THUMBPRINT>"}Important:NOTE:
YOUR_DNS_NAMEmust match what the certificate specifies. The COPIED_CERTIFICATE_THUMBPRINT must match the thumbprint found in the previous step.
Verify that WinRM is using HTTPS:
Execute the following command:
winrm enumerate winrm/config/listenerImportant:The default port used is 5986 (HTTPS). The default HTTP port is 5985.
Delete HTTP listener (Optional):
Execute the following command:
winrm delete winrm/config/Listener?Address=*+Transport=HTTP
Reference: Commands to enable supported authentication mechanisms
Note the following commands can be used to enable the supported authentication mechanisms:
Basic
winrm set winrm/config/service/auth @{Basic="true"}
NTLM
winrm set winrm/config/service/auth @{Negotiate="true"}
Kerberos
winrm set winrm/config/service/auth @{Kerberos="true"}