This action might not be possible to undo. Are you sure you want to continue?
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.
I will use both methods for the configuration steps. both EAC and PowerShell.. We have lots of changes between how you configured Exchange 2007/2010 and 2013. This portable administration together with Remote PowerShell will be awesome. Which of course is the configuration of the server setup. I did post a complete guide for installing Exchange 2013. The fact that EMC is replaced will make the administration easier and more portable. built on Silverlight (I suppose). so I suppose lots of us geeks will use more PowerShell in the near future. 5 . Basic configuration. First thing is that Exchange Management Console is gone and replaced by a refreshed ECP called Exchange Admin Center (EAC). 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. 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. In EAC: on the left side (menu) press “Mail Flow”. I will like the EAC better after used it for a while. but I still like the EMC better. That was part 1.2. The “old” Exchange Management Shell (EMS) is still there. it can be found here. Configure Mail Flow and Certificates If you haven’t read it already. now it’s time for part 2.
com –DomainType Authoritative 6 . For listing and adding a domain like above in PowerShell you should write: Get-AcceptedDomain New-AcceptedDomain –Name testlabs. have the full control and easily build scripts. In EAC: After selecting “Mail Flow” to the left.com –DomainName testlabs. If your domain is not listed and you need to add it. Using PowerShell: Since I’m a geek I like to use PowerShell because it gives you the advantage of see what happens. press the plus mark and fill in the information. press “Accepted Domains” at the top menu in the middle.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. More info about Accepted Domains can be found here. like my example below.
Which it replaces with aao. press “Email Address Format”. called Default Policy. in this case åäö.%råa%räa%röo%s@testlabs. I’m using the custom policy. The Default Policy is showing up. Address type: SMTP and the Email address parameters: %råa%räa%röo%g. 7 . then press the “Save” button.se %r means it replaces the character after. When you have done the change press the “Save” button at the bottom of the page. Check so that the change is correct. Since I live in Sweden and we have some special characters that I want to get rid of. In EAC: By default after the installation we only have one policy.Email Address Policies These policies are used to stamp each user mailbox object with an email address/SMTP address. These policies does not remove any addresses used previously. by selecting the “Default Policy” and pressing the “pen” icon. in the left menu. I want to edit this one. it just adds new addresses to mail objects.
se” Get-EmailAddressPolicy | Update-EmailAddressPolicy It can easily be checked if the policy has been applied. it will show a True or False value. For setting the PrimarySMTP address.”smtp: %firstname.lastname@example.org to your policies. use capital letters for SMTP. Using PowerShell: Let’s start with listing the Policy and the settings in it. If you want to create more than just alias@domain. For checking the value run the command below: Get-EmailAddressPolicy | fl *appl* 8 . then this is done by comma separation.”smtp: %m@testlabs. As a final step let’s do the same configuration to the “Default Policy” that we did using EAC.After the changes have been saved.se” Set-EmailAddressPolicy –identity “Default Policy” –EnabledEmailAddressTemplates “SMTP: %råa%räa%röo%g.se”.se”.%råa%räa%röo%s@testlabs. This is done by pressing the “Apply” text/button down in the right menu. See the example below: Get-EmailAddressPolicy Get-EmailAddressPolicy | fl Get-EmailAddressPolicy | Set-EmailAddressPolicy –EnabledEmailAddressTemplates “SMTP: %råa%räa%röo%g. it needs to be applied.%råa%räa%röo%s@testlabs. and for additional addresses use small letters for smtp.
found under “Mail Flow”. lets view the receive connectors and then make the changes like above. A change has been made to the new version. Then press the “pen” icon for Edit the selected connector.Note: Don’t forget to update the Policy. this is the server you should be looking at. Using PowerShell: Start the Exchange Management Shell. some settings could be of value to have a look at before starting to use the servers. Make sure to select your CAS server(s) and the “Default Frontend servername”. The only thing I did change was the “Maximum receive message size” to 30 MB. It now allows traffic from Anonymous users by default. When you have done your changes for the connector. press the Save button. Get-ReceiveConnector 9 . Receive Connectors Since the HUB Transport server role now is gone and the HUB role is placed together with the CAS role. the default connector now named “Default Frontend servername”. In EAC: Go to the “Receive Connectors”. or else the new addresses won’t be pushed out to the recipients. After the SMTP domains have been added into the Accepted Domain tab. I suppose this is due to that the Edge Transport Role also is removed.
Since this one I’m creating now is for sending to external recipients I’m selecting “Internet”. Give the send connector a friendly name and select what type it should be. If you have a mail gateway then you should select smart host and type in it’s IP address. either by using MX records or through a smart host(s). (Seems like we have a typo. see picture below). let’s create a Send Connector on the CAS server. Press the “plus” icon for Creating a new send connector. Select how to route those mails. found under “Mail Flow”. using the command below Get-ReceiveConnector | fl ide*. In EAC: Go to the “Send Connectors”. My server is 10 . 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.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. Verify that the settings was correctly set.
In my case it will be “*”. Then it takes care of all domains. Press Finish button so the connector get’s created. Next screen will show you which source servers that should be used. Note: By default the connector has a maximum message size of 10MB. Then Press Next for accepting the settings you’ve just made. Press Save. but this can be done by editing the 11 . Press the “plus” icon for adding the address space this connector should use.just sending them directly to Internet so I’m using the MX method. Let’s add these into the connector by pressing the “plus” icon and selecting the Mailbox servers. You can’t configure the maximum send message size when creating the connector. Then press Next.
created connector. found under “Servers”.10. ActiveSync etc. Verify that the settings was correctly set.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. lets view the send connectors and then make the changes like above. 12 .10. certificates needs to be configured so let’s get started.maxmes* Certificates As most of you already know we need to request and import a certificate for Exchange. 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” – FrontEndProxyEnabled:$True Note: The size can be configured between 0 Bytes up to 2TB. This for having a fully working OWA. Select the server and press the “plus” icon for Creating a new certificate request. using the command below Get-SendConnector| fl ide*. Using PowerShell: Start the Exchange Management Shell.10.10. In EAC: Go to the “Certificates”.
Press Next. 13 . Press Next. I don’t want a wildcard certificate. If you want to create the request for a wildcard certificate. Press Browse and select which server you want to store it on. this is the checkbox you should use.I’m using an Internal PKI solution. so in this case I want to “Create a request for a certificate from a certificate authority”. Type in a friendly name for the certificate. Press Next. so I just let it be unchecked. Press Next.
City and State. Department. Press Next. 14 . and the request will generate the names in the end. Country. Press Next. When you’re done press Next.For each service you can here type in the address. Fill in Organization name. Go through the names in the list and make sure that all names that’s needed are included.
it shows up with the friendly name. Type in the URL path to the .cer It’s now time for assigning the services to the certificates. Example: \\tldc01\certificates\certnew.req When the request is completed. which also is my Internal CA. When the certificate is issued. together with the status “Pending request”. 15 .In my example I did type in the path to a share on my domain controller. press the “Complete” button below the status. my file is saved on my DC. Press OK.cer file. This is done by selecting the certificate and press the Edit button. Example: \\tldc01\certificates\certreq. Press Finish.
Check so that the services is assigned to the certificate. Press Save. 16 .Go to “Services” and add the one’s that should be used. Press OK.
cer” – PrivateKeyExportable $true –FriendlyName Exchange2013-PS Enable-ExchangeCertificate –Thumbprint A2E6649A22A99BEAB2654BEB403C92BB9D34B404 –Services “IIS.se – RequestFile “\\tldc01\certificates\test. cn=mail. o=Testlabs. POP.autodiscover. lets view the existing certificates and then make a new cert request like above. l=Malmo.req” Import-ExchangeCertificate –Server TLCAS01 –FileName “\\tldc01\certificates\certnew-ps. or else you can have difficulties finding our created request. IMAP” –Server TLCAS01 Get-ExchangeCertificate Note: Make sure to specify –Server.testlabs. Finally import the issued certificate. ou=Testlabs. Mine landed at my Mailbox server even if I did it on the CAS server. s=Skane.se” –DomainName mail. 17 .se.Using PowerShell: Start the Exchange Management Shell.testlabs. SMTP.testlabs. 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.
testlabs. (If using HTTPS. the configured name needs to be included into the certificate.se tlcas01 tlcas01. Configure site URL's. I’ll go through both the EAC and the PowerShell. 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.) mail. Outlook Anywhere and MAPI vs RPC over HTTPs together with connecting using Outlook 2013. 18 . In EAC: Go to Servers. Select the server in the menu and which type you want to show.se autodiscover.se Sites / URL’s Let’s go through the steps for configuring the sites with the ExternalURL and other settings. Let’s start. Databases. so we can use these names in the site configuration.testlabs. In the previous part we did install the certificate which included the following names. select Virtual Directories.3..testlabs. Let’s start with Autodiscover. so you have the opportunity to select which method you prefer.
Press Authentication.By default. 19 . Press Save. Press Save. General settings shows the URL’s. Next. I did type in the ExternalURL like the pic below. select Exchange ActiveSync (EAS). Press Edit. Integrated Windows Authentication and Basic authentication is enabled. Make sure that Basic authentication is enabled.
select ECP. Authentication default settings is “Use forms-based authentication” enabled. Press Authentication.Next. General settings shows the URL’s. Press Edit. Press Save. 20 . I did type in the ExternalURL like the pic below.
select EWS. Authentication settings. General settings shows the URL’s. 21 . Press Authentication. I did type in the ExternalURL like the pic below.A warning. Press Edit. Press OK. Next. Integrated Windows authentication is enabled by default. make sure to change all virtual directions. Press Save.
the InternalURL was already configured. Press Save. I did also change the Polling interval from 480 minutes to 60.Next. Next. 22 . I did type in the ExternalURL in this setting. General settings shows the URL’s. select OWA. Press Edit. I did type in the ExternalURL like the pic below. For having a faster update of the OAB. select OAB. Press Edit. Press Authentication.
Press Features. Press File Access. Showing the default settings. 23 . Showing the default settings. Press Save.Forms-based authentication is selected. I did select the Logon format: User name only and did select my domain by the browsing button.
Press Save.Next. Press Edit. Both Integrated Windows authentication and Basic authentication was selected by default. General settings shows the URL’s. 24 . I did type in the ExternalURL like the pic below. Press Authentication. select PowerShell.
se/ecp Exchange Web Services (EWS): Get-WebServicesVirtualDirectory | fl *url*. ide* Set-ActiveSyncVirtualDirectory –Identity “TLCAS01\Microsoft-Server-ActiveSync (Default Web Site)” –ExternalUrl https://mail..xml Exchange ActiveSync (EAS): Get-ActiveSyncVirtualDirectory | fl *url*...testlab..Using PowerShell Start the Exchange Management Shell (EMS) and the following commands will do the same work that’s done in EAC.testlab.utodiscover. ide* Set-EcpVirtualDirectory –Identity “TLCAS01\ecp (Default Web Site)” – ExternalUrl https://mail.S/Exchange.rver-ActiveSync Exchange Control Panel (ECP): Get-EcpVirtualDirectory | fl *url*. Autodiscover: Get-ClientAccessServer | fl *uri* Set-ClientAccessServer –Identity TLCAS01 – AutoDiscoverServiceInternalUri https://autodiscover.testlabs... ide* Set-WebServicesVirtualDirectory –Identity “TLCAS01\EWS (Default Web Site)” – ExternalUrl https://mail.asmx 25 .
ide* Set-PowerShellVirtualDirectory –Identity “TLCAS01\PowerShell (Default Web Site)” – ExternalUrl https://mail. ide* Set-OwaVirtualDirectory –Identity “TLCAS01\OWA (Default Web Site)” – ExternalUrl https://mail. ide*.testlabs.testlabs.testlabs.Offline Address Book (OAB): Get-OabVirtualDirectory | fl *url*.se/powershell Databases 26 .pol* Set-OabVirtualDirectory –Identity “TLCAS01\OAB (Default Web Site)” – ExternalUrl https://mail.se/OAB –PollInterval 60 Outlook Web App (OWA): Get-OwaVirtualDirectory | fl *url*.se/OWA PowerShell: Get-PowerShellVirtualDirectory | fl *url*.
In EAC: Go to Servers. Press Cancel. that mailboxes being on this database now will be unavailable. Dismount it by pressing the … icon and press Dismount database.. Also creating new databases. Press Yes. Give the database a friendly name. It does show a warning. Select the database. Let’s start.Let’s go through the steps that’s required for renaming the default database.”. example: DB01. Let’s start with the EAC and then do it in PowerShell. dismount and mount. select Databases. Select the database. Press Maintenance. named “Mailbox Database 0883045. Press Edit. General settings is shown. Press Edit.. Select the default database. 27 .
Press Client Settings. Press Browse and make sure to select the address book. Mailbox limits are shown. Press Limits. these are the default values.Maintenance settings is shown. Press Save. 28 . By default. no Offline address book was selected.
During the creating of the database. example: DB02. Browse for a mailbox server. Press Save. Give the database a friendly name. press Edit. Then go to Client Settings and select the Offline address book. Using PowerShell Start the Exchange Management Shell (EMS) and the following commands will do the same work 29 . And also put in the database path and log path. there is not option for associate the database with the offline address book. When the database is created.What about if you want to create a new database? Let’s start in EAC Press the Add button (+).
Press Edit. Outlook Anywhere Configuration of the feature Outlook Anywhere can also be done from both the EAC and EMS. 30 .edb” –LogFolderPath “F:\Logs\DB01” Mount-Database DB01 Get-OfflineAddressBook For creating a new database (DB02). Retrieve database information Get-MailboxDatabase Get-MailboxDatabase | fl name.*path* Dismount Database Dismount-Database –Identity DB01 After the default database is renamed to DB01. Let’s start with the EAC: Go to the servers menu. It’s done by the commands below: Move-DatbasePath –identity DB01 –EdbFilePath “E:\Database\DB01\DB01. in various ways.that’s done in EAC.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. and select Servers. we have the opportunity in PowerShell to specify all parameters that’s needed for having all options configured. New-MailboxDatabase -Name DB02 -EdbFilePath “E:\Database\DB02\DB02.
testlabs.se. it can now be load balanced based on IP addresses. example: mail. 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. Using PowerShell Start the Exchange Management Shell (EMS) and the following commands will do the same work that’s done in EAC. type in the external name. I’m using Basic authentication for Outlook Anywhere. And the Configuration is completed. as far as I know this will make both the Firewall team and the Load Balancer teams work easier. less ports is used together with the requirement of load balancing affinity/sticky session settings is also gone now. Enable Outlook Anywhere: Enable-OutlookAnywhere –Server TLCAS01 –ExternalHostname mail.testlabs. I think (and hope) most of you will 31 . Outlook instead will use port 443 (HTTPS) or port 80 (HTTP).se –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. This because of there is no need anymore to have the affinity settings.se – InternalHostname tlcas01. Press Save.testlabs.Then go to the “Outlook Anywhere” option.
It’s using HTTPS to initiate the connection. More information around What’s new in Exchange 2013 can be found here.use RPC over HTTPS. A small picture from Network Monitor when the connection initiated by Outlook 2013. 32 . 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. Outlook 2013 Preview. using port 6001 by default for it’s connection.
and supported to run on both Windows 2008 R2 and Windows Server 8. Disaster Recovery. 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). Using EAC: It’s time to like the new EAC “console”. again. I have also read that IOPS requirements for databases have been reduced with another 50% from Exchange 2010. 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. Note: My posts around Exchange 2013 Preview/beta are based on Beta information and it could be changed before it will be released (RTM).. it’s easy and very fast for doing switchover/failover to another server. CAS Array and Public Folders At the end of the post. Some interesting changes around databases are that each database runs under it’s own process in Windows. but I haven’t read it officially so maybe it’s just a rumor. The DAG is the new cluster technology from Exchange 2010 and also included in 2013. here are some background information. which means you can’t use databases from older versions of Exchange directly on Exchange 2013. Though all DAG members needs to run the same OS version. DAG is available for both Standard and Enterprise version of Exchange. for checking the IP addresses. It give us the opportunity to have a mailbox database replicated between two or more servers. Configure DAG. Database Availability Group (DAG) If this expression is new to you. Both for the MAPI network and the Replication network. Store (ESE) is totally rewritten. Let’s get ready to create the DAG and add the Databases as copies on each DAG member/node.4. Running “ipconfig” on both mailbox servers. Site resilience and Public Folder migration. 33 .
34 . Press Add button (+). Witness directory and DAG IP.Go into Control Panel and check the network interfaces. Press Save. Login to the EAC. Type in DAG name. Witness Server. go to Servers and select Database Availability Group.
When the DAG is created. Check the option “Configure database availability group network manually”. select it and Press Edit. this by pressing “Manage membership” button. Add the mailbox servers that should reside in the DAG. Press OK. Press the Add button (+) and add the mailbox servers. Press Save. 35 . It’s now time for adding the mailbox servers into the DAG.
The configuration now gets saved. a network called “MapiDagNetwork” has been created. Press Close. Next thing to do it the DAG Networks. I want to have the control over these networks so I will 36 . as you can see in the right bottom corner.Press Save. failover clustering was installed on mailbox servers.
Press Save. I’m about to create two new networks. My second network will be called Replication Network. let’s remove the automatic created one by pressing “Remove” button. 37 . Press Save.create my own. Since we now have created those two network. and assign the Subnet to it where the clients are supposed to connect. Start by pressing “New DAG Network”. I will give the first network a name like MAPI Network. since that it’s purpose and also assign it to the correct Subnet.
In the menu.Press OK. 38 . The MAPI Network should not be enabled for replication. 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. Which means that you end up with having same database mounted on two (or more) different servers. More info about DAC mode can be found on the link in the end of the post. The MAPI Network is not supposed to be used as replication network. So let’s start up Exchange Management Shell (EMC). go to Databases and select one database. so let’s disable that function by pressing “Disable Replication” on the MAPI network. Final DAG configuration The last step (just a recommendation) is to enable the DAC mode. The DAG should now show two networks called MAPI and Replication. Press OK. This can’t be done through EAC (maybe that will change to RTM). then press the Add database copy button. this for preventing split brain syndrome.
Note: In this menu you also have the option to configure lag time (if using lagging node). Then do the same procedure on all of your databases. Press Save. 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.
40 . when the operation is done. Do the same procedure on all of your databases.Press Close. The seeding operation is running.
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. But I prefer the PowerShell.Press Close..) until it get’s Healthy and everything has been checked and verified. In my test environment it took around 15min to be fine.16. because I have the full control over what’s going on. Let’s start with creating the DAG by using the command below: New-DatabaseAvailabilityGroup –Name DAG01 –WitnessServer TLCAS01 –WitnessDirectory C:\FSW_DAG01 –DatabaseAvailabilityGroupIpAddresses 172.1. It should look like the picture below when everything is completed.
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.1. one for Mapi and one for Replication: New-DatabaseAvailabilityGroupNetwork –DatabaseAvailabilityGroup DAG01 –Name Mapi – Description “Mapi Network” –ReplicationEnabled $False –Subnets “172.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.0.0/24” New-DatabaseAvailabilityGroupNetwork –DatabaseAvailabilityGroup DAG01 –Name Replication –Description “Replication Network” –ReplicationEnabled $True –Subnets “10.16. Specify a mailbox server that at the moments doesn’t hold a copy of the database and add it by 42 .0/8” Remove the automated created network.
But you can only have one that is allowed to make changes/writeable. the first step will be to create a mailbox that holds the public folder hierarchy. 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. you can have copies of the hierarchy. It means that you don’t have any public folder hierarchy (mailbox) created yet. With “normal” mailbox I mean that they reside in the mailbox databases. it’s still required that you configure the public folder replication for the contents. just like user mailboxes does. If you decide to use the Public Folders in Exchange 2013. this is the first warning/error message you will receive. 43 . The advantage of this is that the mailbox itself can now be replicated using DAG technology. and transferred to “normal” mailboxes instead. those are also special mailboxes.running the following commands. This doesn’t mean that the public folder contents is replicated. However they can in someway be compared to shared and room. This will be the writeable copy.
let’s create some test folders too. so it’s hierarchy can be saved. Press Save. example: PF_Hierarchy. 44 . press Edit and configure it. create the first mailbox for the public folders. Now when the hierarchy is created. If you want to configure any storage quota on the public folder content. which sometimes is valuable. Give the public folder a name. press the Add (+) button. Add (+). Press Save. Go back to “Public Folders”. Give the mailbox a friendly name. place it into an organizational unit and select a mailbox database where it should be saved into.Go to the second public folder selection called “Public Folders Mailboxes”. Statistics can also be found under Edit selection.
By pressing the Enable button. 45 .Just for testing purposes I did mail-enable the folder. Here’s a small example how the Mail Flow settings looks like. Press Yes. now we see that we have lots of new settings. Let’s check the properties for the folder again.
How to create a client access array? Right now. this will be one of the first things to try out. Let’s create the folder named Testlabs New-PublicFolder –Name Testlabs Finally. This for not having the possibility to logon as this user. SP3 is right now under development/testing and no official information can be found. you can find a link to a TechNet article. mail enable the public folder Enable-MailPublicFolder –Identity \Testlabs We have public folders located in Exchange 2007/2010. After the architectural change around the CAS role. the following commands will be used for creating the public folder hierarchy and contents folder. it provides you with a great stepby-step guide. 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. The “new” Client Access Server role can now been seen as more of a traditional Front-End server. For example. it’s now “stateless” which means there’s no need for the load balancer to configure affinity/sticky session. where I did mention what changes been made. It can be found here. This means that all CAS servers now will serve all clients with connections to it’s mailbox endpoint server. Client Access Server Array In my previous blog post I did write about some news regarding MAPI and RPC. like shared/room mailboxes is also disabled by default.Using PowerShell: Start up Exchange Management Shell. In an upcoming blog post I will cover how to configure the load balancing for Exchange 2013. I don’t see any specific reason for creating the CAS Array. When I get my hands on SP3. it means that the clients is not required to have the connection established to the same CAS server for having the OWA to work. It utilize as a front-end connection point and redirects/proxies (depending on method) the clients to it’s correct mailbox server. 46 . 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. Create the hierarchy by running the following command New-Mailbox –Name PF_Hierarchy –Alias PF_Hierarchy –Database DB01 –OrganizationalUnit Users This mailbox.
database failover. But first it’s time for 3 weeks of vacation. move mailbox reports. Thanks for reading. I hope it did gave you some valuable information. 47 . 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. until then. disaster recovery etc.