PENDING User doesn't see all linked application in his software center on certain devices

[Bart]

Hi all,
We have an issue with one user who is not able to see linked application in his software center on new staged devices. The user is primary user of these devices.
He has still his original device on which he is able to install software via Software Center. We staged two new devices and on this devices he doesn't see the same software as on his original device.
Other users do not have this problem.Even users which logon to those devices see their linked applications.So, it must be something user related I suppose.

SCCM version 2309 (5.00.9122.1000)
Client OS WIndows 10 22H2 (new device) and 21H2 (original device)
Automatically configure User device affinity is set to No
We are using AD security groups to link a user to a SCCM user collection which is used for deployment.

Any ideas?

Kind Regards,
Bart

 

[Garth]

what do the log say? What troubleshooting have you done?

 

[Bart]

Hi Garth,
I verified the UserAffinity.log. The errors in that log are common errors I also see in the log of other users:

Printscreen from original device (works like it should)
Printscreen from new staged device. Only difference is unsetting auto affinity (which is I think actually the correct setting).

We always add the primary user ourselves to the device. It is automatically done by an import script (which is in place for several years without any issue). And we also see in SCCM that the primary user is added.
It looks like the SCCM client does not get any linked application when requested to the SCCM server.

Are there other logs related to the affinity or primary user setting which I can verify or compare?

 

[Garth]

What does user affinity have to do with deployments?

 

[Bart]

All our applications have a requirement that the user should be primary user of the device. Otherwise the application will not be available for install in Software Center.
Users must request for the availability of an application. When allowed they are added as member of the AD security group for the requested application. The security group is linked with a deployment (install) on the application. So, when they are not primary user they will not see any application even when they are member of the security group. Therefor we always make them automatically primary user of their device and let not SCCM decide based on the usage.