I Am Zorg – CASArray Destroyer

This is an interesting tale, and is something I have never seen done before in all my time working with Exchange.  The client had managed to tweak the configuration of Exchange and modify the CAS configuration so significantly that Exchange was absolutely confused.  Specifically, the CAS Array was modified so much that Autodiscover was no…

2

Exchange 2016 RecoverServer

There have been many great improvements to the Exchange Server installation process in recent years.  Exchange 2010 gave us the ability to perform incremental deployment, where all mailbox servers start off as a regular mailbox server and then we can add it to a Database Availability Group (DAG).  Exchange 2007 introduced the ability to run…

1

Exchange 2016 Upgrades–The Point Of No Return

When designing an upgrade strategy from an older version of Exchange to a newer one, a question that needs to be addressed is do we need to introduce a version of Exchange that may not currently be present?  This may be when upgrading from Exchange 2010 to Exchange 2016.  If that organisation currently does not…

0

Exchange Setup – Certificate Is Expired

The below is one of my Exchange 2013 lab servers which ran into an error when upgrading to Exchange 2013 CU13.  This was because I had deliberately broken Outlook Anywhere in order to replicate a customer situation where they had let the Outlook Anywhere certificate expire.    When running the CU upgrade process, setup failed when…

0

End of Exchange 2007 Support

Today’s the day to say goodbye to our old friend, Exchange 2007.  At this point you should have completed the project to move all mailboxes and resources from Exchange 2007 to a supported version of Exchange, and uninstall the Exchange 2007 servers. Thanks to Exchange 2007 I went to MCM, and discovered just how badly Greg…

2

Transport Rule To Force On-Premises Terminology In a Not So Subtle Way

There are many memes doing the rounds inside Microsoft which are sent out when someone uses the term on-premise rather than on-premises.  Note the extra”S” in the latter.  This is not new, and the last rant on this subject was a year ago Friday Morning Rant – Premise and Tenents.   For another bit of…

0

Decomissioning Exchange 2007 – Public Folder Migration

The end of support date for Exchange 2007 is fast approaching.  At this time all of your migration projects to transition to a newer version should be done.  Note that Exchange 2007 will exit out of extended support on the 11th of April 2017.  The Office 2007 suite has a slightly later end of extended…

0

Unexpected Exchange AD Object Values

Imagine this scenario; you have deployed an Exchange 2013 or Exchange 2016 Cumulative update successfully in your environment and you think that all is fine.  However you then receive an unpleasant surprise when you go to verify the details of the Exchange Schema and Exchange AD object versions.  You can review the process to review…

0

Exchange 2013 CU16 and Exchange 2016 CU5 .NET Framework Requirement

As mentioned in the release posts for Exchange 2013 CU16 and Exchange 2016 CU5, both of these Exchange versions now require .NET framework 4.6.2. Exchange setup will check for the presence of the required .NET framework, if not present setup will halt. This is also true when extending the AD Schema and preparing Active Directory. …

19

Exchange 2016 CU5 Released

Exchange 2016 CU5 has been released to the Microsoft download centre!  Exchange 2016 has a different servicing strategy than Exchange 2007/2010 and utilises Cumulative Updates (CUs) rather than the Rollup Updates (RU/UR) which were used previously.    CUs are a complete installation of Exchange 2016 and can be used to install a fresh server or to…

26