Server CI population during cloud discovery

  • Release version: Yokohama
  • Updated May 14, 2026
  • 2 minutes to read
    • Summarize
    Summarized using AI
    This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.

    Summary of Server CI population during cloud discovery

    Cloud discovery in ServiceNow can now populate Server Configuration Items (CIs) such as Windows and Linux Servers directly during cloud discovery, without needing to run traditional IP-based discovery. This capability significantly reduces discovery time in large environments where only server records are required, bypassing the longer schedules that discover applications and other data.

    Show full answer Show less

    By default, cloud discovery creates only Virtual Machine (VM) Instance CIs. With Discovery and Service Mapping Patterns version 1.31.0 and later, Server CIs can be populated alongside VM Instances by enabling the snitompattern.clouddiscoverypopulateserverci system property. The default setting is none, meaning Server CIs are not created unless configured.

    Key Features

    • Server CI Types Supported: Windows Server CIs, Linux Server CIs, and VM Instance CIs.
    • Supported Patterns: Azure – Virtual Machine (LP) and Azure VM Instance – Uniform Scale Set.
    • Data Collected: Server name (based on VM state), unique object ID, CPU core count, CPU count, disk space, install and operational status, IP address, OS name and version, RAM, and serial number sourced from Azure VM properties.
    • CI Relationships: Servers are related to their virtual machine instances through virtualized by::virtualizes relationships.
    • CI References: Serial numbers are linked to their corresponding Server CIs for identification.
    • Important Note: Use either Server CI population during cloud discovery or IP-based discovery for the same VMs, but not both, to avoid conflicting attribute data.

    Practical Benefits for ServiceNow Customers

    • Faster Discovery: By avoiding IP-based discovery when only server CIs are needed, organizations save time, especially in large cloud environments.
    • Streamlined Data: Focused server CI creation reduces noise from unnecessary application discovery.
    • Configurability: Customers control Server CI creation via a system property, enabling flexible discovery strategies.
    • Improved Accuracy: Data collected is based on Azure VM properties ensuring accurate and consistent server records.

    Configuration Guidance

    To enable Server CI creation during cloud discovery:

    • Set the snitompattern.clouddiscoverypopulateserverci system property to windows, linux, or both depending on desired Server CI types.
    • Ensure you run only one discovery method (cloud discovery with server CI population or IP-based discovery) per VM to prevent attribute conflicts.

    This approach simplifies discovery setups where only server infrastructure visibility is required, optimizing discovery performance and data relevance.

    Cloud discovery can populate Server CIs without running IP-based discovery, reducing discovery time in large environments.

    Server CI cloud discovery overview

    By default, cloud discovery creates Virtual Machine (VM) Instance CIs only. To populate Server CIs, organizations run IP-based discovery, which triggers a separate schedule that discovers servers alongside applications and other data. In large environments, IP-based discovery schedules can take a significant amount of time. Some organizations require only server records from their cloud environment, without discovering application data.

    Starting with Discovery and Service Mapping Patterns version 1.31.0, cloud discovery can create Windows Server CIs, Linux Server CIs, or both alongside Virtual Machine Instance CIs, without running IP-based discovery. The sn_itom_pattern.cloud_discovery_populate_server_ci system property controls whether Server CIs are created. By default, the property is set to none and Server CIs aren't created. For more information, see Configure Server CI creation during cloud discovery.

    The following patterns support Server CI population during cloud discovery:
    • Azure – Virtual Machine (LP)
    • Azure VM Instance – Uniform Scale Set
    Note:
    Use either Server CI population during cloud discovery or IP-based discovery for the same VMs, but not both. Running both may result in conflicting attribute values.

    Data collected by Discovery during horizontal discovery

    Discovery populates the following data when running the Azure – Create Server CI pattern extension. Virtual Desktop Infrastructure (VDI) instances can't be distinguished from other VMs and are registered as Windows Server or Linux Server CIs.

    Table 1. Windows Server [cmdb_ci_win_server]/Linux Server [cmdb_ci_linux_server]
    Field Description
    Name [name] Hostname of the server. The name is sourced from one of the following options:
    • If the VM is running: the VM computer name
    • If the VM is stopped: the OS profile computer name
    • If the VM is stopped and the Server CI already exists in the CMDB: the existing name is retained
    Object ID [object_id] A unique identifier for the server, matching the Azure VM object ID.
    CPU Core Count [cpu_core_count] Number of CPU cores, derived from the VM size.
    CPU Count [cpu_count] Number of CPUs. Default value is 1.
    Disk Space (GB) [disk_space] Total storage capacity of all disks attached to the VM, in gigabytes (GB).
    Install Status [install_status] Install status of the server. Default value is Installed.
    IP Address [ip_address] IP address of the server, sourced from the primary VM network interface.
    Is Virtual [virtual] Indicates the server is a virtual machine. Default value is true.
    Operating System [os] Operating system name.
    Operational Status [operational_status] Operational status of the server. Default value is Operational.
    OS Version [os_version] Operating system version, if available.
    RAM (MB) [ram] Memory capacity in megabytes (MB), derived from the VM size.
    Serial Number [serial_number] Unique identifier for the server, sourced from the Azure VM ID.
    Table 2. Serial Number [cmdb_serial_number]
    Field Description
    Serial Number [serial_number] Unique identifier, sourced from the Azure VM ID.
    Serial Number Type [serial_number_type] Type of serial number. Default value is uuid.
    Valid [valid] Indicates the serial number is valid. Default value is true.
    Configuration Item [cmdb_ci] References the Windows Server [cmdb_ci_win_server] or Linux Server [cmdb_ci_linux_server] table.

    CI relationships

    The Azure – Create Server CI pattern extension creates the following relationships and references to support Server CI discovery. References link to records in other tables and don't appear in the CI Relationship [cmdb_rel_ci] table.

    Table 3. CI relationships
    CI Relationship CI
    Windows Server [cmdb_ci_win_server] Virtualized by::Virtualizes Virtual Machine Instance [cmdb_ci_vm_instance]
    Linux Server [cmdb_ci_linux_server] Virtualized by::Virtualizes Virtual Machine Instance [cmdb_ci_vm_instance]
    Table 4. CI references
    CI Field Referenced CI
    Serial Number [cmdb_serial_number] Configuration Item [cmdb_ci] Windows Server [cmdb_ci_win_server]
    Serial Number [cmdb_serial_number] Configuration Item [cmdb_ci] Linux Server [cmdb_ci_linux_server]