Here at Resolve we like to keep up-to-date with the latest IT systems, and the issues that can arise from them.
Since the release of Microsoft Exchange 2013, I have come across a few issues which have proven to be tricky to fix. For example, last week I came across a problem where forwarding mail in the Outlook Web App meant that (important!) information such as the email address was removed from the forwarding email.
After installing the latest Microsoft Service Pack (SP1) for Exchange Server 2013, which contains previous cumulative updates released, I have found that many of these Exchange-related issues, including the one above, have been resolved.
I thought it would be useful to list some of the most common Exchange 2013 issues, which have now been fixed with the Service Pack:
• Unable to load the OWA Premium interface using Internet Explorer 11
• Mailbox quota warning message uses an incorrect language in Exchange Server 2013
• Users cannot access public folders after upgrading to Exchange Server 2013 Cumulative Update 3
• Meeting requests body and instructions are lost in auto-forwarded meeting requests
• Manual redirection occurs in Outlook Web App if External URLs in each site are the same
Not only does the Service Pack fix issues, it also includes some great additions to the system which are worth a mention:
• Exchange Admin Center now has Command Logging feature available
• Several new formatting and composition capabilities have been added to OWA
• Improvements in the Data Loss Prevention (DLP) feature
• Usability improvements when adding members to new and existing groups in the Exchange Administration Console
• New communication method for Exchange and Outlook called MAPI over HTTP (MAPI/HTTP)
For more information on the additional features, check out the official Microsoft Technet blog by clicking here.
This service pack was released back in February this year, and since the release there has been a common occurrence with the Transport Agent service failing to start. Microsoft has since released a PowerShell Script which resolves this problem, and can be run manually through PowerShell or alternatively a ‘Microsoft Fix it' application wizard, which is available here. It's encouraging to see Microsoft fixing issues between service packs, and future service packs should improve the user experience further.
The latest Service Pack can be found on the Microsoft site (click here for the download page), please read carefully through the instructions and system requirements.
If you have any questions, don't hesitate to give us a call for more information.