Limiting users to a single device
(New in 5.18)
mSuite can be configured to limit each mSuite user account to a single device. When this feature is active, if a user tries to connect with a different device than the one they previously used, they will fail authentication and so will not be allowed to access the system from that "new" device. They will still be able to use the system with their original device.
Before enabling this feature, you should check to see if any mSuite user accounts currently have more than one device associated with them and, if so, delete the additional devices so that each account only has one device. Failure to do this will result in some users not being able to access the system.
To identify all mSuite user accounts that currently have more than one device entry, use SQL Server Management Studio (or equivalent) and run the following query on the mSuite SQL database:
The first time a user's device successfully connects to the mSuite system, it is given a Device ID which is stored in the mSuite database.
Every time a user's device connects and authenticates, the system checks to see that the current device's Device ID matches the one that is stored in the database for that user account. If not, the authentication fails and an alert is generated (provided authentication alerts are enabled).
In order to allow a user to connect a "new" device to the system, the administrator needs to delete that user's existing device record from the Devices view in the mSuite Administration Console.
The definition of a "new" device differs between EAS devices and full mCenter clients:
The mSuite Device ID is associated with the device's serial number which does not change. So, even if a device has been wiped and/or restored to factory settings, provided it is being used with the same mSuite user account, it will still be recognised by mSuite and will not be considered as "new".
WM devices running the full 'mCenter' client
If the 'mCenter' client is removed and re-installed (or the device is hard reset and the 'mCenter' client is re-installed), its mSuite identity changes. So, even though it is the same physical device, it is seen by the mSuite server as "new" and is not therefore allowed to connect to the system.