Exchange 2016 is the latest version of Exchange, and it’s not very different compared to Exchange 2013. When it comes to requirements, there are some differences though:
- Domain Controllers need to be at Windows 2008 level;
- Domain Functional Level (DFL) and Forest Functional level need to be at Windows 2008 level;
- The Exchange servers themselves need to be running Windows 2012 or Windows 2012 R2. At the time of release Windows Server 10 is not supported.
There’s also something like Simplified Architecture. This is the Exchange 2013 Preferred Architecture, enforced on Exchange 2016. This means that there will be only one Exchange 2016 server role on the internal network, the Exchange 2016 Mailbox server. This is the same as the old Exchange 2013 multi-role server, but at this moment there’s no choice left. You have to install the Exchange 2016 Mailbox server, and you cannot opt to install a dedicated Client Access server anymore.
Continue reading Deploy Exchange 2016
While configuring an Exchange 2013 organization in a hybrid scenario with Office 365 the Exchange Hybrid wizard stopped and showed the following error message:
Subtask CheckPrereqs execution failed: Configure Mail flow The Secure Mail Certificate on server HYBRID01 is not bound to the SMTP Service at Microsoft.Exchange.Management.Hybrid.MailFlowTask.CheckCertPrereqs()…
Continue reading The Secure Mail Certificate on server HYBRID01 is not bound to the SMTP Service
When installing an Exchange 2013 Edge Transport server a self-signed certificate is created and configure for use with the SMTP Transport server. The self-signed certificate has the NetBIOS hostname as the Common Name and the FQDN in the Subject Alternate Names field.
You can view this self-signed certificate using the Certificate MMC snap-in:
Continue reading Exchange 2013 Edge Transport Server and SSL Certificates
In my previous blog I wrote about the new SSL offloading capabilities in Exchange 2013 SP1. In this blog I will explain how to use this with a load balancer. In my lab environment I’m using an F5 (virtual) LTM running on Hyper-V. My lab is configured as shown in the following figure:
Continue reading load balancing in Exchange 2013 SP1 with F5
A Lync 2013 Edge server is using external, 3rd party certificates for authentication and encryption of data for federation purposes and external clients connecting to the Lync 2013 environment. I’m using Digicert certificates for this since these work fine in almost all situations.
So I got a message from Digicert to renew my certificate, which I did. Renewed the certificate, same Common Name (CN=access.exchangelabs.nl) and the same Subject Alternative Names entries. The order of the SAN entries was different and so was the Friendly Name of the certificate but this should not cause any problem.
Continue reading Polycom CX600 fail to login after Certificate renewal on Lync 2013 Edge Server