Server 2013


1. Installation guide

Here we go, this is the first part of Exchange 2013 Preview/beta. It's will walk you through the installation procedure using Windows 2008 R2 SP1. Since Exchange Server 2013 beta was released a couple of days ago I’m glad to announce that my first installation is done and here’s a complete walk through. My setup is basic, using one server as domain controller, Windows 2008 R2. Initially for Exchange I’m using 3 servers, 1 server for the CAS role and 2 servers for the Mailbox role. There are some prerequisites that need to be installed/removed before the installation of Exchange can take place. Note: It’s now recommended to install the Mailbox server first. So I’m starting with that server. Step 1. Install the administration pack using the commands below, make sure to restart the server before proceeding to step 2. Import-Module ServerManager Add-WindowsFeature RSAT-ADDS

Step 2. Install the Windows features that Exchange uses, for Mailbox and CAS server use the command below: Import-Module ServerManager Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-overHTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, WebBasic-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-MgmtService, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-StaticContent, Web-Windows-Auth, Web-WMI


Step 3. When the feature is completed. Continue with the installation of the required components, use the links below to download the components. .NET Framework 4.5 RC Windows Management Framework 4.0 Unified Communications Managed API 4.0, Core Runtime 64-bit Office 2010 Filterpack x64 Office 2010 Filterpack SP1 x64 KB 974405 (Windows Identity Foundation) KB 2619234 (RPC over HTTP) KB 2533623 (Remote code execution) Note: Make sure to uninstall the Visual C++ 11 Beta Redistributable (x64) before starting the Exchange 2013 installation. You can have a look at the setup.exe parameters using setup.exe /? setup.exe /help:install

Step 4. Start the installation using unattended installation for the Mailbox server role setup.exe /mode:install /roles:Mailbox, ManagementTools /IAcceptExchangeServerLicenseTerms /InstallWindowsComponents /OrganizationName:Testlabs /TargetDir:"D:\Program Files\Microsoft\Exchange Server\V15" The installation process starts up and prepare the organization for Exchange 2013, install the necessary Windows components. The schema prep can also be done manually using setup.exe /preparead, I’ve chosen to go with the default behavior. When for the Mailbox server role installation is successfully finished it will tell you to restart the server.


Step 5. Start the installation of the Windows features for the CAS server role Import-Module ServerManager Add-WindowsFeature RSAT-ADDS Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-overHTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, WebBasic-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-MgmtService, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-StaticContent, Web-Windows-Auth, Web-WMI Make sure to restart the server after the Windows features got installed. Step 6. Start the installation of the CAS server role setup.exe /mode:install /roles:ClientAccess, ManagementTools /IAcceptExchangeServerLicenseTerms /InstallWindowsComponents /OrganizationName:Testlabs /TargetDir:"D:\Program Files\Microsoft\Exchange Server\V15" Since this is the second server, the schema prep is already done so the installation will skip that step. When it’s finished it will look like the picture below, a restart of the server is required.

The installation of both servers are now completed. Next blog post will be around how to configure Exchange 2013. Thanks for reading, looking forward to your comments about the post and also about Exchange 2013 in general.


now it’s time for part 2. I did post a complete guide for installing Exchange 2013. The easiest way to find the URL path to the EAC is to start the Exchange Management Shell and run the command below: Get-EcpVirtualDirectory | fl *url* The picture below is my output from my lab environment So let’s get things started. it can be found here. Which of course is the configuration of the server setup. both EAC and PowerShell. Configure Mail Flow and Certificates If you haven’t read it already. The fact that EMC is replaced will make the administration easier and more portable. First thing is that Exchange Management Console is gone and replaced by a refreshed ECP called Exchange Admin Center (EAC). I will like the EAC better after used it for a while. built on Silverlight (I suppose). Basic configuration. Start up an Internet browser and go to the URL output from the command above Mail Flow Let’s get the mail flow configured first so we can receive mails from external senders. We have lots of changes between how you configured Exchange 2007/2010 and 2013. This portable administration together with Remote PowerShell will be awesome. but I still like the EMC better. The “old” Exchange Management Shell (EMS) is still there. so I suppose lots of us geeks will use more PowerShell in the near future.. In EAC: on the left side (menu) press “Mail Flow”. I will use both methods for the configuration steps. 5 . That was part 1.2.

com –DomainName testlabs. like my example below. press “Accepted Domains” at the top menu in the middle. More info about Accepted Domains can be found here. In EAC: After selecting “Mail Flow” to the –DomainType Authoritative 6 . For listing and adding a domain like above in PowerShell you should write: Get-AcceptedDomain New-AcceptedDomain –Name testlabs. press the plus mark and fill in the information. If your domain is not listed and you need to add it.Accepted Domains Ensure sure that your domains that should be used for SMTP is listed in here for making Exchange able to receive mails for these domains. have the full control and easily build scripts. Using PowerShell: Since I’m a geek I like to use PowerShell because it gives you the advantage of see what happens.

Email Address Policies These policies are used to stamp each user mailbox object with an email address/SMTP address. Address type: SMTP and the Email address parameters: %råa%räa%röo%g. These policies does not remove any addresses used previously. The Default Policy is showing up. Check so that the change is correct. it just adds new addresses to mail objects. press “Email Address Format”. In EAC: By default after the installation we only have one policy. Since I live in Sweden and we have some special characters that I want to get rid %r means it replaces the character after. called Default Policy. by selecting the “Default Policy” and pressing the “pen” icon. in the left menu. then press the “Save” button.%råa%räa%röo%s@testlabs. When you have done the change press the “Save” button at the bottom of the page. 7 . Which it replaces with aao. in this case åäö. I’m using the custom policy. I want to edit this one.

As a final step let’s do the same configuration to the “Default Policy” that we did using EAC.”smtp:”.%råa%räa%röo%s@testlabs. use capital letters for SMTP. See the example below: Get-EmailAddressPolicy Get-EmailAddressPolicy | fl Get-EmailAddressPolicy | Set-EmailAddressPolicy –EnabledEmailAddressTemplates “SMTP: %råa%räa%röo%g. If you want to create more than just alias@domain. This is done by pressing the “Apply” text/button down in the right menu. then this is done by comma separation. it needs to be applied. Using PowerShell: Let’s start with listing the Policy and the settings in it. it will show a True or False value.%råa%räa%rö”.”smtp: %m@testlabs. and for additional addresses use small letters for to your” Get-EmailAddressPolicy | Update-EmailAddressPolicy It can easily be checked if the policy has been” Set-EmailAddressPolicy –identity “Default Policy” –EnabledEmailAddressTemplates “SMTP: %råa%räa%röo%g. For checking the value run the command below: Get-EmailAddressPolicy | fl *appl* 8 .After the changes have been saved. For setting the PrimarySMTP address.

It now allows traffic from Anonymous users by default. When you have done your changes for the connector. In EAC: Go to the “Receive Connectors”. Using PowerShell: Start the Exchange Management Shell. found under “Mail Flow”. or else the new addresses won’t be pushed out to the recipients. I suppose this is due to that the Edge Transport Role also is removed. The only thing I did change was the “Maximum receive message size” to 30 MB. Receive Connectors Since the HUB Transport server role now is gone and the HUB role is placed together with the CAS role. Get-ReceiveConnector 9 . After the SMTP domains have been added into the Accepted Domain tab. Make sure to select your CAS server(s) and the “Default Frontend servername”. this is the server you should be looking at. some settings could be of value to have a look at before starting to use the servers. lets view the receive connectors and then make the changes like above. the default connector now named “Default Frontend servername”.Note: Don’t forget to update the Policy. press the Save button. Then press the “pen” icon for Edit the selected connector. A change has been made to the new version.

let’s create a Send Connector on the CAS server. using the command below Get-ReceiveConnector | fl ide*. So… for being able to send out mails to external recipients.Get-ReceiveConnector | fl Set-ReceiveConnector –Identity “TLCAS01\Default Frontend TLCAS01” –MaxMessageSize 30MB Note: The size can be configured between 64KB up to 2GB. Verify that the settings was correctly set. Select how to route those mails. Since this one I’m creating now is for sending to external recipients I’m selecting “Internet”.maxmes* Send Connectors When the HUB server role now is gone and after the default installation of Exchange we don’t have any send connectors. found under “Mail Flow”. Give the send connector a friendly name and select what type it should be. (Seems like we have a typo. In EAC: Go to the “Send Connectors”. Press Next. If you have a mail gateway then you should select smart host and type in it’s IP address. see picture below). My server is 10 . either by using MX records or through a smart host(s). Press the “plus” icon for Creating a new send connector.

Then it takes care of all domains. Note: By default the connector has a maximum message size of 10MB. but this can be done by editing the 11 . Press the “plus” icon for adding the address space this connector should use. In my case it will be “*”. Let’s add these into the connector by pressing the “plus” icon and selecting the Mailbox servers. Then Press Next for accepting the settings you’ve just made. Press Save.just sending them directly to Internet so I’m using the MX method. Then press Next. Next screen will show you which source servers that should be used. Press Finish button so the connector get’s created. You can’t configure the maximum send message size when creating the connector.

10” – FrontEndProxyEnabled:$True Note: The size can be configured between 0 Bytes up to 2TB.10. In EAC: Go to the “Certificates”. lets view the send connectors and then make the changes like above. ActiveSync etc. 12 . Get-SendConnector Get-SendConnector| fl This creates a new send connector using the DNS/MX method New-SendConnector –Name “Outbound” –AddressSpaces „*‟ –SourceTransportServers TLMB01 –MaxMessageSize 30MB This creates a new send connector using the smarthost method New-SendConnector –Name “Outbound” –AddressSpaces „*‟ –SourceTransportServers TLMB01 –MaxMessageSize 30MB –DNSRoutingEnabled:$false –SmartHosts “10.10. Select the server and press the “plus” icon for Creating a new certificate request. Using PowerShell: Start the Exchange Management Shell. Verify that the settings was correctly set.maxmes* Certificates As most of you already know we need to request and import a certificate for Exchange. using the command below Get-SendConnector| fl ide*.10.10.10” This creates a new send connector using the smarthost method together with using the CAS server as a proxy server for sending the mails New-SendConnector –Name “Outbound” –AddressSpaces „*‟ –SourceTransportServers TLMB01 –MaxMessageSize 30MB –DNSRoutingEnabled:$false –SmartHosts “10.created connector. This for having a fully working OWA. found under “Servers”. certificates needs to be configured so let’s get started.

so in this case I want to “Create a request for a certificate from a certificate authority”. If you want to create the request for a wildcard certificate. Press Next. this is the checkbox you should use. Type in a friendly name for the certificate.I’m using an Internal PKI solution. Press Next. I don’t want a wildcard certificate. Press Browse and select which server you want to store it on. 13 . so I just let it be unchecked. Press Next. Press Next.

Press Next. Press Next. 14 .For each service you can here type in the address. City and State. Go through the names in the list and make sure that all names that’s needed are included. Country. Fill in Organization name. and the request will generate the names in the end. When you’re done press Next. Department.

my file is saved on my DC. Example: \\tldc01\certificates\certnew.In my example I did type in the path to a share on my domain controller. it shows up with the friendly name. Press Finish.cer file. 15 . Type in the URL path to the . press the “Complete” button below the status.cer It’s now time for assigning the services to the certificates. This is done by selecting the certificate and press the Edit button. together with the status “Pending request”. which also is my Internal CA. Example: \\tldc01\certificates\certreq. Press OK. When the certificate is issued.req When the request is completed.

Check so that the services is assigned to the certificate. 16 . Press Save.Go to “Services” and add the one’s that should be used. Press OK.

s=Skane. o=Testlabs.req” Import-ExchangeCertificate –Server TLCAS01 –FileName “\\tldc01\certificates\certnew-ps. POP. ou=Testlabs.Using PowerShell: Start the Exchange Management Shell. lets view the existing certificates and then make a new cert request like above. SMTP. cn=mail. or else you can have difficulties finding our created” – PrivateKeyExportable $true –FriendlyName Exchange2013-PS Enable-ExchangeCertificate –Thumbprint A2E6649A22A99BEAB2654BEB403C92BB9D34B404 –Services “IIS.autodiscover. Finally import the issued” –DomainName – RequestFile “\\tldc01\certificates\test. 17 . IMAP” –Server TLCAS01 Get-ExchangeCertificate Note: Make sure to specify –Server. l=Malmo.testlabs. Mine landed at my Mailbox server even if I did it on the CAS server. Get-ExchangeCertificate Get-ExchangeCertificate | fl This creates a new certificate request and saves it to a share New-ExchangeCertificate –Server TLCAS01 –GenerateRequest –FriendlyName Exchange2013PS –PrivateKeyExportable $true –SubjectName “c=SE.

)    autodiscover. In the previous part we did install the certificate which included the following names. so we can use these names in the site configuration. In EAC: Go to Servers. the configured name needs to be included into the certificate. Let’s start with Autodiscover.testlabs. 18 .testlabs. select Virtual tlcas01  tlcas01. Outlook Anywhere and MAPI vs RPC over HTTPs together with connecting using Outlook 2013. so you have the opportunity to select which method you Sites / URL’s Let’s go through the steps for configuring the sites with the ExternalURL and other settings.testlabs. Select the server in the menu and which type you want to show. Then press Edit. Databases and Outlook Anywhere This part will include details on how the configuration could be made for Site URL’s/Virtual Directories. I’ll go through both the EAC and the PowerShell. Databases.. (If using HTTPS.3. Configure site URL's. Let’s start.

Next. Press Edit. select Exchange ActiveSync (EAS). Press Save. Press Authentication. Make sure that Basic authentication is enabled. I did type in the ExternalURL like the pic below. 19 . Integrated Windows Authentication and Basic authentication is enabled. General settings shows the URL’s.By default. Press Save.

select ECP. Press Authentication. I did type in the ExternalURL like the pic below. 20 .Next. Press Save. General settings shows the URL’s. Authentication default settings is “Use forms-based authentication” enabled. Press Edit.

Next. Integrated Windows authentication is enabled by default. Press Edit.A warning. Authentication settings. Press OK. 21 . I did type in the ExternalURL like the pic below. select EWS. General settings shows the URL’s. make sure to change all virtual directions. Press Authentication. Press Save.

select OWA.Next. For having a faster update of the OAB. Press Save. I did also change the Polling interval from 480 minutes to 60. Press Authentication. I did type in the ExternalURL in this setting. select OAB. General settings shows the URL’s. Press Edit. Next. the InternalURL was already configured. I did type in the ExternalURL like the pic below. 22 . Press Edit.

I did select the Logon format: User name only and did select my domain by the browsing button. Showing the default settings. Showing the default settings. Press Features. Press Save.Forms-based authentication is selected. 23 . Press File Access.

Press Save. Both Integrated Windows authentication and Basic authentication was selected by default. select PowerShell. I did type in the ExternalURL like the pic below. General settings shows the URL’s.Next. Press Authentication. 24 . Press Edit.

.. ide* Set-EcpVirtualDirectory –Identity “TLCAS01\ecp (Default Web Site)” – ExternalUrl Exchange Web Services (EWS): Get-WebServicesVirtualDirectory | fl *url*..testlabs.Using PowerShell Start the Exchange Management Shell (EMS) and the following commands will do the same work that’s done in EAC..S/Exchange.utodiscover. ide* Set-WebServicesVirtualDirectory –Identity “TLCAS01\EWS (Default Web Site)” – ExternalUrl https://mail.rver-ActiveSync Exchange Control Panel (ECP): Get-EcpVirtualDirectory | fl *url*.asmx 25 . ide* Set-ActiveSyncVirtualDirectory –Identity “TLCAS01\Microsoft-Server-ActiveSync (Default Web Site)” –ExternalUrl https://mail.xml Exchange ActiveSync (EAS): Get-ActiveSyncVirtualDirectory | fl *url*. Autodiscover: Get-ClientAccessServer | fl *uri* Set-ClientAccessServer –Identity TLCAS01 – AutoDiscoverServiceInternalUri https://autodiscover.testlab..testlab.

testlabs. ide*.pol* Set-OabVirtualDirectory –Identity “TLCAS01\OAB (Default Web Site)” – ExternalUrl Databases 26 .se/OAB –PollInterval 60 Outlook Web App (OWA): Get-OwaVirtualDirectory | fl *url*. ide* Set-OwaVirtualDirectory –Identity “TLCAS01\OWA (Default Web Site)” – ExternalUrl https://mail. ide* Set-PowerShellVirtualDirectory –Identity “TLCAS01\PowerShell (Default Web Site)” – ExternalUrl https://mail.Offline Address Book (OAB): Get-OabVirtualDirectory | fl *url* PowerShell: Get-PowerShellVirtualDirectory | fl *url*.testlabs.

Dismount it by pressing the … icon and press Dismount database. named “Mailbox Database 0883045. Select the default database. example: DB01.”.. In EAC: Go to Servers. select Databases. Select the database. that mailboxes being on this database now will be unavailable. Let’s start with the EAC and then do it in PowerShell.. dismount and mount. Press Yes. Let’s start. Press Maintenance. Press Cancel. Also creating new databases. Give the database a friendly name. Press Edit.Let’s go through the steps that’s required for renaming the default database. It does show a warning. 27 . Press Edit. Select the database. General settings is shown.

these are the default values.Maintenance settings is shown. Press Client Settings. Mailbox limits are shown. By default. Press Browse and make sure to select the address book. Press Save. no Offline address book was selected. Press Limits. 28 .

What about if you want to create a new database? Let’s start in EAC Press the Add button (+). Give the database a friendly name. When the database is created. there is not option for associate the database with the offline address book. example: DB02. Browse for a mailbox server. Using PowerShell Start the Exchange Management Shell (EMS) and the following commands will do the same work 29 . Press Save. And also put in the database path and log path. During the creating of the database. press Edit. Then go to Client Settings and select the Offline address book.

Outlook Anywhere Configuration of the feature Outlook Anywhere can also be done from both the EAC and EMS. Let’s start with the EAC: Go to the servers menu. in various ways. It’s done by the commands below: Move-DatbasePath –identity DB01 –EdbFilePath “E:\Database\DB01\DB01. New-MailboxDatabase -Name DB02 -EdbFilePath “E:\Database\DB02\DB02. we have the opportunity in PowerShell to specify all parameters that’s needed for having all options configured. 30 .that’s done in EAC.*path* Dismount Database Dismount-Database –Identity DB01 After the default database is renamed to DB01.edb” –LogFolderPath “F:\Logs\DB01” Mount-Database DB01 Get-OfflineAddressBook For creating a new database (DB02).edb” LogFolderPath “F:\Logs \DB02″ -OfflineAddressBook “\Default Offline Address Book” -Server TLMB01 Mount-Database DB02 Note that the OfflineAddressBook is specified during the creation of the database. and select Servers. Press Edit. I want to move the database file and the logs to another drive. Retrieve database information Get-MailboxDatabase Get-MailboxDatabase | fl name.

testlabs. I’m using Basic authentication for Outlook Anywhere. With that said no more load balancing of static RPC ports. Just make sure that the load balancer verifies the Exchange services before sending traffic to it. And the Configuration is completed.testlabs. type in the external –ExternalClientAuthenticationMethod Basic – InternalClientAuthenticationMethod Ntlm –IISAuthentication Ntlm –SSLOffloading:$false Get-OutlookAnywhere –Server TLCAS01 MAPI and RPC The MAPI/RPC (RPC over TCP) traffic is now gone and replaced with RPC over HTTP/s instead.testlabs. it can now be load balanced based on IP addresses. as far as I know this will make both the Firewall team and the Load Balancer teams work easier. example: mail.Then go to the “Outlook Anywhere” option. I think (and hope) most of you will 31 . Press Save. This because of there is no need anymore to have the affinity less ports is used together with the requirement of load balancing affinity/sticky session settings is also gone now. Outlook instead will use port 443 (HTTPS) or port 80 (HTTP). Using PowerShell Start the Exchange Management Shell (EMS) and the following commands will do the same work that’s done in EAC. Enable Outlook Anywhere: Enable-OutlookAnywhere –Server TLCAS01 –ExternalHostname – InternalHostname tlcas01.

More information around What’s new in Exchange 2013 can be found here. with this said I’ll show you the new Outlook 2013 Preview/beta and how it connects and also the traffic it’s using. connects to my mailbox in Exchange 2013. using RPC over HTTPS. using port 6001 by default for it’s connection. A small picture from Network Monitor when the connection initiated by Outlook 2013.use RPC over HTTPS. Outlook 2013 Preview. 32 . It’s using HTTPS to initiate the connection.

Disaster Recovery. Database Availability Group (DAG) If this expression is new to you. Though all DAG members needs to run the same OS version. I have also read that IOPS requirements for databases have been reduced with another 50% from Exchange 2010. 33 . The advantage of this is that if one server fails. Site resilience and Public Folder migration. it’s easy and very fast for doing switchover/failover to another server. the DAG can have utilize up to 16 copies of each database (16 different servers). here are some background information. again. Some interesting changes around databases are that each database runs under it’s own process in Windows. Configure DAG.4. CAS Array and Public Folders At the end of the post. which means you can’t use databases from older versions of Exchange directly on Exchange 2013.. The DAG is the new cluster technology from Exchange 2010 and also included in 2013. Using EAC: It’s time to like the new EAC “console”. Store (ESE) is totally rewritten. and supported to run on both Windows 2008 R2 and Windows Server 8. Running “ipconfig” on both mailbox servers. I will link to some interesting TechNet articles around High Availability. We’ll see what happens when it’s being release and probably Microsoft will release an update mailbox calculator. Both for the MAPI network and the Replication network. but I haven’t read it officially so maybe it’s just a rumor. Note: My posts around Exchange 2013 Preview/beta are based on Beta information and it could be changed before it will be released (RTM). DAG is available for both Standard and Enterprise version of Exchange. It give us the opportunity to have a mailbox database replicated between two or more servers. for checking the IP addresses. Let’s get ready to create the DAG and add the Databases as copies on each DAG member/node.

Witness directory and DAG IP. go to Servers and select Database Availability Group. Login to the EAC. Witness Server. Press Add button (+). Press Save. 34 .Go into Control Panel and check the network interfaces. Type in DAG name.

Add the mailbox servers that should reside in the DAG. Press the Add button (+) and add the mailbox servers.When the DAG is created. It’s now time for adding the mailbox servers into the DAG. 35 . Check the option “Configure database availability group network manually”. Press Save. this by pressing “Manage membership” button. Press OK. select it and Press Edit.

Press Close. as you can see in the right bottom corner. The configuration now gets saved. I want to have the control over these networks so I will 36 . a network called “MapiDagNetwork” has been created. Next thing to do it the DAG Networks. failover clustering was installed on mailbox servers.Press Save.

since that it’s purpose and also assign it to the correct Subnet. Press Save. 37 . I’m about to create two new networks. Press Save. and assign the Subnet to it where the clients are supposed to connect. My second network will be called Replication Network. Start by pressing “New DAG Network”.create my own. Since we now have created those two network. let’s remove the automatic created one by pressing “Remove” button. I will give the first network a name like MAPI Network.

Which means that you end up with having same database mounted on two (or more) different servers. Set-DatabaseAvailabilityGroup –Identity DAG01 –DatacenterActivationMode DagOnly Database copies On each mailbox database we now need to add a copy to another server for having the redundancy. Press OK.Press OK. then press the Add database copy button. The MAPI Network is not supposed to be used as replication network. go to Databases and select one database. this for preventing split brain syndrome. Final DAG configuration The last step (just a recommendation) is to enable the DAC mode. This can’t be done through EAC (maybe that will change to RTM). so let’s disable that function by pressing “Disable Replication” on the MAPI network. 38 . More info about DAC mode can be found on the link in the end of the post. So let’s start up Exchange Management Shell (EMC). The DAG should now show two networks called MAPI and Replication. In the menu. The MAPI Network should not be enabled for replication.

39 .Specify mailbox server that at the moments doesn’t hold a copy of the database and add it by pressing the browse button. Then do the same procedure on all of your databases. Note: In this menu you also have the option to configure lag time (if using lagging node). The database now get’s copied (Seeding). Press Save.

The seeding operation is running. 40 . when the operation is done.Press Close. Do the same procedure on all of your databases.

15 Configure the DAG so that the networks can be manually configured: Set-DatabaseAvailabilityGroup –Identity DAG01 –ManualDagNetworkConfiguration $True Add the mailbox servers into the DAG: Add-DatabaseAvailabilityGroupServer –Identity DAG01 –MailboxServer TLMB01 41 . because I have the full control over what’s going on. It might take a while (some minutes.16.Press Close. Using PowerShell: The Web interface is nice to work with. In my test environment it took around 15min to be fine.) until it get’s Healthy and everything has been checked and verified.1. Let’s start with creating the DAG by using the command below: New-DatabaseAvailabilityGroup –Name DAG01 –WitnessServer TLCAS01 –WitnessDirectory C:\FSW_DAG01 –DatabaseAvailabilityGroupIpAddresses 172. But I prefer the PowerShell.. It should look like the picture below when everything is completed.

16. one for Mapi and one for Replication: New-DatabaseAvailabilityGroupNetwork –DatabaseAvailabilityGroup DAG01 –Name Mapi – Description “Mapi Network” –ReplicationEnabled $False –Subnets “172.Add-DatabaseAvailabilityGroupServer –Identity DAG01 –MailboxServer TLMB02 Enable DAC mode for the DAG: Set-DatabaseAvailabilityGroup –Identity DAG01 –DatacenterActivationMode DagOnly List the DAG Networks: Get-DatabaseAvailabilityGroupNetwork Create two new DAG Networks.1.0/8” Remove the automated created network. it will not be used: Remove-DatabaseAvailabilityGroupNetwork –Identity DAG01\MapiDagNetwork Database copies On each mailbox database we now need to add a copy to another server for having the redundancy. Specify a mailbox server that at the moments doesn’t hold a copy of the database and add it by 42 .0/24” New-DatabaseAvailabilityGroupNetwork –DatabaseAvailabilityGroup DAG01 –Name Replication –Description “Replication Network” –ReplicationEnabled $True –Subnets “10.0.0.

However they can in someway be compared to shared and room. How can the hierarchy mailbox be created? Using EAC: Go to Public Folders section. Add-MailboxDatabaseCopy –Identity DB01 –MailboxServer TLMB02 Add-MailboxDatabaseCopy –Identity DB02 –MailboxServer TLMB02 Add-MailboxDatabaseCopy –Identity DB03 –MailboxServer TLMB02 Verify the replication status on each mailbox server: Get-MailboxDatabaseCopyStatus –Server TLMB01 Get-MailboxDatabaseCopyStatus –Server TLMB02 Public Folders The Public Folder databases are now gone. the first step will be to create a mailbox that holds the public folder hierarchy. those are also special mailboxes. With “normal” mailbox I mean that they reside in the mailbox databases.running the following commands. This doesn’t mean that the public folder contents is replicated. you can have copies of the hierarchy. it’s still required that you configure the public folder replication for the contents. 43 . This will be the writeable copy. But you can only have one that is allowed to make changes/writeable. just like user mailboxes does. It means that you don’t have any public folder hierarchy (mailbox) created yet. this is the first warning/error message you will receive. If you decide to use the Public Folders in Exchange 2013. and transferred to “normal” mailboxes instead. The advantage of this is that the mailbox itself can now be replicated using DAG technology.

Now when the hierarchy is created. Give the mailbox a friendly name. so it’s hierarchy can be saved. Press Save. Give the public folder a name. Statistics can also be found under Edit selection. place it into an organizational unit and select a mailbox database where it should be saved into. press Edit and configure it. If you want to configure any storage quota on the public folder content. 44 . Press Save. create the first mailbox for the public folders. Add (+). which sometimes is valuable. let’s create some test folders too. Go back to “Public Folders”. example: PF_Hierarchy.Go to the second public folder selection called “Public Folders Mailboxes”. press the Add (+) button.

By pressing the Enable button. Let’s check the properties for the folder again.Just for testing purposes I did mail-enable the folder. now we see that we have lots of new settings. Here’s a small example how the Mail Flow settings looks like. 45 . Press Yes.

Create the hierarchy by running the following command New-Mailbox –Name PF_Hierarchy –Alias PF_Hierarchy –Database DB01 –OrganizationalUnit Users This mailbox. In an upcoming blog post I will cover how to configure the load balancing for Exchange 2013. 46 . After the architectural change around the CAS role. like shared/room mailboxes is also disabled by default. I haven’t tried to migrate public folder contents from earlier versions of Exchange since SP3 for Exchange 2010 is required for having coexistence between Exchange 2010 and Exchange 2013. Client Access Server Array In my previous blog post I did write about some news regarding MAPI and RPC. It can be found here. SP3 is right now under development/testing and no official information can be found. it means that the clients is not required to have the connection established to the same CAS server for having the OWA to work. I don’t see any specific reason for creating the CAS Array. where I did mention what changes been made.Using PowerShell: Start up Exchange Management Shell. it’s now “stateless” which means there’s no need for the load balancer to configure affinity/sticky session. mail enable the public folder Enable-MailPublicFolder –Identity \Testlabs We have public folders located in Exchange 2007/2010. it provides you with a great stepby-step guide. This means that all CAS servers now will serve all clients with connections to it’s mailbox endpoint server. you can find a link to a TechNet article. what about them? In the end of this post. since the traffic will be proxied from the CAS servers to the correct active Mailbox servers. For example. Let’s create the folder named Testlabs New-PublicFolder –Name Testlabs Finally. the following commands will be used for creating the public folder hierarchy and contents folder. This for not having the possibility to logon as this user. this will be one of the first things to try out. When I get my hands on SP3. It utilize as a front-end connection point and redirects/proxies (depending on method) the clients to it’s correct mailbox server. How to create a client access array? Right now. The “new” Client Access Server role can now been seen as more of a traditional Front-End server.

database failover. But first it’s time for 3 weeks of vacation. 47 . I hope it did gave you some valuable information. disaster recovery etc. until then. Keep on reading the posts and you’re more than welcome to comment on them.Upcoming topics: load balancing Exchange 2013 using different load balancers. Thanks for reading. move mailbox reports.

Sign up to vote on this title
UsefulNot useful