Is there a way to preserve SSO, Email, etc config when cloning?

[Community Alums]

I've been combing the community and the wiki the last few days and have found some info, but figured I'd ask the experts here and see if I can get the nuts and bolts of it.

We have 4 instances....lots of cloning, and always have to do the post cloning procedures to reconfig the SSO, certificates, email, MID servers etc. Is there a way to exempt this information from being overwritten when we clone so it makes our lives easier?

I know there is ways to exclude tables and such and I have even found some info on the SSO, but every time we clone we have to log in through the side door and reconfig everything so we are able to use SSO.

Any info, places to research etc. would be greatly helpful, thanks!

[A523]

You can add preservation data. Type clone in the Navigation filter and you will see 'Preserve Data'. There you can add table and/or rows that you do not want to clone. E.g. you can add Mid_server(ecc_agent) table to leave the mid alone, sys_certificate for the certificate, sys_installation_exit for SSO scripts. You may want to preserve some of your properties (sys_properties) as well. You probably want to save properties related to email and sso.

You can also add clean-up script. For example, if you clone prod, some of the data, you may not want, people to see. So you can put those script to remove those data.

It is pretty powerful.

Remember, you need to define those on the source instance.

See this wiki for more info System Clone - ServiceNow Wiki

[Community Alums]

Jimmy,

Thank you! Gives me a great start on what to look in to and where I need to go.

Appreciate it.