How to disable SCCM Integration changing the 'Assigned To' field?

Antti Luusua · ‎10-14-2020

Hello SNow Community,

sorry if my question has already been answered but couldn't find any help while searching these forums or otherwise.

We are trying to migrate using ServiceNow's asset management but have a few hurdles along the way. One of the issues is that our Servicenow has SCCM integration, and while it is working, we would like to manually assign the assets to people. Currently the 'Assigned To' field is set by SCCM Integration by taking the Primary User from SCCM but this is not a 100 % accurate information at all times. We cannot disable this function in SCCM since our Helpdesk uses it in other ways but it should not take any part in SNow asset management.

I'm guessing I would have to edit the SQL query and remove the part where it queries SCCM for the user name but I fear that I break something I do that.

Any help would be greatly appreciated!

akash_mehta · ‎10-14-2020

You don't have to modify the SQL statement; you can bring it in and populate it into another field if you like for reference purpose.

You should make these changes at the Transform Map level...

1) In the SCCM 2016 Computer Identity Transform Map

2) There is a script that runs a function called "runIt();" - in that function there is a "setAssignedTo();" function that you can comment out.

This will stop populating the assigned to value on the CI (and asset since it is synchronized).

Additional thoughts:

1) At other customers, I have created a field on the cmdb_ci_computer table called "Discovered User" or "Primary User" and set this value from the SCCM transform map into this field - it allows you to see what the discovery source thinks is the primary user and compare it

2) I tend to just make this field a string field instead of a reference field - just in case this user is a service account or some sort of admin account that may not be in ServiceNow user table

Hope that helps.

-Akash

View solution in original post

akash_mehta · ‎10-14-2020

You don't have to modify the SQL statement; you can bring it in and populate it into another field if you like for reference purpose.

You should make these changes at the Transform Map level...

1) In the SCCM 2016 Computer Identity Transform Map

2) There is a script that runs a function called "runIt();" - in that function there is a "setAssignedTo();" function that you can comment out.

This will stop populating the assigned to value on the CI (and asset since it is synchronized).

Additional thoughts:

1) At other customers, I have created a field on the cmdb_ci_computer table called "Discovered User" or "Primary User" and set this value from the SCCM transform map into this field - it allows you to see what the discovery source thinks is the primary user and compare it

2) I tend to just make this field a string field instead of a reference field - just in case this user is a service account or some sort of admin account that may not be in ServiceNow user table

Hope that helps.

-Akash

Antti Luusua · ‎10-14-2020

Thank you so much Akash. This looks to be just what I needed. I commented out the setAssignedTo() function. Also your suggestion about populating another field is a great idea, I will for sure look into that.

Just to make sure, I added a screencap of the function I commented out. It is the correct one, yes?

akash_mehta · ‎10-15-2020

That is correct. Glad I was able to help. Thank you for marking the question as "Correct".

Aarav1 · ‎08-05-2021

@akash.mehta is there any other solution for it because we want the first user from sccm to integrate than this should stop so any other alternative u have for the problem