Monday, September 26, 2016

I needed to access a Cisco UCS Blade enclosure at one of my customers after a major ESX failure. When attempting to access the KVM over the Java applicate for the Cisco UCSB-B200-M3 blade servers, I received the following error:

The viewer has terminated.Reason: The network connection has been dropped.

After troubleshooting the issue for a while, I decided to downgrade my version of Java to an older build. I tried the following build of Java in a Virtual Machine:

Java SE Runtime Environment 7u79

Success!

There is an issue with the latest Java build and the Cisco UCS KVM application.

Sunday, September 18, 2016

When migrating from Exchange 2013 to Exchange 2016, I encountered an error 0x80190194 when downloading the Offline Address Book on workstations.

0x80190194 The Operation Failed

0x80190194 is a very common error when downloading the OAB and there are many server side problems which can generate this error.

Exchange 2013 by default had the servers responsible for the Offline Address Book hard coded as a Virtual Directory as shown below.

In Exchange 2016, by default we no longer want to hard code the Virtual Directories and instead enable GlobalWebDistribution which allows the Autodiscover service to automatically select the best Virtual Directory for the distribution request.

To set this up, we want to ensure the VirtualDirectories attribute for each Offline Address Book is set to $null. We also want to ensure GlobalWebDistribution is enabled so that Autodiscover can take care of it.

Monday, September 12, 2016

This issue may be encountered when migrating to Exchange 2016 from Exchange 2013 when MAPI over HTTPS is enabled. The default Exchange 2013 MAPI over HTTPS authentication settings set IIS and Internal Authentication methods as Negotiate and External as null. This is shown below:

The Default Exchange 2016 MAPI over HTTPS authentication settings are configured as "Ntlm, OAuth and Negotiate"

Proxying MAPI over HTTPS connections between Exchange 2016 and Exchange 2013 requires NTLM be enabled. The default Exchange 2013 MAPI over HTTPS authentication settings will cause Outlook connectivity issues when both Exchange 2016 and Exchange 2013 are in the same Active Directory site.

The error which is generated by the Exchange Remote Connectivity Analyzer in this configuration is as follows: