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