After you install and configure Workspace ONE UEM, you can verify that the installation was successful. By verifying the installation, you can ensure that all components are functioning correctly.

Verify the Correct Site URL Population

During the Workspace ONE UEM installation, your URLs populate on a system settings page. Learn more about how to verify your URLs have populated correctly.

The Workspace ONE UEM system settings have a page that displays your site URLs. Verify these values have populated correctly as part of the installation.

  1. Open a browser and access the console using the publicly signed URL.
  2. Verify the Workspace ONE UEM version by selecting AboutWorkspace ONE UEM.
  3. Log in to the Workspace ONE UEM console by selecting a language, if applicable, and entering your credentials.
  4. Accept the terms of use.
  5. Define a Password Question and/or Security PIN.
  6. Verify Correct Site URL Population.
    1. Navigate to Groups & Settings > All Settings > System > Advanced > Site URLs and verify the URLs populated correctly.

      The only Site URL that might include “localhost” is the Peripheral Service URL. Google Play has a hostname connected to a port number.

  7. Change SOAP and REST API URLs from the Workspace ONE UEM console URL to the Workspace ONE UEM Devices Services server URL:

    For example, https://acme-console.com /AirWatchServices becomes https://acme-ds.com /AirWatchServices and https://acme-console.com/API  becomes https://acme-ds.com/API.

    Workspace ONE UEM recommends a standalone API server, for deployments of up to 100,000 devices and higher, in which case, change the Site URL to match your dedicated API server URL.

Verify Connectivity

After the installation has completed, verify connectivity between your various endpoints to ensure they are operational. Learn more about how to verify connectivity with Workspace ONE UEM endpoints.

After installation, navigate to the various endpoints for each of the installed components to ensure that they are up and running.

  1. Navigate to https://localhost/AirWatch from the Console server. An SSL error displays. Select to Proceed anyway and then the Workspace ONE UEM console login page displays.
  2. Navigate to https://localhost/DeviceManagement/Enrollment on the Device Services server. On a device connected through data network connection or internal Wi-Fi, navigate to https://<DS_URL > /DeviceManagement/Enrollment.
  3. From the Workspace ONE UEM Devices Services Server, if that is where you installed the AWCM component, verify AWCM communication by opening the status page: https://<DS_URL > :2001/awcm/status.

Verify Workspace ONE UEM Services Are Started

After installing Workspace ONE UEM, start each service for the installed components to ensure they are running. Learn more about how to verify your Workspace ONE UEM service have all restarted upon complettion of the installation.

The Workspace ONE UEM installer properly configures the associated Windows services, and the start type and recovery options for each service should not be modified. If services are not automatically restarted, use Windows Services Manager to reset Window Services to Automatically Delayed Start.After a typical installation, open the Windows Services Manager to verify that the installed component services are running.

  1. Open the Services Manager.
  2. From the left pane, select Local Server then navigate to Tools > Services.

    You will see all AirWatch Services at the top of the services list in alphabetical order. Each of these services start with AirWatch in the name.

  3. Verify that each of these services show Started as the Status.

Validate GEM Functionality

In addition to verifying other services are up and running, GEM Inventory Service has its own validation steps to make sure the service is operational. Learn how to validate GEM functionality with Workspace ONE UEM.

After installation, ensure that the GEM Inventory Service is up and running.

  1. On your Console server, navigate to C:\AirWatch\Logs\Services\. Delete the AirWatchGemAgent.log file.
  2. Open the Server Manager.
  3. From the left pane, select Local Server and navigate to Tools > Services.
  4. You will see all Workspace ONE UEM Services at the top of the services list in alphabetical order. Each of these services start with AirWatch in the name. For the AirWatch GEM Inventory Service, right-click and select Restart.
  5. To see if a log regenerates, select the C:\AirWatch\Logs\Services\ folder. If a log regenerates with errors, contact Workspace ONE UEM Support for further assistance.

    If you do not see a log file in this folder, then this is normal. You do not need to contact Workspace ONE Support.

Deactivate Services on Multiple Console Servers

Some of the Workspace ONE UEM services can only be active on one primary console. Learn how to deactivate applicable services on servers.

To ensure maximum performance, certain Workspace ONE UEM services must only be active on one primary console server. If you deploy these services, deactivate them on non-primary servers after you have fully installed Workspace ONE UEM.

Workspace ONE UEM Services that must only be active on one server are:

  • AirWatch Device Scheduler
  • Directory Sync
  • Content Delivery Service
  • AirWatch GEM Inventory Service
Note: This task is only applicable if you have multiple console servers.

Deactivate these services on any console servers other than the primary server:

  1. On your non-primary console servers, open the Server Manager.
  2. From the left pane, select Local Server and navigate to Tools > Services.
  3. The active Workspace ONE UEM Services at the top of the services appear in alphabetical order. For the AirWatch Device Scheduler, Directory Sync, Content Delivery Service, and AirWatch GEM Inventory Service, right-click and select Stop.
  4. After the services have stopped, change the Startup Type for each service to Manual or Disabled. Changing the Startup Type prevents the service from restarting after any reboot.
  5. When you upgrade your Workspace ONE UEM console, the Content Delivery Service automatically restarts. To maintain expected performance, manually deactivate the applicable services again on all extra servers.