Skip to main content

Configure Android Enterprise in FileWave

Android management requires a binding between FileWave and an Android Enterprise organization at Google. Before starting, check whether the intended enterprise is already configured. If it is working, keep it and continue to Android Enrollment; do not create another binding. Google describes managed Google Play accounts enterprises and managed Google domains.

FileWave supports:

  • Fully Managed Android Devices
  • Personal Devices (BYOD)
  • Zero-Touch Enrolment (reseller registered devices)

Details of supported versions of Android OS may be observed in the FileWave Downloads pages.

Android Communication

Google's design for device management is very much a straight line of communication, with Google acting as a relay of information.  Strictly speaking, devices are enrolled with Google.  A binding is created between FileWave and Google, providing FileWave the ability to define configuration, instal Apps and send commands to devices.

In FileWave 17.0, new enterprise connections can use FileWave Android Management Service (FWAMS), without an activation JSON file. Existing enterprises continue using their current connection, including their local service account token. Upgrading does not require recreating the enterprise.

Choose the setup route

For a new enterprise on FileWave 17.0, use FWAMS. The legacy route is for an existing service account JSON token; it is not a prerequisite for FWAMS, and new customers should not request a shared activation JSON. For a server running an earlier release, contact FileWave Technical Support about the appropriate setup or upgrade route.

If you are evaluating FileWave and need setup assistance, contact your assigned FileWave Systems Engineer (SE). Existing customers should contact FileWave Technical Support.

If you use a legacy service account JSON, keep it in secure storage. Do not post or forward it, or include it in screenshots.

Set up Android Enterprise

Before you bind an enterprise

Complete these checks for either new-enterprise setup route:

  • Have the organizational Google administrator available to complete registration and, when applicable, enable third-party Android management for the intended organizational units.
  • Ensure the Android connections in Default TCP and UDP Port Usage are allowed.
  • Use an administrator account permitted to configure EMM enterprises.

Review default enrolment global rules and policies before enrolling devices.  Google supports multiple EMM bindings.  Each has its own Enterprise ID and users or groups may be selected as a provider.  

Adding a third-party EMM affects Google endpoint management and Android app management. Advanced Google endpoint management cannot coexist with a third-party EMM; review Google's coexistence requirements before making changes.

If these services are already used in the organisation, review Coexistence Requirement for Google Managed Domains before continuing.

Do not replace or unlink existing enterprise configuration merely to follow this guide

Configure the enterprise binding

Create a new enterprise only when none is configured on the intended FileWave Server. A configured enterprise cannot be switched between FWAMS and legacy setup in this dialog. Contact FileWave Support to discuss a migration requirement; do not unlink or recreate a working enterprise to change routes.

EMM Configuration is located within:

  • Preferences > Google > Configure Enterprise.  FileWave permissions will be required to view this tab.

image.png

If this tab is missing, contact FileWave Support if you are an existing customer, or your assigned FileWave SE if you are evaluating FileWave. Once activated, the FileWave Central software will need to be re-opened to present this tab.

If a server service is required during any setup, ensure this is actioned by an internally authorised member of staff.  For hosted customers, please raise a request with FileWave Technical Support.

FWAMS connectivity

For FileWave 17.0 FWAMS connections, allow the FileWave Server to reach fwams.filewave.com, fwauths.filewave.com and servauth.filewave.com. Follow Default TCP and UDP Port Usage for connection requirements. Hosted customers should ask FileWave to handle any server-side changes.

Create a new enterprise in FileWave Central 17.0

If using Zero-Touch Enrolment, please follow Google's Zero-Touch Guide for linking the intended FileWave Server with Google.

  1. Open Configure Enterprise. For a new FWAMS connection, choose the FileWave Android Management Service setup method. No service account JSON upload is needed.
  2. If you intentionally need the legacy route and already have a service account token, select I have a service account token (Legacy) instead and use Choose File to supply that JSON. Complete only one setup route.
  3. Enter a recognizable enterprise display name and select Sign Up.
  4. Open the generated signup link and complete Google's Android Enterprise registration with the intended organizational account. Follow Google's prompts for your existing managed domain or new organization, review the terms, and finish registration.
  5. Wait for the FileWave success confirmation, then return to Central. Reopen Configure Enterprise if needed and confirm the expected enterprise is shown. Generating a signup link alone does not complete setup.

The expected enterprise must be shown and signup must finish without an error before you proceed to device enrollment. If Google registration completed but FileWave reports a setup/finalization error, keep that enterprise; do not start a replacement enterprise. Contact your FileWave support contact to resolve the error and complete setup.

If these do not display as intended, current customers please contact FileWave Technical Support, whilst evaluation customers should contact the appointed FileWave SE. 

Do not create enrolment tokens or attempt enrolment until all appears as expected.

Keep the configured enterprise. In FileWave 17.0, Unlink Enterprise removes FileWave-side EMM configuration and managed-device records when the enterprise no longer exists at Google. For a FWAMS enterprise, Delete Enterprise also deletes the enterprise at Google. These are removal operations, not setup-completion steps. Deleting an enterprise is destructive and can wipe managed devices; do not use either action to finish this exercise.

Next: enroll one Android device

FileWave recommends testing Android Enrolment, before attempting enrolments on larger groups of devices.  

Choose the ownership and management mode before following any factory-reset instructions.