5/23/14 2013 SP1 CU5 released: https://blog.jasonsherry.net/2014/05/28/exchange-2010-sp3-ur6-and-2013-cu5-released/

Last updated: 4/14/14

1. Important: 3/4 Transport server doesn’t start after upgrade and some products that use Transport Agents don’t work
   • Issue is related to an XML file getting updated incorrect during the install of SP1
     • SP1 introduced a badly formatted XML comment line in two assembly redirection policy files that affects third-party products that use transport agents
     • From KB2938053: “This problem occurs because the global assembly cache (GAC) policy configuration files contain invalid XML code.”
   • Threads on products that have this issue, but many other products do also
     • http://forums.avg.com/us-en/avg-forums?sec=thread&act=show&id=240770
     • http://community.trendmicro.com/t5/Business-Security-Forum/Scanmail-amp-Exchange-2013-SP1-can-t-start-transport-service/m-p/151097
     • http://www.codetwo.com/kb/codetwo-and-exchange-2013-sp1
   • MUCH more details here on Tony Redmon’s Windows IT Pro blog
     • Exchange 2013 SP1 suffers late-breaking bug that affects third-party products
   • Details on XML formatting issues in Michel de Rooij blog
     • Exchange 2013 SP1 Transport Agent Fix
   • FIX RELEASED: Third-party transport agents cannot be loaded correctly in Exchange Server 2013: http://support.microsoft.com/kb/2938053
     • This fix is actually a PowerShell script that fixes the XML formatting
2. Important: When building a DAG cmdlet will fail if NetBIOS and AD short domain name don’t match – 4/14/2014
   • From this FB post: https://www.facebook.com/groups/MSEX2013/permalink/801310969898022/
     • In Exchange 2013 SP1, when building a DAG, you will see issues with Set-DAG and Add/Remove-DatabaseAvailabilityGroupServer cmdlets if your Domain NETBIOS name is not equal your AD short name, eg NETBIOS name is “FOO”, and your domain name is “bar.contoso.local”. Both cmdlets will terminate with a Dr Watson. The DAG will still build fine, except for the FSW resource – there will be no FSW assigned to the DAG. We already have a FIU you can request through PSS, or create the FSW manually as a temporary workaround.
   • Work around: Manually create the FSW, contact PSS for fix, wait for public fix
3. Minor: “Ceres” Search Foundation install error
   • From Paul Robichaux’s blog post
     • “When deploying the RTM build of Exchange 2013 SP1, I found that one of my servers was throwing an error I hadn’t seen before during installation”
4. Minor: Default apps in Outlook Web App do not work if Exchangeis installed in Window Server 2012R2
   • From KB2938292 posted on 3/19/2014
     • “When you install Microsoft Exchange Server 2013 on a Window Server 2012 R2-based computer, default”
     • This issue will be fixed in Exchange Server 2013 Cumulative Update 5
   • Work around: Edit the web.config and add the following line to the “<appSettings> section:
     UseLegacyRequestUrlGeneration” value=”true”/>
     • 3/25: A peer of mine is working on a blog post with more details and I will post a link to it when he post it.

Related items

1. 3/4 Outlook2013SP1 Issue: Fails to connect to Exchange in a multi-forest environment
   • http://support.microsoft.com/kb/2936893

Related Posts

• Exchange 2010 SP3 RU3 and 2013 CU3 Released & Known Issues
• Exchange 2013 RTM CU2 released (Again on 7/29) & Known Issues