Abstract
Often, we get requests to rename assignment groups in ServiceNow; less often, we need to rename security groups. Most/all groups are sourced from Active Directory. In general, groups are referred to from other tables. Renames therefore need to account for this in order to maintain referential integrity.
That implies keeping the same record (with value of key field/GUID of sys_id remaining the same) and simply changing the display value. Note that simply deleting a record and replacing it w/ one of matching GUID is also not desirable, since deletion of a record in SN generally deletes all incoming references. So even if you restored the record, you would in most cases have to rebuild incoming references to it. Instead, follow this procedure.
Rename in AD
Change the full name in Active Directory. ServiceNow groups are stored in the yale domain under ou=ServiceNow.
Groups follow the convention 'ServiceNow_[group name]' in the AD. We generally avoid using commas and ampersands in group names.
Rename in ServiceNow
In the group form, make the "Full Name" field visible. Change this name to match the target name entered in the AD. Verify that the "Name" or short name field is updated after saving your changes.
Verify
The names in AD and the SN 'Full Name' field must match exactly, or the next import will create a near-duplicate group in SN. You can force the Yale LDAP group import from Scheduled Jobs in ServiceNow. Check to see that:
- the group in question has been renamed
- the number of groups has not increased