Time for more Lync/Skype4B troubleshooting! We had a customer call in the other day. He had an older iPhone (4S, iOS 8) and still used Lync Mobile for iOS.

Now, it worked fine when he was on the go (which he was much of the time). But when he tried to log in while in the office, he sees a sign-in error: One of our Support Engineers went on-site with his iPhone 6 (iOS 9), running. He tried to connect to their server—and saw the same kind of error!

However, the download links for the V4 downloads are still provided for those that prefer to work with the V4 bootable images. Memtest for mac. Windows Downloads: • • • Linux/Mac Downloads: • • • Notes: • Installation and usage instructions are available on the • V4 Source code is no longer provided as a separate download however is still contained within the bootable images.

The Problem: iOS Looks at Internal Certificates and Says “Huh?” We encountered this error ourselves. Internally, just after building our Lync Server 2013 instance. It’s an issue with the device and Lync/Skype for Business’ internal certificates.

If I try to load Skype for Business on my Mac and log in on the network with my domain. If I put in the IP address of the internal server and our external address (though our. Then open the Keychain Access certificate management utility.

Ordinarily, the Lync Server/Skype for Business Server will send certificates out to devices for authentication. Depending on your location (e.g., which network you’re on), these certificates are deployed as external (outside the local network) or internal (within the local network) certificates.

After version 5.4 of the Lync Mobile iOS client, iOS began having trouble verifying certificate authenticity. It appears to happen much more on internal certificates than externals. As far as we can tell, there is no single cause we can point to. Even Microsoft isn’t sure. On both of the KB pages mentioning this error: • • They say, “The cause of each message is slightly different, but both errors are caused by the inability to verify the authenticity of a certificate or certification authority.”, with a little more detail, but no definite cause.

Which is okay—he gets to the important point fast. How to fix it. How to Install a Root Certificate on iPhone First, verify you have a trusted root CA (certification authority) installed. Likely you installed this during Skype for Business setup, and it’s fine, but it never hurts to check. (Reference on certificates during Skype4B Server setup: The solution to the internal cert error is simple: Install your Root CA certificate on the iPhone. There’s actually several ways. • Email it over.

Attach the certificate file to an email & send it to your iPhone. Tap the cert and you’ll see an installation screen with an Install button. After tapping that, you’ll probably see a warning: “The authenticity of ‘RootCert1’ cannot be verified.” Well, it’s your cert, so it’s OK to install. Tap “Install” and proceed. You should only need to do this once. • Post the cert file to a private URL for download. Doing this lets you follow the same installation process as emailing.

You’ll just use the iPhone’s browser (Safari, by default) to locate & install the root certificate. I recommend using a private, internal-only webpage for this. You don’t want any certificate file available for public download!

I hadn’t actually heard of this before. If you use a large number of Apple devices, the Configurator lets you configure them simultaneously. Like Group Policy on Windows systems. Adding a certificate via an Apple Configurator Configuration Profile automates the installation & deployment. Which method you use depends on your network setup.

We used email, as the customer in question didn’t use Apple Configurator and email was a fast (and successful) way to test. Have you encountered an internal certificate error in Lync/Skype for Business? Please comment or email on how you resolved it.

If you haven’t yet, I hope this post helps you do so!