Requesting an instance rename with Now Support Service Catalog - Support and Troubleshooting

Requesting an instance rename with Now Support Service Catalog Issue ServiceNow has created an automated workflow to support the instance rename process. Users with the NS Admin role can request an instance rename via a Service Catalog item to create a Change, which is completed using end-to-end automation .

Note: This procedure is only applicable to some hosted instances, including production and sub-production. Demonstration, On-Premise, Developer instances, Jumpstart instances, and Temp instances are excluded from this rename automation. If you need an on-premise instance rename, please create a Case with ServiceNow Technical Support.

Learn more about this Service Catalog and its benefits on Now Community .

You can request Instance Rename by following these steps:

Navigate to Now Support Click on the Automation Store On the left side, click on Service Catalog , click on Instance Management Go to the second page and click on Rename an Instance

Select the instance to rename from the filtered reference field Note: If you are having trouble finding your instance, use "*" for a "contains" query. For OEM instances, the rename request should be made by OEM vendors. If you are not an OEM vendor, an error message will be shown and you will not be able to submit the request. The OEM instance naming convention requires to have " oem " in the name to differentiate from the enterprise instance. Provide a new instance name (Please refer to Instance rename policy before providing a new instance name) Select Maintenance Start time from available slots IMPORTANT: Please plan the instance rename several days in advance if possible. Note that if there are other change requests already pending for that instance (in particular instance moves) it will not be possible to schedule an instance rename until after those other change requests have been completed Specify how long the old URL should be active after renaming. Note: By default, ServiceNow retains the old URL for 2 business days . You can request to retain the old URL for up to 30 days . Acknowledge disclaimers for rename action and ServiceNow Instance Rename Policy Click on Submit A new change request is created for the rename request, and the request is displayed automatically. As needed, add people to the Watch list as necessary. Click Update Important notes After the completion of the instance rename process, you might receive an " Unknown host " error message while submitting a clone request or a " Target instance already exists " error message while trying to create a new clone target. This usually means that there are already existing clone target records created for the renamed instance from another source instance. Please review and follow KB0715227 and KB0686736 to update your clone target. As a Customer Administrator, you can not rename an instance of a child company. If you need to rename your child company instance, you will need to log into your child company account to initiate the instance rename process. As a Partner Administrator, you can not rename your customers' instances. You will have to ask the customer administrator of that company to submit an instance rename request. The change window for the instance rename will appear on the change ticket as the planned start and end time. Beginning at the Planned Start Time the instance will not be available for up to 2 hours. Do not run any clones to/from the instance once the rename has started. New instance and old instance URLs are simultaneously available for the time provided in the request. During this time, the cloning functionality is not available. After the rename, the following settings may require updating: Email settings are reset to the out-of-box values and updated to reflect the new instance name. This change is made after the new instance URL becomes available. Any inbound emails sent to the old instance email may be lost after this change has been made. Customers will likely need to update the email settings in their instance to reflect any previously implemented customization. If the customer is using Single Sign On through the Multi-Provider SSO plugin, they will need to check each of their Identity Provider records (Multi-Provider SSO > Identity Provider) and update any URLs in those settings which point to the old instance name. MID Server considerations Each MID server will need to be updated individually to point to the new instance name: Go to the MID server installation path Edit the .\agent\config.xml file using a text editor (such as WordPad), as follows: Locate the element Change the value to the URL of the NEW Instance Also, if there are any changes to the certificates, install the new certificates by following the documentation below: Add SSL certificates for the MID Server URL Retention Extension considerations It is important to know that after the default 2-7 days URL retention, ServiceNow implement a URL redirection (accessing "old.service-now.com" will cause a HTTP Redirect (301) to "new.service-now.com"). This can potentially cause issues for Integrations which are unable to handle 301 redirection.