Server CI population during cloud discovery

  • Release version: Zurich
  • 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 typically creates Virtual Machine (VM) Instance CIs by default. To also populate Server CIs (Windows Server and Linux Server), organizations traditionally run IP-based discovery, which can be time-consuming in large environments. Starting with Discovery and Service Mapping Patterns version 1.31.0, Server CIs can be created directly during cloud discovery without the need for IP-based discovery, significantly reducing discovery time when only server records are required from the cloud environment.

    Show full answer Show less

    Key Features

    • Server CI Creation Control: The snitompattern.clouddiscoverypopulateserverci system property controls whether Server CIs are created. By default, it is set to none, meaning Server CIs are not created unless explicitly configured.
    • Supported Patterns: Server CI population is supported by Azure – Virtual Machine (LP) and Azure VM Instance – Uniform Scale Set patterns.
    • Data Collected: When Azure – Create Server CI pattern extension runs, it collects detailed server attributes such as hostname, object ID, CPU cores, disk space, IP address, operating system, RAM, serial number, and operational status.
    • CI Relationships: The process establishes relationships where Windows and Linux Server CIs are linked to their corresponding Virtual Machine Instance CIs using “Virtualized by::Virtualizes” relationships. Serial numbers are referenced to ensure unique identification.
    • Note on Usage: 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

    • Reduced Discovery Time: Enables faster population of server records in large cloud environments by eliminating the need for the slower IP-based discovery process.
    • Focused Discovery: Ideal for organizations that only require server CIs from their cloud infrastructure without additional application or network data.
    • Accurate Server Representation: Produces detailed and uniquely identified Server CIs with relevant operational and configuration data, improving CMDB accuracy.
    • Improved CMDB Relationships: Automatically creates meaningful relationships between Server CIs and their underlying VM instances, supporting better configuration management and visibility.

    Configuration Guidance

    To enable Server CI creation during cloud discovery, update the snitompattern.clouddiscoverypopulateserverci system property according to your discovery needs. This approach avoids running IP-based discovery and helps streamline your discovery schedules and CMDB population.

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