Configure WinRM over HTTPS with Basic Authentication

1. Configure the service account with Remote Management User and CIMV2 privileges for the server you want to monitor.
2. On the Windows server you are monitoring, obtain the thumbprint from the certificate for the Windows server to use with WinRM and enable WinRM.

   Ensure that you use an account with administrator privileges to configure WinRM on the server you want to monitor. As a best practice for security, this account should not be the same account as the service account in Step 1.

   1. Verify the certificate is installed in the Local Computer certificate store (Certificates (Local Computer)PersonalCertificates).

      If you do not see the Local Computer certificate store, launch the Microsoft Management Console (StartRunMMC) and add the Certificates snap-in (FileAdd/Remove Snap-inCertificatesAddComputer accountNextFinish).
   2. Open the certificate and select GeneralDetailsShow: <All>.
   3. Select the Thumbprint and copy it.
   4. To enable the firewall to connect to the Windows server using WinRM, enter the following command: winrm quickconfig.
   5. Enter y to confirm the changes and then confirm the output displays WinRM service started.

      If WinRM is enabled, the output displays WinRM service is already running on this machine. You will be prompted to confirm any additional required configuration changes.
   6. To verify that WinRM is communicating using HTTPS, enter the following command: winrm enumerate winrm/config/listener and confirm that the output displays Transport = HTTPS.

      By default, WinRM/HTTPS uses port 5986.
   7. From the Windows server command prompt, enter the following command: winrm create winrm/config/Listener?Address=*+Transport=HTTPS @{Hostname=”<hostname>";CertificateThumbprint=”Certificate Thumbprint"}, where hostname is the hostname of the Windows server and Certificate Thumbprint is the value you copied from the certificate.

      Use the command prompt (not Powershell) and remove any spaces in the Certificate Thumbprint to ensure that WinRM can validate the certificate.
   8. From the Windows server command prompt, enter the following command:

      c:\> winrm set winrm/config/client/auth @{Basic="true"}

   9. Enter the following command: winrm get winrm/config/service/Auth and confirm that Basic = true.
3. Enable Basic Authentication between the PAN-OS integrated User-ID agent and the monitored servers.

   1. Select DeviceUser IdentificationUser MappingPalo Alto Networks User-ID Agent SetupServer Monitor Account.
   2. In domain\username format, enter the User Name for the service account that the User-ID agent will use to monitor servers.
   3. Enter the Domain’s DNS Name of the server monitor account.

   4. Enter the Password and Confirm Password for the service account.
   5. Click OK
4. Configure server monitoring for the PAN-OS integrated User-ID agent.

   1. Select the Microsoft server Type (Microsoft Active Directory or Microsoft Exchange).
   2. Select Win-RM-HTTPS as the Transport Protocol to use Windows Remote Management (WinRM) over HTTPS to monitor the server security logs and session information.

   3. Enter the IP address or FQDN Network Address of the server.
5. To enable the PAN-OS integrated User-ID agent to communicate with the monitored servers using WinRM-HTTPS, verify that you successfully imported the root certificate for the service certificates that the Windows server uses for WinRM on to the firewall and associate the certificate with the User-ID Certificate Profile.

   1. Select DeviceUser IdentificationConnection Security.
   2. Click Edit.
   3. Select the Windows server certificate to use for the User-ID Certificate Profile.

   4. Click OK.
6. Commit your changes.
7. Verify that the status of each monitored server is Connected (DeviceUser IdentificationUser Mapping).