The location reporting feature in FileWave is disabled by default. It is recommended that you; verify that this feature is in accordance with your organization’s policies and AUP (Acceptable Use Policy). Notify your end users before activating location reporting, as enabling the feature will prompt for permission to location information.
If there are any reasons, legal or otherwise, that you do not wish to enable tracking on a global level within your organization, your FileWave license can be adjusted to enable personal mode. This will disable devices from sending application usage as well as location information.
To have verify the current status of personal data collection. From FileWave Admin : Server Menu → "Activation Code..." → There you will see "Allow collection of personal data:" with Yes or No after it.
To have personal data enabled or disabled on your license, please submit a support ticket with "Personal data License" in the subject.
Only tickets from authorized support agents whose names are on the support contract will be accepted to adjust license personal data settings.
There are two different types of location tracking in FileWave, Passive Tracking and Lost Mode. macOs, Windows, Chromebooks, and Android devices use the Passive tracking to gather the location of the device without locking it down. Supervised iOS devices set to Missing mode will put the device in Lost mode, which locks down the device making it unusable by the end user.
When the iOS device is in Lost Mode do not reboot it. If the device losses Wifi you will no longer be able to take the device out of Lost Mode since it will no longer be connecting to FileWave.
When the device is in Lost Mode, a new option in the tools menu is available, "Play Lost Mode Sound (iOS 10.3+)"
This is receiving tracking data continuously.
Make sure location services is enabled.
Prepare the clients
MacOS and Windows - Be sure that "Disable Personal Data Collection" option in the client preferences of your clients is not checked.
You can set the "Disable personal data collection" one at a time with Client Monitor or Create a Superprefs (Creating a Superprefs Fileset) to change them in bulk.
iOS - Make sure the same version of your server is also the Enterprise version of the FileWave App Portal .ipa has been sent out to all your
|iOS devices: Can be downloaded from the FileWave Server download page near the bottom|
Force enable location tracking server side
By force enabling EMM tracking you are ignoring "Allows collection of personal data" in your license. Even is the license is set to false, this will collect data.
settings.EMM['FWCLIENT_FORCE_ALL_DEVICES_TRACKING_ENABLED'] = True
Right click on your macOS, Windows, Chromebook, and Android device(s)
|For multiple devices use the filter options at the top of the client view, then select all|
Select Normal from the "Client State" option.
Accept any device prompts
|iOS||macOS||Windows||Android (EMM may not prompt)|
Warning: In order to avoid legal issues concerning user location tracking, it is highly recommended that you enable location tracking only on devices when a unique user may authorize the service.
Any user can agree to tracking, admin or not. Only an administrator can disable location services and/or FileWave's rights to location, as per Apple Inc. policy
Any user can agree to tracking, can disable location services, and revoke FileWave's right to location, as per Apple Inc. policy
The Windows operating system does not prompt the local user for access to location. Later versions of Windows do have a location service that can be turned off.
Upon installing or upgrading the Android FileWave Client to version 10.1 or greater, the user is requested to approve all rights an application needs. This includes location services, running in the background and several other rights.
A user can turn off their location tracking at anytime, but you can make a policy fileset that will Force Location for EMM Android Devices
It is important to note the way a client verifies it is able to ask the system for location information.
For example setting the state to "Missing" but it has a Superprefs file telling it the refresh interval is 0 See the flowchart for reference: