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
Now with Exchange server 2013 scenario testing on the way it’s time again to install Exchange Server 2007 in our lab again. Since Windows 2008 R2 is fully supported with Exchange Server 2007 SP3 this is my preferred server.
The easiest way to install the prerequisite server roles and features is to use PowerShell. The first server you’re going to install (and that is going to change Active Directory) needs the Remote Server Administration Tools (RSAT). RSAT also includes Active Directory Users and Computers, it can be useful to install it on other servers as well. Use the following command to install RSAT:
Add-WindowsFeature RSAT-ADDS Continue reading Install Exchange 2007 SP3 on Windows 2008 R2
Exchange server 2013 consists of two server roles, the Mailbox Server (sometimes referred to as the back-end) and the Client Access Server (sometimes referred to as the front-end). All clients connect to the CAS Server and the CAS Server proxies the request to the appropriate mailbox server.
It is possible to install the server roles on dedicated servers, multiple Exchange 2013 CAS servers with a hardware load balancer and multiple Exchange 2013 Mailbox servers with a Database Availability Group. This is the preferred way for large companies with lots of mailboxes, lots of servers and maybe multiple (global) datacenter. To be honest, this is where Exchange 2013 is designed for. But it is also possible for smaller organizations to install just two Exchange 2013 server with both roles on it, a DAG for mailbox resiliency and a hardware of software load balancers for the protocol resiliency.
Continue reading Installing Exchange 2013 – Part I
Now that Exchange 2010 SP3 is available it’s also possible to install it on Windows Server 2012. Normally that’s not a problem, but you have to be careful with the prerequisite software. Windows Server 2012 comes with .NET Framework 4.5 and Management Framework 3.0 (including Powershell 3.0) but Exchange 2010 still requires .NET Framework 3.5 and Powershell 2.0. Luckily Powershell 2.0 and Powershell 3.0 can coexist on the same box with any issues.
Install .NET Framework 3.5 and Powershell 2.0
To install .NET Framework 3.5 (which automatically includes Powershell 2.0 on Windows Server 2012) you can use Server Manager, but there’s a little snag because Server Manager does not know where the install files are located 🙂 Continue reading Exchange 2010 SP3 on Windows Server 2012