Mobility Suite may be used for the soul purpose of managing Norton Mobile Security (NMS) on mobile devices, without the use of the Work Hub or MDM. Real-world scenarios may include the use of Mobility Suite in conjunction with a 3rd-party MDM vendor. The following instructions outline how to deploy and configure NMS in such a scenario.
Ensure that Threat Protection is properly licensed in Mobility Suite
Create an API key, if one has not yet been created:
In the Mobility Manager console, access: Settings > Mobility Manager configuration > APIs > Create New Access Key
Once the devices appear in the console, they will be associated with a special user account called Operational User (Note: This process is not immediate). This account exists for managing devices which do not have the Work Hub installed, and thusly are not associated with a typical user account.
To target these devices, and manage their NMS settings via Device Policy, create a new Device Policy or edit an existing policy:
Policies and rules > Device policies > <edit policy>
Click on the Groups field, and a new Device Group will be listed as unassociated device group. Add the unassociated device group under Groups to target these devices
Adjust the Threat protection settings as desired, then save the Device Policy
Devices will then receive the NMS settings as defined in the Device Policy (Note: This process is not immediate)
Subscribing will provide email updates when this Article is updated. Login is required.