Installing Exchange 2013 CU1 in co-existence

A simple walkthrough of the install of  Exchange 2013 CU1 in a Exchange 2010 environment. This is based on a clean server 2012 install.

Just to emphasize one thing first: CAS-arrays are out. CAS in 2013 is just a simple proxy to redirect to the correct user mailbox, so they are no longer needed.

  1. Download CU1 from, and extract.
  2. Download and install the Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit from
  3. Download and install the Microsoft Office 2010 Filter Packs – Version 2.0 from
  4. Download and install the Microsoft Office 2010 Filter Packs – Version 2.0 – Service Pack 1 from
  5. Install RSAT AD DS and AD LDS Tools on the server; or run the next point on a DC. Depending on you preference and/or deployment scenario.
  6. Run  setup.exe /preparead /iacceptexchangeserverlicenseterms from an elevated command prompt. This will take a few minutes
  7. The same applies for  “setup.exe /prepareschema /iacceptexchangeserverlicenseterms” and  “setup.exe /preparedomain /iacceptexchangeserverlicenseterms” though they shouldn’t take as long.
  8. Good, now the AD bit is done, and the prereqs are there. All that remains is to actually install Exchange 2013; which will also handle server roles and features automatically.

Check for updates; always a good idea, though you probably won’t find any:




Introduction, License Agreement and Recommend Settings, nothing to worry about obviously.

You’ll notice that there are only two roles in 2013. Mailbox and CAS. Hub Transport-services are incorporated in the Mailbox-role. In my case I’ll only need the mailbox-role on this server.


Default install path. I rarely see a reason to change this.



The option to disable malware-scanning. Malware-scanning has been redesigned for 2013, while Forefront for Exchange has been taken off the market. While still early, I see no reason to disable this. Default is enabled.



Wait, what, that’s it? Yes it is. Readiness will run and prereqs will install, and you’ll be good to go.

Leave a Reply

Your email address will not be published. Required fields are marked *