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. …

5

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…

3

Exchange 2016 CU4 Released

Exchange 2016 CU4 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…

13

Exchange 2016 CU3 Released

Exchange 2016 CU3 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…

11

Remote PowerShell – PSSession WhoAmI

For those who worked with NT and Novell Netware many, many moons ago they became familiar with a handy function– who am I.  Windows folks may also recall it when working with the Client and Gateway Services for Netware, and whoami.exe was also added to the NT Resource Kit.  Remember the days of all the…

2

Unable Connect Exchange Remote PowerShell Using Windows 10 Anniversary Update

After updating Windows 10 you may be unable to connect to a remote PowerShell session.  This is an issue for versions of Exchange 2010 onwards as we use remote PowerShell for administration.  The same applies for Exchange Online in Office 365.  Note that directly loading the Exchange PSSnapin is not supported apart from a limited…

12

Exchange Self Signed SHA2 Certificates

In recent builds, Exchange has been updated to support the newer SHA2 certificates.  Exchange 2010 SP3 RU13 and Exchange 2013 CU 12 updated the SMIME control’s certificate to SHA2. Additionally, Exchange 2013 CU13 and Exchange 2016 CU2 added support for generating the self signed certificates as SHA2 certs. The below is for reference to save…

9

Script To Start Exchange Services

Running scripts to start and stop services has been a task long associated with Exchange.  For those who pre-date Exchange 2000, do you remember the fun issues with the increased WaitToKillServiceTimeout value?  By default in ye olde days HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\WaitToKillServiceTimeout was 20,000 ms (20 secs).   Installing Exchange increased that to 600,000 ms (10 minutes).  To quickly…

1

Busting The Exchange InternalNLBBypassURL Myth

In several recent engagements, there has been some interesting discussions about how to configure the CAS namespaces for the Exchange Web Services virtual directory.  Specifically this was around the configuration of the InternalNLBBypassUrl in Exchange 2013 and 2016.  Since this was set on Exchange 2007/2010 servers, there seems to be a desire to change it…

1