The console page that should be used to see this information is Devices > List View > Device Details View > More > Troubleshooting. This page allows the administrator to view various information about a specific device, such as profile status, application status, device-related logging, compliance status, commands history, and so on. This page can help troubleshoot issues related to device enrollment, configuration, management, and communication.

The component that should be focused on when troubleshooting this device connectivity issue to VMware Workspace ONE UEM is Device Services. Device Services is a component of Workspace ONE UEM that handles device enrollment, management, and communication. Device Services also hosts the AWCM service, which is responsible for delivering push notifications to devices. If Device Services is not working properly, devices may not be able to check in with Workspace ONE UEM or receive profiles, commands, or policies3.

The service that the organization administrator has direct control over to enable verbose logging to troubleshoot this issue is ACC (AirWatch Cloud Connector) service. ACC is a service that integrates Workspace ONE UEM with internal enterprise systems, such as Active Directory or Certificate Authority. ACC enables Workspace ONE UEM to use internal resources without exposing them to the Internet. If some users are unable to enroll their devices using their Active Directory accounts, it could indicate that there is a problem with ACC configuration, connectivity, or synchronization. Enabling verbose logging for ACC can help identify and troubleshoot the root cause of the issue.

The log file that should be viewed is On the Device Services Server \Logs\Services\InterrogatorQueueService.log. InterrogatorQueueService.log is a log file that records the profile samples from devices and updates them in the Workspace ONE UEM console. Profile samples are data that show the status and details of profiles installed on devices. If profile status on multiple devices is not updating, it could indicate that there is a problem with InterrogatorQueueService configuration, connectivity, or performance. The administrator should view and analyze the InterrogatorQueueService.log file to identify and troubleshoot the issue.

The possible root cause of this issue is that the Secure Email Gateway server is unable to connect to the Exchange server. This could be due to network issues, firewall settings, or authentication problems. If the Secure Email Gateway server cannot communicate with the Exchange server, it will not be able to deliver email to the newly enrolled devices. The previously enrolled devices may still be able to receive email because they have cached credentials or sessions with the Exchange server. The users who reported this issue are able to access their email through OWA on their computers because OWA does not rely on the Secure Email Gateway server.

The most likely cause of this issue is that the VMware Workspace ONE administrator set “RAM Required” for the application in the “Details” tab options. The “RAM Required” option specifies the minimum amount of RAM needed for the application to run on Windows devices. If some devices do not meet this requirement, they will not be able to complete the installation of the application. The administrator should check and adjust the “RAM Required” option for the application according to the device capabilities.

The communication path that should be reviewed is AWCM outbound to UAG. AWCM (AirWatch Cloud Messaging) is a service that delivers push notifications to devices and enables device-based commands from the Workspace ONE UEM Console3. AWCM also communicates with UAG (Unified Access Gateway) to send server traffic rules for tunnel to proxy certain URLs. If AWCM cannot communicate with UAG, the server traffic rules will not be updated on UAG and the sites/apps will be proxied incorrectly. The administrator should check and resolve any issues with AWCM outbound to UAG communication.

 The form of logging that should be used to accomplish this goal is device-based targeted logging. Device-based targeted logging allows the administrator to enable debug logging for multiple devices at once, based on various criteria, such as platform, model, ownership, and so on1. Device-based targeted logging can help collect more detailed information about device events, actions, and errors for troubleshooting purposes.

The feature that is included in VMware Workspace ONE Assist in Attended Mode is view and export detailed device information, access activity logs, run commands, and manage files. This feature allows the administrator to remotely access the device screen and perform various actions to troubleshoot issues or assist the user. The administrator can also view the device details, such as battery level, network status, memory usage, and so on. The administrator can also access the device logs, run commands such as ping or traceroute, and manage the device files1.

The most likely cause of this test connection failure is that the provided Workspace ONE Access API key is incorrect. The Workspace ONE Access API key is required to establish a secure connection between Workspace ONE UEM and Workspace ONE Access services. If the API key is incorrect, the test connection will fail and the integration will not work. The administrator should verify and correct the API key in the Workspace ONE UEM console1.

The step that would assist in troubleshooting this problem is using network traffic tools to capture Android traffic. Network traffic tools, such as Wireshark or Fiddler, can capture and analyze the network packets sent and received by the Android devices3. This can help identify any errors, delays, or anomalies in the communication between the devices and the console. Network traffic tools can also show the HTTP headers and body of the requests and responses, which can provide more information about the device status and configuration.

The root cause of this problem is that this organization group is not a Customer type OG. The Hub Services settings page is only available for Customer type OGs, which are the top-level OGs in the hierarchy1. The Hub Services settings page allows the administrator to configure various features and services for the Intelligent Hub app, such as notifications, people, home, and catalog1. The administrator should navigate to the Customer type OG to access the Hub Services settings page.

The strategy that accurately describes the solution for this problem is running the keytool import targeting the new certificate. The AWCM keystore is a Java keystore file that contains the SSL certificates used by AWCM to establish secure connections with devices and other components. If the SSL certificates are rotated on IIS and the load balancer, but not on the AWCM keystore, then AWCM will not be able to communicate with devices using push notifications. To resolve this issue, the administrator must import the new SSL certificates into the AWCM keystore using the keytool command2.

The action that the administrator should take to resolve this status is to contact the user and ensure the iOS device is unlocked and powered on. The NotNow status means that the device has received the profile but has not installed it yet2. This could be because the device is locked, powered off, or has a pending user action. The administrator should ask the user to unlock the device, power it on, and accept any prompts or notifications related to the profile installation.

Flushing the cache via the Workspace ONE UEM console. Memcached is a service that caches data in memory for faster access and performance. If a configuration value is updated in Workspace ONE UEM, it may take some time for Memcached to refresh the cached data and reflect the new value. Flushing the cache via the Workspace ONE UEM console can force Memcached to clear the cached data and update it with the latest value.