1. Add your own internet domain to the “Accepted Domains” list

In contrast with previous versions of Exchange (2010, 2007, 2003), there is no longer the MMC application to manage the server. Everything is done with the new Exchange Control Panel (ECP) and the Exchange Management Shell (EMS).

Open the Internet browser and go to the following address:https://exchange.your-domain/ecp

It will redirect us to the login screen in order to authenticate before accessing the ECP.

Once you have entered your credentials, the ECP window appears:

As we've already mentioned, all of the management operations happen here. The first step to configure our server is to add our Internet domain to the "Accepted Domains" list. To do so, go to the Mail Flow option (on the left pane) and select “Accepted Domains” in the menu bar above. There should be a default setting, usually the internal domain name (here servolutions.dom) that you can leave as it is. Now, add a new accepted domain by clicking on the "+" icon:

Now, a pop-up window opens. Add the Internet domain that we want our server to accept. In the "Name" field enter a descriptive name for our rule (In this case, "Domain name for the Internet" is the name that I've chosen). In the Accepted domain field enter the name of your Internet domain name (in this case, servolutions.com). Mark the "Authoritative domain" option and once done, click the SAVE button in the lower part of the window.

This setting indicates that this Exchange server will accept e-mails directed to the "servolutions.com" domain. The Authoritative domain option is to indicate that this server will be the one that processes all of the e-mails sent to the servolutions.com domain.

2. Configure a send connector for outgoing emails

The send connector is used to pipe outgoing emails from Exchange via your providers SMTP relay server to the internet.

In Exchange 2013 the “Hub Transport” role that existed in Exchange 2010 and 2007, is now integrated to the Mailbox server role. So now, all you have to do is click on the Send Connectors menu option.

Here, we add a new send connector by clicking on the "+" icon. A new window will open. In the "Name" field enter a descriptive name for the connector (I've named it "Send Internet Mail"), select the Internet option and click in next.

In most cases your Exchange server will be on a normal internet connection with a dynamic IP address and you should use the webspace provider's SMTP relay server to send out internet through. This ensures our emails are not flagged as spam by the receiving end since it originate from a public IP address.

So in Exchange terms we will use a relay “Smart host” to send e-mail. For this option please select "Route mail through smart hosts" and in the next field add the smart host's address (FQDN).

Once finished, click on Save. The configuration will look like the image shown below.

Click Next. In the next window we will enter the authentication data for the SMTP relay server / smart host. Every commercial relay server requires authentication to keep spammers from abusing them. Choose "Basic authentication" and enter your provider's SMTP server username and password. Note that if you have multiple logins for the server it is notimportant which one you use. It will not affect the email sender name, this log in is purely used to allow you to send email through the relay server.

Click on the Next button.

The next screen asks for the send connector e-mail routing rules. Here we can instruct our Exchange server to use a different e-mail server (smart host) to send e-mails depending on the domain we send to. This is seldom useful and does not allow different smart hosts depending on thesender domain. If you want that please check out our MultiSendcon, the multi-domain send connector for Exchange

In our case only one server is required, so in the next screen we should put an asterisk "*" in the "Domain" field. The asterisk means that e-mail to any other domain outside our organization will be routed through this external smart host. Click on the Next button.

Another window will appear. In this screen we can indicate in which Exchange server this rule will apply. In this case, it applies to our one Exchange server. To set this rule, click on the “+” button and the next window (below) will appear. Here we select the server that this rule will apply. As we have one Exchange server only, we select it here and then click on the "add->" button, so it should look like this:

Once finished just click on the OK button and it'll return to the previous window with the changes made.

Once we are satisfied with the changes, click on finish.

And now we're finished with our outgoing e-mail rule. But one more change should be applied to make it complete: The maximum outgoing message size is set to 10MB by default. This is how to change it: Please click the pencil icon to review and edit our changes:

Change the maximum message size for outgoing emails to a value that is more convenient here and save the changes clicking on the Save button.

With this done, we’re finished with the outgoing mail configuration. Now we’re ready to take a look at the e-mail receiving configuration.

3. Configure the receive connector for incoming email

POPcon uses SMTP to forward emails to Exchange. For this to work we need to have a Receive Connector configured on the Exchange 2013 side and make sure the configuration settings of the new receive connector are correct, especially the maximum email size (which is set to 10MB by default and can cause many problems) and we need to add the anonymous user to the permission group in order to allow POPcon to transfer email into the Exchange server.

Important: You also need to make sure to not install the Windows "Simple Mail Transfer Protocol" service. This service could block the Exchange SMTP transport from actually answering the SMTP IP port (25) and could cause Emails to loop back to the internet if installed. Check Administrative tools, Services and disable this service in case it is installed.

Back to the Exchange configuration: In order to configure the incoming mail rules, open the Exchange Control Panel, go to the "Mail Flow" option located on the left pane and in the right pane, click on "Receive Connectors". The screen will look like the one pictured below.

Select the "+" icon to create a new receive connector and then a new window will appear. In the name field, you can use any descriptive name (in this example we use "Outside World"). In Role select Frontend Transport (Warning: In some systems this does not work and POPcon ends up getting a "Temporary error" when it tries to forward emails to Exchange. If that happens in your case please Hub Transport instead of Front-End. For "Type" select the Internet radio button. Once done click on next.

In the new receive connector dialog we configure it to bind to a particular IP address. We can not use "All available IP addresses" since the default connector already does that. So please change this to the standard server IP address or to be more exact the IP that is reachable from POPcon if there are more than one network cards involved. Edit the setting (click on the pencil icon). A new window will appear:

Change the IP address by selecting the "Specify an IPv4 address…" radio button and enter the server's IP address of the network adapter. Leave the port field in 25 since that is the SMTP default port number. Once finished, click on save.

But we are not finished yet and need to make a couple of adjustments to the newly created receive connector. Open the new "Outside World" connector and edit the settings by selecting it and clicking on the pencil icon.

In the General option we need to change the "“Maximum receive message size" from the default 10MB to 100MB, so larger E-Mails don't get stuck between POPcon and the Exchange Server. If you want you can later limit the maximum message size in the Exchange general options or even for an individual user in their mailbox options and cause Exchange to return undeliverable messages if the email is too large. Check the image below:

Once finished, click on the save button.

Now go to the Security option. Make sure to mark the checkbox which says "Anonymous users" (inside the red square in the image below). Anonymous users are all email senders from outside your organiation, so this check mark allows email senders from outside to deliver email into Exchange. Check the "Anonymous users" checkbox and click on the savebutton.

Now, go to the Scoping option. Make sure to add the localhost (127.0.0.1) and the Exchange server's real IP address, like in the image below. Also make sure that the "Network adapter bindings" option shows the server's IP address and port 25. You can change the FQDN field to reflect the mail server’s fully qualified hostname or you can leave it as it is. That option is not important for POPcon. Click on the save button. With that, we're finished setting up our receive connector.

4. Assign email addresses to users

All you need to do now is to add SMTP email addresses to users in the active directory. Users can have more than one SMTP address, for example they can have info@yourcompany.com in addition to jeff.smith@yourcompany.com.

Exchange provides the convenient E-Mail Address Policies feature that allows you to assign identically formatted email addresses to all (including future) users.

We edit the default email address policy like this: Open the Exchange Control Panel and select the Mail Flow option on the left pane, then select Email Address Policies menu option on the right pane. Select the default policy and click on the edit/pencil icon.

This opens the E-mail address format window. Go straight to "Email Adress Format" and click in the edit button (again, the pencil icon). Select the domain in which we want to apply the new rule (in this example, servolutions.com) and below we can select the format that we will use for all of our e-mail addresses (in this caseJohn.Smith@servolutions.com). Finally, we mark the checkbox named "Make this format the reply email address" in order to force users to use this naming rule. Once finished, click on Save.

Once the changes are saved, the Default Policy window will be updated.

And that's really all. Now the server is correctly set up to send email out to the internet, receive internet from the internet (via POPcon - see below) and we have given users appropriate email addresses.

5. Installing and configuring POPcon or POPcon PRO

After going through the above 4 steps your Exchange is configured to send out email but it still can't pull down email from POP3 or IMAP mailboxes on your provider server. For this you need to install and configure POPcon.

Configuring POPcon is quite straightforward. You need to follow these steps:

a) Configure a Postmaster email address on the GENERAL configuration tab.

b) Add one or more POP3 mailboxes on the POP3/IMAP tab.

c) Configure the Exchange server name on the EXCHANGE configuration tab.

Download and run the self-extracting installer of POPcon or POPcon PROand follow the instructions during the installation. It will install the POPcon Administrator program and the POPcon service that runs in the background on your system.

Run POPcon Adminstrator from Start > Programs > POPcon

POPcon Screenshot

Click on "Configure" to open up the POPcon configuration screen.

a) Configure a Postmaster email address on the GENERAL configuration tab.

On this first configuration page you only need to enter the email address of your Postmaster or Administrator user. The Postmaster will receive all emails without a valid recipient as well as general POPcon status notifications. It is very important to define a real email address from inside your exchange server here because mails can be lost irretrievably if POPcon forwards some mail with no recipient information to the postmaster and that account does not exist in your exchange server.

You can leave the log file options to their default settings for now.

Next go to the POP3/IMAP tab to configure the POP3 or IMAP mailbox accoutns you want POPcon to download email from.

b) Add one or more POP3 mailboxes on the POP3/IMAP tab.

POPcon PRO collects mail from as many POP3 accounts you like. Just click on Add to add another POP3 host or account to the list of Polled POP3 Hosts. For each server or account you need to fill in the POP3 server settings as shown below.

If you are using catch-all style mailboxes (mailboxes that receive email for a whole domain, regardless of the recipient part before the "@") POPcon needs to filter recipients from incoming mail so only the recipients at your own internet domain are accepted. Please add the domain you consider your own in the "Accepted Recipient Domains" box. This is the same domain you configured earlier in the Exchange Default Policy.

Individual account settings

This dialog lets you input the specifics about a POP3 or an IMAP server you want to have polled by POPcon PRO.

This is the information POPcon PRO needs to know about each server:

Server type:

Here you can select on the four supported server types:

POP3: Default. POP3 servers are by far the most common mail server types on the internet.

POP3-SSL: Some POP3 Servers need SSL encryption enabled for the connection in order to protect passwords and sensitive information. Choose this type to have a SSL-encrypted connection to a POP3 server.

IMAP: IMAP Servers are also quite common and theoretically allow the client to manipulate email folders and move email between folders online. In our case the protocol is used to download email from the INBOX of the IMAP server to your exchange server.

IMAP-SSL: Supports SSL connections to IMAP servers for added protection.

Access:

Configure the server name, account name and password to connect to the mail server here.

Servername: The name the server you want to have polled. You can also enter the IP address directly.

Username: The username needed to log into your POP3 or IMAP mail server.

Password: The password needed to log into your mail server.

IP portnumber: Almost always the TCP/IP port for POP3 mail is 110. Under some circumstances, internet routers or firewalls change the port number. Please ask your network administrator or internet provider. The standard port for POP3-SSL is 995, for IMAP it is 143 and for IMAP-SSL this should be set to 993.

Timeout: Leave this to the default value.

Please ask your POP3 mailbox hosting provider if you do not have the above information.

Type of mailbox / distribution:

POPcon PRO supports both catch-all and single user mailboxes

Catch-all mailbox ("*@domainname.com"): For this type of mailbox, POPcon PRO will distribute the email retrieved from this server according to what it finds in the TO:, CC:, BCC: and other header-fields of the mail. If you choose this option, don’t forget to add your internet domain name(s) to the "Accepted Recipient Domains" box. on the POP3/IMAP configuration dialog

Single user mailbox ("user@domainname.com"):This type of mailbox receives email for only one specific Exchange mailbox. You need to specify the receiver of the email here. POPcon PRO will then direct all mail retrieved from this server to the recipient email address given here.

Delete / keep email on the server:

This block allows you to configure POPcon PRO to either delete email after downloading or keep it on your POP3 or IMAP server for a specified amount of time or indefinitely.

Delete downloaded email: This is the default setting – POPcon PRO will delete the Email on your POP3 or IMAP server after successfully downloading it.

Leave a copy of downloaded email (indefinitely):This option will cause POPcon PRO to leave a copy of the email on the server. Only use this option during testing or when you are sure the mail will be deleted eventually, i.e. by another system periodically downloading an deleting email.

Leave a copy of downloaded email for n number of days: Causes POPcon PRO to leave a copy of the email on the POP3/IMAP server for the specified number of days before deleting it. You can use this option to allow access to a single POP3 or IMAP mailbox by two different systems.

c) Configure the Exchange server name on the EXCHANGE configuration tab.

On this configuration screen you can specify the Exchange™-(SMTP) Server you want the mail to be directed to. Normally this will be the computer name of your Exchange™ server (like "MYSERVER").

You can leave all other settings default

These three steps to configure POPcon will provide you with a working set-up. Test it out by confirming the new configuration with OK and then use the "Trigger mail retrieval" button on the POPcon Administrator main screen to start the first mail download. You can follow what is happening in the scrolling log display on that screen. Watch out for any error messages there. There is also a POPcon log file (c:\program files\POPcon\POPconSrv.log – open with notepad) that you can view at your leisure.

6. Server down? Know about server problems before your users do

We recently introduced ServerPulse, a new service that monitors your servers and immediately alerts you by text message and email if there are any problems. ServerPulse also watches important server operating parameters: Disk space, used RAM and CPU load - so you'll know about problems even before they bring down a system.

Just imagine: Your client doesn't call you because his server is down. Instead you'll call him first

What will that do for your relationship with your client?

This is what ServerPulse will do for you:

• If one of your servers stops working the ServerPulse web server will send you a text message to your mobile phone and an email.
  
  You’ll know exactly which of your servers stopped working and when it happened. You can then decide what to do about it – call someone to put the plug back in :) , restart a virtual machine by remote access or go on-site to check yourself. Once the server is back online you’ll get another notification.
   
• ServerPulse will also notify you if a disk drive starts filling up or a process eats up all the memory. That means you can do something about it before it causes bigger problems.
  We love this feature ourselves because as Microsoft Exchange consultants we see it happening frequently: Exchange shuts down because of the dreaded error message “452 4.3.1 insufficient system resources”, meaning low disk space. And the system administrator never saw it coming without ServerPulse.
   
• And just to be sure you can use our website and our free apps to check the server status on your mobile at any time.
  

Give the service a try - it's free for 30 days: ServerPulse.

7. Check out the ChangeSender Outlook Add-in

ChangeSender Exchange Send-as Add-in adds one important piece of functionality to Microsoft Outlook when used with Exchange Server: It allows you to send as any of your email addresses and even group addresses or those of other users if allowed by the administrator. Effectively this is the Exchange Send-as function without the limitations of the ActiveDirectory

Without the ChangeSender Exchange send-as components, Exchange always sends out emails on your default email address fixed in the ActiveDirectory even when answering emails received on one of your additional email addresses. Also, Exchange does not allow sharing the same email address (i.e. department-wide or company-wide email addresses) between users. ChangeSender solves both problems by adding a configurable "send as" selection box to your Outlook email form.

ChangeSender Features

• Automatically selects the right send-as address when replying to emails. ChangeSender uses the address of the original email as sender address for replies.


• Easy selection of send as addresses for new emails via a new sender address selection box in Outlook.


• Multiple users can send from the same sender address (i.e. send as sales@yourcompany.com or support@yourcompany.com)


• Sender appearance fully configurable as "Any name" <any@address.com> for each individual email address. Does notshow up as "sent on behalf of...".


• Very simple installation and administration.


• Administrator can restrict or allow user choices for the sender address and prevent users from sending as other users.


• Works with Exchange 2010, 2007, 2003, 2000 and with Outlook 2010, 2007, 2003, 2002, 2000 versions.

ChangeSender in Outlook 2007 screenshot

Tools Link

• Exchange 2013 Server Role Requirements Calculator
  • http://blogs.technet.com/b/exchange/archive/2013/05/14/released-exchange-2013-server-role-requirements-calculator.aspx
  • http://www.stevieg.org/2013/05/exchange-2013-server-role-requirements-calculator-what-does-it-mean-for-exchange-implementations
• New mobile app for The UC Architects
  • http://www.windowsphone.com/s?appid=5cdcf6e7-09c3-474f-a741-51bccfa043a2
• AD FS on Azure guidance
  • http://www.microsoft.com/en-us/download/details.aspx?id=38845
• Ask the Perf Guy: Sizing Exchange Server 2013
  • http://blogs.technet.com/b/exchange/archive/2013/05/06/ask-the-perf-guy-sizing-exchange-2013-deployments.aspx
• Script: Paul’s Test-ExchangeServerHealth.ps1
  • http://exchangeserverpro.com/powershell-script-health-check-report-exchange-2010/
• Removing Exchange messages by message class
  • http://eightwone.com/2013/05/16/removing-messages-by-message-class-from-mailbox/
• Exchange 2013 Management Pack
  • http://www.microsoft.com/en-us/download/details.aspx?id=39039
  • http://blogs.technet.com/b/momteam/archive/2013/05/14/exchange-2013-management-pack-released.aspx
• Lync 2013 Management Pack
  • http://blogs.technet.com/b/nexthop/archive/2013/05/17/notes-from-the-field-lync-server-2013-and-active-monitoring-with-system-center-operations-manager.aspx
• Lync Hybrid Voice offers simplified
  • http://blogs.technet.com/b/nexthop/archive/2013/05/13/lync-hybrid-offers-simplified.aspx
• Lync Server root certificate updates for push notifications, federation with Microsoft.com
  • http://blogs.technet.com/b/lync/archive/2013/05/02/lync-mobile-push-notifications.aspx
  • http://blogs.technet.com/b/nexthop/archive/2013/05/09/lync-server-federation-with-microsoft-com-root-certificate-change.aspx
• Remember folks, SQL clustering is ONLY supported in Lync 2013 when migrating from Lync 2010
  • http://technet.microsoft.com/en-us/library/jj205248.aspx
• Lync 2013 client updates released
  • http://support.microsoft.com/kb/2768004
• Custom Lync config.xml file for PortQryUI
  • http://flinchbot.wordpress.com/2013/05/10/portqueryui-config-xml-file-for-lync/
• Lync 2013 Jumpstart with Brian Ricks and Aaron Steele
  • https://www.microsoftvirtualacademy.com/liveevents/Core-Solution-Lync-Svr-JumpStart?CR_CC=200211921
• Lync remote code execution vulnerability
  • https://greiginsydney.com/lync-remote-code-execution-vulnerability-may-2013/
• Lync bandwidth calculator
  • http://www.microsoft.com/en-us/download/details.aspx?id=19011

Exchange 2013 Installation

Installing Exchange Server 2013

Hi all, 

Used this post for my test lab install.

Install Following
http://www.microsoft.com/en-gb/download/details.aspx?id=26604
http://www.microsoft.com/en-gb/download/details.aspx?id=30349
Ensure the account you are using is a member of Exchange Security group Delegated Setup

Exchange Server 2013 preview published , all server components can install on the newest server OS (Windows Server 2012) . If you hope to try it ,you can download it from : http://technet.microsoft.com/en-US/evalcenter/hh973395.aspx?wt.mc_id=TEC_116_1_6

    Today , I will to introduction how to installing Exchange Server 2013 preview .

    My test lab environment OS is all Windows Server 2012 datacenter RTM , forest and domain level are Windows Server 2012.

    The first phase is prepare AD , this phase need to running three commands :

     1.PrepareSchema :

      2.PrepareAD :

      3.PrepareDomain :

    When you finished AD preparation , now you will start to install Exchange Server 2013 preview . Because Exchange Server 2013 just have Mailbox and CAS roles , and Microsoft recommand first install Mailbox role .

    Now insert Exchange Server 2013 Preview image to starting install. 

    "STOP!!!!!!!"  I think you may to ask "You need to install Exchange requirements firstly".

    The answer is NO , Exchange Server 2013 more simplifying the installation process. When you start to install , you will into Check for Update ? dialog box :

    

      Check finished , will copy install file to local :

        Copy finished , will into Introduction dialog box :

    Click Next , will into License Agreement dialog box :

       Accept and click Next , will into Error Reporting dialog box :

     Select your option and click Next , will into Server Role Select dialog box , now you can select your need to installing Exchange role , Mailbox or CAS or both . By default , setup will automatically install Windows Server roles and features :

    Click Next , will into Installation Space and Location dialog box :

    Choose a location and click Next , will into Malware Protection Settings dialog box :

     Select your option and click Next , will into CEIP dialog box :

 

    Select your option and click Next will into Readiness Checks phase :

      Check if OK you can click install to start installing process , waiting some 10 minutes, install finished :

 

    Click complete , you can find Exchange Server 2013 preview shortcut in Start :

       The last , Exchange 2013 have not EMC (Exchange Management Console) mmc snap-in console , in 2013 they called EAC (Exchange Admin Center) , you can throw web browse to access , the address is : http(s)://CAS(FQDN)/ecp .

      Now you can build a test lab to testing more new features .

EXCHANGE 2013 ARCHITECTURE

Exchange 2013 Architecture:

Hi,

Microsoft Released Exchange 2013 which is latest release of the messaging and communications system

on the Windows operating system with the release of Exchange Server 2013, now the eighth major release of Exchange in the over 15-year history of the product, Microsoft has made significant improvements in the areas of global scalability, mobile and tablet client support, security, compliance, reliability, unified communications, and integration with SharePoint 2013 and Lync 2013.

As with Exchange Server 2010, the Exchange Server 2013 product only comes in an x64-bit version.

Exchange Server 2013 requires either Windows Server 2008 R2 or Windows Server 2012 (both x64-

bit only operating systems) to run as the core operating system.

What’s the Same Between Exchange Server 2007/2010 and Exchange Server 2013?

The core infrastructure of Exchange Server 2013 is basically the same as Exchange Server 2007 and

2010. Microsoft continues to use the Jet EDB database as the main database store. Some time ago, it

was rumored that Microsoft would rewrite Exchange to run off SQL Server; however, neither

Exchange Server 2013 nor versions coming out from Microsoft in the foreseeable future will change

the basic EDB database structure.

Exchange Server 2013 still has the concept of a Mailbox server where EDBs are stored, and where

user mailbox data resides. An Exchange server can have multiple Exchange databases running on the

system, and multiple Exchange servers can reside in an environment for both scalability as well as

redundancy.

What’s Missing in Exchange Server 2013 That Was in Previous Versions?

For administrators, the biggest change is the Exchange Management Console (EMC) is completely

gone. No more graphical user interface (GUI)–based administration; however, that doesn’t mean that

administrators are stuck with just PowerShell in the Exchange Management Shell (EMS) environment.

What Microsoft has done is expand the Exchange Control Panel (ECP) from Exchange Server 2010

into the new Exchange Administration Center (EAC).

The Exchange Administration Center allows the administrator a web-based access to everything the

administrator used EMC for before. The administrator can create and manage user mailboxes, manage

Exchange servers, manage public folders, create send and receive connectors, perform eDiscovery

tasks.

Architectural Changes in Exchange Server 2013

• With Exchange Server 2013, Microsoft eliminated the Hub Transport role and the Unified Messaging role, so the core roles are now the Client Access server and the Mailbox server (MBX) roles. 
• The Client Access server (CAS) no longer does data rendering; the role just focuses on authentication, redirection, and proxy. 
• The Mailbox server role now includes Client Access protocols, Hub Transport services, mailbox databases, and Unified Messaging services.
• Because the Client Access server role is drastically simplified to just support HTTP, HTTPS, POP,and IMAP client protocols with no requirement for session affinity between the CAS and MBX roles,Exchange Server 2013 now has better failover and the ability to do simple Level 4 load balancing.
•  CAS and MBX servers no longer need to be geographically close to one another, whereas in the past, the two roles needed to be on the same subnet with high-speed connectivity because of the amount of data transferred between the two servers and the dependence on split roles shared between the two servers. As such, the CAS role can now be geo-centralized with MBX servers distributed to various sites in the enterprise. In addition, with the elimination of integrated components between the CAS and the MBX servers, the requirement of identical patch levels between CAS and MBX servers is no longer a dependency. Organizations can patch and update CAS and MBX servers in a pattern and manner that makes sense to the organization, greatly providing better flexibility in updating an Exchange environment, and greatly improving the uptime of Exchange. 

Architecture Benefits

Building block architecture - for all sizes orgs

Deploying a 2013 CAS enabled you to serve previous & future Exchange versions

Now Layer 4 load balancer - Session affinity no longer required - Entire session state takes place on the active copy hosting the mailbox

CAS now just a protocol proxy.

Functional Layering

CAS now just a protocol proxy

All protocols now hosted as Services on mailbox role.

Changes CAS Role

Still domain joined machine. Comprised of three components

CAS protocols- Http - IMAP - POP,SMTP,UM

Basically its an Exchange aware proxy server - Has all logic - knows where to proxy requests

CAS Array in 2013 - no mapi over tcp - only outlook anywhere - https

No need to layer 7 - designed to work with TCP affinity - layer 4

Image 1

Mailbox to be first one installed as all config is on mailbox server

  

Client Access Service runs on the mbx server, acting as endpoint for CAS protocols such as pop / imap

Transport stack and mail queue previous on hub transport run by the transport service on mailbox server

UM service runs on mbx server

Image 2 Proxying protocols - Note SMTP only for Send / Receive external

 

Benefits of no longer supporting RPC/TCP

Reliable stable model - manages network latency better.

Session always on the mailbox server

No more administrator made a change message to users.

Outlook Connectivity in 2013

1.Recieves HTTP request - AD lookup to retrieve user information / auth user

2.Active manager lookup of the mailbox GUID to identify users database location

3.Proxies request to the mailbox server

Legacy Coexistence - N-2 support - Legacy name space only required is migrating from 2007

Can proxy requests or Cross site redirect to legacy load balancer 37:11

 

Above shows legacy Proxy and cross site proxy request - no legacy name space.

Namespace simplified

Any CAS can now answer to the namespace , no requirement to load balance namespace layer 7

Example of Single Common Namespace.

 

`

Leveraging the clients ability to get multiple DNS IP addresses back for the single name space

User gets IP for VIP1 and second IP for VIP2

Sue will round robin across these, may even bounce between array - has no impact on users

Same server to service the session is no longer required because the session is only located on the mailbox

Server, so any CAS  / load balancer can service the request

CAS Front End Transport Service / Architecture

Handles in inbound and outbound SMTP traffic - NOT the same as hub transport

Does not queue mail - is stateless - is a layer7 proxy - enough routing logic inside of service to allow

Use of layer 4

Listens on 25 and 587

SMTP Receive - Protocol Agents (Not content filtering) just connection filtering recipient and sender filtering

Hub Selector - Choose which mailbox server that contains the hub transport mailbox service that it can send the message to. Via SMTP not RPC

 

From a Mailbox goes to the SMTP receive and then to SMTP to outside world.

Delivery Groups - aka where are we going to send the message to next.

AKA - DAG or AD Site or mailbox

Mailbox Server hosts the components that process, render and store Exchange data.

Includes components previously found in separate roles - mail.que

Only CAS connects directly to the Mailbox Server - All clients connect to the CAS

DAG still the same regards to 16 mailbox server - boundary for replication and DAG members can be in different sites

MAILBOX RELATED CHANGES

Managed Store -

 Store.exe as in previous version has now gone, replaced with Managed Store that’s using a worker model

Store.Service.exe controller process that’s equivalent to store.exe

Manages mounts/dismounts starts or shutdown are worker process - logs failures when store.service detects problems

Manages the life cycle of the worker processes

Store.worker proceess - One per database - RPC endpoint is database guid

Responsible for block mode replication for passive database

Reads against DB, writes to log stream, ESE cache

Replication Service - Hosting Active Manager - Detecting DB failures - Issues Mount/dismount to store - Initiates failovers and failures reported by ESE & Managed Availability

ESE Cache Management

Memory allocated for ESE cache now per database as there is a store.worker process per database

ESE Cache allocated depends on number of local DB copies and number of Active DBs

20% of max cache allocated to passive copies

Max cache calculated at start-up time.

IOPs reductions - Improvements in the logical store schema - Several Messages per page

Large sequential IO used

Support for large mailboxes 100Gb+ / slider bar in Outlook 2013 to manage OST file size

Elimination of Scheduled Maintenance

Now ran within time based assistants - when there's time and resources they will run

Background maintenance can be completed over a longer period of time.

Quota notifications generated at logon time

Modern Public Folders - Public folder database no longer exists

If you want pubic folders you create a PF mailbox - first one called the hierarchy mailbox that stores a writable copy of the public folder tree.

Each subsequent content mailbox add content - when size limited you want its created  - create another. Each once has a copy of the hierarchy mailbox to be able to direct requests

Only one writeable copy of the date - public folder therefore uses continuous replication

New Search Infrastructure

 - FAST - CTS - Content Transformation Service & IMS Interaction Management Service

CTS - Incoming Docs - Parse docs / filter / word break and put into FAST core

IMS - Incoming Queries - Parse query - send back results

 

In Exchange 2013 as messages come in a Transport Layer with are sent to CTS - indexing only once

Mailbox server updates and ExSearch updates and Mailbox CTS reads changes from Transport CTS

If it went to another copy in the DAG the message is not re-indexed as the replicated site reads from the CTS - Transport and copies it across

Transport Related Changes - On mailbox Server is 3 services

Exchange Transport - State full service handling SMTP mail flow and content inspection

Exchange Mailbox Transport Delivery - Receives mail from the transport service and delivers to db

Exchange Mailbox Transport Submission - Takes mail from DB and submits to Transport service

Transport Service Responsible for inbound / outbound mail - transport rules AV , routing. Queuing message mail.que

Transport Pipeline

  Exchange 2013 Poster Download