5V0-62.22 · Question #24
An administrator has been troubleshooting an issue where a single device is unable to check in to VMware Workspace ONE UEM and receive commands All services are functioning, and this issue appears…
The correct answer is D. Gather Device Side Logging. The troubleshooting step that should be taken next to find the root cause, while not causing any data loss to the end user's device, is to gather device side logging. Device side logging can help collect more detailed information about device events, actions, and errors for…
Question
An administrator has been troubleshooting an issue where a single device is unable to check in to VMware Workspace ONE UEM and receive commands All services are functioning, and this issue appears to be isolated to this specific device. Service logs have also been reviewed and do not show any instances of communication with the device in question. Which troubleshooting step should be taken next to find the root cause, while not causing any data loss to the end user's device?
Options
- BRenew the Device Root Certificate.
- CUse Device Wipe, and then re-enroll the device.
- DGather Device Side Logging.
How the community answered
(20 responses)- B10% (2)
- C15% (3)
- D75% (15)
Explanation
The troubleshooting step that should be taken next to find the root cause, while not causing any data loss to the end user's device, is to gather device side logging. Device side logging can help collect more detailed information about device events, actions, and errors for troubleshooting purposes. Device side logging can be enabled from the Workspace ONE UEM console or from the device itself. Device side logging does not affect the user's data or settings on the device.
Topics
Community Discussion
No community discussion yet for this question.