This post is also available in: Polish
Exchange Team released today long awaited Service Pack 1 for Microsoft Exchange Server 2013.
This update raises Exchange 2013 version number to 15.0.847.32
Service Pack 1 for Exchange 2013 can be downloaded here:
Microsoft Exchange Server 2013 Service Pack 1 (SP1)
And list of changes can be found here:
Description of Exchange Server 2013 Service Pack 1
Installation of Service Pack 1 for Exchange 2013 will made changes in Schema and Active Directory.
To apply schema changes run:
setup.exe /PrepareSchema /IAcceptExchangeServerLicenseTerms
To apply Active Directory changes run:
setup.exe /PrepareAD /IAcceptExchangeServerLicenseTerms
Upgrade to SP1 you can start GUI installer or run:
setup.exe /m:upgrade /IAcceptExchangeServerLicenseTerms
About new features improved by SP1 you can read on TechNet:
New features and improvements included in Exchange 2013 SP1
- Windows Server 2012 R2 support -Windows Server 2012 R2 is now a supported operating system in Exchange 2013 SP1. Exchange 2013 SP1 also supports installation in Active Directory environments running Windows Server 2012 R2
- Exchange Admin Center Cmdlet Logging – The Exchange 2010 Management Console includes PowerShell cmdlet logging functionality. Listening to your feedback, we’re happy to announce that this functionality is now included in the Exchange Admin Center (EAC). The logging feature enables you to capture and review the recent (up to 500) commands executed in the EAC user interface while the logging window is open. Logging is invoked from the EAC help menu and continues logging while the logging window remains open.
- Edge Transport servers return
- New communication method for Exchange and Outlook – SP1 introduces a new communication method for Exchange Server and Microsoft Outlook called MAPI over HTTP(MAPI/HTTP). This communication method simplifies connectivity troubleshooting and improves the user connection experience with resuming from hibernate or switching networks. MAPI/HTTP is disabled by default, allowing you to decide when to enable it for your organization. MAPI/HTTP can be used in place of RPC/HTTP (Outlook Anywhere) for your Outlook 2013 SP1 clients while Outlook 2013 RTM and older clients continue to use RPC/HTTP. Learn more about deploying MAPI/HTTP.
- Enhanced text editor for OWA – OWA now uses the same rich text editor as SharePoint, thereby improving the user experience, and enabling several new formatting and composition capabilities that you expect from modern Web application – more pasting options, rich previews to linked content, and the ability to create and modify tables.
- OWA Junk Email Reporting – OWA customers can report missed spam in the inbox (false negative) and misclassified as spam (false positive) messages to Microsoft for analysis by using its built-in junk email reporting options
- S/MIME for Message Signing and Encryption – Microsoft Exchange Online and Exchange 2013 SP1 now support S/MIME-based message security.
- DLP Policy Tips available in the desktop and mobile version of Outlook Web App – Data loss prevention (DLP) Policy Tips are informative notices that are displayed to senders in Outlook when they try sending sensitive information. In Exchange 2013 SP1, this functionality has been extended to both the desktop version of Outlook Web App and the mobile version (named OWA for Devices).
- DLP Classification based on Document Fingerprints – Deep content analysis is a cornerstone of DLP in Exchange. Document Fingerprinting expands this capability to enable you to identify standard forms used in your organization, which may contain sensitive information.
- DLP sensitive information types for new regions – SP1 provides an expanded set of standard DLP sensitive information types covering an increased set of regions, which makes it easier to start using the DLP features.
- Using AD FS claims-based authentication with Outlook Web App and ECP – Deploying and configuring Active Directory Federation Services (AD FS) using claims means multifactor authentication can be used with Exchange 2013 SP1 including supporting smartcard and certificate-based authentication in Outlook Web App.
- SSL Offloading support – SSL offloading is supported for all of the protocols and related services on Exchange 2013 Client Access servers. By enabling SSL offloading, you terminate the incoming SSL connections on a hardware load balancer instead of on the Client Access servers.
- Public Attachment Handling in Exchange Online – Although there are both private (internal network) and public (external network) settings to control attachments using Outlook Web App mailbox policies, admins require more consistent and reliable attachment handling when a user signs in to Outlook Web App from a computer on a public network such as at a coffee shop or library.
- Exchange OAuth authentication protocol – Information workers in Exchange on-premises organizations need to collaborate with information workers in Exchange Online organizations when they are connected via an Exchange hybrid deployment. New in Exchange 2013 SP1, this connection can now be enabled and enhanced by using the new Exchange OAuth authentication protocol.
- Hybrid deployments with multiple Active Directory forests
- Database Availability Group without an Administrative Access Point – Windows Server 2012 R2 enables you to create a failover cluster without an administrative access point. Exchange 2013 SP1 introduces the ability to leverage this capability and create a database availability group (DAG) without a cluster administrative access point. Creating a DAG without an administrative access point reduces complexity and simplifies DAG management. In addition, it reduces the attack surface of a DAG by removing the cluster/DAG name from DNS, thereby making it unresolvable over the network.
Issues that the SP1 dla Exchange 2013 resolves:
- 2860242 HTML format is lost after saving as an MSG file in Exchange 2013
- 2900076 Mailbox quota warning message uses an incorrect language in Exchange Server 2013
- 2910199 “Reply all by IM” chat window displays seven recipients in Outlook Web App
- 2913999 Meeting request body and instructions are lost in delegate’s auto-forwarded meeting request
- 2918655 Microsoft.Exchange.Servicehost.exe crashes after you enable FIPS
- 2918951 Users cannot access public folders after you upgrade to Exchange Server 2013 Cumulative Update 3
- 2925281 Outlook connectivity issue if SSLOffloading is “True” in Exchange 2013
- 2925544 Empty ExternalURL value for ActiveSync virtual directory after build-to-build upgrade of Exchange Server 2013
- 2927708 Resource mailboxes that are created by EAC will not be updated by policies in Exchange Server 2013
- 2928748 Default from delegate’s address in shared mailboxes in Exchange Server 2013
- 2928803 Long server connection for Outlook after a database failover in Exchange Server 2013
- 2930346 POP3 access does not work if the name of the resource mailbox differs from the user’s name
- 2930348 Manual redirection occurs in Outlook Web App if External URLs in each site are the same
- 2930352 Outlook Web App cross-site silent redirection does not work in Exchange Server 2013
As always we recommend to install SP1 in test environment first.