As we can see, There is a near 2-1 ration of those who use Get-Help, even occasionally, to those who don’t use it at all. This would seem to indicate that this is a rather integral feature in Exchange that administrators expect to be working. However, since around CU3 for Exchange 2016, any Exchange 2016 server installed on the Windows Server 2016 OS will find Get-Help broken. On the first run of Get-Help for a cmdlet, an administrator is met with:
Wow. What the? So this is a bug. It does not exist in Exchange 2013, of any flavor, and it also does not exist in Exchange 2016 when Exchange is installed on Windows Server 2012 R2. So what is the fix?None
Yes, you read that correctly. None.
If you scour the TechNet forums (Search term ‘Get-Help Deserialization Exchange 2016’), there are numerous posts on this issue. Microsoft has also been notified by a few Microsoft MVPs where the concern has fallen on deaf ears. While we all understand that there is a push to push all organizations to the cloud and ignore the on-premises market. I would hope that it doesn’t speak to the quality of the code for Windows 2016 or Exchange 2016, but it certainly seems to be a questionable decision by Microsoft…..
The same issues DOES NOT EXIST for Get-Help for your Exchange Online tenant….. Hmmm….
Hopefully this is temporary, but I express no comfort in the fact that the issue has existed for over 6 months now….
NOTE
There are workarounds, so look for a post on workarounds which will be ready for Friday.
