Exchange 2013 and Exchange 2010 mixed environment throws error message "The arbitration mailbox 'SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}' for the organization '' is located on a server that doesn't have Exchange 2013 installed. The arbitration mailbox must be moved to an Exchange 2013 server before you can enable auditing."

Issue: While enabling auditing or trying to access audit info following warning message would appear:

The arbitration mailbox 'SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}' for the organization '' is

located on a server that doesn't have Exchange 2013  installed. The arbitration mailbox must be moved to an Exchange

2013 server before you can enable auditing.

Cause: As per Microsoft article http://technet.microsoft.com/en-us/library/dn249849(v=exchg.150).aspx , SystemMailbox mentioned above should be moved to  Exchange 2013 database once Exchange 2013 is introduced into the environment.

Resolution: Move 'SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}' mailbox from Exchange 2010 based mailbox DB to Exchange 2013 DB.

Steps:

1. Find out location of arbitration databases using following exchange powershell cmdlet:

Get-Mailbox -Arbitration | fl Name, Displayname, ServerName, Database, AdminDisplayVersion

It would print information similar to the following

Name                : SystemMailbox{1f05a927-c4a9-4cc7-80bd-a557eb562135}

DisplayName         : Microsoft Exchange Approval Assistant

ServerName          : exchange

Database            : Mailbox Database 0147642087

AdminDisplayVersion : Version 14.3 (Build 123.4)

Name                : SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}

DisplayName         : Microsoft Exchange

ServerName          : exchange

Database            : Mailbox Database 0147642087

AdminDisplayVersion : Version 14.3 (Build 123.4)

Name                : FederatedEmail.4c1f4d8b-8179-4148-93bf-00a95fa1e042

DisplayName         : Microsoft Exchange Approval Assistant

ServerName          : exchange

Database            : Mailbox Database 0147642087

AdminDisplayVersion : Version 14.3 (Build 123.4)

Name                : SystemMailbox{bb558c35-97f1-4cb9-8ff7-d53741dc928c}

DisplayName         : Microsoft Exchange

ServerName          : exchange2013

Database            : Mailbox Database 0562670298

AdminDisplayVersion : Version 15.0 (Build 995.29)

Name                : Migration.8f3e7716-2011-43e4-96b1-aba62d229136

DisplayName         : Microsoft Exchange Migration

ServerName          : exchange2013

Database            : Mailbox Database 0562670298

AdminDisplayVersion : Version 15.0 (Build 995.29)

2. Either use information from above to get database names where version is 15.0 or above or use following exchange powershell cmdlet to print information about all databases in your environment:

Get-MailboxDatabase -IncludePreExchange2013 | fl Name, Server, AdminDisplayVersion

It would print information similar to the following:

Name                : Mailbox Database 0147642087

Server              : EXCHANGE

AdminDisplayVersion : Version 14.3 (Build 123.4)

Name                : Mailbox Database 0562670298

Server              : EXCHANGE2013

AdminDisplayVersion : Version 15.0 (Build 995.29)

3. Now move SystemMailbox in question using EAC  (under migration) or using following shell cmdlet (modify  with DB name identified above for exchange 2013)

Get-Mailbox -Arbitration -Identity "SystemMailbox{e0dc1c29-89c3-4034-b678-e6c29d823ed9}" | New-MoveRequest -TargetDatabase

Reference: http://technet.microsoft.com/en-us/library/dn249849(v=exchg.150).aspx

Microsoft Exchange Server 2013 upgrade to SP1 or RU5 or RU6 will fail with error message " The Windows component RSAT-Clustering-CmdInterface isn't installed on this computer and needs to be installed before Exchange Setup can begin."

Issue: While trying to upgrade Microsoft Exchange Server 2013 RTM or releases below SP1/RU5/RU6 that is installed on Windows 2012 Server to either SP1 or RU5 or RU6   error message "The Windows component RSAT-Clustering-CmdInterface isn't installed on this computer and needs to be installed before Exchange Setup can begin." may appear on the screen.

Following is the screenshot while performing silent upgrade

If you will check ExchangeSetup.log file located usually under C:\ExchangeSetupLogs\ folder you will find entries similar to the following:

[11/25/2014 05:04:26.0209] [1] Failed [Rule:RsatClusteringCmdInterfaceInstalled] [Message:The Windows component RSAT-Clustering-CmdInterface isn't installed on this computer and needs to be installed before Exchange Setup can begin.]

[11/25/2014 05:04:26.0490] [1] [REQUIRED] The Windows component RSAT-Clustering-CmdInterface isn't installed on this computer and needs to be installed before Exchange Setup can begin.

[11/25/2014 05:04:26.0490] [1] Help URL: http://technet.microsoft.com/library(EXCHG.150)/ms.exch.setupreadiness.RsatClusteringCmdInterfaceInstalled.aspx

The link mentioned above as of today while I am writing this note is not working.

Following is the screenshot from the log file in question:

Solution: Install the required module using the following Windows PowerShell command whiand restart setup.exe program to upgrade.

Install-WindowsFeature RSAT-Clustering-CmdInterface

Following is the screenshot (ignore warning about automatic updates since I like to control updates on my servers)

Note: For more information about this module please refer Microsoft documentation on "Failover Clustering module"

How to allow certain types of file attachments (HTML/XML) through OWA (2010/2013)

GOAL: At times there may be sites that have business case to allow file attachments e.g. .HTML or .XML to be opened/accessed through OWA. Though these are be default not allowed to be opened due to security concerns but there may be sites where it is business requirement. 

STEPS:

From early days of Exchange 2003/2007 there were means available to allow such attachments through OWA. I am only adding here for very recent versions of the exchange only. Especially because they have Microsoft Exchange powrshell cmdlets which can do it very quickly. 

1. Open Microsoft Exchange Management Shell in case of Exchange 2010/2013 

2. Once shell is connected up and running use the following cmdlet to add extension to the AllowedFileTypes 

Set-OwaVirtualDirectory -identity "owa (default web site)" -AllowedFileTypes @{Add='.html'}

This would add .html to AllowedFileList for both "Plublic Computer File Access" and "Private Computer File Access".

In case you are working with an attachment time that is in the BlockedFileTypes or ForceSaveFileTypes list you need to remove those from there first.

After this change now will be up to the internet browser you are using.

For IE 8 it will work like a charm. Users will be able to OPEN and SAVE .HTML attachments as they they like.

With IE 9 and onward there is an issue, it would not allow HTML files to open and same is currently applicable to FireFox (on the time when I am writing it). Another issue is that if you click on SAVE button that will change any URLs within HTML with something like redir.aspx?........

Workaround for this issue is to add .HTML to ForceSaveFileTypes list and then use "Save Target As..." option within IE 9, 10 and 11.

Chrome appears to have no issue at this stage.

To me it appears this is combination of filtering within exchange and the way headers are passed on to browsers. IE 8 and Chrome can handle it but IE 9, 10, 11 and FireFox is having issue.

Microsoft Windows NLB - Configure Exchange CAS high availability

Although for sites with high volume of network traffic coming to the CAS servers it is recommended to have hardware NLB, for sites that are small in size or do not have hardware NLB in hand Microsoft provides Windows Network Load Balancing as an option.

What I am going to mention below is something I built for my lab running Exchange 2013. You may want to check Microsoft best practices for your version of exchange before you follow this post. 

Legal Stuff: I or anyone related to me would not be responsible for any issue or loss caused if you follow this post.

Prerequisites: 

1. Server names used for CAS Servers e.g. CAS1.katwal.local and CAS2.katwal.local

2. Make sure both CAS servers has TWO NIC cards (network interfaces). 

3. Write down IP addresses of the both CAS servers:

     CAS1.katwal.local = 10.0.0.10/255.0.0.0

     CAS2.katwal.local = 10.0.0.11/255.0.0.0

4. Dedicated IP address for NLB : 10.0.0.50/255.0.0.0

5. NLB/CAS URL name: mail.katwal.local  (I assume you already prepared your CAS servers for this alias e.g. SSL certificates are already having autodiscover.katwal.local and mail.katwal.local in their SAN and certificates are already installed on each CAS server)

6. Rename network interfaces that we are going to use on both CAS servers for NLB (to NLB) to make sure we can differentiate them.

Prepration of network interfaces for NLB configuration:

1. As I mentioned above change the network interfaces names to make sure we can differentiate them. In my case I renamed them to NLB.

2. On both servers assign the IP addresses as mentioned above and subnet mask. Make sure you DO NOT fill any DNS information or WINS information.

3. By going to ADVANCED TCP/IP settings screen, under DNS tab uncheck "Register this connection's addresses in DNS" on both servers. Similarly under WINS tab select "Disable NetBIOS over TCP/IP"

4. Check Network Adapter bindings on both machines to make sure NLB adapters are the first adapters in binding. I will give example from Windows 2008 R2 machine below:

• Open NETWORK CONNECTIONS folder.
• Press ALT key to bring up the menu bar, go to ADVANCED menu
• Select Advanced Settings
• Under Adapters and Binding section, reorder positions of NIC interfaces to make sure NLB is the first interface and other network interface is second.

INSTALL AND CREATE NLB CLUSTER:

By default Network Load Balancing feature is not installed on the servers. Following are the steps to install and configure a NLB cluster:

1. Select START > Administrative Tools> Server Manager

2. Select Features > Add Features,  Select Network Load Balancing Manager, Select Install

3. Close Wizard when Network Load Balancing Manager is installed.

4. On CAS1 server select START > Administrative Tools > Network Load Balancing Manager

5. When NLB Console will start, right click on Network Load Balancing Cluster and select New Cluster.

6. On New Cluster: Connect screen, type FQDN for CAS1 server e.g. CAS1.katwal.local  and select Connect.

7. Select Network Interface with IP 10.0.0.10 and select Next button.

8. On  New Cluster:Host Parameters windows select all default and select Next.

9. On New Cluster: Cluster IP addresses window select ADD button and add IPv4 IP address of NLB cluster which is 10.0.0.50 with subnet mask of 255.0.0.0, select OK, select NEXT

10. On New Cluster: Cluster Parameters window under Full Internet Name section type the URL name selected above: mail.katwal.local 

11. Leave Cluster Operation Mode to be set to Unicast and select NEXT.

12. On Add/Edit Port Rule window, select Finish.

13. Allow some time for cluster to converge and turn into green colour icon.

14. Now log on to CAS2 server and use PING command to check if mail.katwal.local replies back on IP address that was assigned to NLB (10.0.0.50).

15. Just in case there is some issue with getting the reply back, check DNS Server configuration.

16. To add CAS2 server to the NLB Cluster open NLB Manager Console

17. Right Click on the cluster (mail.katwal.local) and select  Add Host To Cluster.

18. In Host Field type FQDN for CAS2 server (CAS2.katwal.local) and select Connect.

19. Select NLB interface with IP address of 10.0.0.11 and select Next, Next.

20. Leave everything to default as we did earlier and select Finish.

21. Now you should see second node of CAS2 will start to converge just as CAS1 did earlier and you should see it with the green icon.

22. Verify that when one of the nodes is turned off from NLB Manager we can still get reply for URL (mail.katwal.local) from IP address 10.0.0.50. Additional test will be to turn of both nodes from NLB manager and check if we cannot get to mail.katwal.local and then start only one node at a time.  

23. If using virtual machines you may want to have static MAC address that was provided when cluster was configured. You can get to it by using NLB manager and get to to the properties of Cluster and selecting Cluster Parameter tab. Once you have the MAC address if you are using VMWARE you can go to the properties of NIC we used for NLB and add the MAC address for making it static. Similarly in Hyper-V Manager configure NIC used for NLB and fill  in info under Static section. on Hyper-V also select Enable Spoofing of MAC Addresses.

24. To confirm changes to NIC have not broken anything restart both nodes one at a time and confirm that both nodes converge without issues.

25. Next step is to make sure NIC forwarding is done so that all OWA requests only go to NIC selected for NLB. Following is example of the command I ran on both of my CAS servers. 

netsh interface ipv4 set interface NLB forwarding=enabled

Make sure you start command prompt using Run As Administrator. Reply expected after running above command line is OK.

26. Now you can go ahead and start with Exchange Server 2013 Servers control panel (ECP) to define Internal and external URLs as you want those.

Exchange 2013 - Test-OutlookWebServices to verify four services functionality

Problem Description: At times we need to check if any of the following is having an issue

AUTODISCOVER
EXCHANGE WEB SERVICES
AVAILABILITY SERVICE
OFFLINE ADDRESS BOOK

Those who are familiar with old version of Test-OutlookWebServices might have to watch for few changes in Exchange 2013.

Resolution:

1. By default user can run Test-OutlookWebServices. If you get error message similar to the following that means a user mailbox/test mailbox is not provided.

[PS] C:\Windows\system32>Test-OutlookWebServices Unable to find the client accesss monitoring user. Please run C:\Program Files\Microsoft\Exchange Server\V15\Scripts\New-TestCasConnectivityUser.ps1. Exception: Microsoft.Exchange.Monitoring.MailboxNotFoundException: Failed to find the mailbox. Mailbox = 'extest_1d3bbbbcd5f34@katwal.local'. at Microsoft.Exchange.Monitoring.CommonTestTasks.GetDefaultTestAccount(ClientAccessContext context) at Microsoft.Exchange.Monitoring.TestWebServicesTaskBase.GetMonitoringAccount()    
+ CategoryInfo : InvalidData: (:) [Test-OutlookWebServices], TestWebServicesTaskException    
+ FullyQualifiedErrorId : 5322965D,Microsoft.Exchange.Monitoring.TestOutlookWebServicesTask    
+ PSComputerName : exchange2013.katwal.local

 You can create a test user using the PS script mentioned in the error message above. Following are steps:
[PS] C:\Windows\system32>cd $exscripts
[PS] C:\Program Files\Microsoft\Exchange Server\V15\scripts>.\new-TestCasConnectivityUser.ps1

Please enter a temporary secure password for creating test users. For security purposes, the password will be changed regularly and automatically by the system.

Enter password: ***********

Create test user on: EXCHANGE2013.katwal.local
Click CTRL+Break to quit or click Enter to continue.:

UserPrincipalName: extest_1d3bbbbcd5f34@katwal.local WARNING: The command completed successfully but no settings of 'katwal.local/Users/extest_1d3bbbbcd5f34' have been modified.

You can enable the test user for Unified Messaging by running this command with the following optional parameters : [-UM DialPlan -UMExtension ] . Either None or Both must be present.

[PS] C:\Program Files\Microsoft\Exchange Server\V15\scripts>


Now when we will run the Test-OutlookWebServices we should run without issues.


2. Another method is to specify a particular mailbox. Following is an example:

[PS]C:\Windows\System32>Test-OutlookWebServices -identity:rajan@katwal.local -MailboxCredential (Get-Credential)

Exchange 2013 setup on Domain Controller throws error message "Unable to set shared config DC"

PROBLEM DESCRIPTION: While installing Microsoft Exchange 2013 on a server that is also a Windows Domain Controller, Transport Service installation will fail with the following error message:

Error:

The following error was generated when "$error.Clear(); 

          $maxWait = New-TimeSpan -Minutes 8

          $timeout = Get-Date;

          $timeout = $timeout.Add($maxWait);

          $currTime = Get-Date;

          $successfullySetConfigDC = $false;

          while($currTime -le $timeout)

          {

            $setSharedCDCErrors = @();

            try

            {

              Set-SharedConfigDC -DomainController $RoleDomainController -ErrorVariable setSharedCDCErrors -ErrorAction SilentlyContinue;

              $successfullySetConfigDC = ($setSharedCDCErrors.Count -eq 0);

              if($successfullySetConfigDC)

              {

                break;

              }

              Write-ExchangeSetupLog -Info ("An error ocurred while setting shared config DC. Error: " + $setSharedCDCErrors[0]);

            }

            catch

            {

              Write-ExchangeSetupLog -Info ("An exception ocurred while setting shared config DC. Exception: " + $_.Exception.Message);

            }

            Write-ExchangeSetupLog -Info ("Waiting 30 seconds before attempting again.");

            Start-Sleep -Seconds 30;

            $currTime = Get-Date;

          }

          if( -not $successfullySetConfigDC)

          {

            Write-ExchangeSetupLog -Error "Unable to set shared config DC.";

          }

        " was run: "Unable to set shared config DC.".

CAUSE: Server has IPv6 turned off. 

SOLUTION: 

1. Turn back on IPv6 for the network adapter.

2. Restart the server

3. Start again the Microsoft Exchange 2013 setup, it will find that last installation was incomplete and will complete it.

4. Check to make sure all services for exchange are operational and all configurations.

Usually recommendation is not to install Exchange on Domain Controllers. Some might have to do this due to lack of resources or just because they need to do something for a presentation, demo or testing. 

Exchange 2013 prereq using command line

Following is the command to install most of the prerequisites before installing Microsoft Exchange 2013

WINDOWS SERVER 2012
=====================
(POWERSHELL)

Import-Module ServerManager

 

Install-WindowsFeature AS-HTTP-Activation, Desktop-Experience, NET-Framework-45-Features, RPC-over-HTTP-proxy, RSAT-Clustering, Web-Mgmt-Console, WAS-Process-Model, Web-Asp-Net45, Web-Basic-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-Mgmt-Service, Web-Net-Ext45, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI, Windows-Identity-Foundation

WINDOWS SERVER 2008 R2 (SP1)
==========================

Import-Module ServerManager

Add-WindowsFeature Desktop-Experience, NET-Framework, NET-HTTP-Activation, RPC-over-HTTP-proxy, RSAT-Clustering, RSAT-Web-Server, WAS-Process-Model, Web-Asp-Net, Web-Basic-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-Mgmt-Service, Web-Net-Ext, Web-Request-Monitor, Web-Server, Web-Stat-Compression, Web-Static-Content, Web-Windows-Auth, Web-WMI