We probably all know these blurry images appearing in Lync 2013 clients during the Lync call.
The image distortion results from the difference between the maximum image size that can be stored in the thumbnail Photo attribute in Active Directory (96×96 pixels) and the size of the photo in the Lync call window.
Be advised that the KB3206632 update for Windows Server 2016 is a whopping 1 GB. The biggest change for Exchange Server 2013 is support for . Be advised organizations running Exchange 2016 or 2013 on . Both Cumulative Updates introduce an important fix for indexing of Public Folder when they were in the process of being migrated.
NET 4.6.1 should start testing with and planning to deploy . To ensure proper indexing, it is recommended to move public folder mailboxes to a different database so they will get indexed properly.
Many times in previous Exchange upgrade/migration engagements, I have come onsite to the customer’s environment to find that they have already made an unsuccessful attempt to begin installing the new Exchange infrastructure.
Many times this is due to simple things, like not properly patching the servers first, or maybe not having the proper permissions in Active Directory to make the necessary schema changes.
This KB fixes – among other things – the problem with DAG members experiencing crashing IIS application pools.However, when you pull back the shades from all the spotlight, you’ll hear administrators asking the same question, “What’s better now and what can it really do it to improve my environment?” For those running Exchange 2013, do not expect to be wowed.As with every new product version, there’s always something shiny and new to discuss.The new features and all the greatness it can bring to your messaging environment will be discussed and analyzed like a Monday night football game.