---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/australia/it-operations-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Use Windows Remote Management for classification

# Use Windows Remote Management for classification {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
You can configure the discovery of Windows hosts using the Windows Remote Management
(WinRM) protocol.

## Before you begin

* Install and configure a Windows MID Server on the local network.
* WinRM service must be enabled on all discoverable Windows hosts.
{#t_EnableDeviceClassWinRemoteMgmt__ul_lpt_wwt_st}

Roles required: discovery_admin, agent_admin, admin

## About this task

By default, the system uses the WMI protocol for device classification of Windows hosts. Administrators can instead use the WinRM protocol for more efficient lightweight data transfer and remote command execution.

## Procedure

1. Enable the WinRM service on all Windows hosts you want to discover.
2. Navigate to DiscoveryMID Servers.
3. Select the MID Server you will use for discovery of Windows hosts.  
   The system displays the MID Server record.
4. From the Configuration Parameters related list click New.  
   The system displays a MID Server Configuration Parameter record.
5. In the Parameter name field, select the mid.windows.management_protocol parameter from the choice list.
6. Enter a value of WinRM.  
   Figure 1. MID Server configuration parameter
7. Click Submit.  
   The system displays the MID Server record.
8. **Optional:** Add other Windows Remote Management protocol parameters as needed.  
   {#t_EnableDeviceClassWinRemoteMgmt__table_yy2_hxt_st__entry__4}

   | Parameter | Description | Default | Requires MID Server restart |
   |-|-|-|-|
   | mid.powershell_api.winrm.remote_port | Specifies the communications port the MID Server uses to communicate with the WinRM protocol. | 5985 | No |
   | mid.powershell_api.session_pool.target.max_size | Specifies the maximum number of sessions allowed in the pool per target host. | 2 | Yes |
   | mid.powershell_api.session_pool.max_size | Specifies the maximum number of sessions allowed in the session pool. | 25 | Yes |
   | mid.powershell_api.idle_session_timeout | Specifies the timeout value of idle Powershell sessions in seconds. | 60 | Yes |
   | mid.powershell_api.winrm.additional_pssesion_options | Specifies additional WinRM PSSession options the MID Server applies when creating a session. | None |   |
   | mid.powershell_api.winrm.always_taskkill | Specifies whether the MID Server always sends a TaskKill command to close the PowerShell process. Enable only when unexpected PowerShell processes remain when used with WinRM. | false |   |
   | mid.powershell_api.winrm.remote_https_port | Specifies the HTTPS port that WinRM uses to connect to remote hosts. | 5986 |   |
   | mid.powershell_api.winrm.skip_ssl_cert_check | Specifies whether the MID Server skips the SSL certificate check with WinRM. | false |   |
   | mid.powershell_api.winrm.skip_ssl_cert_check_options | Specifies the options used to skip the SSL certificate check with WinRM. | `-SkipCACheck -SkipCNCheck -SkipRevocationCheck` |   |
   | mid.powershell_api.winrm.use_reverse_dns_lookup | Specifies whether the MID Server uses the FQDN when the IP address is not in the list of TrustedHosts for WinRM. | true |   |
   | mid.powershell_api.winrm.use_ssl | Specifies whether the MID Server uses SSL with WinRM. | false |   |
   | mid.powershell_api.winrm.working_mode | Specifies the WinRM working mode. Possible values: http, https. | http |   |
   [Table 1. Additional WinRM parameters]

   {#t_EnableDeviceClassWinRemoteMgmt__table_yy2_hxt_st}

## What to do next

Run a discovery from the [Discovery schedule](https://www.servicenow.com/docs/VO0owNull6HAfXGFWMKxhg#t_CreateADiscoverySchedule "A discovery schedule determines what horizontal discovery searches for, when it runs, and which MID Servers are used. Create a discovery schedule for your local environment or a schedule for discovering the resources in your cloud service account.") to find Windows machines on your network.

*[\>]: and then