Windows 2012 R2 reached the RTM state back in august 2013, and is going to be GA on October 18th. 2013.
New software from Microsoft is always exiting and because I love my Exchange very much, and is so lucky to have access to the RTM version from MSDN, I wanted to test if Exchange 2013 CU2 could run on the brand new server platform.
February 2014 Update
With the release of service pack 1 for Exchange 2013, you are now good to go for using Exchange 2013 on Windows Server 2012 R2.
Get Service Pack 1 here
November 2013 Update
CU3 Works fine with the latest updates to Windows Server 2012 R2.
PLEASE NOTE: Microsoft DO NOT support Exchange 2013 on Windows Server 2012 R2 yet – support will come with SP1 which is scheduled to be released in the start of 2014. Because the support from Microsoft is not there yet, I created a new lab environment to test the installation of Exchange. The guide is how to install Exchange 2013 CU2 on Windows 2012 R2 (STILL NOT SUPPORTED BY MICROSOFT – so install on your own risk)
Use Service Pack 1 on Windows Server 2012 R2
Microsoft has found a critical problem in the WebReady Document Viewing and Data Loss Prevention modules of Exchange, which can lead to remote code execution in Exchange.
See the Security Bulletin MS13-061 from Microsoft and download the updates to you favorite Exchange version.
The Exchange Team has released CU1 for Exchange 2013.
With this update it is now possible to migrate from Exchange 2010, which require that you have SP3 installed.
Besides hotfixes in the update it also new functionality to Exchange 2013, which you can read about here.
The update is in the new update format, which means that the download is a complete exchange installation, which you besides upgrading an existing installation also can install a completely fresh installation with this update. Read about the new service module here.
This update also marks the end of my participation in the Exchange TAP program, which I have been part of, for the last year, and have given me a lot of knowledge about Exchange 2013 and coexisting with Exchange 2007/2010.
You can get the update here.
A new version of pst capture has been released. Go get it here if you want to get rid of you old pst files.
On a Windows Server 2012 with Exchange 2013 installed, you might have a problem with emails getting stuck in the submission queue, and after 2 days you get an NDR message:
#550 4.4.7 QUEUE.Expired; message expired ##
I had this problem with meeting invites that contains an html signature and on some e-mails.
The problem is related to Exchange 2013 when it is installed on Windows 2012.
Workaround is not to use RTF formatted emails, and don’t use my signature in meeting invites.
I have also changed the transport service so messages will expire after 1 hour, and notifying the users that the RTF formatted email could not be delivered.
You can change the transport service with this command:
Set-TransportService “SERVERNAME” -MessageExpirationTimeout 01:00:00
The problem should be fixed in a future update for Exchange 2013.
Do you ever make drawings in Visio, then you can’t live without the new stencils for Lync Server 2013, Exchange Server 2013 and Sharepoint 2013.
Go get the updated stencils which contains over 300 new ones here
The new Lync Server 2013 and Exchange 2013 has now been made available to all MSDN users.
I have been working with Exchange 2013 the last 8 months as part of the Exchange 15 TAP program, and I must say, it is a cool product, and I am looking forward to tell and learn my customers about the new features.
The upgrade process of the customers will begin in the first half of 2013 when Exchange 2010 Service Pack 3 is released, which is a requirement for co-existing.
The Exchange 2007 upgrade process is not supported yet, but will also be supported in the first half of 2013.
The RTM version of Office 2013 can also be downloaded from MSDN.
The RTM build for UCMA 4, which is used by Lync Server 2013 and Exchange Server 2013 can be downloaded here
On October 11th 2012 Exchange 2013 and Lync 2013 reached the RTM state.
I have been part of the RDP and TAP program on Exchange 2013 since February and it has been a very exciting journey where I have been able to earn and see Exchange 2013 evolve to what you all will see in a very short time, when it’s reach GA.
As a start Exchange 2013 will only be supported in new installations, which means that we will have to wait until 2013 to begin upgrade existing Exchange 2007/2010 installations.
There is now direct upgrade path from Exchange 2003, so you will need to upgrade to Exchange 2010 first, and then deploy Exchange 2013.
Read more from the Exchange Team blog: http://blogs.technet.com/b/exchange/archive/2012/10/11/the-new-exchange-reaches-rtm.aspx
And don’t forget to read the Lync Team blog: http://blogs.technet.com/b/lync/archive/2012/10/11/lync-2013-is-finished.aspx
When you access the new Exchange Admin Center in Exchange Server 2013 (currently beta 2), you might receive an access denied when you login, like the one below.
Your Admin account is, on a lower Exchange version like Exchange 2010 or Exchange 2007.
You can either move you admin account from powershell with the move-mailbox cmdlet or instead attached the last part of this url (with bold): https://servername.company.local/ecp?exchClientver=15