Category: Support

Just a quick reminder that Exchange Server 2007 will have no support after April 11th 2017. Although every install will continue without any issue after this date, it is a risk continuing the use of this product. Security fixes won’t come available, but also little things like timezone/daylight savings changes aren’t updated which could have a high impact in your organisation. You can transition to Exchange Server 2010 but preferably Exchange Server 2013. However, I would suggest migrating to Exchange

The Exchange Team blog reminded us today that in about a year the extended support for Exchange Server 2007 will end. This means no more updates of any kind, not even security updates. Feature updates already stopped 4 years earlier when Mainstream support ended. The product will continue to run, but how longer it’s being kept in production that will add some risk to your environment due to security issues not being fixed. You can find lifecycles of other Microsoft

Today the Exchange Team blog posted an article about upgrading the Domain Functional (DFL) level of your Active Directory environment away from Windows Server 2003 and the fact that raising the level might have some impact on your Exchange servers (and other applications). It is possible that they might not be able to authenticate. If you do run into issues after raising the DFL, the solution is either restarting the Kerberos Key Distribution Center service on all DC’s or restarting all DC’s

UPDATED 28/3/2024: See update below article. A little heads up. While working on an extensive design including Exchange Server 2013 with Service Pack 1 installed on Windows Server 2012 R2, my eye caught a comment in the Facebook group Exchange Server 2013 (Facebook login required). VMwares vSphere 5.1 and higher are shown to be validated by Microsofts Server Virtualization Validation Program (SVVP) to run Windows Server 2012 R2 VM’s. The hypervisor needs to be validated also as a requirement for