Exchange 2013 New

Slide 1

Ricoh India Ltd

Exchange Server 2013

1Prepared By : Shaban Khan & Ashwani DixitAgenda15/02/20142Exchange Server HistoryExchange 2013 Comparison with older versions.Exchange 2013 ArchitectureExchange 2013 FeaturesExchange 2013 live demoExchange 2013 High AvailabilityDescribe Exchange Administrator console(EAC)Describe Exchange Management Shell (EMS)Question & AnswerExamExchange Server History15/02/20143In April, 1996, Microsoft released Exchange Server 4.0, a migration whose planning had begun three years before. This was the first version of the Exchange mail server sold publically, and it was marketed as a step up from Microsoft Mail 3.5Exchange Server 5.0

Launched in 1997.Exchange 5.0 introduced the Exchange Administrator console and Simple Mail Transfer Protocol (SMTP) network access.Need Windows NT 4.0 server OSNew feature introduced as Calendaring and OWA.Server tied email, calendaring and address books all together.Microsoft release the first version of Outlook Web Access.

Exchange Server 5.5In November of the same year, Microsoft released Standard and Enterprise versions of Exchange 5.5. This release marked the point at which Microsoft Outlook replaced the Exchange Client, halting its versioning forevermore.Exchange Server 4.0Exchange Server 5Exchange Server History15/02/2014This was the first version to have a full dependency on Active DirectoryUsed Active Directory for the Global Address List (GAL)

Ability to be configured as a front-end server for Microsoft Outlook Web Access, Microsoft Outlook Mobile Access, Microsoft ActiveSync, Post Office Protocol 3 (POP3), Internet Message Access Protocol (IMAP), and Simple Mail Transfer Protocol (SMTP) Integrated support for mobile devicesStandard: Maximum 16-gigabyte (GB) database limit per database (75 GB with Microsoft Exchange Server 2003 Service Pack 2)Enterprise: 16 terabyte database limit, limited only by hardware.Exchange 2003 only Enterprise cluster supported

Exchange Server 2000Exchange Server 2003Exchange Server History15/02/20145Exchange Server 2007Exchange Management Console The Exchange Management Console combines all your management tasks into one user interface. Exchange Management Shell The Exchange Management Shell is a new task-based command line shell and scripting language for system administration. High availability for Mailbox servers Exchange Server 2007 includes three Inbox features that provide high availability for Mailbox servers: Local continuous replication (LCR): In an LCR environment, the second copy is located on the same server as the production storage group. Cluster continuous replication (CCR): In a CCR environment, the second copy is located on the passive node in the cluster.Single copy clusters (SCC). A single copy cluster is a clustered mailbox server that uses shared storage to allow multiple servers to manage a single copy of the storage groups. This is similar to clustering in previous versions of Exchange ServerExchange Server History15/02/20146Exchange Server 2007Exchange server role base architecture with 5 different rolesMicrosoft introduce outlook anywhere feature.Exchange Server 2007 Database PortabilityOutlook client connected with mailbox server.Enhanced active sync feature.Availability When multiple Exchange 2007 computers that are running the Hub Transport server role are deployed in a site, mail flow between Hub Transport servers and Mailbox servers is automatically load balanced and does not require any additional configuration by the administrator.Exchange Server 201015/02/20147Exchange Server 2010Exchange 2010 continue with 5 rolesCloud on your terms: Deploy mailboxes on-premises, online, or a combination of both with a hybrid deployment.In-place archiving and retention: Automatically retain data based on policy or business requirements and store older content in an In-Place Archive, allowing you to remain compliant.Continuous Background Online DefragmentationExchange Certificate wizardsAll client connectivity with the CAS server.MailTipsOnline Move Mailbox

Exchange Server 201015/02/20148




15/02/201412

Exchange 2007/2010 ArchitectureExchange 2007/2010 Architecture15/02/201413

Exchange Server 201315/02/201414Exchange Server 2013 release on December 3, 2012

Server Roles in Exchange 2013 (Return to Basics)

The Mailbox Server Role: Formerly know as back-end server in Exchange 2003The Client Access Role: Formerly know as front-end server in Exchange 2003Features introduce in Exchange 2013Replace exchange management console by Exchange administrator centre.Microsoft first time introduced web base management console.In place DLP provided by Microsoft in Exchange 2013.Introduce Offline OWA new feature in Exchange 2013.Apps management for client.All Outlook client connectivity through RPC over HTTP.15/02/201415Exchange 2013 ArchitectureEnhanced Exchange Database dependency service: There are Information Store processes (Microsoft.Exchange.Store.Service.exe and Microsoft.Exchange.Store.Worker.exe) which have been completely rewritten in C# to provide greater stability and to allow each database to run under its own process.

So we call the newly rewritten Information Store process the "Managed Store" now which has FAST Search integrated into it with better search and indexingThe Path of Email into the database

When mail comes into the Mailbox server it first goes into memory and then into transaction logs.

From transaction logs it is written to the database

A checkpoint file helps ensure all logs are written

15/02/201416Exchange 2013 Architecture

15/02/201417

Exchange 2013 Architecture15/02/201418

Exchange 2013 Architecture15/02/201419Exchange 2013 Architecture



15/02/201422

When you have a mixed environment is called coexistence and the entire process is called transitioning not upgrading.Ultimately, you install Exchange 2013 into an existing environment, move over mailboxes to the new Exchange servers, and decommission the older systems.Coexistence with Legacy Exchange ServersExchange 2013 Architecture15/02/201423Exchange 2013 Deployment and PrerequisitesProcessor: x64 architecture-based with Intel or AMD 64 platformMemory: Mailbox 8 GB minimum Client Access 4 GB minimum Combination Mailbox/Client Access 8 GB MinimumHardware/Virtual RequirementsDisk: 30 GB free space on drive you install Exchange 2013Virtualization Points to ConsiderBoth server roles are supportedMake sure you use an approved vendor

15/02/201424Exchange 2013 Deployment and PrerequisitesMailbox and Client Access RolesWindows Server 2012 Standard or DatacentreWindows Server 2008 R2 Standard or Enterprise with SP1Windows Server 2008 R2 Datacentre RTM or later

Server Operating Systems require for Exchange 2013Management Tools:Windows Server 2012 R2 Standard or DatacentreWindows Server 2008 R2 Standard or Enterprise with SP1Windows Server 2008 R2 Datacentre RTM or later

15/02/201425Exchange 2013 Deployment and PrerequisitesMicrosoft office requirementOutlook 2013 (15.0.4420.1017)Outlook 2010 Service Pack 1 with the Outlook 2010 November 2012 update (14.0.6126.5000).Outlook 2007 Service Pack 3 with the Outlook 2007 November 2012 update (12.0.6665.5000). Entourage 2008 for Mac, Web Services EditionOutlook for Mac 2011

Outlook clients earlier than Outlook 2007 are not supported. Email clients on Mac operating systems that require DAV, such as Entourage 2008 for Mac RTM and Entourage 2004, are not supported.

We strongly recommend that you install the latest available service packs and updates available so that your users receive the best possible experience when connecting to Exchange 201315/02/201426Exchange 2013 Deployment and PrerequisitesActive Directory PreparationEvery AD site we deploy Exchange is must have at least one Domain controller and Global catalog server (RODCs are not supported)

Need to makes sure your AD forest/domain functional levels at least Server 2003

You need to prepare the schema either before or during the install process (which must be done in the same site as the AD schema master)

15/02/201427Exchange 2013 Deployment and PrerequisitesExchange Server 2013 PrerequisiteWindows Servers features (Can be install automatically during Exchange installation or install through PowerShell)Microsoft .NET Framework 4.5Windows Management Framework 3.0Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bitMicrosoft Office 2010 Filter Pack 64 bitMicrosoft Office 2010 Filter Pack SP1 64 bitMicrosoft Knowledge Base article KB974405 (Windows Identity Foundation)Knowledge Base article KB2619234 (Enable the Association Cookie/GUID that is used by RPC over HTTP to also be used at the RPC layer in Windows 7 and in Windows Server 2008 R2)Knowledge Base article KB2533623 (Insecure library loading could allow remote code execution) 15/02/201428Exchange 2013 ManagementExchange Administration Console (EAC)There are two ways to manage Exchange 2013

15/02/201429Exchange 2013 ManagementExchange Management Shell (EMS)

EMS is both a command-line tool and a scripting platform

Through PowerShell commands you can manage EVERY aspect of Exchange, whereas through the EAC you can manager ALMOST every aspect of Exchange.Learning PowerShell is not an option if you are working with Exchange... it is necessity.15/02/201430Exchange 2013 ManagementWhat are cmdlets?Simple verb-noun structureCommon verbs are: Get, Set, Remove, Test, Enable, Disable, Install, Uninstall, New and Move.Exp. Get-ServicePiplelines | help to string cmdlets togetherGet-Service | where-object {$_.Status -eq "Running"}A good Example of Exchange cmdlets include:A good Example of Exchange cmdlets include:Get-MailboxGet-MailboxStatics Get-mailbox | Set-Mailbox -prohibitsendquota 500MB15/02/201431

Exchange 2013 ManagementExchange ToolboxThe Toolbox is a collection of diagnostic, troubleshooting, and recovery tools installed with Microsoft Exchange.15/02/2014Recipients in Exchange 2013There are many different recipient types and they all have features an properties that must be explored thoroughly in order to know what you can and cannot do with eachRecipient Types: MailboxesUser Mailboxes:The most common recipient type, each mailbox is associated with an active directory account.Linked Mailboxes:Accessed by users in a separate, trusted forest (often used when Exchange is deployed in a resource forest)

Recipient Types: SharedShared Mailbox: Not associated with a single user but is shared by many users as a collaboration tool.

Shared mailboxes are great for people to monitor and/or send email from a common account like [email protected] or [email protected]

You can grant Full Access, Send As or Send on Behalf delegate permissions15/02/201433Recipients in Exchange 2013Recipient Types: GroupsDistribution Group: A mail-enabled AD group (that is static and based on group membership) that can only be used to distribute message.Security Group: An AD universal security group that can be used to distribute messages but can also access resources.Dynamic Distribution Group:Uses filters to create the group based on those filters and conditions established so that person can be part of the group or removed dynamically based on their attributes and the group membership is derived at the time any given message is sent.15/02/201434Recipients in Exchange 2013Recipient Types: ResourcesEquipment Mailbox:Used for scheduling purposes for items like projectors, laptops, even company cars or whatever items need to be managedRoom Mailbox:Used for scheduling purposes for various meeting locations (like the conference room, the auditorium, the lab, a training room an so forth)Mail Contact:An Active Directory contact that is mail-enabled using an external email address.Recipient Types: ContactsMail User:An Ad user that can log into AD and can access resources but has external email address.15/02/201435Exchange 2013 database managementEvery email that goes to your Mailbox server must go into a database and this creates challenges because of the huge variety of messages Exchange handles

15/02/201436Exchange 2013 database management

15/02/201437Exchange 2013 database managementDatabase availability Group



15/02/201440Certificates:

Exchange uses "self signed" certificates by default. These work but the aren't appropriate for a production deployment. We need to obtain and install better certs on the Exchange server for a production deployment.

How to deploy Exchange certificate:

Use the Exchange Certificate Wizard to obtain a Certificate Signing Request (CSR).User the CSR to complete the CA authority certificate process.Down the certificate and complete the pending certificate Wizard.Assign the service to the new certificate and demonstrate that it works.Exchange 2013 Certificate Management15/02/201441Question & AnswerExchange 201315/02/201442Thank You201243

Documents

Exchange 2013 New