Microsoft Exchange Server 2013 – At a glance

Before you install Microsoft Exchange Server 2013, we recommend that you review this topic to ensure that your network, hardware, software, clients, and other elements meet the requirements for Exchange 2013. Exchange Server 2013 RTM to the public release is as part of the planned release of Office 2013 products.

Microsoft Exchange Server 2013 enables you to maintain control, increase user productivity, and keep your organization safe:

  • Remain in control, online and on-premises. Exchange Server 2013 enables you to tailor your solution based on your unique needs and ensures your communications are always available while you remain in control, on your own terms – online, on-premises, or a hybrid of the two.
  • Do more, on any device. Exchange Server 2013 helps your users be more productive by helping them manage increasing volumes of communications across multiple devices and work together more effectively as teams.
  • Keep your organization safe. Exchange Server 2013 keeps your organization safe by enabling you to protect business communications and sensitive information to meet internal and regulatory compliance requirements.
  • Available in these languages: Arabic, English, Chinese (Simplified), Chinese (Traditional), Dutch, French, German, Hebrew, Italian, Japanese, Korean, Portuguese (Brazil), Russian, Spanish
  • Available in these editions: 64-bit

Understanding the coexistence scenarios that are supported for Exchange 2013 and earlier versions of Exchange

  • Exchange Server 2003 and earlier versions: Not supported
  • Exchange 2007: Supported (Requires Exchange 2007 Service Pack 3 (SP3) and an update rollup, to be released at a later date, on all Exchange 2007 servers in the organization, including Edge Transport servers.)
  • Exchange 2010: Supported (Requires Exchange 2010 SP3 (to be released at a later date) on all Exchange 2010 servers in the organization, including Edge Transport servers.)
  • Mixed Exchange 2010 and Exchange 2007 organization: Supported (Requires Exchange 2007 SP3 and an update rollup, to be released at a later date, on all Exchange 2007 servers in the organization, including Edge Transport servers. Also requires Exchange 2010 SP3 (to be released at a later date) on all Exchange 2010 servers in the organization, including Edge Transport servers.)
  • Hybrid Deployment: Exchange 2013 supports hybrid deployments with Office 365 tenants that have been upgrade to the latest version of Office 365.

Lists the requirements for the network and the directory servers in your Exchange 2013 organization.

Schema master: the schema master runs on the first Windows Server 2012 or Windows Server 2008 R2 or Windows Server 2008 or Windows Server 2003 domain controller installed in a forest. The schema master must be running any of the following:

  • Windows Server 2012 Standard or Datacenter
  • Windows Server 2008 R2 Standard or Enterprise
  • Windows Server 2008 R2 Datacenter RTM or later
  • Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
  • Windows Server 2008 Datacenter RTM or later
  • Windows Server 2003 Standard Edition with Service Pack 2 (SP2) or later (32-bit or 64-bit)
  • Windows Server 2003 Enterprise Edition with SP2 or later (32-bit or 64-bit)

Global catalog server: In each Active Directory site where you plan to install Exchange 2013, you must have at least one global catalog server running any of the following:

  • Windows Server 2012 Standard or Datacenter
  • Windows Server 2008 R2 Standard or Enterprise
  • Windows Server 2008 R2 Datacenter RTM or later
  • Windows Server 2008 Standard or Enterprise (32-bit or 64-bit)
  • Windows Server 2008 Datacenter RTM or later
  • Windows Server 2003 Standard Edition with Service Pack 2 (SP2) or later (32-bit or 64-bit)
  • Windows Server 2003 Enterprise Edition with SP2 or later (32-bit or 64-bit)

Domain controller: In each Active Directory site where you plan to install Exchange 2013, you must have at least one writeable domain controller running any of the following:

  • Windows Server 2012 Standard or Datacenter
  • Windows Server 2008 R2 Standard or Enterprise SP1 or later
  • Windows Server 2008 R2 Datacenter RTM or later
  • Windows Server 2008 Standard or Enterprise SP1 or later (32-bit or 64-bit)
  • Windows Server 2008 Datacenter RTM or later
  • Windows Server 2003 Standard Edition with Service Pack 2 (SP2) or later (32-bit or 64-bit)
  • Windows Server 2003 Enterprise Edition with SP2 or later (32-bit or 64-bit)

Active Directory forest: Active Directory must be at Windows Server 2003 forest functionality mode or higher.

The Active Directory driver: Microsoft Exchange Server 2013 uses Active Directory to store and share directory information with Windows. Active Directory forest design for Exchange 2013 is similar to Exchange Server 2010, except in a few ways, which is The Active Directory driver, the core Microsoft Exchange component that allows Exchange services to create, modify, delete, and query for Active Directory Domain Services (AD DS) data. In Exchange 2013, all access to Active Directory is done using the Active Directory driver itself. Previously, in Exchange 2010, DSAccess provided directory lookup services for components such as SMTP, message transfer agent (MTA), and the Exchange store. The Active Directory driver also uses Microsoft Exchange Active Directory Topology (MSExchangeADTopology), which allows the Active Directory driver to use Directory Service Access (DSAccess) topology data. This data includes the list of available domain controllers and global catalog servers available to handle Exchange requests.

IPv6 Support: In Exchange 2013, IPv6 is fully supported, but only when IPv4 is also installed. You can disable IPv4 so only IPv6 is enabled, but uninstalling IPv4 isn’t supported. If Exchange 2013 is deployed in this configuration, all Exchange servers can send data to and receive data from devices, servers, and clients that use IPv6 addresses.

Micrososft don’t support the installation of Exchange 2013 on a computer that’s running in Windows Server Core mode. The computer must be running the full installation of Windows Server. If you want to install Exchange 2013 on a computer that’s running in Windows Server Core mode, you must convert the server to a full installation of Windows Server by doing one of the following:

  • Windows Server 2008 R2   Reinstall Windows Server and select the Full Installation option.
  • Windows Server 2012   Convert your Windows Server Core mode server to a full installation by running the following command.  Install-WindowsFeature Server-Gui-Mgmt-Infra, Server-Gui-Shell -Restart

Supporting Client: Exchange 2013 supports the following minimum versions of Microsoft Outlook and Microsoft Entourage for Mac:

  • Outlook 2013
  • Outlook 2010 SP1 with April 2012 Cumulative Update
  • Outlook 2007 SP3 with July 2012 Cumulative Update
  • Entourage 2008 for Mac, Web Services Edition
  • Outlook  for Mac 2011

What do you need to know before you begin?

  • Estimated time to complete: 60 minutes
  • Make sure you’ve read the release notes prior to installing Exchange 2013.  Release Notes for Exchange 2013.
  • Each organization requires at a minimum one Client Access server and one Mailbox server in the Active Directory forest. Exchange 2013 doesn’t require you to deploy a Client Access server in each Active Directory site containing a Mailbox server. For example, you can deploy Mailbox servers to non-Internet-facing sites and then proxy communications to those Mailbox servers from Client Access servers in Internet-facing sites. If you’re separating your server roles, we recommend installing the Mailbox server role first.
  • The computer you install Exchange 2013 on must have a supported operating system (such as Windows Server 2008 R2 with Service Pack 1 (SP1) or Windows Server 2012), have enough disk space, be a member of an Active Directory domain, and satisfy other requirements.  Exchange 2013 System Requirements.
  • To run Exchange 2013 setup, you must install Microsoft .NET Framework 4.5, Windows Management Framework 3.0, and other required software. To understand the prerequisites for all server roles, see Exchange 2013 Prerequisites.
  • You must ensure the account you use is delegated membership in the Schema Admins group if you haven’t previously prepared the Active Directory schema. If you’re installing the first Exchange 2013 server in the organization, the account you use must have membership in the Enterprise Admins group. If you’ve already prepared the schema and aren’t installing the first Exchange 2013 server in the organization, the account you use must be a member of the Exchange 2013 Organization Management role group. Administrators who are members of the Delegated Setup role group can deploy Exchange 2013 servers that have been previously provisioned by a member of the Organization Management role group.
  • For information about keyboard shortcuts , see Keyboard Shortcuts in Exchange 2013.

Download Microsoft Exchange Server 2013, Click here

NOTES:

  • After you install any server roles on a computer running Exchange 2013, you can’t use the Exchange 2013 Setup wizard to add any additional server roles to this computer. If you want to add more server roles to a computer, you must either use Add or Remove Programs from Control Panel or use Setup.exe from a Command Prompt window.
  • After you install Exchange 2013 on a server, you must not change the server name. Renaming a server after you have installed an Exchange 2013 server role is not supported.
  • If you have User Access Control (UAC) enabled, you must right-click Setup.exe and select Run as administrator.
  • The organization name can’t contain more than 64 characters. The organization name can’t be blank.
  • Pre-requisites option installs only the Windows features required by Exchange. You must manually install other prerequisites manually. For more information, see Exchange 2013 Prerequisites.

Exchange Server 2013 comes with a number of new features as well as improvements on existing features that are already familiar to those who have worked with Exchange Server 2010.

List as follows:

  • Server roles to just two; Client Access server and Mailbox server
  • New Outlook 2013 and Outlook Web App user interfaces, and offline access for OWA
  • No more Exchange Management Console, all administration is now performed using the new web-based Exchange Administration Center , Exchange Management Shell (using PowerShell 3.0)
  • Improvements to high availability features and manageability
  • Public folders are now stored in mailbox databases and can take advantage of Database Availability Groups for replication and high availability
  • Data loss prevention capabilities that can be integrated into Transport Rules

About author

You might also like

Apple

Visual Studio for Mac

Visual Studio Code is free and available on your favorite platform—Linux, Mac OSX, and Windows. First-class support for building ASP.NET 5 and Node.js applications A lightweight, fast, keyboard-centric tool Support

GreatPlains 2010

Microsoft Dynamics GP “12” Web Client Architecture

The Web Client is the full GP application delivered through the Web. The key pieces to be delivered will be the core application components, ISV dictionaries, and in-house customizations –

Office 2010

Exchange server 2010 – SAN certificate creation for autodiscover,EWS and OWA etc…!

Good News for installations guys out there, Exchange server 2010 SAN certificate creation very easy…click here to read my blog ENJOY!!!!!!!!!!!!!!!!!!!!

0 Comments

No Comments Yet!

You can be first to comment this post!

Leave a Reply