VMware 5V0-62.22 Exam With Confidence Using Practice Dumps

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 statement that describes the root cause of this issue is that the protocol is missing in the Secure Email Gateway hostname value. The Secure Email Gateway hostname value is the URL that Workspace ONE UEM uses to connect to the Secure Email Gateway edge service on UAG and perform email management tasks, such as quarantine, wipe, or block. The protocol is required to indicate that the connection is secure and encrypted. If the protocol is missing, Workspace ONE UEM will not be able to connect to the Secure Email Gateway edge service, and the test connection will fail. The administrator should add the protocol to the Secure Email Gateway hostname value.

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.