--- 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 --- # Server CI population during cloud discovery # Server CI population during cloud discovery {#ariaid-title1} * Release version: Yokohama * * Updated May 14, 2026 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) 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 Server and Linux Server CIs alongside Virtual Machine Instance CIs, without requiring the traditional IP-based discovery. This enhancement, introduced in Discovery and Service Mapping Patterns version 1.31.0, is designed to significantly reduce discovery time in large cloud environments by avoiding the longer IP-based discovery schedules. It is especially useful for organizations that only need server records from their cloud environment without additional application data. Show full answer Show less ## Key Features * **Server CI Creation Control:** The system property `snitompattern.clouddiscoverypopulateserverci` governs whether Server CIs are created during cloud discovery. By default, this is set to *none*, meaning Server CIs are not created unless explicitly enabled. * **Supported Patterns:** Server CI population works with Azure -- Virtual Machine (LP) and Azure VM Instance -- Uniform Scale Set patterns. * **Data Collected:** When enabled, discovery collects detailed server attributes including hostname, unique object ID, CPU core count, CPU count, disk space, install status, IP address, virtual status, operating system and version, RAM, serial number, and operational status. * **CI Relationships and References:** The created Windows and Linux Server CIs are linked to their corresponding Virtual Machine Instance CIs through virtualized by/virtualizes relationships, ensuring accurate infrastructure mapping. * **Conflict Avoidance:** Customers should use either Server CI population during cloud discovery or IP-based discovery for the same VMs, but not both, to prevent conflicting attribute data. ## Practical Application for ServiceNow Customers By enabling Server CI creation during cloud discovery, you can: * Reduce total discovery time in large cloud environments by bypassing IP-based discovery for server information. * Maintain accurate and up-to-date server CI records in your CMDB for Windows and Linux servers derived from Azure VMs and scale sets. * Leverage enhanced visibility into server configurations with detailed attributes and clear relationships to VM instances. * Configure the process via a simple system property, allowing flexible enablement based on your organizational requirements. This capability supports streamlined CMDB population for cloud infrastructures, improving operational efficiency and data accuracy while minimizing discovery overhead. Cloud discovery can populate Server CIs without running IP-based discovery, reducing discovery time in large environments. ## Server CI cloud discovery overview {#server-ci-cloud-discovery__section_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.{#server-ci-cloud-discovery__p_old_behavior} 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](https://servicenow-prod.fluidtopics.net/VkzSuyB_UKcI_oNdDlx4MQ "Create Server CIs during cloud discovery without running IP-based discovery, reducing discovery time in large environments.").{#server-ci-cloud-discovery__p_new_behavior} The following patterns support Server CI population during cloud discovery: * Azure -- Virtual Machine (LP) * Azure VM Instance -- Uniform Scale Set {#server-ci-cloud-discovery__ul_patterns} 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 {#server-ci-cloud-discovery__section_data_collected} 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.{#server-ci-cloud-discovery__p_data_collected} {#server-ci-cloud-discovery__table_server_fields__entry__2} | 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 {#server-ci-cloud-discovery__ul_name_options} | | 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 1. Windows Server \[cmdb_ci_win_server\]/Linux Server \[cmdb_ci_linux_server\]] {#server-ci-cloud-discovery__table_server_fields} {#server-ci-cloud-discovery__table_serial_number__entry__2} | 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. | [Table 2. Serial Number \[cmdb_serial_number\]] {#server-ci-cloud-discovery__table_serial_number} ## CI relationships {#server-ci-cloud-discovery__section_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.{#server-ci-cloud-discovery__p_relationships} {#server-ci-cloud-discovery__table_relationships__entry__3} | 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 3. CI relationships] {#server-ci-cloud-discovery__table_relationships} {#server-ci-cloud-discovery__table_references__entry__3} | 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\] | [Table 4. CI references] {#server-ci-cloud-discovery__table_references} * **[Configure Server CI creation during cloud discovery](https://servicenow-prod.fluidtopics.net/VkzSuyB_UKcI_oNdDlx4MQ)** Create Server CIs during cloud discovery without running IP-based discovery, reducing discovery time in large environments. **Previous topic:** [Enable direct field population for query performance](https://servicenow-prod.fluidtopics.net/Mtv_gzH2PisJvt4rvH3VJA "Populate Service Account, Logical Datacenter, and Virtual Machine Object fields in configuration item (CI) tables to improve query performance.") **Next topic:** [Configure Server CI creation during cloud discovery](https://servicenow-prod.fluidtopics.net/VkzSuyB_UKcI_oNdDlx4MQ "Create Server CIs during cloud discovery without running IP-based discovery, reducing discovery time in large environments.") **Related reference** * [Azure virtual machine pattern-based discovery](https://servicenow-prod.fluidtopics.net/DMOatbPNKNSVNJJ49t_3BA "Discovery and Service Mapping Patterns finds Azure virtual machines (VMs) on your cloud environment. Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.") * [Azure Virtual Machine Scale Sets (VMSS) Instance discovery](https://servicenow-prod.fluidtopics.net/3aDAK8376xdApU6Is8XntQ "The Discovery and Service Mapping Patterns application uses the Azure - VM Scale Set (LP) and the Azure VM Instance - Uniform Scale Set patterns to find Azure Virtual Machine Scale Sets (VMSS). Discovering some of these resources may require updating to the latest version of the Discovery and Service Mapping Patterns application from the ServiceNow Store.")