Exchange 2013 Preview Installation on Windows Sever 2008 R2 SP1

With a lot of this missing and that missing, Exchange 2013 installation got through after good 3 hours of installation time. I am not sure why it took so long to complete though. May be my hypervisor isn’t performing too well Smile with tongue out

This post is going to run through a quick look at Exchange 2013 Preview installation on Windows Server 2008 R2. Below are the lab details:

E15DC – Domain Conroller

E15MBX – Mailbox Server Role

E15CAS – CAS Server Role.

Domain Name: e15.exchange.local (No it is not a child domain. The root domain itself is named like that!)

Prerequisites For Windows Server 2008 R2 SP1

Exchange 2013 Preview supports below server operating systems only

  • Windows Server 2008 R2 SP1
  • Windows Server 2012

Since I used Windows Server 2008 R2 SP1 for this installation below are the prerequisites that I needed to install:

OS Components

Windows Server Roles and Features

Mailbox Server Role

Import-Module ServerManager

Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI –Restart

CAS Server Role

Import-Module ServerManager

Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI –Restart

Once you have installed all the OS prerequisites on the server where Exchange 2013 will be installed, and have completed the reboot; make sure to uninstall Visual C++ 11 Beta Redistributable (x64) – 11.0.50531

If you leave Visual C++ 11 Beta Redistributable (x64) – 11.0.50531 uninstalled setup will ask you to remove it during the readiness check.

Note: You may need to reboot the servers many times before the installation could be started.

 

Active Directory

Schema Master Windows Server 2003 SP2 or later x86 / x64
Global Catalog Windows 2008 or later. On safer side, I recommend using Windows 2008 SP2 or later
Domain Controller Windows 2008 or later. On safer side, I recommend using Windows 2008 SP2 or later
Permissions
  • Enterprise Admins
  • Schema Admins
Domain Functional Level Windows Server 2003 Native or above
Forest Functional Level Windows Server 2005 or above
RODCs Exchange cannot work with RODCs. So NO RODCs in the site where you are trying to install exchange 2013 Preview.

 

In short, you must have at least one DC and GC running Windows Server 2008 or later. Schema master role can be owned by a domain controller that is Windows 2003 SP2.

After finishing all prerequisite checks and installations. We are good to go for first Exchange 2013 preview server role installation. Microsoft says there is no specific order of installation however mailbox server role and then CAS server installation is recommended.

As usual there are two ways to install Exchange 2013. The CLI way and the GUI way. You may notice some differences compared to legacy versions (Exchange 2007 and 2010) though.

Installing Exchange 2013 using CLI

Exchange 2013 preview seems to have replaced setup.com to setup.exe and offers below switches for installation.

Setup.exe [/Mode:<setup mode>] [/IAcceptExchangeServerLicenseTerms]
[/Roles:<server roles to install>] [/InstallWindowsComponents]
[/OrganizationName:<name for the new Exchange organization>]
[/TargetDir:<target directory>] [/SourceDir:<source directory>]
[/UpdatesDir:<directory from which to install updates>]
[/DomainController:<FQDN of domain controller>]
[/AnswerFile:<filename>] [/DoNotStartTransport] [/LegacyRoutingServer]
[/EnableErrorReporting] [/NoSelfSignedCertificates]
[/AddUmLanguagePack:<UM language pack name>]
[/RemoveUmLanguagePack:<UM language pack name>] [/NewProvisionedServer:<server>]
[/RemoveProvisionedServer:<server>] [/ExternalCASServerDomain:<domain>]
[/MdbName:<mailbox database name>] [/DbFilePath:<Edb file path>]
[/LogFolderPath:<log folder path>] [/Upgrade]

For example below command will install Exchange 2013 preview at the default installation location on C:\Program Files\Microsoft

Setup.exe /mode:Install /role:ClientAccess,Mailbox /OrganizationName:Exchange Geek /IAcceptExchangeServerLicenseTerms

Installing Exchange 2013 using GUI

The same setup.exe file located at the root of the installation media or installation source directory launches the GUI setup. You just need to double click it.

image

And this is the first page of the setup wizard. You may notice that the setup wizard follows the non glossy and non 3D window look. May be inspired by the Windows Phone interfaces?

On the very first page setup wizard asked if I wanted to check for the updates on internet. Since my virtual machines were not connected to internet I did not choose to let it do so and simply moved on to the next screen which copies the file.

image

 

Next is the introduction page which has links to the learning resources on Microsoft Technet.

image

This screen lets you select the server role to be installed. You can choose to install the server role you are planning to install here.

 

image

You can specify the location of exchange binaries on the Installation Space and Location page of the wizard.

 

image

After clicking next on the previous page Exchange Organization page appears asking you to enter the organization name. You can also select whether to apply the Active Directory Split Permissions model.

 

image

You will see this screen only if you are installing a mailbox server role. Exchange 2013 preview bundles the anti malware protection with mailbox server role. You can select to enable or disable the anti malware protection. Read more about Anti Malware Protection here

 

Similarly, if you are installing Exchange 2013 CAS role you will be asked whether the server you are installing is an internet facing server and if yes then to specify the FQDN for the external access.

Next few pages will let you select the options for error reporting, and CIEP. I am skipping those pages just to avoid the unnecessary length of this post.

 

That’s all! You have your exchange server 2013 Preview lab ready for testing and learning. Enjoy!

Exchange Server 2013 Preview Release – at a glance

Microsoft announced its IT Pro review version of Microsoft Exchange; named Microsoft Exchange 2013. Just like other previous releases of the products; Microsoft seems to have maintained the consistency in drastic architectural changes to make the product more scalable and more efficient. Let us take a look at the high level changes that you will see in Exchange 2013 Preview.

Roles:

Oops! I don’t see anything called Hub Transport, Unified Messaging and Edge Transport Server roles. Yes! You guessed it correct. There are no HT, UM and ET roles. Only two roles at the moment viz. MBX and CAS.

Mailbox Server role will handle the mailbox and unified messaging roles together with a improvements to the way mailboxes and information store databases are managed.

Client connectivity does not use RPC anymore. It will HTTPS traffic to and fro the CAS role.

Transport is an integrated component of the CAS role.  That means NO HUB TRANSPORT. A figure below that is copied over from Microsoft Website shows how it works.

image

Mailbox server role has a lot of improvements done too.

 

Management:

Microsoft Exchange 2013 Preview release uses a completely new GUI based management interface now called EAC. EAC known as Exchange Administration Center replaces the MMC based Exchange Management Console.

Another component of management interfaces, Exchange Management Shell now uses the WinRM 3.0 as a base to run the exchange server management snap in.

Public Folders:

Although Microsoft kept insisting on moving your public folder data to a sharepoint based website, they seem to have been continuing the support for public folders. Surprisingly, instead of deprecating the support for PFs MS has introduced few more changes to the PF database architecture that can support the HA. You may notice a significant difference between the legacy way of public folders and the way they are handled by Exchange 2013.

Storage Engine:

If you are an ESE lover, there is a good news for you. Exchange 2013 still sticks to the ESE as a database engine.

High Availability:

Mailbox Server High Availability = DAG has become and almost unwritten equation in industry by now. Exchange 2013 continues with the two very well known terms called DAG and CAS Array. DAG and CAS Array have been improved to support stringent RTO/RPOs of the organizations.

I personally liked Windows Server 2012 RC and hope Exchange 2013 along with it can do some magic to reduce administrative burdens and TCO for many organizations.

 

This is the first post on my blog about Exchange 2013. Stay tuned for the geeky insight of the product. It has just started, a long way to go 😉

 

Finally, here are few links that can help you:

Download: http://technet.microsoft.com/en-us/exchange/fp179701

CHM Help: http://www.microsoft.com/en-us/download/details.aspx?id=30338