Omnissa Workspace ONE (Airwatch) - Run Admin Command

Omnissa Workspace ONE (Airwatch) - Run Admin Command performs administrative commands on enrolled devices for:

Assets returned by the selected query or assets selected on the relevant asset page.

See Creating Enforcement Sets to learn more about adding Enforcement Actions to Enforcement Sets.

📘
Note

Not all asset types are supported for all Enforcement Actions.

See Actions supported for Activity Logs, Adapters Fetch History, and Asset Investigation modules.

See Actions supported for Aggregated Security Findings.

See Actions supported for Software.

Required Fields

These fields must be configured to run the Enforcement Action.

Action name - The name of this Enforcement Action. The system sets a default name. You can change the name.
Configure Dynamic Values (optional) - Toggle on to enter a Dynamic Value statement. See Creating Enforcement Action Dynamic Value Statements to learn more about Dynamic Value statement syntax.

Use stored credentials from the adapter - Select this option to use credentials from the adapter connection. By default, the first connection is selected.
- When you select this option, the Select Adapter Connection drop-down becomes available. Select the adapter connection to use for this Enforcement Action.
  📘
  Notes
  - If you do not select this option, you must provide connection credentials as Additional Fields.
  - Connection Grouping: When using stored adapter credentials, devices are automatically grouped by their connection ID to ensure each device is wiped using the correct Workspace ONE UEM instance.

Compute Node - The Axonius node to use when connecting to the specified host. For more details, see Working with Axonius Compute Nodes.

Admin Command - Select the administrative command to execute on the devices. Currently the only available option is:
- Enterprise Wipe - Unenroll the device and remove all managed enterprise resources including applications and profiles.
  📘
  Notes
  - This action cannot be undone.
  - The device must be re-enrolled before Workspace ONE UEM can manage it again.
  - This action requires the device UUID from the Workspace ONE adapter. Ensure devices have been discovered by the Omnissa Workspace ONE (Airwatch) adapter before running this action.

Additional Fields

These fields are optional.

💡
Connection and Credentials
When Use stored credentials from the adapter is disabled, some of the connection fields below are required to create the connection, while other fields are optional.

AirWatch Domain - Base domain for the Workspace ONE UEM API (e.g., asXXX.awmdm.com or https://asXXX.awmdm.com). /

Authentication Method - Select the authentication method to use:

User Credentials - Authenticate using the following fields: User Name, Password, and API Key.

OAuth - Authenticate using the following fields: Client ID, Client Secret, and Access Token Domain where you can select between 4 possible domains.

Refer to the adapter documentation for explanations on the above fields.

API Rate Limit (Calls per Minute) - Enter a rate limit for the number of requests per minute to be sent to Omnissa. If left empty, the number of requests initiated by the connection for this adapter will be unlimited.

Verify SSL, HTTPS Proxy, HTTPS Proxy User Name, and HTTPS Proxy Password - Refer to the adapter documentation for explanations on these optional fields.

Gateway Name - Select the Gateway through which to connect to perform the action.

Devices per Request - Number of devices to process in each API request. Default: 50. Valid range: 1-1000.
- For large device lists, consider using smaller batch sizes to avoid API timeouts.

APIs

Axonius uses the Workspace ONE UEM MDM API - POST mdm/devices/admin-actions/{action}

Required Ports

Axonius must be able to communicate via the following ports:

TCP port 443 (HTTPS)

Required Permissions

The stored credentials, or those provided in Connection and Credentials, must have the following permission(s) to perform this Enforcement Action:

REST API Devices Execute - Enables access to execute APIs in the Devices collection, including administrative commands such as Enterprise Wipe.

📘
Note
Permission names are based on the Workspace ONE UEM console role configuration. The exact permission names should be confirmed with your Workspace ONE UEM administrator, as they may vary based on your environment configuration and version.
For more information about configuring API user permissions in Workspace ONE UEM, see the Using UEM Functionality With a REST API documentation.

To learn more about Enforcement Actions, see Enforcement Actions.

Version Matrix

This Enforcement Action was tested only with the versions marked as supported, but may work with other versions. Please contact Axonius Support if you have a version that is not listed and it is not functioning as expected.

Version	Supported	Notes
2604	Yes	Tested with Workspace ONE UEM release 2604