Post-Clone Checklist, anyone?

[sbailey1]

We're getting ready to refresh all of our instances from PROD in preparation for go-live. When we clone, we run through a checklist (which we're still trying to develop out) to tweak those things we know need to be tweaked. Mailbox password, user account lockout, color scheme (for visual platform indication), etc. Does anyone else have a checklist for post-clone cleanup we can use to match up against ours to make sure we've caught everything? I'll be glad to post our version as well, if others would find that useful.

[carleen_greenle]

Hi guys, we really appreciate your input here, we are even thinking about making a wiki article based on this post.

I just wanted to make a note in regards to pokey's pdf. If you delete update sets, then later are upgraded you will lose any customizations you have made within those update sets. The update sets are containers that hold "customer updates" that are applied whenever you are upgraded.

I have been asked by other clients before how to make the Completed update set list more manageable, but have yet to find a good solution. I'll see if development can provide a suggestion or possibly a solution in a future release.

[randrews]

I like it when the nav menu highlighted items are the same as the instance color so I added this setting

System definition Application Categories ... on each item set the color of the instance on the style line for the ones you are highlighting

[shetzel]

Carleen -

Thanks for the tip, I'll update my document to remove this line. I can see where this would cause a problem if I wanted to upgrade my DEV instance instead of cloning from PROD.

To make the list more manageable I'm going to filter to only show "State = In progress". I've set this up as a default for the module "Local Update Sets" under Application "System Update Sets".

Sbailey / kstainsby -

Great additions and info. I really like the color coding and use of tables, I'll have to update mine. I'm not sure of the property? glide.installation.production I was not aware of this one. Or, if there is an auto upgrade flag, I would be interested if anyone has more detail on either.

I've updated kstainsby's document from what I've learned from Carleen about update sets (Section 7). For (Section 😎 this may be optional ( I don't recall ). It was probably affecting some development I was completing or troubleshooting of our VPN connection with Service-Now. FYI - our integrated Active Directory authentication still functions with this change completed on both our TEST and DEV environments.

All -

Important to note: your email properties may be different from mine. For example, "Outgoing (SMTP) mail server" We route our outgoing mail through an internal server, out of the box default is to use Service-Now I believe.

Email properties:

I listed properties for PROD (as kstainsby mentions) for reference because I had an issue where my properties were corrupted during a clone.

Test environment I delete to avoid notifications from sending to our admins. TEST is our 'sandbox' where anything goes, I only want email notifications sending from PROD to the users and DEV to my admins.

[shetzel]

Found a mistake; Email Properties: For prod you should not have an entry in the field "email address to which all..."

[john_roberts]

New wiki page to start tracking some of the common items.
http://wiki.service-now.com/index.php?title=Post-Cloning_Checklist