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


---

# Configure support for Windows servers with non-English OS

# Configure support for Windows servers with non-English OS {#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 your ServiceNow AI Platform to support Windows servers
that use non-English Windows operating system (OS).

## Before you begin

You can perform this procedure only on the MID Servers that serve locations using non-English operating system. Alternatively, you can perform this configuration on all MID Servers in one go, even MID Servers that are used for locations using English operating systems.

Role required: mid_server

## About this task

If your organization does not deploy Service Mapping, this
configuration is not necessary.

Sometimes organizations choose to use operating systems in local languages. While
having a localized operating system (OS) may be user-friendly, it poses a problem
when it comes to automatically discovering Windows servers running the localized OS.
During the discovery and mapping process Service Mapping sends discovery
commands to Windows servers on your infrastructure via a MID Server. If a Windows server
returns a message in a language other than English, Service Mapping does not
recognize it as a valid response and the interaction fails.

If your organization uses non-English operating system for some of the Windows
servers, you must perform this procedure to make sure that Service Mapping can access all
Windows servers, not exclusively Windows servers using the English operating system.
This configuration allows the MID Server, that is located
between Service Mapping and
Windows servers, to recognize a non-English response from a Windows server and to
change the language of the CI operating system into English.

This configuration affects only the user for which you perform this procedure.

## Procedure

1. Navigate to AllMID ServersProperties in the Modules pane.
2. Click New.
3. In the Name field, enter <kbd class="ph userinput">mid.servicewatch.wmi.mui</kbd>.
4. In the Value field, enter <kbd class="ph userinput">true</kbd>.
5. In the MID server field, select the server to which you want to apply this change.

   | Option | Action |
   | To apply the change to all MID Servers in your organization | Leave the MID Server field blank. |
   | To apply the change to a specific MID Server | Select the relevant MID Server from the list. |
   |-|-|

   {#t_ConfigureSupport4nonEnglishCIs__choicetable_qwg_1cl_ht}
6. Click Submit.
**Related tasks**   

* [Resolve pattern-related mapping errors](https://servicenow-prod.fluidtopics.net/VKXk_DDhJfEvbCyem_bCuA "You can troubleshoot mapping errors caused by patterns.")  
**Related topics**   

* [MID Server](https://www.servicenow.com/docs/access?context=mid-server-landing&version=yokohama&pubname=yokohama-servicenow-platform&ft:locale=en-US)

*[\>]: and then