How to avoid SG-SCCM Assigned to field from being overwritten after import

[Donna12]

Our field service people go into ServiceNow and change the assigned to field of a CI from from Joe to Jane.  Once the import completes, it is changed back to Joe again.  How can this be avoided?  the tech may either completely wipe out the assigned to field or change the name.  What is best practice for these scenarios?  Is it better if the tech make changes in SCCM?    The other concerns is this OOB 'v_GS_SYSTEM_CONSOLE_USAGE.TopConsoleUser0'.  We want it to stay with whomever it is assigned to. We are using the most recent SG-sccm connector and here is the script. Thanks

SELECT
v_R_System.Name0 as name,
v_GS_COMPUTER_SYSTEM.domain0 as domain,
v_GS_COMPUTER_SYSTEM.Model0 as model,
v_GS_COMPUTER_SYSTEM.Manufacturer0 as manufacturer,
v_GS_COMPUTER_SYSTEM.ResourceID,
v_GS_SYSTEM_CONSOLE_USAGE.TopConsoleUser0 as username,
v_GS_COMPUTER_SYSTEM.NumberOfProcessors0 as numberofprocessors,
v_GS_SYSTEM.SystemRole0 as SystemRole,
v_GS_OPERATING_SYSTEM.Caption0 as caption,
v_GS_OPERATING_SYSTEM.Version0 as Version,
v_GS_SYSTEM_ENCLOSURE.ChassisTypes0 as chassistype,
WorkstationStatus_DATA.LastHWScan,
v_GS_PC_BIOS.SerialNumber0 as BIOSSerialNumber,
v_GS_COMPUTER_SYSTEM_PRODUCT.IdentifyingNumber0 as SystemSerialNumber,
v_GS_COMPUTER_SYSTEM_PRODUCT.UUID0 as UUIDSerialNumber,
v_GS_SYSTEM_ENCLOSURE.SerialNumber0 as ChassisSerialNumber,
v_GS_BASEBOARD.SerialNumber0 as BaseboardSerialNumber,
WorkstationStatus_DATA.TimeKey as TimeKey,
v_GS_OPERATING_SYSTEM.TimeStamp as OsTimeStamp,
v_R_System.Creation_Date0 as AssignedDate,
null as OUName,
v_GS_SYSTEM_ENCLOSURE.SMBIOSAssetTag0 as AssetTag
FROM v_GS_COMPUTER_SYSTEM
LEFT JOIN WorkstationStatus_DATA ON v_GS_COMPUTER_SYSTEM.ResourceID = WorkstationStatus_DATA.MachineID
LEFT JOIN v_GS_SYSTEM ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_SYSTEM.ResourceID
LEFT JOIN v_GS_PC_BIOS ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_PC_BIOS.ResourceID
LEFT JOIN v_GS_OPERATING_SYSTEM ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_OPERATING_SYSTEM.ResourceID
LEFT JOIN v_GS_COMPUTER_SYSTEM_PRODUCT ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_COMPUTER_SYSTEM_PRODUCT.ResourceID
LEFT JOIN v_GS_SYSTEM_ENCLOSURE ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_SYSTEM_ENCLOSURE.ResourceID
LEFT JOIN v_GS_BASEBOARD ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_BASEBOARD.ResourceID
LEFT JOIN v_GS_SYSTEM_CONSOLE_USAGE ON v_GS_COMPUTER_SYSTEM.ResourceID = v_GS_SYSTEM_CONSOLE_USAGE.ResourceID
LEFT JOIN v_R_System ON v_GS_COMPUTER_SYSTEM.ResourceID = v_R_System.ResourceID

[sethivarun]

Hi Donna, 

IT seems like more a process and access situation. 

few suggestion about this are : 

1) limit the assigned to field access to a limited few have access to change the name. 

2) set up data source precedence for the sccm devices

3) if the field is supposed to be only populated by SCCM, make the field read only so that no one except SCCM can update the field value. Any changes in the value would then be driven by the sccm feed.

[Donna12]

Hello and thanks for your quick reply.  You will see that I am a novice with these questions.  Hope you don't mind...

2.How is this done?

The current process is for techs to change right in SN when needed so that when business pulls reports ,it doesn't look like someone who was fired owns a computer.  Tech change a few fields right in SN and then we also get stuff from SCCM imports.

I am thinking I have to get everyone to only use SCCM and JAMF when updating CI's.

What do most organization do in these scenarios?

Thanks kindly

[sethivarun]

It depends on organization to organization . If the process in the organization is matured enough and the data coming from the JAMF and SCCM is up to date then the automation is something that can be pursued. 

If there is a significant lag in the data that is coming in, then you could look at moving the data maintenance to manual input. 

[Tim80]

You could also create a new field, SCCM Primary User (make it read only) and have the SCCM-SG populate that field. Then have your techs populate the Assigned To field.