How to transition Exchange 2010 to Exchange 2013 Part 1

By admin on April 2nd, 2013

With Exchange 2013 Cumulative Update 1 coexistence between Exchange 2010 (Service Pack 3) and Exchange 2013is finally supported. It’s been a long journey but let’s now focus on how to install Exchange 2013 and coexist with the latest and greatest Exchange version, 2013.

In this part I will cover how to install Exchange 2013 CU1.

In my lab I set up the following:

I use split DNS so the domain is called both internal and external. Since it’s been common to have a TMG in front of Exchange I have included one and we will go through what configuration we will have to do there as well. See table below for all fact of the servers.

Function Version Server name Roles IP
Domain Controller 2012 Ex15-DC DC/GC/DNS
Exchange 2010 Ex15-Ex2010 MBX/CAS/HUB
TMG 2010 Ex15-TMG
Client (internal) Win8 Ex15-ClientInt Outlook  
Client (external) Win8 Ex15-ClientExt Outlook

Load Balancer

Of course there is no good reason for using a load balancer for only one server but in this blog series we will also build a DAG later on so I added a KEMP for that purpose and we will also look at how to configure it.

And the next server we will set up will be the Exchange 2013 server, note that to be able to install Exchange 2013 all Exchange 2010 servers in the organization will need Exchange 2010 Service Pack 3 before we can install. If any Exchange 2010 servers in your organization (including Edge servers) does not yet have SP3, start by upgrading them or the Exchange 2013 setup will fail because of a “hard block”.

Our Exchange 2013 server will have the following characteristics:


Version Server name Roles IP
Exchange 2013 Ex15-Ex1 MBX/CAS

The next thing to do is to install an Windows 2012 server. Even though I won’t set up a DAG in this part 1 of this blog (will come in later posts) I recommend you who will to base your Exchange 2013 server on Windows Server 2012 Standard as Failover Cluster is included. in standard and much more affordable.

I won’t cover the Windows setup in details but when you have Windows 2012 in place follow the steps below.

Open Windows PowerShell


Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Clustering-CmdInterface, RSAT-Clustering-Mgmt, RSAT-Clustering-PowerShell, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, 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-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation, Telnet-Client

Note: Telnet-client is not required but very nice to have when testing and troubleshooting SMTP.

Restart your server.

Download and install Unified Communications Managed API 4.0 Runtime

Download Exchange Server 2013 RTM Cumulative Update 1 (CU1). Note that you can install from CU1 and don’t have to upgrade from RTM.

Extract the the content to a directory of you choice, in my case C:Ex1013

Start an elevated cmd and run setup if you like to run the GUI based setup or run the command you prefer to do a unattended setup. In this blog I will do it through the GUI.

You will be asked to check for updates, it’s unlikely that any updates will be found.

After you click next files will be copied and setup will initialize.

A few next and a accepted license agreement later you will be asked to install with recommended or custom settings, I go for custom in this case.

As I will install one Exchange 2013 server I go for both Client Access role and Mailbox role. Since I didn’t do anything specific to Windows roles and features I check “Automatically install Windows Server roles and features that are required to install Exchange Server”.

Pick your destination where you want Exchange to be installed. I go for default .

Next I select to keep Malware Protection enabled.

Setup will check that all components are in place and that the server is ready to be installed. A restart will probably be needed after all Windows components are installed. so lets restart and try again.

After rerunning setup you will see something like above, don’t worry about the warnings about Filter Pack.

Hit install and beside getting Exchange 2013 installed on the server your organization will now get some new stuff in AD,  yes as usual there are schema updates so be prepared that this might take a while (and require permissions).

Some 35 minutes later you have a brand new Exchange 2013 CU1 server! Congrats!

In part 2 of this blog series we will take a look at what we should configure on this brand new server, stay tuned!

Exchange 2013 Preview Installation, Client Access Role (Front-End)

By admin on July 17th, 2012

In my previous post I wrote about installing the Mailbox Role aka Back-End role. Installing the Front-End is not much different and I show you how in this post.

Once again have a look at Pro-Exchange for the prerequisites, note that they are slightly different for the Front-End server.

When you have completed the prerequisites run a cmd as administrator and then run setup from there. Your first screen will be setup asking to connect to Internet for updates:

Updates will be downloaded.

When all updates necessary has been downloaded setup copies it’s files. Note, if you cancel the setup before it finishes you will be asked if you want to use the downloaded updates from your first run.

Click next and you get the Introduction page where you can read about Exchange. Right now there is no content for the Exchange 2013 Deployment Assistant but I recommend you keep looking because the content on previous versions of Exchange has been really good.

Accept the License Agreement and click next

Choose to turn of or off Error Reporting.

Setup will now check for required software and automatically go to the next screen when it’s done.

Select the role you want to deeply, in this case the Client Access Role

Select where to install Exchange, the default path is C:Program FilesMicrosoftExchange ServerV15

One of the differences from installing the Mailbox Role id that you get to specify a external hostname, you should enter the fqdn of your external access to Exchange, like This information will be used to configure all virtual directories external URL.

A readiness check is performed and when you got all components in place hit Install.

Wait some time, and see the end result below.

It’s been a long day with some great news about Exchange, Lync, Office and Office 365 but it’s 4.30 AM in Sweden right now so I better get some sleep and be back tomorrow with some information about how and what to configure.

Exchange 2013 Preview Installation, Mailbox Role (Back-End)

By admin on July 17th, 2012

This article will show you what Exchange 2013 Preview Setup looks like and how you perform it. First of all have a look at the prerequisites to install over at Pro-Exchange.

When you are done with the prereqs simply run setup from a elevated cmd.

The first screen you will see is this:

Note that you might not have the last option, I rerun the setup after I had to expand the disk so I downloaded updates the first time I run setup

Setup will download updates needed for your install:

When all updates needed are downloaded files will be copied:

Your next screen provides you with details on planning and information about Exchange 2013

Click next and accept the License Agreement:

Choose if you like to send Error Reporting to Microsoft, since this is a preview I recommend you do. This information helps the team to review problems that might occur in the product.

Setup will now check that you have all required software installed on your server

When you have all prerequisites in place you will get to select witch role you want to install. It’s recommended that you start with the mailbox role.

Select where to install Exchange, the default path is C:Program FilesMicrosoftExchange ServerV15

Select if you want to disable malware scanning or not

Setup will now verify you organization and your server. Note that you need to request some of the hotfixes from Microsoft Support, this can be done online and you will get a email with a link for the hotfix.

Setup will now go through 12 steps and the information about what’s happening is limited in in the GUI. If you want detailed information consult the Setuplogs located in C:ExchangeSetupLogs. Note that the setup process (especially step 7 and 10) might take some time, in my case almost an hour

And after some wait you end up with this:

That was the mailbox role installation, my next post will be about installing the front end server

And if you were looking for the Exchange Management Console stop looking because you wont find it! It’s been replaced with Exchange Admin Center, EAC and to find it fire up Exchange Management Shell and run the following command:

Get-EcpVirtualDirectory | fl *URL*

Now copy the Internal URL into your browser and log on!

Updated Exchange 2010 Installation Checklist

By admin on April 19th, 2011

Microsoft has released a updated version of the Exchange Server 2010 Install Guide Templates. As mention before there are a lot of advantages of using a standardized  form of documentation and the Install Guide Templates makes that task easier.

A personal reflection about the CAS template is that it mentions Windows NLB and that is a supported solution for load balancing Exchange 2010 but no longer the recommended way so think about what solution that will be the best for you and don’t just follow the guide.

Exchange 2010 installation checklist

By admin on April 8th, 2010

Note: Microsoft Exchange Server 2010 Install Guide Templates has been updated, see Updated Exchange 2010 Installation Checklist

As a consultant I know the importance of try to make things as similar as possibly. When I do migration or a installation of Exchange I always try to follow my own checklist to make sure I don’t forget something and to have configurations as alike as possibly. Some of the advantages by this approach are:

  • Ease when it comes to documentation
  • Better support
  • Fewer support calls