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.


The “old” Exchange Management Shell (EMS) is still there. 5 . Which of course is the configuration of the server setup. so I suppose lots of us geeks will use more PowerShell in the near future. I will like the EAC better after used it for a while. now it’s time for part 2.. Configure Mail Flow and Certificates If you haven’t read it already. We have lots of changes between how you configured Exchange 2007/2010 and 2013. That was part 1. First thing is that Exchange Management Console is gone and replaced by a refreshed ECP called Exchange Admin Center (EAC). but I still like the EMC better.2. built on Silverlight (I suppose). it can be found here. 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. I will use both methods for the configuration steps. I did post a complete guide for installing Exchange 2013. The fact that EMC is replaced will make the administration easier and more portable. In EAC: on the left side (menu) press “Mail Flow”. 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. This portable administration together with Remote PowerShell will be awesome. both EAC and PowerShell.

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. Using PowerShell: Since I’m a geek I like to use PowerShell because it gives you the advantage of see what happens. More info about Accepted Domains can be found here. like my example below. press “Accepted Domains” at the top menu in the –DomainName testlabs.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. In EAC: After selecting “Mail Flow” to the left. If your domain is not listed and you need to add –DomainType Authoritative 6 .

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

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

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

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

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

maxmes* Certificates As most of you already know we need to request and import a certificate for Exchange.10.10” – FrontEndProxyEnabled:$True Note: The size can be configured between 0 Bytes up to 2TB. lets view the send connectors and then make the changes like above. In EAC: Go to the “Certificates”. certificates needs to be configured so let’s get started. Select the server and press the “plus” icon for Creating a new certificate request.created connector.10. using the command below Get-SendConnector| fl ide*. ActiveSync etc.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.10. 12 . found under “Servers”. Using PowerShell: Start the Exchange Management Shell. Verify that the settings was correctly set. This for having a fully working OWA. 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.

Press Next.I’m using an Internal PKI solution. 13 . this is the checkbox you should use. I don’t want a wildcard certificate. Press Next. Type in a friendly name for the certificate. Press Next. 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. Press Browse and select which server you want to store it on. so I just let it be unchecked.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

The MAPI Network should not be enabled for replication.Press OK. Final DAG configuration The last step (just a recommendation) is to enable the DAC mode. Which means that you end up with having same database mounted on two (or more) different servers. go to Databases and select one database. In the menu. The MAPI Network is not supposed to be used as replication network. 38 . 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. 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). so let’s disable that function by pressing “Disable Replication” on the MAPI network. then press the Add database copy button. Press OK. This can’t be done through EAC (maybe that will change to RTM). this for preventing split brain syndrome. The DAG should now show two networks called MAPI and Replication.

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

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

1.Press Close. because I have the full control over what’s going on. In my test environment it took around 15min to be fine. But I prefer the PowerShell.16. Let’s start with creating the DAG by using the command below: New-DatabaseAvailabilityGroup –Name DAG01 –WitnessServer TLCAS01 –WitnessDirectory C:\FSW_DAG01 –DatabaseAvailabilityGroupIpAddresses 172.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 .. It might take a while (some minutes. Using PowerShell: The Web interface is nice to work with. It should look like the picture below when everything is completed.) until it get’s Healthy and everything has been checked and verified.

0/8” Remove the automated created network.0/24” New-DatabaseAvailabilityGroupNetwork –DatabaseAvailabilityGroup DAG01 –Name Replication –Description “Replication Network” –ReplicationEnabled $True –Subnets “10. one for Mapi and one for Replication: New-DatabaseAvailabilityGroupNetwork –DatabaseAvailabilityGroup DAG01 –Name Mapi – Description “Mapi Network” –ReplicationEnabled $False –Subnets “ 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.0.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. Specify a mailbox server that at the moments doesn’t hold a copy of the database and add it by 42 .

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

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

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

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

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

Sign up to vote on this title
UsefulNot useful