I have been working on a large System Center 2012 deployment recenetly and we needed to get SCCM User Device Afiinity working to feed Service Manager with Asset owners.Nice and easy, created an GPO to audit successful logon events, set a client policy with User and Device Affinity settings, everything was good or thats what i thought…….All of the Windows 8 clients started showing Primary Users as windows manager\dwm-1 (or dwm- some number)

I have been working on a large System Center 2012 deployment recenetly and we needed to get SCCM User Device Afiinity working to feed Service Manager with Asset owners. Nice and easy, created an GPO to audit successful logon events, set a client policy with User and Device Affinity settings, everything was good or thats what i thought…….All of the Windows 8 clients started showing Primary Users as windows manager\dwm-1 (or dwm- some number)UDA_1I am delving more into this to see if i can either stop Windows 8 logging these events or for SCCM to not use them, either way i’ll keep you posted. UPDATE So I have been messing around with this issue for a little while and have come up with a couple of ideas/solutions. The first one is to configure SCCM so that we have to approve all affinity data and hence we just would not approve the entries for window manager\dwm-1 This obviously is not really acceptable if we want things automated. The second and preferred solution is to still allow the automatic affinity associations but break out the PowerShell to manage the incorrect mapping we get. Below is a script that could be scheduled to run on a regular basis (and in my situation just prior to my SCSM import connector running)
$Devices = get-CMUserDeviceAffinity -username "window manager\dwm-*"
Foreach ($Device in $Devices)
{
Remove-CMUserAffinityFromDevice -ResourceID $Device.ResourceID -UserName $Device.UniqueUserName -Force
}