Archive for July 2012

Installing Exchange Server 2013 Preview on Windows Server 2008 R2 SP1

Microsoft launched Exchange Server 2013 Preview on July 16th 2012. Lets have a look, how to install Exchange Server 2013 Preview on Windows Server 2008 R2 SP1.
I am installing E2K13 Preview on Windows Server 2008 R2 SP1. But you can install it on Windows Serve 2012 RC as well.

First we will install prerequisites, and the way of prerequisite installation remains the same as it was in Exchange 2010.
Step 1: Run the below command in Windows Power shell.

 Restart the server after the installation.

Step 2: Install the prerequisites, there are total 8 prerequisites for E2K13 Preview and is how they looks

You can download the all the prerequisite from here
Install all the prerequisite as both Mailbox and Client Access Server Role will be on the same server.
You will have to restart the server several time as while installing the prerequisites.

Now we are going to run /PrepareAD now running /PrepareAD is the same with small change. I should be run like Setup /PrepareAD /OrganizationName:EXCHANGE /IAcceptExchangeServerLicenseTerms
You will have to run it with /IAcceptExchangeServerLicenseTerms swith or it won't work. This is something as in Exchange 2007and 2010 it use to ask "Press key if you don't agree the License Terms".

Once /PrepareAD is complete successfully you are ready to install E2K13 Preview. Run the set up file or install it from shell or command prompt.

Select Don't check for updates right now and click next.
Accept the License Agreement and click on next.

Specify your Error Reporting preference and click next, I have selected No.

Configure Client Access Server and click next

Make you Server Role Selection and click next
Installation path, I have kept it on default location, click next
Malware scanning, which is brand new in 2013. I've disable it. You can read more about this under Anti-Spam and Anti-Malware Protection in the TechNet documentation.
Select an option for the Customer Experience Improvement Program and click next
Final readiness checks will be done.
Installation of Exchange Server 2013 Preview is successfully done.
In my next article I will be writing on OWA, EAC and few other features of E2K13.


Outlook Web App isn’t available. If the problem continues, please contact your help desk.

After upgrading exchange server 2010 SP1 to SP2 with update rollup 3 on main site and all other site, users on non internet facing CAS server sites started getting the error when they access OWA, Active Sync and Outlook Anywhere.

OWA Error
Exchange Server 2010 environment:
AD Sites: 5
Boston (main site): Exchange Server 2010 SP2 with Update Rollup 3
San Diego: Exchange Server 2010 SP2 with Update Rollup 3
New Jersey: Exchange Server 2010 SP2 with Update Rollup 3
San Francisco: Exchange Server 2010 SP2 with Update Rollup 3
New York: Exchange Server 2010 SP2 with Update Rollup 3

First thing which comes in my mind is, OWA sub folders at location C:\Program Files\Microsoft\Exchange Servers\V14\ClientAceess\Owa\. I checked and compared the folder version of Boston server and New York server, and found that New York subfolder version is higher than Boston.
New York Server
Boston Server                 

Copy the file from Boston server and pasted it on New York server and restarted the IIS service on New York server, but still getting the same error message.Reverted the change on New York server.
One thing I noticed when upgrading the Boston server was, when updating the exchange server with Update Rollup 3, it took very long time to start the MS Exchange Information Store service and we had to restart the server.

Now to update the Owa subfolders on Boston server, there are 2 ways.
1: Copy the file from New York server and paste it on Boston server.
2: Reinstall the Update Rollup 3 on Boston server.

Note: I have seen lots of people suggest updating the SP2, but in my case I didn’t had to update the SP2.

I went with 2nd option, I reinstall Update Rollup 3, and again it took long time to start the service, but this time it completed successfully.
After reinstalling the UR3, compared the Owa version and now they all are update like all the servers in environment.
Checked the issue, but still getting the same error. We are using CAS Proxy and Boston server is the Proxy server. Here is, how proxy looks.

CAS Proxy

I noticed that, New York and San Francisco CAS server got ExternalURL in OWA  and ECP virtual directory, which is absolutely wrong.

OWA ExternalURL
External URL on non Internet facing server
Here is how things should be on all non Internet facing CAS server if you are doing CAS Proxy:

  • Make sure all non internet facing CAS servers don’t have ExternalURL set on OWA and ECP virtual directory.
  • Make sure you have authentication set to Basic and Integrated Windows Authentication
  • Make sure that non internet facing CAS server is not on Island or remote location, if it is, make sure you got strong bandwidth and replication is in good state.

Removed the ExternalURL from OWA and ECP from New York and San Francisco servers.

OWA ExternalURL Clear
Remove External URL
Checked the Authentication type on both, OWA and ECP virtual directory and it was set to Form based authentication, which is again wrong.

OWA Authentication
Wrong authentication on owa virtual directory
Changed the authentication from Form Based to Basic and Integrated Windows authentication on all the servers. Restarted the IIS service on all the non internet facing servers.

OWA Authentication Set
Correct authentication
Logged into each users mailbox of non internet facing CAS servers in OWA and now it's working as it suppose to be. Checked ECP (Exchange Control Panel), and it’s working great.

Successful OWA Access
Successful owa login
Successful ECP Access
Successful ecp login
After making all the changes, tested active sync and outlook anywhere and it's working perfectly.