Post-clone Discovery configuration

  • Release version: Xanadu
  • Updated June 3, 2025
  • 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 Post-clone Discovery configuration

    When a ServiceNow instance clone occurs, Discovery schedules are copied from the source to the target instance. However, additional post-clone configuration is required to ensure these Discovery schedules (both Cloud-based and IP-based) function correctly on the target instance. This guidance helps you configure Discovery schedules properly, maintain optimal performance, and avoid common issues caused by cloning.

    Show full answer Show less

    Post-clone Configuration for IP-based Discovery Schedules

    After cloning and completing the clone request in the Clone Admin Console, the necessary configuration depends on the MID Server selection method used in the original Discovery schedule:

    • Specific MID: Update the MID Server record associated with each Discovery schedule on the target instance.
    • Cluster: Create the MID Server cluster on the target instance, attach the MID Server to this cluster, and update the cluster name in the Discovery schedule. Alternatively, you may remove the MID cluster record from the Clone Exclude Tables to avoid cloning the cluster.
    • Use Behavior: Manually recreate or attach the required behaviors and functionalities, then link these behaviors to the Discovery schedule. Note that Discovery functionalities are not cloned automatically.
    • Auto-select: Verify all MID Servers on the target instance are correctly configured with appropriate IP ranges, supported applications, and capabilities.

    Post-clone Configuration for Cloud Discovery Schedules

    Similarly, for Cloud Discovery schedules, after cloning:

    • Update the Cloud Service Account records to reference the correct Discovery credentials.
    • Update MID Server assignments for the Discovery schedules.
    • Follow the same MID Server selection method steps as for IP-based Discovery schedules (Specific MID, Cluster, Use Behavior, Auto-select) to finalize the configuration.

    These steps ensure Cloud Discovery schedules function properly on the cloned instance.

    Important Notes on Clone Exclusions

    • Credential aliases are cloned, but the underlying credentials are not. Post-clone, you must verify and update credential aliases in the Connection & Credential Aliases [sysalias] table to point to correct credentials on the target instance.
    • MID Server related tables are not cloned. You must manually configure MID Servers and their associations after cloning.

    Practical Value for ServiceNow Customers

    By following these post-clone configuration steps, ServiceNow customers ensure their Discovery schedules continue to operate correctly after cloning. This prevents failed Discovery runs, maintains data accuracy in CMDB updates, and supports uninterrupted operational workflows. Proper configuration of MID Servers, behaviors, clusters, and credentials post-clone is essential for optimal Discovery performance.

    When a clone occurs, Discovery schedules are copied from the source instance to the target instance. Additional configuration is necessary for these schedules to function correctly on the target instance, helping you properly configure Cloud-based and IP-based Discovery schedules and maintain optimal performance.

    Note:

    For general information about instance cloning, see the Clone FAQS-Frequently Asked Questions [KB0715621] article in the Now Support Knowledge Base.

    For instructions on how to deactivate or cancel a Discovery schedule after creating a clone, see the A Post-Clone script to Deactivate and Cancel Discovery Schedules [KB0789119] article in the Now Support Knowledge Base.

    Post-clone target configuration for IP-based Discovery schedules

    After completing the Request a clone in the Clone Admin Console process, post-clone configuration is determined by the MID Server selection method you chose in the Discovery schedule on the source instance.

    Table 1. Target instance configuration for IP-based Discovery schedules
    MID Server selection method Next steps
    Specific MID Update the MID Server record for each Discovery schedule.
    Cluster Create the cluster, attach the MID Server to the cluster, and then update the cluster name in the Discovery schedule.

    Alternatively, remove the MID cluster [ecc_agent_cluster] record from the Clone Exclude Tables [clone_data_exclude]. For more information, see Exclude a table from cloning.
    Use Behavior Create the behaviors, create a functionality or attach an existing functionality, then go back to the Discovery schedule and attach the behavior to the Discovery schedule.
    Note:
    Discovery functionalities aren’t cloned with an instance.
    Auto-select Verify all MID Servers on the target instance are set up with target IP ranges, supported applications, and capabilities.

    Post-clone target configuration for Cloud Discovery schedules

    After completing the Request a clone in the Clone Admin Console process, you must access the Cloud Service Account [cmdb_ci_cloud_service_account] table and update the service accounts with the proper reference to the Discovery credentials. You must also update the MID Servers for the Discovery schedule. Additional post-clone configuration is determined by the MID Server selection method that you chose in the original Discovery schedule.

    Table 2. Target instance configuration for Cloud Discovery schedules
    MID Server selection method Next steps
    Specific MID Update the MID Server record for each Discovery schedule.
    Cluster Create the cluster, attach the MID Server to the cluster, and then update the cluster name in the Discovery schedule.

    Alternatively, remove the MID cluster [ecc_agent_cluster] record from the Clone Exclude Tables [clone_data_exclude]. For more information, see Exclude a table from cloning.
    Use Behavior Create the behaviors, create a functionality or attach an existing functionality, then go back to the Discovery schedule and attach the behavior on the target instance.
    Note:
    Discovery functionalities aren’t cloned with an instance.
    Auto-select Verify that all MID Servers are set up with target IP ranges, supported applications, and capabilities.
    For more information, see the Cloud discovery schedules fail after the instance clone [KB1759363] article in the Now Support Knowledge Base.

    Clone Exclusions

    Credential aliases are cloned but their credentials aren’t cloned. If Discovery schedules have credential aliases, you must go to the Connection & Credential Aliases [sys_alias] table and confirm the alias points to the correct credentials. After cloning, update the Discovery schedules and add credentials within the target instance.

    Additionally, no MID Server related tables are cloned. For more details, see the MID Servers and Clones [KBKB0786475] article in the Now Support Knowledge Base.