Exchange 2013

What’s new in Exchange 2013 transport services? Let’s take a look.

Let us take a look as to how an Outlook client connects to an Exchange 2013 mailbox.

The Exchange Team has changed their recommendation around the disk space required to install Exchange 2013, to be in line with the way 2013 works.

Microsoft has released a hotfix to correct a .Net 4.5 issue in Windows 2008 R2 and 2012 & it applies to Exchange 2013 as well.

You will be in for a surprise when you run a batch move to migrate mailboxes from legacy Exchange versions to 2013, as the transaction log files starts growing at a faster rate and even fills up the disk!

You are trying to introduce the first Exchange 2013 server into an existing 2010 network, but running the 2013 setup complains that there are 2010 servers which doesn’t have SP3 applied in your environment.

The change in Exchange 2013 architecture with just two roles has had an effect on the connection filtering anti-spam agent.

With the release of Exchange 2013, the recommendation around the placement of the mail.que database has been changed.

What are the options available to load balance Exchange 2013 traffic?

Finally, the Exchange Team has realised that there are deployments out there which hosts more than 50 databases per server in the 2010 world!