> For the complete documentation index, see [llms.txt](https://docs.infraon.io/infinity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infraon.io/infinity/user-guide/infraon-configuration/it-operations/discovery/windows-servers.md).

# Windows Servers

The Windows Servers page allows you to configure and initiate discovery of Windows servers using the WMI protocol. It enables you to discover Windows server inventory and configure availability and performance monitoring based on the selected discovery option.

The selected Data Collector connects to the target Windows server using the configured WMI device credentials. After successful authentication and WMI communication, the Data Collector retrieves information such as the server's operating system, hardware, network, and other inventory details, then sends the collected data to Infraon. Based on the selected discovery option, you can also configure the server for availability and performance monitoring.

## Initiate Windows Servers

There are three tabs on the Windows Servers page:

Discovery Details | Filters | Schedule&#x20;

### Discovery Details

The Discovery Details section provides the discovery profile, device information, credentials, agent details, and data collector details settings.

Discovery Details | **Profile and Discovery Information**

<table data-header-hidden><thead><tr><th width="140" valign="top"></th><th width="171.22222900390625" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top">Label</td><td valign="top">Action</td><td valign="top">Description / Example</td></tr><tr><td valign="top">Profile Name*</td><td valign="top">Enter a name</td><td valign="top">Enter a name for the Discovery Profile. Discovery Profiles are used to save discovery preferences and identify profiles for tracking and periodic discovery.</td></tr><tr><td valign="top">Data Collector Details</td><td valign="top">Configure details</td><td valign="top"><p>Select the Data Collector to be used for the Windows Servers discovery process.</p><p></p><p>The Data Collector is installed within the customer's network and communicates with the target environment using the configured protocols and credentials.</p><p>It collects the required inventory, availability, and performance information and sends the data to Infraon for monitoring.</p></td></tr><tr><td valign="top">Discovery Options</td><td valign="top">Select an option</td><td valign="top"><ol><li>Discover inventory with availability and performance monitoring. </li><li>Discover only Inventory Information.</li><li>Discover inventory with availability and performance monitoring.</li></ol></td></tr><tr><td valign="top">Discover only Inventory Information</td><td valign="top">Select an option</td><td valign="top">Discovers and collects basic inventory information about the selected devices or resources, such as device details, configuration, and hardware/software information. Availability and performance monitoring are not enabled.</td></tr><tr><td valign="top">Discover inventory with availability monitoring</td><td valign="top">Select an option</td><td valign="top">Discovers inventory information and enables availability monitoring to check whether the device or resource is reachable and operational.</td></tr><tr><td valign="top">Discover inventory with availability and performance monitoring</td><td valign="top">Select an option</td><td valign="top">Discovers inventory information and enables both availability and performance monitoring. IMS checks device availability and collects performance metrics for ongoing monitoring.</td></tr><tr><td valign="top">Provide Profile Details</td><td valign="top">Enter details</td><td valign="top"><p>Add a brief description of the discovery profile and the Windows servers to be discovered.</p><p></p><p><strong>Example</strong>: Windows Production Servers.</p></td></tr><tr><td valign="top">IP Address*</td><td valign="top">Enter IP details</td><td valign="top">Enter an IP address, IP range, or subnet to be discovered.</td></tr><tr><td valign="top">Import from CSV</td><td valign="top">Import a file</td><td valign="top">Import a device list from a CSV file instead of manually entering the IP address, IP range, or subnet. This option is optional.</td></tr><tr><td valign="top">Device Credentials</td><td valign="top">Select a credential</td><td valign="top"><p>Create device credentials before discovering Windows Servers.</p><p> </p><p>Select a WMI credential containing the authentication and connection details required to communicate with the Windows server.</p><p> </p><p>The selected credential allows IMS to establish connectivity and collect server inventory, availability, and performance information.</p></td></tr></tbody></table>

{% hint style="info" %}
Note: Import from CSV and Device Credentials are optional. Fields marked with an asterisk (\*) are mandatory.
{% endhint %}

Click **Next** to configure **Filters**.

### Filters

The Filters section allows you to control which Windows servers are included or excluded from discovery and select the server components to be monitored.

The Filters section contains three areas:

* Default Filters
* Device Filters
* Server Component Filters

Filters | **Default Filters**

<table data-header-hidden><thead><tr><th width="133.77783203125" valign="top"></th><th width="170.66668701171875" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description / Example</strong></td></tr><tr><td valign="top">Filter By Ping</td><td valign="top">Enable or disable</td><td valign="top">Filters Windows servers based on their response to a ping check.</td></tr><tr><td valign="top">Ping Monitor</td><td valign="top">Enable or disable</td><td valign="top">Enables ping monitoring to check whether the Windows server is reachable.</td></tr></tbody></table>

&#x20;Filters | **Device Filters**

<table data-header-hidden><thead><tr><th width="119.5555419921875" valign="top"></th><th width="187.4444580078125" valign="top"></th><th valign="top"></th></tr></thead><tbody><tr><td valign="top"><strong>Label</strong></td><td valign="top"><strong>Action</strong></td><td valign="top"><strong>Description / Example</strong></td></tr><tr><td valign="top">Device Filters</td><td valign="top">Select a condition</td><td valign="top">Configure conditions to include or exclude specific Windows servers from discovery.</td></tr><tr><td valign="top">Include Devices / Exclude Devices</td><td valign="top">Select an option</td><td valign="top">Specify whether matching devices should be included in or excluded from discovery.</td></tr><tr><td valign="top">Equals / Contains</td><td valign="top">Select an operator</td><td valign="top">Select the operator used to match the specified value.</td></tr><tr><td valign="top">Number or Device Name</td><td valign="top">Enter a value</td><td valign="top">Enter the value used to identify the Windows servers.</td></tr></tbody></table>

The filter condition follows:

Include Devices / Exclude Devices **→ IP Address / Device Type / Device Name → Equals / Contains → Number or Device Name**

You can add additional filter conditions as required.

Filters | **Server Component Filters**

<table data-header-hidden><thead><tr><th width="95.5555419921875"></th><th width="233.22222900390625"></th><th></th></tr></thead><tbody><tr><td><strong>Label</strong></td><td><strong>Action</strong></td><td><strong>Description / Example</strong></td></tr><tr><td>Process</td><td>Enable or disable Process monitoring</td><td>Monitors running processes on the server and provides information about their status and activity.</td></tr><tr><td>Service</td><td>Enable or disable Service monitoring</td><td>Tracks server services and provides visibility into their operational status.</td></tr><tr><td>SQL</td><td>Enable or disable SQL Core Monitoring</td><td>Provides monitoring information for SQL database components and their performance.</td></tr><tr><td>DotNet</td><td>Enable or disable DotNet Core Monitoring</td><td>Provides monitoring information for .NET components and their runtime status.</td></tr><tr><td>Exchange</td><td>Enable or disable Exchange Core Monitoring</td><td>Provides visibility into Microsoft Exchange components and their availability.</td></tr><tr><td>SharePoint</td><td>Enable or disable SharePoint Core Monitoring</td><td>Provides monitoring information about SharePoint components and their operational status.</td></tr><tr><td>Active Directory</td><td>Enable or disable Active Directory Monitoring</td><td>Provides visibility into Active Directory services and directory-related activities.</td></tr><tr><td>IIS</td><td>Enable or disable IIS Monitoring</td><td>Provides monitoring information about Internet Information Services (IIS) and hosted web applications.</td></tr></tbody></table>

{% hint style="info" %}
Note: The Filters tab is optional. You can click Next without configuring Device Filters or Server Component Filters.
{% endhint %}

Click **Next** to configure the Schedule.

<figure><img src="https://2706319170-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHOkWBaqDGJVTArkIQTsj%2Fuploads%2FxlMTA8TFMH2cOAPhsYyj%2Fimage.png?alt=media&amp;token=e7e97fea-3fb6-493c-b873-24aa18dc2f76" alt=""><figcaption></figcaption></figure>

### Schedule

The Schedule section determines when the Windows Server Discovery should be initiated. You can start the discovery immediately using Discover Now or configure a Discovery Schedule to run it at a specified date and time. To learn more, [click here](broken://pages/i6SE7zM6h63y3lyABGzq#schedule).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.infraon.io/infinity/user-guide/infraon-configuration/it-operations/discovery/windows-servers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
