If you are having issues with your Workspace ONE Assist performance or service, consider troubleshooting your issue before calling support.

These troubleshooting steps address the most common issues with the Workspace ONE Assist service. The problems below are grouped by category. Some problems may have more than one possible cause and solution.

Generate Certificates


While running the "Certificate Seed Script.sql" file in Step 10 of the Generate Workspace ONE Assist Certificates task, you might see an error. This error reads "The conversion of a varchar data type to a datetime data type resulted in an out-of-range value."

Possible cause

Such an error is likely the result of a difference in locale between the machine upon which the SQL script was generated and the database server on which it is being run.


There are two possible solutions.

  • Ensure that the same date format is set in the SQL script by running the cert provisioning tool on a machine with the same locale settings as the database server.

OR (if the first solution is not possible).

  • Manually edit the date format in the SQL script. For more information about date formats, see http://www.sql-server-helper.com/tips/date-formats.aspx. References in this documentation to any specific service provider, manufacturer, company, product, service, setting, or software do not constitute an endorsement or recommendation by VMware. VMware cannot be held liable for any damages, including without limitation any direct, indirect, incidental, special, or consequential damages, expenses, costs, profits, lost savings or earnings, lost or corrupted data, or other liability arising out of or related in any way to information, guidance, or suggestions provided in this documentation.

Remote Management Not Available - Device Registration Issues

Problem - Workspace ONE Assist Link Does Not Display in Workspace ONE UEM

"Remote Management" link does not display in the More Actions drop-down menu as seen in Device Details View OR device is not shown in the Device List View.

Possible cause

Registration failed or Intelligent Hub might not have been deployed properly. Intelligent Hub might have not been installed on the device properly or registration to Workspace ONE Assist Server has failed.


Attempt to re-register the device. Update Resource portal to ensure that Intelligent Hub can be properly downloaded and installed on device. A Workspace ONE UEM administrator must re-register the device.

Problem - Registration Check Returns Failed

Device does not register with Workspace ONE UEM or the Workspace ONE Assist portal.

Possible cause

P7b file missing root/intermediate certificates in certificate chain. In MMC (Microsoft Management Console) certificate console when opening the certificate, the certificate path is missing and certificate status displays: the issue of this certificate can not be found.


Reinstall the certificate including intermediate and root certificate. Reinstall all the certificates for this client and ensure that the root certificate is placed into the root certificate folder and the intermediate certificate is placed in intermediate certificate folders in the MMC certificate console.

For more information about the device registration failed error, see the knowledge base article, 'Device registration check failed' error is displayed in Workspace ONE UEM Console when initiating a remote session on enrolled devices.

Problem - Error Message, 'Registration Failed: Server Not Found'

Device does not register with Workspace ONE UEM or the Workspace ONE Assist portal.

Possible cause 1

Workspace ONE Assist Site URL capital and lower-case letters. In Workspace ONE Assist tool versions and prior, the URL for remote management server is CAPS sensitive. In the example shown below, the URL uses upper-case and lower-case letters ‘https://rmSTAGE01.awmdm.com’.

Solution 1

Remove upper case characters from the Workspace ONE Assist site URL. Review the Workspace ONE Assist site configuration. You must ensure that the URL has all lower-case letters. In the example above, the URL must be ‘https://rmstage01.awmdm.com’.

Possible cause 2

Firewall is ON but misconfigured. If the firewall is incorrectly configured on the Workspace ONE Assist Server, it might be preventing device registrations from being received.

Solution 2

Turn off firewall or set up exceptions. When the firewall is on and it is not correctly configured, it might be preventing device registrations. Devices register with the Anchor web service, hosted on port 443 on the Workspace ONE Assist server. If this port is blocked on the firewall, registrations are jeopardized. Turn off the firewall and see if registrations succeed. If they do, review the exceptions to ensure that the Anchor web service on port 443 or other port defined for this service is in the list of exceptions.

Problem - Error Message, "RM failed to register. Certificate invalid server."

Possible Cause:

The device fails to register because the Assist agent does not trust the enrollment certificate. This certificate was bundled in the Workspace ONE Assist installer up to version 20.07 and had to be updated periodically.
Note: This error does not apply to iOS.


To resolve this error, upgrade the Workspace ONE Assist agent to v20.11 or later. If the issue persists, please contact Workspace ONE Support.

Workspace ONE Assist Agent v20.11 has removed the dependency on the deployment certificate on all platforms (Android, Win10, macOS, iOS, and Windows CE). Instead, the Assist Agent builds the certificate chain with the embedded root and intermediaries; and receives the deployment and leaf certificates from the Assist server. This implementation ensures that the Assist application only makes enrollment requests to a trusted Workspace ONE Assist server, and all connections are secure.

Issues Connecting to Devices

If you are having connectivity issues with your Workspace ONE Assist performance or service, consider troubleshooting your issue before calling support. These troubleshooting steps address the most common connectivity issues with the Workspace ONE Assist service.

Problem - Browser Window Does Not Open Remote Management Portal

The Workspace ONE Assist portal is not opening on Workspace ONE UEM users’ browser window.

Possible cause 1

Incompatible web browser. The browser being used by VMware Support staff is not compatible with Workspace ONE Assist.

Solution 1

Use a different web browser. Install or switch to a compatible browser. The following is a list of browsers currently supported by the Workspace ONE Assist Tool.

  • Google Chrome
  • Safari

Possible cause 2

Browser pop ups are blocked. The browser being used is blocking pop-up windows from the Workspace ONE Assist portal.

Solution 2

Enable pop-ups in browser settings. UEM console users must update their browser settings to allow pop-ups from the Workspace ONE Assist portal.

Problem - Remote Support Validation Fails

During Workspace ONE Assist validation steps, one or all the three validation steps and ‘Launch Session’ button does not appear.

Possible cause(s): Certificate mismatch, Workspace ONE Assist server issues. Client-server certificates might be incorrectly deployed or there might be issues with availability of Workspace ONE Assist server and console.

Solution: Review certificates and ensure that Workspace ONE Assist servers are operational. Ensure that T10 interface certificate has been properly deployed on the Workspace ONE Assist servers, ensure that Workspace ONE Assist servers are online and operational.

Modify Database Record for Multi-Node Configuration

In order for the Workspace ONE Assist server to operate correctly in a multi-node configuration, you might need to modify DB records in [ApAdmin].[dbo].[Server].[FQDN]. Some installations result in these tables pointing to the external Virtual IP (VIP) address by default. This default arrangement must be changed.

Note: Active-passive configurations with standard, all-in-one installations do not need this FQDN change inside the database table. Applying this change in such an environment might break the configuration. Consult with support if you are unsure which configuration you have.

Ensure that each [FQDN] record in the [ApAdmin].[dbo].[Server] table in the database points to the internal IP address of the VIP (also known as Virtual IP) for the load balanced pool.

The number of [FQDN] records is equal to the number of application/connection proctor servers in your deployment. Therefore, you must update each one in the table. For example, if your deployment has four connection proctor servers, then you must locate and modify 4 [FQDN] records in the [ApAdmin].[dbo].[Server] table.

After you finish the record modification, restart all Workspace ONE Assist Servers.