Issue
Use this quick start to restore basic services of a cloned instance.
- Restore email service
- Verify scheduled jobs are running properly on nodes of the cloned instance
For a complete list of post-cloning tasks, see the Post-Cloning Checklist.
Restore email service
ServiceNow intentionally disables a cloned instance's email service to prevent it from sending duplicate or unwanted email.
|
|
Warning: Due to a bug in Microsoft Internet Explorer 11, this procedure should not be performed with IE 11. Instead, either use a different version of IE, use a different browser, or perform the workaround below. |
Use the following steps to restore email service.
- Login to the cloned instance.
- Navigate to System Mailboxes > Outbound > Outbox.
- Verify that there are no unexpected emails in the Outbox. Delete any unwanted email from the Outbox.
- Navigate to System Properties > Email.
- Select Mail sending enabled (SMTP).
- Select Mail receiving enabled (POP3).
- Click Save.
- Navigate to https://<your server name>.service-now.com/sys_properties_list.do?sysparm_query=GOTOname%3Dglide.email.smtp.active and set value to true.
- Navigate to https://<your server name>.service-now.com/sys_properties_list.do?sysparm_query=GOTOname%3Dglide.email.read.active and set the value to true
Verify scheduled jobs are running properly on nodes of cloned instance
To ensure uninterrupted service and that scheduled jobs are running properly, scheduled jobs should be running on nodes of the cloned instance. Your ServiceNow administrator should understand the effects of changing scheduled jobs to different nodes before performing these steps. Contact technical support if you have questions.
- Log in to the cloned instance.
- Navigate to System Scheduler > Scheduled Jobs.
- Creating Personal Lists to display the Claimed By and System ID fields.
- Filter out entries with empty Claimed By and System ID fields.
- Select a scheduled job you want to run on a particular node.
- Set the System ID field to the node you want to run the scheduled job on or leave it blank to have it run on the next available node.
- Verify there are no scheduled jobs whose System ID is not part of your target instance. If the System ID is incorrect, clear the value.
