We call these party PCs! You find them in training labs, loaner devices, law enforcement squad cars, etc. This is where strong process comes in, especially on the asset side where an asset manager is more often than not concerned about chain of custody. Who did we give it to, who has responsibility for it, what cost center, BU etc has fiscal responsibility. Software asset managers also need to know for software that is installed on that machine. Though not out-of-the-box some customers decided to break the automatic syncing of the assigned to field on the CI and the Asset. Then use the CI side to reflect what the device management software is reflecting for top console user (SCCM), last logged in user (SCCM) with the assigned to on the asset record reflecting who is responsible for the device. Often times the party PC's have someone that is responsible for the management of those devices, like a lab room or loaner equipement, etc...
Also leverage the newer attribute on the asset called Asset function and set the value to shared.
