Device Primary User, which ultimately can set hardware asset primary user and/or custodian

Aaron_Boock

Is device Primary User set strictly based on SCCM user device affinity via SCCM connector?

OR

Is device Primary User set using top console user from SCCM?

joivan_hedrick

The former, SCCM sets the Primary user through UDA. Then SCCM Connector runs and sets that primary user onto any Windows Computer objects, optionally followed by the Cireson Hardware Asset Sync workflow setting the primary user from Windows Computer objects into Hardware Assets. 

joivan_hedrick

The former, SCCM sets the Primary user through UDA. Then SCCM Connector runs and sets that primary user onto any Windows Computer objects, optionally followed by the Cireson Hardware Asset Sync workflow setting the primary user from Windows Computer objects into Hardware Assets. 

Eugene_Rack

Good afternoon
Is there a way to allow the support team to manually update the Primary Owner without it being overwritten by the SCCM connector information relating to Primary Owner?

Konstantin_Slavin-Bo

@Eugene_Rack
On what? A Windows Computer or Cireson Assets?

Windows Computers; no, as that would get overwritten by the SCCM connector on next sync. You would need to use another field.

On Cireson Assets; I think this would be possible, as the Cireson Hardware Asset Sync workflow could be deactivated.

Eugene_Rack

Sorry, yes on a windows computer. Thanx for your answer, I thought that would be case. May have to use another field.

Konstantin_Slavin-Bo

The Custodian on the Windows Computer form is not sync'ed by the SCCM connector, so you could utilize that field to serve your purpose?

Peter_Settle

Have you looked at this knowledge article on the Cireson Support portal?

https://support.cireson.com/KnowledgeBase/View/1335#/