Microsoft Exchange Server 2013 Standard with Service Pack 1

* Required Fields

Regular Price: $37,000.00

Special Price: $519.99

security logo

Microsoft Exchange Server 2013 Standard with Service Pack 1

Double click on above image to view full picture

Zoom Out
Zoom In

Microsoft Exchange Server 2013 Standard with Service Pack 1

Microsoft Exchange Server 2013 enables you to maintain control, increase user productivity, and keep your organization safe. You can move to the cloud on your terms with flexible migration options. Your users can do more on any device, helping them manage increasing volumes of email and work together more effectively as teams. You can also protect your business communications and sensitive information, while meeting internal and regulatory compliance requirements. With Exchange Server 2013, you can work smarter, anywhere.

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.

Edge Transport servers return
Edge Transport servers minimize attack surface by handling all Internet-facing mail flow, which provides SMTP relay and smart host services for your Exchange organization, including connection filtering, attachment filtering and address rewriting.

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. Depending on the results of the analysis, we can then adjust the anti-spam filter rules for our Exchange Online Protection (EOP) service.

S/MIME for Message Signing and Encryption
Microsoft Exchange 2013 SP1 now supports S/MIME-based message security with Outlook Web App. Secure/Multipurpose Internet Mail Extensions (S/MIME) allows people to help protect sensitive information by sending signed and encrypted email within their organization. Administrators can enable S/MIME for mailboxes by synchronizing user certificates and then configuring Outlook Web App to support S/MIME.

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). You’ll see it in action if you have an existing DLP policy with Policy Tips turned on for Outlook. If your policy already includes Policy Tips for Outlook, you don't need to set up anything else. Go ahead and try it out!

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. For example, you can create a fingerprint based off a blank employee information form, and then detect all employee information forms with sensitive content filled in.

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. SP1 adds region support for Poland, Finland and Taiwan.

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. In a nutshell, to implement AD FS to support multifactor authentication:
   Install and configure Windows Server 2012 R2 AD FS (this is the most current version of AD FS and contains additional support for multifactor authentication).
   Create relying party trusts and the required AD FS claims.
   Publish Outlook Web App through Web Application Proxy (WAP) on Windows Server 2012 R2.
   Configure Exchange 2013 to use AD FS authentication.
   Configure the Outlook Web App virtual directory to use only AD FS authentication. All other methods of authentication should be disabled.
   Restart Internet Information Services on each Client Access server to load the configuration.
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. Using SSL offloading moves the SSL workloads that are CPU and memory intensive from the Client Access server to a hardware load balancer.
SSL offloading is supported with following protocols and services:
   Outlook Web App
   Exchange Admin Center (EAC)
   Outlook Anywhere
   Offline Address Book (OAB)
   Exchange ActiveSync (EAS)
   Exchange Web Services (EWS)
   Mailbox Replication Proxy Service (MRSProxy)
   MAPI virtual directory for Outlook clients
   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.

Browser Support for AppCache
Internet Explorer 10 and Windows Store apps using JavaScript support the Application Cache API (or AppCache), as defined in the HTML5 specification, which allows you to create offline web applications. AppCache enables webpages to cache (or save) resources locally, including images, script libraries, style sheets, and so on. In addition, AppCache allows URLs to be served from cached content using standard Uniform Resource Identifier (URI) notation. The following is a list of the browsers that support AppCache:
   Internet Explorer 10 or later versions
   Google Chrome 24 or later versions
   Firefox 23 or later versions
   Safari 6 or later (only on OS X/iOS) versions

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. The new Exchange OAuth authentication process will replace the Exchange federation trust configuration process and currently enables the following Exchange features:
   Exchange hybrid deployment features, such as shared free/busy calendar information, MailTips, and Message Tracking.
   Exchange In-place eDiscovery

Hybrid deployments with multiple Active Directory forests
New in Exchange 2013 SP1, hybrid deployments are now supported in organizations with multiple Active Directory forests. For hybrid deployment features and considerations, multi-forest organizations are defined as organizations having Exchange servers deployed in multiple Active Directory forests. Organizations that utilize a resource forest for user accounts, but maintain all Exchange servers in a single forest, aren’t classified as multi-forest in hybrid deployment scenarios. These types of organizations should consider themselves a single forest organization when planning and configuring a hybrid deployment.

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.


System Requirement


x64 architecture-based computer with Intel processor that supports Intel 64 architecture (formerly known as Intel EM64T)
AMD processor that supports the AMD64 platform
Intel Itanium IA64 processors not supported


Varies depending on Exchange roles that are installed:
Mailbox   8GB minimum
Client Access   4GB minimum
Mailbox and Client Access combined   8GB minimum

Disk space

At least 30 GB on the drive on which you install Exchange
An additional 500 MB of available disk space for each Unified Messaging (UM) language pack that you plan to install
200 MB of available disk space on the system drive
A hard disk that stores the message queue database on with at least 500 MB of free space.


DVD-ROM drive, local or network accessible

Screen resolution

1024 x 768 pixels or higher

Mailbox or Client Access

Windows Server 2008 R2 SP1 Standard or Enterprise
Standard – for Exchange 2013 Client Access servers

Management workstation

Windows Server 2012
Windows Server 2008 R2 Standard with SP1
Windows Server 2008 R2 Enterprise with SP1
Windows Server 2008 R2 Datacenter RTM or later
64-bit edition of Windows 8 Release Preview
64-bit edition of Windows 7 with SP1

File format Disk partitions formatted as NTFS file systems, which applies to the following partitions:
System partition
Partitions that store Exchange binary files
Partitions containing transaction log files
Partitions containing database files
Partitions containing other Exchange files

Use spaces to separate tags. Use single quotes (') for phrases.

Write Your Own Review

You're reviewing: Microsoft Exchange Server 2013 Standard with Service Pack 1

How do you rate this product? *

  1 star 2 stars 3 stars 4 stars 5 stars