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


---

# Discover all resources in a datacenter on-demand

# Discover all resources in a datacenter on-demand {#disco-resources-in-datacenter__title-disco-resources-in-datacenter}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

At any time, you can run Discovery on a datacenter to update the CMDB.{#disco-resources-in-datacenter__shortdesc-disco-resources-in-datacenter}

## Before you begin

* A cloud account must exist with service accounts and associated datacenters. You must run on-demand Discovery to discover datacenters before you can schedule Discovery.
* Use the Cloud Discovery Workspace, and at least version 1.15 of Discovery and Service Mapping Patterns from the ServiceNow Store.

{#disco-resources-in-datacenter__ul_fkb_t5n_pgb}

Role required: sn_cmp.cloud_admin

## Procedure

1. In the Cloud Admin Portal, navigate to ManageCloud Accounts.
2. Click a cloud account and, on the Datacenters tab, select a datacenter.  
   The Resources tab lists the resources in the CMDB.
3. Change the state to Draft and then click Discover Now.  
   Note that Discover Now is disabled if neither CAPI or Patterns is installed. Follow these scenarios to proceed.  
   Note:  
   Discover now will also be disabled with an message suggesting you to install the latest Discovery and Service Mapping Patterns. This can be fixed by installing version 1.15.1 at least or by triggering the manual migration step.

   | Scenario | Next steps |
   | Discover Now is disabled for System Admin login | * The page suggests that you must install the latest patterns application to proceed. * The banner at the top of the page prompts you to visit Go to Applications Manager for installation {#disco-resources-in-datacenter__ul_iz2_yzr_bcc} |
   | Discover Now is disabled for sn_cmp Cloud Admin login | * The page suggests that you must install the latest patterns application to proceed. * The page requests to contact the system admin for installation of patterns application. {#disco-resources-in-datacenter__ul_jz2_yzr_bcc} |
   | Latest patterns application is installed | Discover Now is activated. Note: Discovery will now use Patterns as the default mechanism. |
   |-|-|

   {#disco-resources-in-datacenter__choicetable_hz2_yzr_bcc}
4. Run Discover Now and wait for Discovery to finish.
5. Change the state of the cloud account to Published.  
   Discover now will be disabled with the same message shown. This can be fixed by installing 1.15.1+ version or by triggering the manual migration step
{#disco-resources-in-datacenter__steps_vgv_t2t_wy}

## Result

Discovery populates the CMDB with the discovered resources and updates the information on the Resources tab. You can view Discovery results in the Discovery Log tab.  
Note:  
By default, Discovery stores the discovered VM hardware types in the Hardware Type \[cmdb_ci_compute_template\] table. If you notice an unusually large number of records in this table, use the Cloud Hardware Type \[cmdb_ci_cloud_hardware_type\] table to store the discovered VM hardware types. For more information, see [Enable the Cloud Hardware Type class
extension](https://servicenow-prod.fluidtopics.net/KNU5OxYrIVSiFCfHbBF~6A "Enable the Cloud Hardware Type [cmdb_ci_cloud_hardware_type] table to store the predefined virtual machine (VM) hardware type records for Amazon AWS Cloud Microsoft Azure Cloud and Google Cloud Platform (GCP). This class extension helps prevent duplication of the VM hardware type records in the Hardware Type [cmdb_ci_compute_template] table, which improves performance for Discovery and related flows."). All Cloud Provisioning and Governance features, such as provisioning, quotas, and so on continue to work as is after you switch to the Cloud Hardware Type table.
**Related reference**   

* [View the Discovery Log](https://servicenow-prod.fluidtopics.net/ao5OrQtRxbDaPsjhkL2QeA#r_DiscoveryLog "The system collects logs to reflect the activity that takes place during a horizontal discovery based on both patterns and probes. Use the logs to fine-tune or troubleshoot the discovery process.")

*[\>]: and then