Three main reasons to run into a unexpected User Mode entries in the SEPM:
AD import of user objects. If a computer does not match an imported computer object (computer name/computer domain) and matches an imported user object (user name/user domain), the computer will be in user mode.
A “new” computer checks in to the SEPM and does not match any existing SEPM entries. Its preferred mode is 0 (user mode). As other “new” computers check in, they may have the same user name/user domain as one of the user entries created by this first computer. Keep in mind, this will only happen to computers that act like new entries in the SEPM (purged due to client timeout, deleted by administrator, OS uninstall/reinstall causing new hardwareID to be generated).
A SEPM administrator switches one of the computer entries to user mode. “new” computers that have one of the user name/domain combinations that match will be added as user mode. Once again, this only affects computers that appear as new to the SEPM (don’t line up with existing entries due to purge by client timeout, administrator deletion, new HWID, etc).
Are you importing AD user objects?
Can you avoid importing these objects if you do not intend to use them?
Were any clients installed in User Mode?
Check the ersecreg.log and ersecreg-1.log for any computer that is sending:
Preferredmode=”0”
What is the client timeout configuration?
You may need to increase this value to more appropriately match the environment in order to prevent clients from purging too early.
Did youconverted any computer objects to user objects?