Keeping sys_id's same throughout the instances when Ldap integration is used

[Anupriya1]

Hello Experts,

We are using LDAP integration in all the instances to create users/groups. So, right now sys_id's are not in sync.

One way I know is, to perform the import in Production environment and sync the table to non-prod.

Does anyone know what is the best practice to keep the sys_id's in sync when LDAP is used.

May thanks!

[Sebastian R_]

I think the best practise depends on your usage of user/groups on the non-production instance.

If you don´t need the users/groups in files which are tracked in update sets it should be enough to sync the records with a regular clone of the production instance.

If you need the records really up to date (e.g. because you need the groups regularly for configuration records) you probably need a custom solution which fits your use cases.

You can also have a look at Instance Data Replication but this requires an additional subscription.

[Ashutosh Munot1]

Hi,

Yes this happens because we let LDAP run on all instances like Dev, TEST, QA and PROD. 

What we usually do is clone the instance frequently which helps us to keep our foundation data in sync with all instance's. We clone every 2 weeks.

Thanks,
Ashutosh

[Tony K · Accepted solution]

You can check out this thread. I've been trying to find a way to keep them in synch as well after turning off each instance connecting to ldap on it's own. That just throws off the sys id's then which is why I turned it off. 

https://community.servicenow.com/community?id=community_question&sys_id=982556b6db2eaf006c1c02d5ca96...