SCCM updates "assigned" and "assigned to" fields.

[Flybook]

Hello experts,

It is our understanding that OOB interface from SCCM is changing the assigned and assigned to fields to most likely user. These two fields are used for end user compute devices and are set by the our staff. We do not want SCCM changing these fields for any device. If there is a possible solution to stay OOB, we would like to adopt that and stop SCCM updating these two fields. If not, Is this a mapping/interface that we can customize so that these fields do not get updated by SCCM?

We would like to know if Reconciliation Definitions can be used to limit a Discovery Source from updating these particular fields. Please let me know if this is a viable solution. It might be an easier fix to implement than the ACLs.

Thank you!

[ersureshbe]

Hi, I recommend to check the Robust transform map any mapping enabled part of Assigned and Assigned To field. If yes, disable the field mapping else check Assigned and Assigned To field are changes based on other field value updates with the help of SCCM. 

To identify, you should manually play in the field changes from the form.

[mattystern]

Hi Flybook,

This will depend on which SCCM plugin you are using. We have a legacy integration with SCCM 2016. In this plugin, you could modify the data source "Computer Identity" such that this doesn't update. I went to SCCM > Data Sources > SCCM 2016 Computer Identity and then clicked the "Transform maps" option. From here, you could comment out line 6 (or the function between lines 24 > 35)

For the newer Service Graph connector for Microsoft SCCM, I think this would also be under "SG-SCCM Computer Identity." Since we are using the legacy plugin, I am not 100% confident. For more reading on this, check out the documentation here: Service Graph connector for Microsoft SCCM (3.2.1) Hope this helps!

-Matt

[Flybook]

Hi  Matt,

Thank you for your response but taking this approach will be changing the OOB behavior which we are trying to avoid. 

We are looking for an alternate solution.

Thank you!

[lholl]

To tack on to this thread, there is a property that allows SCCM to overwrite the assigned_to if enabled: glide.wmi.assigned_to_always_overwrite

Set this to false and you will not see any overwrites occur, but the initial write will happen if the field is blank.