---
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


---

# Reclassify a Windows Workstation machine as a server

# Reclassify a Windows Workstation machine as a server {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

By default, Discovery
automatically classifies computers using certain Windows operating systems as
workstations. However, you might want specific computers in your network that are acting as
servers to be classified by their function and not their operating system.

## Before you begin

Role required: none

## About this task

Use the following variables, preceded by cidata, to construct a reclassification condition. For example, to reclassify based on a machine's IP address, use cidata.ip_address.

* name
* dsn_domain
* os_domain
* ip_address
* serial_number
{#t_ReClassWinWorkstnAsSvr__ul_hnt_3t2_q4}

The following procedure reclassifies any Windows workstation operating
system (Windows Vista, XP, or
Windows 7) that is acting
as a server.

## Procedure

1. Navigate to AllDiscovery DefinitionCI ClassificationWindows.
2. Create a new classification record, such as Windows XP Server.
3. Select Windows Server `[cmdb_ci_win_server]` as the table.
4. Right-click in the header bar and select Save from the context menu.  
   The Classification Criteria and Triggers Probes Related Lists appear.
5. Configure the following Classification Criteria:  

   |-|-|
   | Name | Select a variable to use as the classification criteria from the list above. For example, to reclassify a machine by name, enter <kbd class="ph userinput">cidata.name</kbd>. This works for servers that have a uniform naming convention, such as SRV001, SRV002, etc., regardless of operating system. |
   | Operator | Select an operator for the classification condition. In networks containing servers named with a specific convention, you might select starts with or contains. |
   | Value | Enter the value for the condition. In our example of a network with a server naming convention, this value would be the root of that convention, such as SRV This condition will classify all computers as servers if their machine name is SRVXXX. |
   [ ]

   {#t_ReClassWinWorkstnAsSvr__simpletable_af1_1v2_q4}
6. Select the Triggers Probe related list and add the appropriate probes.
   1. Copy the list of probes from another Windows server classification, including the Condition scripts.
   2. Ensure that the Windows - Identity probe has a phase of Identification (the default is Exploration).  
      The completed form looks like this:
   {#t_ReClassWinWorkstnAsSvr__substeps_vgd_fw2_q4}

## 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 check the cmdb_ci_win_server table and related tables to see how data is populated in the CMDB.

*[\>]: and then