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