---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama 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: Yokohama
* 
* Updated January 30, 2025
* 
* ![](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 |
   [Table 1. Additional WinRM parameters]

   {#t_EnableDeviceClassWinRemoteMgmt__table_yy2_hxt_st}

## What to do next

Run a discovery from the [Discovery schedule](https://servicenow-prod.fluidtopics.net/CIQEq9XeYjrEAd3sKWHEVg "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