Configure Server Monitoring Using WinRM
Table of Contents
Expand All
|
Collapse All
Next-Generation Firewall Docs
-
PAN-OS 9.1 (EoL)
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- Cloud Management of NGFWs
-
- Management Interfaces
-
- Launch the Web Interface
- Configure Banners, Message of the Day, and Logos
- Use the Administrator Login Activity Indicators to Detect Account Misuse
- Manage and Monitor Administrative Tasks
- Commit, Validate, and Preview Firewall Configuration Changes
- Export Configuration Table Data
- Use Global Find to Search the Firewall or Panorama Management Server
- Manage Locks for Restricting Configuration Changes
-
-
- Define Access to the Web Interface Tabs
- Provide Granular Access to the Monitor Tab
- Provide Granular Access to the Policy Tab
- Provide Granular Access to the Objects Tab
- Provide Granular Access to the Network Tab
- Provide Granular Access to the Device Tab
- Define User Privacy Settings in the Admin Role Profile
- Restrict Administrator Access to Commit and Validate Functions
- Provide Granular Access to Global Settings
- Provide Granular Access to the Panorama Tab
- Panorama Web Interface Access Privileges
-
- Reset the Firewall to Factory Default Settings
-
- Plan Your Authentication Deployment
- Configure SAML Authentication
- Configure Kerberos Single Sign-On
- Configure Kerberos Server Authentication
- Configure TACACS+ Authentication
- Configure RADIUS Authentication
- Configure LDAP Authentication
- Configure Local Database Authentication
- Configure an Authentication Profile and Sequence
- Test Authentication Server Connectivity
- Troubleshoot Authentication Issues
-
- Keys and Certificates
- Default Trusted Certificate Authorities (CAs)
- Certificate Deployment
- Configure the Master Key
- Export a Certificate and Private Key
- Configure a Certificate Profile
- Configure an SSL/TLS Service Profile
- Replace the Certificate for Inbound Management Traffic
- Configure the Key Size for SSL Forward Proxy Server Certificates
-
- HA Overview
-
- Prerequisites for Active/Active HA
- Configure Active/Active HA
-
- Use Case: Configure Active/Active HA with Route-Based Redundancy
- Use Case: Configure Active/Active HA with Floating IP Addresses
- Use Case: Configure Active/Active HA with ARP Load-Sharing
- Use Case: Configure Active/Active HA with Floating IP Address Bound to Active-Primary Firewall
- Use Case: Configure Active/Active HA with Source DIPP NAT Using Floating IP Addresses
- Use Case: Configure Separate Source NAT IP Address Pools for Active/Active HA Firewalls
- Use Case: Configure Active/Active HA for ARP Load-Sharing with Destination NAT
- Use Case: Configure Active/Active HA for ARP Load-Sharing with Destination NAT in Layer 3
- Refresh HA1 SSH Keys and Configure Key Options
- HA Firewall States
- Reference: HA Synchronization
-
- Use the Dashboard
- Monitor Applications and Threats
- Monitor Block List
-
- Report Types
- View Reports
- Configure the Expiration Period and Run Time for Reports
- Disable Predefined Reports
- Custom Reports
- Generate Custom Reports
- Generate the SaaS Application Usage Report
- Manage PDF Summary Reports
- Generate User/Group Activity Reports
- Manage Report Groups
- Schedule Reports for Email Delivery
- Manage Report Storage Capacity
- View Policy Rule Usage
- Use External Services for Monitoring
- Configure Log Forwarding
- Configure Email Alerts
-
- Configure Syslog Monitoring
-
- Traffic Log Fields
- Threat Log Fields
- URL Filtering Log Fields
- Data Filtering Log Fields
- HIP Match Log Fields
- IP-Tag Log Fields
- User-ID Log Fields
- Tunnel Inspection Log Fields
- SCTP Log Fields
- Authentication Log Fields
- Config Log Fields
- System Log Fields
- Correlated Events Log Fields
- GTP Log Fields
- Syslog Severity
- Custom Log/Event Format
- Escape Sequences
- Forward Logs to an HTTP/S Destination
- Firewall Interface Identifiers in SNMP Managers and NetFlow Collectors
-
- User-ID Overview
- Enable User-ID
- Map Users to Groups
- Enable User- and Group-Based Policy
- Enable Policy for Users with Multiple Accounts
- Verify the User-ID Configuration
-
- App-ID Overview
- App-ID and HTTP/2 Inspection
- Manage Custom or Unknown Applications
-
- Apply Tags to an Application Filter
- Create Custom Application Tags
- Workflow to Best Incorporate New and Modified App-IDs
- See the New and Modified App-IDs in a Content Release
- See How New and Modified App-IDs Impact Your Security Policy
- Ensure Critical New App-IDs are Allowed
- Monitor New App-IDs
- Disable and Enable App-IDs
- Safely Enable Applications on Default Ports
- Applications with Implicit Support
- Application Level Gateways
- Disable the SIP Application-level Gateway (ALG)
- Maintain Custom Timeouts for Data Center Applications
-
- Best Practices for Securing Your Network from Layer 4 and Layer 7 Evasions
- Set Up Antivirus, Anti-Spyware, and Vulnerability Protection
- Set Up File Blocking
- Prevent Brute Force Attacks
- Customize the Action and Trigger Conditions for a Brute Force Signature
- Enable Evasion Signatures
- Monitor Blocked IP Addresses
- Threat Signature Categories
- Create Threat Exceptions
- Custom Signatures
- Threat Prevention Resources
-
- Decryption Overview
-
- Keys and Certificates for Decryption Policies
- SSL Forward Proxy
- SSL Forward Proxy Decryption Profile
- SSL Inbound Inspection
- SSL Inbound Inspection Decryption Profile
- SSL Protocol Settings Decryption Profile
- SSH Proxy
- SSH Proxy Decryption Profile
- Decryption Profile for No Decryption
- SSL Decryption for Elliptical Curve Cryptography (ECC) Certificates
- Perfect Forward Secrecy (PFS) Support for SSL Decryption
- SSL Decryption and Subject Alternative Names (SANs)
- High Availability Support for Decrypted Sessions
- Decryption Mirroring
- Configure SSL Forward Proxy
- Configure SSL Inbound Inspection
- Configure SSH Proxy
- Configure Server Certificate Verification for Undecrypted Traffic
- Enable Users to Opt Out of SSL Decryption
- Temporarily Disable SSL Decryption
- Configure Decryption Port Mirroring
- Verify Decryption
-
- How Decryption Broker Works
- Layer 3 Security Chain Guidelines
- Configure Decryption Broker with One or More Layer 3 Security Chain
- Transparent Bridge Security Chain Guidelines
- Configure Decryption Broker with a Single Transparent Bridge Security Chain
- Configure Decryption Broker with Multiple Transparent Bridge Security Chains
- Activate Free Licenses for Decryption Features
-
- About Palo Alto Networks URL Filtering Solution
- How Advanced URL Filtering Works
- URL Filtering Use Cases
- Plan Your URL Filtering Deployment
- URL Filtering Best Practices
- Activate The Advanced URL Filtering Subscription
- Configure URL Filtering
- Test URL Filtering Configuration
- Log Only the Page a User Visits
- Create a Custom URL Category
- URL Category Exceptions
- Use an External Dynamic List in a URL Filtering Profile
- Allow Password Access to Certain Sites
- URL Filtering Response Pages
- Customize the URL Filtering Response Pages
- HTTP Header Logging
- Request to Change the Category for a URL
-
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure an Aggregate Interface Group
- Use Interface Management Profiles to Restrict Access
- Virtual Routers
- Service Routes
- RIP
- Route Redistribution
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
- Dynamic DNS Overview
- Configure Dynamic DNS for Firewall Interfaces
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
-
- Policy Types
- Policy Objects
- Track Rules Within a Rulebase
- Enforce Policy Rule Description, Tag, and Audit Comment
- Move or Clone a Policy Rule or Object to a Different Virtual System
-
- External Dynamic List
- Built-in External Dynamic Lists
- Configure the Firewall to Access an External Dynamic List
- Retrieve an External Dynamic List from the Web Server
- View External Dynamic List Entries
- Exclude Entries from an External Dynamic List
- Enforce Policy on an External Dynamic List
- Find External Dynamic Lists That Failed Authentication
- Disable Authentication for an External Dynamic List
- Register IP Addresses and Tags Dynamically
- Use Dynamic User Groups in Policy
- Use Auto-Tagging to Automate Security Actions
- CLI Commands for Dynamic IP Addresses and Tags
- Application Override Policy
- Test Policy Rules
-
PAN-OS 11.1 & Later
- PAN-OS 11.1 & Later
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
-
- Tap Interfaces
-
- Layer 2 and Layer 3 Packets over a Virtual Wire
- Port Speeds of Virtual Wire Interfaces
- LLDP over a Virtual Wire
- Aggregated Interfaces for a Virtual Wire
- Virtual Wire Support of High Availability
- Zone Protection for a Virtual Wire Interface
- VLAN-Tagged Traffic
- Virtual Wire Subinterfaces
- Configure Virtual Wires
- Configure a PPPoE Client on a Subinterface
- Configure an IPv6 PPPoE Client
- Configure an Aggregate Interface Group
- Configure Bonjour Reflector for Network Segmentation
- Use Interface Management Profiles to Restrict Access
-
- DHCP Overview
- Firewall as a DHCP Server and Client
- Firewall as a DHCPv6 Client
- DHCP Messages
- Dynamic IPv6 Addressing on the Management Interface
- Configure an Interface as a DHCP Server
- Configure an Interface as a DHCPv4 Client
- Configure an Interface as a DHCPv6 Client with Prefix Delegation
- Configure the Management Interface as a DHCP Client
- Configure the Management Interface for Dynamic IPv6 Address Assignment
- Configure an Interface as a DHCP Relay Agent
-
- DNS Overview
- DNS Proxy Object
- DNS Server Profile
- Multi-Tenant DNS Deployments
- Configure a DNS Proxy Object
- Configure a DNS Server Profile
- Use Case 1: Firewall Requires DNS Resolution
- Use Case 2: ISP Tenant Uses DNS Proxy to Handle DNS Resolution for Security Policies, Reporting, and Services within its Virtual System
- Use Case 3: Firewall Acts as DNS Proxy Between Client and Server
- DNS Proxy Rule and FQDN Matching
-
- NAT Rule Capacities
- Dynamic IP and Port NAT Oversubscription
- Dataplane NAT Memory Statistics
-
- Translate Internal Client IP Addresses to Your Public IP Address (Source DIPP NAT)
- Create a Source NAT Rule with Persistent DIPP
- PAN-OS
- Strata Cloud Manager
- Enable Clients on the Internal Network to Access your Public Servers (Destination U-Turn NAT)
- Enable Bi-Directional Address Translation for Your Public-Facing Servers (Static Source NAT)
- Configure Destination NAT with DNS Rewrite
- Configure Destination NAT Using Dynamic IP Addresses
- Modify the Oversubscription Rate for DIPP NAT
- Reserve Dynamic IP NAT Addresses
- Disable NAT for a Specific Host or Interface
-
- Network Packet Broker Overview
- How Network Packet Broker Works
- Prepare to Deploy Network Packet Broker
- Configure Transparent Bridge Security Chains
- Configure Routed Layer 3 Security Chains
- Network Packet Broker HA Support
- User Interface Changes for Network Packet Broker
- Limitations of Network Packet Broker
- Troubleshoot Network Packet Broker
-
- Enable Advanced Routing
- Logical Router Overview
- Configure a Logical Router
- Create a Static Route
- Configure BGP on an Advanced Routing Engine
- Create BGP Routing Profiles
- Create Filters for the Advanced Routing Engine
- Configure OSPFv2 on an Advanced Routing Engine
- Create OSPF Routing Profiles
- Configure OSPFv3 on an Advanced Routing Engine
- Create OSPFv3 Routing Profiles
- Configure RIPv2 on an Advanced Routing Engine
- Create RIPv2 Routing Profiles
- Create BFD Profiles
- Configure IPv4 Multicast
- Configure MSDP
- Create Multicast Routing Profiles
- Create an IPv4 MRoute
-
-
PAN-OS 11.2
- PAN-OS 11.2
- PAN-OS 11.1
- PAN-OS 11.0 (EoL)
- PAN-OS 10.2
- PAN-OS 10.1
- PAN-OS 10.0 (EoL)
- PAN-OS 9.1 (EoL)
- PAN-OS 9.0 (EoL)
- PAN-OS 8.1 (EoL)
- Cloud Management and AIOps for NGFW
End-of-Life (EoL)
Configure Server Monitoring Using WinRM
To map users to IP addresses based on login/logout events,
you can configure the PAN-OS integrated User-ID agent to monitor
servers using WinRM.
You can configure the PAN-OS
integrated User-ID agent to monitor servers using Windows
Remote Management (WinRM). Using the WinRM protocol improves speed,
efficiency, and security when monitoring server events to map user
events to IP addresses. The PAN-OS integrated User-ID agent supports the
WinRM protocol on Windows Server 2008 Active Directory and Microsoft
Exchange Server 2008 or later versions of both.
There are
three ways to configure server monitoring using WinRM:
- Configure WinRM over HTTPS with Basic Authentication—The firewall authenticates to the monitored server using the username and password of the service account for the User-ID agent and the firewall authenticates the monitored server using the User-ID certificate profile.
- Configure WinRM over HTTP with Kerberos—The firewall and the monitored servers use Kerberos for mutual authentication and the monitored server encrypts the communication with the firewall using a negotiated Kerberos session key.
- Configure WinRM over HTTPS with Kerberos—The firewall and the monitored server use HTTPS to communicate and use Kerberos for mutual authentication.
Configure WinRM over HTTPS with Basic Authentication
When you configure WinRM to use HTTPS with
basic authentication, the firewall transfers the credentials for
the service account in a secure tunnel using SSL.
- Configure the service account with Remote Management User and CIMV2 privileges for the server you want to monitor.
- 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.
- 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).
- Open the certificate and select GeneralDetailsShow: <All>.
- Select the Thumbprint and copy it.
- To enable the firewall to connect to the Windows server using WinRM, enter the following command: winrm quickconfig.
- 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.
- 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.
- 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.
- From the Windows server command prompt, enter the
following command:
c:\> winrm set winrm/config/client/auth @{Basic="true"}
- Enter the following command: winrm get winrm/config/service/Auth and confirm that Basic = true.
- Verify the certificate is installed in the
Local Computer certificate store (Certificates
(Local Computer)PersonalCertificates).
- Enable Basic Authentication between the PAN-OS integrated
User-ID agent and the monitored servers.
- Select DeviceUser IdentificationUser MappingPalo Alto Networks User-ID Agent SetupServer Monitor Account.
- In domain\username format, enter the User Name for the service account that the User-ID agent will use to monitor servers.
- Enter the Domain’s DNS Name of the server monitor account.
- Enter the Password and Confirm
Password for the service account.
- Click OK
- Configure server monitoring for the PAN-OS integrated
User-ID agent.
- Select the Microsoft server Type (Microsoft Active Directory or Microsoft Exchange).
- 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.
- Enter the IP address or FQDN Network Address of
the server.
- 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.
- Select DeviceUser IdentificationConnection Security.
- Click Edit.
- Select the Windows server certificate to use for the User-ID
Certificate Profile.
- Click OK.
- Commit your changes.
- Verify that the status of each monitored server is Connected (DeviceUser IdentificationUser Mapping).
Configure WinRM over HTTP with Kerberos
When you configure WinRM over HTTP with Kerberos,
the firewall and the monitored servers use Kerberos for mutual authentication
and the monitored server encrypts the communication with the firewall
using a negotiated Kerberos session key.
- Configure the service account with Remote Management User and CIMV2 privileges for the server you want to monitor.
- Confirm that WinRM is enabled on the Windows server you
are monitoring.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.
- To enable the firewall to connect to the Windows server using WinRM, enter the following command: winrm quickconfig.
- 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.
- To verify that WinRM is communicating using HTTP,
enter the following command: winrm enumerate winrm/config/listener and
confirm that the output displays Transport = HTTP.By default, WinRM/HTTP uses port 5985.
- Enter the following command: winrm get winrm/config/service/Auth and confirm that Kerberos = true.
- Enable the PAN-OS integrated User-ID agent and the monitored
servers to authenticate using Kerberos.
- If you did not do so during the initial configuration, configure date and time (NTP) settings to ensure successful Kerberos negotiation.
- Configure a Kerberos server profile on the firewall to authenticate with the server to monitor the security logs and session information.
- Select DeviceUser IdentificationUser MappingPalo Alto Networks User-ID Agent SetupServer Monitor Account.
- In domain\username format, enter the User Name for the service account that the User-ID agent will use to monitor servers.
- Enter the Domain’s DNS Name of
the server monitor account.Kerberos uses the domain name to locate the service account.
- Enter the Password and Confirm Password for the service account.
- Select the Kerberos Server Profile you
configured in Step 3.2.
- Click OK.
- Configure server monitoring for the PAN-OS integrated
User-ID agent.
- Configure the Microsoft server type (Microsoft Active Directory or Microsoft Exchange).
- Select WinRM-HTTP as the Transport Protocol to use Windows Remote Management (WinRM) over HTTP to monitor the server security logs and session information.
- Enter the FQDN Network Address of
the server.If you are using Kerberos, the network address must be a fully qualified domain name (FDQN).
- Commit your changes.
- Verify that the status of each monitored server is Connected (DeviceUser IdentificationUser Mapping).
Configure WinRM over HTTPS with Kerberos
- Configure the service account with Remote Management User and CIMV2 privileges for the server you want to monitor.
- 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.
- 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).
- Open the certificate and select GeneralDetailsShow: <All>.
- Select the Thumbprint and copy it.
- To enable the firewall to connect to the Windows server using WinRM, enter the following command: winrm quickconfig.
- 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.
- To verify that WinRM is communicating using HTTPS,
enter the following command: winrm enumerate winrm/config/listener.
Then confirm that the output displays Transport = HTTPS.By default, WinRM/HTTPS uses 5986.
- 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.
- Enter the following command: winrm get winrm/config/service/Auth and confirm that Basic = false and Kerberos= true.
- Verify the certificate is installed in the
Local Computer certificate store (Certificates
(Local Computer)PersonalCertificates).
- Enable the PAN-OS integrated User-ID agent and the monitored
servers to authenticate using Kerberos.
- If you did not do so during the initial configuration, configure date and time (NTP) settings to ensure successful Kerberos negotiation.
- Configure a Kerberos server profile on the firewall to authenticate with the server to monitor the security logs and session information.
- Select DeviceUser IdentificationUser MappingPalo Alto Networks User-ID Agent SetupServer Monitor Account.
- In domain\username format, enter the User Name for the service account that the User-ID agent will use to monitor servers.
- Enter the Domain’s DNS Name of
the server monitor account.Kerberos uses the domain name to locate the service account.
- Enter the Password and Confirm Password for the service account.
- Select the Kerberos Server Profile you
created in Step 3.2.
- Click OK.
- Configure server monitoring for the PAN-OS integrated
User-ID agent.
- Configure the Microsoft server type (Microsoft Active Directory or Microsoft Exchange).
- 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.
- Enter the FQDN Network Address of
the server.If you are using Kerberos, the network address must be a fully qualified domain name (FDQN).
- 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.The firewall uses the same certificate to authenticate with all monitored servers.
- Select DeviceUser IdentificationConnection Security.
- Click Edit.
- Select the Windows server certificate to use for the User-ID
Certificate Profile.
- Click OK.
- Commit your changes.
- Verify that the status of each monitored server is Connected (DeviceUser IdentificationUser Mapping).