Wednesday, 29 August 2012

Server Roles in Exchange Server 2013

In Exchange Server 2007 and Exchange Server 2010, we have 5 Server roles like Mailbox, Client Access, Hub Transport, Unified Message and Edge Transport Server. Exchange Server 2013 has only 2 server roles; they are Mailbox Server Role and Client Access Server.

Mailbox Server Role:
Mailbox Server role in Exchange server includes the Mailbox server components found in Exchange 2010, and the Client Access protocols, Hub Transport service, Mailbox databases, and Unified Messaging functionality. The Mailbox server handles all activity for a given mailbox.

Client Access Server Role:
The Client Access server provides authentication, redirection, and proxy services. The Client Access server itself doesn't do any data rendering. The Client Access server is a thin and stateless server. There is never anything queued or stored on the Client Access server. The Client Access server offers all the usual client access protocols like HTTP, POP and IMAP, and SMTP and all the client connection including public folder access goes via Client Access Server role.

You may have a question like, what happened to Hub Transport Server and Unified Messaging Server role in Exchange Server 2013

Functionality of the Hub Transport Server and Unified Messaging Server are still available but the Hub Transport Server and Unified messaging server role components distributed to Mailbox and client access server roles in Exchange Server 2013

What’s new in Exchange Server 2013

In this post we will have a look on the new features that are introduced in Exchange Server 2013 and on the later topics we will discuss more on the same.

Only two Server Roles in Exchange 2013

With Exchange 2007 and Exchange 2010 we have 5 server roles but Exchange 2013 preview only has Mailbox server role and Client Access Server role. It feels like we are going back to Exchange 2003 concept. Having only 2 doesn't mean that other server roles are removed in Exchange 2013, all the Hub and UM role Componentsfunctionalities are shared between Mailbox and Client Access Server roles

Exchange 2013 has new Management Console

Exchange 2007 and Exchange 2010 have the new management console like Exchange Management console, Exchange Control Panel and Exchange Management Shell. Exchange 2013 Preview has a brand new management console named Exchange Administration Center (replacement of Exchange Management Console) and Exchange Management Shell.

Exchange Administration Center is a web based unified management console which replaces the legacy exchange management console and the Exchange control panel. This is similar to administration center available in Windows 2012. We can access the EAC using http://ClientAccess-ServerName/ECP

High Availability Concept in Exchange 2013

High Availability for Mailbox databases will have the same Database Availability Group. The rewritten code of transactional logs and exchange managed Store make the failover faster.

Messaging policy and compliance

Exchange 2013 preview has a new feature named Data Loss Prevention which helps to protect sensitive data and inform users of compliance policies. Data Loss Prevention also does the same functions like Mail Tips.

Archiving Retention and E Discovery

In place hold in Exchange 2013 allows to place a query based hold or litigation hold and the In-place e-discovery allows searching and preserving data across multiple data repositories. In Place e-discovery feature allows the ability to perform discovery search across Exchange mailbox, SharePoint 2013 preview and Lync 2013 preview.

Archive Mailbox Search from OWA– Exchange 2013 allows the option to search the Mailbox and Archive mailbox from OWA and users can apply personal tags to default folders from OWA.

New Mail flow Architecture

Because of the new architecture in Exchange 2013 with 2 server roles, Mail flow in exchange 2013 has a new architecture made up of several different services like the Front End Transport service on Client Access servers, the Hub Transport service on Mailbox servers, and the Mailbox Transport service on Mailbox servers.

Transport Rules

Transport rules in Exchange 2013 preview is similar to exchange 2010 transport rules and having few additional options on the transport rule predicates and actions.

Self-Signed certificate automatically trusted by Client Access

Earlier certificate warning in OWA, because of the self-signed certificate issue is not available in Exchange 2013. Mailbox Server will have a default self-signed certificate and this will be automatically trusted by the client access server in exchange server 2013

New Public Folders concepts in Exchange 2013

Public Folders are now created in Public Folders Mailbox. This public folder architecture uses the specially designed mailboxes to store both the hierarchy and the public folder content. This new design also means that there is no longer a public folder database. Public folder replication now uses the continuous replication model.

New Site Mailbox

Site Mailboxes improve collaboration and user productivity by allowing access to both documents in a SharePoint site and email messages in an Exchange mailbox, using the same client interface. To have the Site Mailbox functionality we need to deploy SharePoint

Unsupported Configuration:

  • Exchange 2003 cannot be supported in a coexistence environment.
  • Exchange 2013 preview Mailboxes can be accessed via the client like outlook 2007 SP3, Outlook 2010 SP1 and Outlook 2013 preview

Lot of new features are available in Exchange 2013 and those information will be added later.

Monday, 27 August 2012

Step by Step installation of Exchange 2013 – Part 2

On this second part of "Step by Step installation of Exchange 2013 - 2", we will look at how to install the Exchange 2013 Preview. In short we have the environment setup with the below details

Prerequisite check before installing Exchange Server 2013 preview version

  1. Domain controller, schema Master and Global Catalog servers are running with Windows Server 2003 Sp1 or later
  2. Domain and Forest functional level is Windows Server 2003 or later
  3. Exchange 2013 Server is joined to the domain
  4. Exchange 2013 is installed with all the prerequisites that are mentioned in my previous post
  5. Schema Preparation is completed
  6. Active Directory Preparation is completed and
  7. We are going to install Exchange 2013 Server using the account that has the Local Administrator Permission, Domain Administrator and Enterprise Administrator permission on the Domain

Note: Exchange 2013 has 2 server roles, they are Mailbox Server role and Client Access Server role. We have the option to install each server roles in separate servers or it can be installed together. Single Server role or both the servers roles can be selected during the installation, then Exchange Management Tools will be installed together.

Step 4: How to Install Exchange 2013 Preview

To initiate the exchange 2013 installation, click on the setup file available on the installation media. Once the Setup is clicked below window appears up, take necessary action and click next to continue


On the next window Exchange 2013 installation files will get copied and once it is completed click next to continue


On the Introduction page, read the information and click next to continue. If you plan to use Deployment assistant click on the necessary option.


On the next page, click I accept on the License Agreement page and click next to continue


On the Error Reporting Window, Click Yes and click Next to continue


Next window will automatically check for the required software that are missing in the Server, if any issue, it will prompt you. If no error click next to Continue


On the Server Role Selection Windows, if it is standalone installation select both the Mailbox and Client Access Server role and click next to continue


Installation Space and Location windows will allow an option to change the installation path, make necessary change or leave the default path and click next


Malware Protection Setting, this option is new in exchange 2013 which will by default scan all the emails, if you are using other option disable the option and click next to continue


If this Exchange 2013 server is a internet facing client access server then check the option and enter the internet domain name


On the Customer Experience Improvement Program, read the information, choose the required option and click next to continue


Readiness check windows will check of the all the options prior to install the Exchange Server 2013. If everything is normal, then the installation will start


 


Once the readiness check is completed Exchange Server 2013 installation will happen. Once it is completed, click finish is complete the installation.


Exchange Server 2013 preview has the new exchange management console named Exchange Admin Center (web based console). To open Exchange Admin Center, use the Client Access Servers exchange control panel url http://clientaccess-servername/ecp

Let us know if you are facing any issue in installing Exchange Server 2013. We will assist you.

Step by Step installation of Exchange 2013 – Part 1

In this post, we will have a look on how to install Exchange 2013 Preview on a Windows Server 2008 R2 server. I separated this post into two parts where the first part will discuss the Preparation of Exchange Server 2013 for installation and the Second part discuss on how to install Exchange Server 2013 Preview

This first part of "Step by Step installation of Exchange 2013" discusses the below topics

Step by Step installation of Exchange 2013 – Part 1


  • How to Prepare the Exchange 2013 server with the Prerequisites installation

  • How to Prepare the Active Directory Schema for Exchange 2013 installation

  • How to Prepare the Active Directory for Exchange 2013 installation

  • How to Install Exchange 2013 Server


[box type="info"] Before Performing the below steps 1. Make sure your Domain Controller, Global Catalog Servers are Running With Windows Server 2003 SP2 or later 2. Make Sure the domain and the forest functional Level is windows Server 2003 3. Join the Exchange 2013 server to domain 4. Login with the account having Enterprise Admin, Schema Admin and Local Admin permission[/box]

Step 1: How to Prepare the Exchange 2013 server with the Prerequisites installation


Active Directory Requirements


Domain Controller, Global Catalog and Schema Master servers has to be running on Windows Server 2003 SP1 or latter

Domain and Forest functional level has to be window 2003 or later

Operating System Requirements


Exchange Server 2013 can be installed on full installation of 64 bit version Windows Server 2008 R2 Sp1 or Windows Server 2012

Exchange 2013 Management Tools can be installed on Windows 7 64 bit or Windows 8 64 version

Exchange Server 2013 prerequisites


We are installing Exchange 2013 preview on Windows Server 2008 R2 Preview and below prerequisites are installed before running the Exchange 2013 setup

From Windows PowerShell run the below command

Import-Module ServerManager


And then run the below command to install all the windows features that are needed to install Exchange 2013 Preview

Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-Auth, Web-Client-Auth, Web-Digest-Auth, Web-Dir-Browsing, Web-Dyn-Compression, Web-Http-Errors, Web-Http-Logging, Web-Http-Redirect, Web-Http-Tracing, Web-ISAPI-Ext, Web-ISAPI-Filter, Web-Lgcy-Mgmt-Console, Web-Metabase, Web-Mgmt-Console, Web-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI


Once the above features are installed, then download all the below components are install it on the Exchange 2013 Server

  1. Microsoft .NET Framework 4.5 RC

  2. Windows Management Framework 3.0

  3. Microsoft Unified Communications Managed API 4.0, Core Runtime 64-bit

  4. Microsoft Office 2010 Filter Pack 64 bit

  5. Microsoft Office 2010 Filter Pack SP1 64 bit

  6. Microsoft Knowledge Base article KB974405 (Windows Identity Foundation)

  7. 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)

  8. Knowledge Base article KB2533623 (Insecure library loading could allow remote code execution)


Once the above 8 components has been installed then perform the below steps

Uninstall Microsoft Visual C++ 11 Beta Redistributable (x64) from Windows AddRemove Programs

  • Register ASP.NET with .NET Framework 4.5 in Internet Information Services (IIS) – You can do this by running the below switch from command prompt

  • C:WindowsMicrosoft.NETFramework64v4.0.30319aspnet_regiis.exe -ir –enable

  • And then restart IIS using IISReset

  • Join the computer to the Domain


Step by Step installation of Exchange Server 2013


Now we assume the Domain controlled is in place and the Exchange Server 2013 preview server has been prepared with above prerequisites

Step 2: How to Prepare the Active Directory Schema for Exchange 2013 installation


If you are preparing Active Directory from other servers, then prerequisites like .Net framework 4.5 and Windows Management Framework 3.0 has to be installed and before running the Active Directory preparation switch run the below switch from Windows PowerShell

Add-WindowsFeature RSAT -ADDS


Navigate the Exchange 2013 preview installation directory and prepare the Active Directory Schema using the below commands in command prompt.

Note: /IAcceptExchangeServerLicenseTerms has to be added while running Setpup.exe commands to prepare the schema



Step 3: How to Prepare the Active Directory for Exchange 2013 Preview installation


If you are preparing Active Directory from other servers, then prerequisites like .Net framework 4.5 and Windows Management Framework 3.0 has to be installed and before running the Active Directory preparation switch run the below switch from Windows PowerShell

Navigate the Exchange 2013 installation Directory and Prepare the Active Directory using the below commands from command prompt.

Note: Exchange Organization name and the /IAcceptExchangeServerLicenseTerms has to be specified while preparing the Active Directory



Once the Active Directory preparation is completed, the below default Exchange security groups or the default management roles will be created



Once the Preparation of Schema and Active Directory is completed, if you are having multiple domains than the below switch can be used to prepared the domains PrepareDomain or PrepareAllDomain

So for we completed the below tasks

  • We prepared the Domain environment,

  • We prepared the Exchange 2013 server with the prerequisites installation and

  • Active Directory Schema Preparation and Active Directory Domain Preparation are completed


In the next part of Step by Step installation of Exchange 2013 – Part 2 will discuss on how to install Exchange Server 2013 on Windows Server 2008 R2 SP1

Saturday, 4 August 2012

Public Folders in Exchange Server 2013

In Exchange 2013, we don't have a Public Folder Database, but we have the option to create Public Folders. Wondering how we can create a public folder without a Public Folder Mailbox database? Yes it is possible and we can create the public Folders on a Special Mailbox called Public Folder Mailbox.

Public Folder Mailbox will allow the option to have the same functionality as like legacy version of public folders and it store both the hierarchy and the public folder contents.


We will have a look on the below topics related to Public Folders in Exchange Server 2013



    • Creating a New public Folder Mailbox

    • Creating a New Public Folder

    • Creating the Sub Folders

    • Mail enabling Public Folder

    • Assigning Send As and Send on Behalf of permission on a Public Folder

    • Permission on Public Folders



Creating a New Public Folder Mailbox


By default there won't be any public folder mailbox created on the exchange server. If we want to have the Public Folders in Exchange Server 2013, then we need to create a New Public Folder Mailbox. The first created Public Folder Mailbox will have a writable copy of the Public Folder hierarchy

Note: We cannot directly create a public Folder in first place without having a Public Folder Mailbox. Without having a Public Folder mailbox and Creating a Public Folder in Exchange 2013 will show the below error message



Below screen shows the Public Folders options on Exchange Admin Center.



To create a New Public Folder Mailbox, login to Exchange Admin Center -> Navigate to Public Folders on the left side menu -> Select the Public Folder Mailbox option on the centre screen -> Click on the + symbol to create the first Public Folder Mailbox

Type the Name and Select the OU and Mailbox Database for the New Public Folder Mailbox and click Save. For this new Public Folder Mailbox I create a separate mailbox database to separate the mailbox and Public Folder mailbox in different database.



Below screen show the newly created Public Folder Mailbox.



Creating a Public Folder in Exchange Server 2013


To create a New Public Folder, login to Exchange Admin Center -> Navigate to Public Folders on the left side menu -> Select the Public Folder option on the centre screen -> Click on the + symbol to create the New Public Folder

Enter the Name for the Public Folder and click on Save will create a new Public Folder on the Public Folder Mailbox. The Path of the Public Folder Mailbox will default to the root of the Public Folder Mailbox.



Below screen shows the newly created Public Folder

Creating Sub Folders on Public Folder


To create a New Sub Public Folder, login to Exchange Admin Center -> Navigate to Public Folders on the left side menu -> Select the Public Folder option on the centre screen -> On the Search option search option enter the full name of the Public Folder and click enter will resolve the name and the Path will set to that folder

Now clicking on the + symbol will create a new sub public folder on the selected Public Folder.



Below screen shows the Confirmation of Sub Public Folder creation on the Top level Public Folder named HR Managers



Mail Enabling a Public Folder in Exchange Server 2013


To mail enable a Public Folder, login to Exchange Admin Center -> Navigate to Public Folders on the left side menu -> Select the Public Folder option on the centre screen on which you want to mail enable



On the above right bottom corner we have the option the mail enable or mail disable a public Folder, click on Mail Enable will enable the mail attributes on the Public Folder. If the Public Folder name is like Human Resource Managers then the email address will be assigned as humanresourcemanager@domainname.com

Assigning Send as and Send on Behalf of Permission on Exchange 2013 Public Folder


To assign a Send as or Send on Behalf of Permission on a Public Folder, go to the properties of the Public Folder (double click the concerned public folder or the select the concerned public Folder and click on edit) and select Delivery Option, here we have the option to grant Send As and Send On Behalf of permission to a user, also we have the option to set a forward option.



Permissions on Public folders in Exchange Server 2013


By default, when a public folder is created, Authentication users will get a Author Permission and the Anonymous user with None Permission.



Assigning Public Folder Client Permission


We have the option to set the Client Level Permission using the Exchange Shell command, below shows an example



Assigning Public Folder Administrative Permission


As like previous version of Exchange 2007 and 2010, we don't have the Public Folder Administrative permission option in Exchange Server 2013. I believe because of the new public folder architecture there is no need of Add-PublicFolderAdministrativePermission

Public Folder Move request and Public Folder Migration Request


Because of Public Folders in Exchange Server 2013 are created in Public Folder Mailbox, like the option to see the Mailbox Move request status in exchange server 2010, we have the option in exchange server 2013 to see the Public Folder Move request using the Get-PublicFoldersMoveRequest and the Get-PublicFoldersMoveRequestStatistics.

Also if we have Get-PublicFolderMigrationRequest and Get-PublicFolderMigrationRequestStatistics

Public Folder Database command lets


[notice]Microsoft mentioned that there is no Public Folder Database is Exchange Server 2013, but the Exchange Shell commands have the option to create New-PublicFolderDatabase and Get-PublicFolderDatabase cmdlets[/notice]

Above are the basic details that I gathered related to Public Folders in Exchange Server 2013, if you want me to add another details related to Public Folders in Exchange Server 2013, please leave your comments…

Friday, 3 August 2012

Exchange Server 2013 Services

Below are the services available on Exchange Server 2013 preview and its basic functionalities. All the services related to Exchange Server are in dependant with Microsoft Exchange Active Directory Topology, if this service fails exchange won't function properly.

Microsoft Exchange Active Directory Topology: Provides Active Directory topology information to Exchange services, If this service is stopped Exchange Server 2013 won't function properly

Microsoft Exchange Anti-spam Update: The Microsoft Forefront Protection 2010 for Exchange Server anti-spam update service.

Microsoft Exchange Diagnostics: Agent that monitors server health

Microsoft Exchange EdgeSync: Replicates configuration and recipient data from the Hub Transport servers to the Edge Transport servers.

Microsoft Exchange Frontend Transport: This service proxies SMTP connections inbound to Hub servers and outbound from Hub servers

Microsoft Exchange Health Manager: Manages Exchange server health

Microsoft Exchange IMAP4: Provides Internet Message Access Protocol service to clients

Microsoft Exchange IMAP4 Backend: Provides Internet Message Access Protocol service to Mailboxes

Microsoft Exchange Information Store: Manages the Microsoft Exchange Information Store. This includes mailbox databases and public folder databases

Microsoft Exchange Mailbox Assistants: Performs background processing of mailboxes in the Exchange store

Microsoft Exchange Mailbox Replication: Processes mailbox move requests.

Microsoft Exchange Mailbox Transport Delivery:

Microsoft Exchange Mailbox Transport Submission:

Microsoft Exchange Monitoring: Allows applications to call the Exchange diagnostic cmdlets

Microsoft Exchange POP3: Provides Post Office Protocol version 3 service to clients

Microsoft Exchange POP3 Backend: Provides Post Office Protocol version 3 service to mailboxes

Microsoft Exchange Replication: The Microsoft Exchange Replication service provides replication functionality for mailbox databases on Mailbox servers in a database availability group

Microsoft Exchange RPC Client Access: Manages client RPC connections for Exchange

Microsoft Exchange Search: Drives indexing and querying of data for Exchange

Microsoft Exchange Search Host Controller: This service provides host level deployment and management services for applications

Microsoft Exchange Server Extension for Windows Server Backup: Enables Windows Server Backup users to back up and recover application data for Microsoft Exchange Server

Microsoft Exchange Service Host: Provides a host for several Microsoft Exchange services

Microsoft Exchange Throttling: Limits the rate of user operations

Microsoft Exchange Transport: Exchange Transport Service

Microsoft Exchange Transport Log Search: Provides remote search capability for Microsoft Exchange Transport log files

Microsoft Exchange Unified Messaging: Enables Microsoft Exchange Unified Messaging features. This allows voice and fax messages to be stored in Microsoft Exchange and gives users telephone access to e-mail

Microsoft Exchange Unified Messaging Call Router: Enables Microsoft Exchange Unified Messaging Call Router features

Other services - IIS Admin Service which handles SMTP and other Web related features and the Net.Tcp Port Sharing Service plays an important role on the Message Transport.

I hope this is informative...