---
sourceDocument: Australia IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/de-DE/it-operations-management

 Release :

    - australia

ft:locale :

    - de-DE

ft:publication_title :

    - Australia IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Post-clone Discovery configuration

# Post-clone Discovery configuration {#ariaid-title1}

* Freigeben Version: Australia
* 
* Aktualisiert 12. März 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 Minuten Lesedauer

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.  
Hinweis:  
For general information about instance cloning, see the [Clone FAQS-Frequently Asked Questions \[KB0715621\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=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\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0789119) article in the Now Support
Knowledge Base.

## Post-clone target configuration for IP-based Discovery schedules {#PostCloneDiscoveryConfig__section_lkd_skl_kfc}

After completing the [Request a clone](https://www.servicenow.com/docs/access?context=t_StartAClone&version=australia&pubname=australia-platform-administration&ft:locale=en-US) process, post-clone configuration is determined by the MID Server selection method you chose in the Discovery schedule on the source instance.  
{#PostCloneDiscoveryConfig__table_yb1_v45_nfc__entry__2}

| 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](https://www.servicenow.com/docs/access?context=t_ExcludeATableFromCloning&version=australia&pubname=australia-platform-administration&ft:locale=en-US). |
| 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. Hinweis: 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. |
[Tabelle : 1. Target instance configuration for IP-based Discovery schedules]

{#PostCloneDiscoveryConfig__table_yb1_v45_nfc}

## Post-clone target configuration for Cloud Discovery schedules {#PostCloneDiscoveryConfig__section_nkd_skl_kfc}

After completing the [Request a clone](https://www.servicenow.com/docs/access?context=t_StartAClone&version=australia&pubname=australia-platform-administration&ft:locale=en-US) 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.  
{#PostCloneDiscoveryConfig__table_pkd_skl_kfc__entry__2}

| 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](https://www.servicenow.com/docs/access?context=t_ExcludeATableFromCloning&version=australia&pubname=australia-platform-administration&ft:locale=en-US). |
| 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. Hinweis: 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. |
[Tabelle : 2. Target instance configuration for Cloud Discovery schedules]

{#PostCloneDiscoveryConfig__table_pkd_skl_kfc}
For more information, see the [Cloud discovery schedules fail after the instance clone \[KB1759363\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB1759363) article in the Now Support Knowledge Base.

## Clone Exclusions {#PostCloneDiscoveryConfig__section_sxk_htl_kfc}

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\]](https://support.servicenow.com/kb?id=kb_article_view&sysparm_article=KB0786475) article in the Now Support
Knowledge Base.
**Zugehörige Informationen**   

* [Managing Instance Clone](https://www.servicenow.com/docs/access?context=using-instance-clone&version=australia&pubname=australia-platform-administration&ft:locale=en-US)