Instance Cloning -- Notifications disablen?

[simonvolkwe]

Hello together,

I have a question about cloning from a LIVE instance to a DEV instance.

In this article, which describes post-clone and pre-clone activities very well, it says that I should disable notifications before cloning.(Post-Cloning Checklist - Support and Troubleshooting)

Why is that?

Since I am cloning to a dev instance where notifications cannot be sent by default, I can theoretically leave it out, right?

Thanks in advance, and if you have any experience or tips regarding cloning and what to look out for, or what is often forgotten with preserver/excluded records, please feel free to write.

Greetings

Simon

[Dr Atul G- LNG]

Hi @simonvolkwe 

You can check under  clone profile, else you can do it after cloning manually.

[Ankur Bawiskar]

@simonvolkwe 

yes you need to do this as part of post clone script.

Post-clone cleanup scripts 

If my response helped please mark it correct and close the thread so that it benefits future readers.

[simonvolkwe]

Thank you all.

Ok then I will create these scripts. 

If this is a task which has to be done by every cloning process.

Why isnt Service Now building one OOB(default) Post clone script? There are plenty of default Excludes, Preservers and post clone scripts?

I feel like this should have been part of it.

Greetings

Simon

[Dr Atul G- LNG · Accepted solution]

Hi @simonvolkwe 

Did you get a chance to look at the OOTB post-cleanup scripts?

[simonvolkwe]

Ohh so it is an OOB post cleanup script.

Thank you very much thats the answer to my question. ^^

My bad sorry i only looked into all cleanupscripts which were already part of my clone profile.