Here you should use the public SSL certificate you installed on IIS for your Device Services server. Make sure that REST API is enabled in the OG where you are enabling AWCM. Make sure that AWCM is enabled in the Site URL’s page in the Air Watch Console. The Internal Service URL should contain https:// instead of and should have the port number after the URL and “/awcm” at the end. If this page doesn’t come up or if there is an SSL error stop and fix it before you go on.
Check the SSL Certificate common name, it should match the name of the DS URL.
Use the Test Connection button to ensure that Air Watch is connecting and authenticating properly to your directory system.
SSL certificates are used on millions of websites to provide security and confidentiality for online transactions.
However, there are a few problems that can occur with their deployment that cause error messages to be shown to website visitors.
This article lists some of the common issues and methods for troubleshooting Global Protect.
The article assumes you are aware of the basics of Global Protect and its configuration.
Depending on the cause of the connection error, internet browsers will usually display a warning messages such as "This Connection is Untrusted", "The site's security certificate is not trusted" or "Your Connection is not private".
The SSL certificate for this website is not trusted Certificate Name Mismatch Error Mixed content Error An internet browser will state that a website certificate is untrusted if that certificate has not been signed by a trusted Certificate Authority.
While uncommon, it is possible for an installation of Java to become corrupt.
You can uninstall it and re-install ACC to have Air Watch install the correct version OR you can determine what version is currently installed in the Windows Add/Remove Programs panel, and download the version from the Oracle website: The other common issue can occur during Windows updates where the Java installation path gets removed from the System Variables, preventing Windows from running Java applications properly.
This is most commonly caused by either a networking issue (ACC cannot reach AWCM) or an issue with Java installed on the server.