Keep asset assignment from being changed by SCCM?

[Stefan_Garcia]

Hi all,

Currently we have SCCM updating our Assigned to field on computers, and it tends to rotate those users every two days or so. I don't want that rotating out the Assigned to field on the asset, which it is currently doing, but what would be the best way to do that?

Intended process would be:

SCCM can update Assigned to if it's blank

If Assigned to has been updated manually, SCCM should no longer be able to update that value

I suppose it would also be enough to just stop SCCM from updating the Assigned to value in the first place. I tried adding reconciliation rules to the computer class for the Assigned to attribute, but I must have done something wrong as that did not work. And I would prefer not to go into the service graph and modify its' transform map.

Thanks!

[Pascal Verdieu]

Offhand, the information on if a specific field was changed by someone is somewhere, haven't got the opportunity to look it up yet.  Then, yes, you would need to modify the transform map and use a script for the Assigned_To field which would look like this

var isManuallyAssignedTo;
#Code here to set isManuallyAssignedToto the sys_id of the user who is currently assigned to or null
return (isManuallyAssignedTo != null && isManuallyAssignedTo != '') ? isManuallyAssignedTo : source.getValue('assignedTo');

[Alan Akins]

I think you've got two primary options:

1. (customization) Remove the mapping to the assigned_to field in the transform.
2. (configuration) Set up an IRE reconciliation rule on the appropriate CI Class (Computers probably is the better choice) to put manual updates as a higher priority than SCCM. This will work in this way: that if the assigned_to is empty, SCCM will be allowed to write to it. But if someone has manually updated the assigned_to, then SCCM will not be allowed to change it.

We have used #1 in the past and it works fine. But it is a customization, so now we are using #2.