Configure RpcClientAccessServer Attribute on Mailbox Database

Recently, my team was notified on an issue happening to outlook clients. Outlook was not able to launch for all users in a particular site. The outlook connection status indicated that it is trying to connect to the F5 load balancer/CAS array, but immediately drops the connection.


We suspected an issue at the load balancer end and hence planned to bypass the load balancer and directly connect to the CAS server instead.

We tried to manually configure outlook for a test mailbox with the fqdn of the CAS server, but the profile configuration was not successful. DAG was configured and the mailbox database in which the mailbox resided had a copy on another Mailbox server. I tried to activate the passive copy and the observed the status, but the issue persisted.

It was then noticed that the RpcClientAccessServer attribute for the mailbox database was configured to point to the fqdn of the cas array, which was expected. In order for outlook to bypass the cas array and directly connect to the CAS server this attribute value should be changed and made to point to the CAS server.

Following cmdlets were used for this :

First to view the current configuration, the below command was executed in Exchange shell :-

Get-MailboxDatabase -identity MailboxDatabase | select rpcclientaccessserver

Now to modify th attribute to point to CAS server,

Set-MailboxDatabase -identity MailboxDatabase -RpcClientAccessServer ‘CASServerFQDN’

Once this change was performed, outlook connected directly to CAS and the connection was established. Later it was identified that there were some network/port issues which prevented the connection. The above change was then reverted and the RpcClientAccessServer attribute was pointed to CAS array.


Error “Outlook Web App didn’t initialize. If the problem continues, please contact your helpdesk.”

Recently, I faced an issue logging in to OWA on our client’s Exchange 2010 server. The error reported was as follows :

Outlook Web App didn’t initialize. If the problem continues, please contact your helpdesk.
Couldn’t find a base theme (folder name=base)


Initial troubleshooting steps were taken, like restarting the Microsoft Exchange Form Based Authentication service, re-creating OWA virtual directories etc..

Upon further researching on the issue, I found a similar post online where the OWA crashed after installing the Exchange updates..

So, in order to resolve the issue all you need to do is launch Exchange Management Shell, navigate to the location C:\Program Files\Microsoft\Exchange Server\V14\Bin and then execute the power shell script UpdateCas.ps1.


This script will find your OWA/ECP virtual directories, update them and make some modifications to metabase etc.. Once completed, you will be able to access your OWA/ECP like before.. 🙂


Reference :-

Enable Export-Mailbox and Import-Mailbox commands on Exchange 2010 & Exchange 2013

You might have faced this issue at some point that when trying to execute the Export or Import command on EMS for the first time. The error may indicate that such command does not exist. In order to resolve this, you have to perform the following :->

  • Check and confirm if the Exchange Server Admin tasks are installed in Exchange Management Shell, by trying to execute the command Get-PSSnapin
  • If not possible, it means that its is not included in the list. In that case execute the below command Get-PSSnapin -registered
  • To install the required Admin tasks for the server, execute the command Add-PSSnapin Microsoft.Exchange.Management.PowerShell.E2010


Note: For Exchange Server 2007, execute the command Add-PSSnapin Microsoft.Exchange.Management.PowerShell.Admin

  •  In order to provide multiple users or groups permission to run these commands, execute the below command “New-RoleGroup -Name “Exchange Mailbox Import Export” -Roles “Mailbox Import Export” -Members “<yourdomain\yourgroupname>” -DisplayName “”Exchange Mailbox Import Export” -Description “This group handles permissions to the import and export commands in powershell.”


Note: Command to delete email from all mailboxes in Exchange 2010 & Exchange 2013 

Get-Mailbox -Database mdb | Export-Mailbox -SubjectKeywords “New” -DeleteContent 

Where mdb is the Mailbox Database and New is the email subject.

Also, the below command should be executed to have the permission to run the above command

get-mailbox -Database “Mailbox Database”| add-mailboxpermission -user administrator -AccessRights FullAccess



Reference :

Upgrade Exchange Server 2013 RTM to SP1 on Windows Server 2012 R2

The Exchange Server 2013 RTM version number is 15.0 (Build 516.32). We are planing to upgrade it to Exchange Server 2013 Sp1 which is [Build no – 15.00.0847.032]. 

Before proceeding with the upgrade make sure you have a proper backup in place. Also, update your server with the latest patches.

You can check your current Exchange Schema Version using the Powershell command “Exchange Schema Version = ” + ([ADSI](“LDAP://CN=ms-Exch-Schema-Version-Pt,” + ([ADSI]”LDAP://RootDSE”).schemaNamingContext)).rangeUpper”

  • Make sure you have downloaded the setup files to your local server
  • Check and confirm that the mail flow is working
  • Execute the command “Get-ServerComponentState ServerName” and confirm that the status of all Exchange components are Active
  • Execute the command “Set-ServerComponentState ServerName –Component HubTransport –State Draining –Requester Maintenance &”Set-ServerComponentState ServerName –Component UMCallRouter –State Draining –Requester Maintenance” to put the components in Maintenance Mode
  • Execute the command “Set-ServerComponentState ServerName –Component ServerWideOffline –State inactive –Requester Maintenance” to change the status of all the components to Inactive state
  • Check and confirm that all components are in Inactive state using the command “Get-ServerComponentState ServerName


  • Now launch Exchange Management Shell and navigate to the Exchange 2013 SP1 setup folder
  • Execute the command “setup.exe /preparead /IAcceptExchangeServerLicenseTerms” to prepare your AD server for the upgrade

Note : You may face several issues during this process. The issues that were reported during the upgrade while I was working are discussed here :-

A reboot from a previous installation is pending. Please restart the system and rerun Setup.


Checked the following registry keys :

  • HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Updates\UpdateExeVolatile
  • HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations

Since I was not able to find the Updates key, had to manually create the same along with the string value UpdateExeVolatile. The value of the string was set to 0 [which indicates that system restart is not required]. Also, deleted the key PendingFileRenameOperations.

After performing the above steps, re ran the PrepareAD command again. The Prerequisites and Organization Checks completed successfully.


  • Next step is to run the Setup.exe file from its location. Double click the Setup.exe file and proceed. You might face the below error at some point during the readiness checks ;

Service ‘WMSVC’ failed to reach status ‘Running; on this server

Error 2

Upon searching regarding the error online, it led me to Web Management Service in IIS Manager.

  • Launch IIS Manager
  • Select the Server and on the right hand side, under Management double click Management Service


  • Assign the SSL certificate you have previously installed to the service and Start the WMSVC service


This resolved the issue and the setup installation completed successfully.

Now the pending work is to remove the Exchange services from the Maintenance Mode. Execute the below commands for the same :

  • Set-ServerComponentState ServerName –Component ServerWideOffline –State active –Requester Maintenance
  • Set-ServerComponentState ServerName –Component HubTransport –State active –Requester Maintenance
  • Set-ServerComponentState ServerName –Component UMCallRouter –State active –Requester Maintenance

Confirm that all Exchange components are in Active state by executing the command : Get-ServerComponentState ServerName

Restart the Exchange Services and test the mail flow. Confirm that the SP1 upgarde completed successfully by executing the ‘Get-ExchangeServer | fl‘ in EMS.


Verify the build number in the above screen shot.


Note:- Please also check the link ‘’ for resolving issues with SP1 upgrade. 🙂


Reference :


Unable to login to Exchange 2013 OWA !!

Recently on the process of an Exchange 2007 to Exchange 2013 migration, I happen to notice an issue with the new Exchange 2013 server. A standard SSL certificate was purchased and installed on the Exchange 2013 server recently as well. When accessing the OWA URL, all I get is a blank page as shown below :

exchange 2013 owa

I tried accessing the Exchange Management Shell, only to receive the error “The WinRM shell client cannot process the request“.

exchaneg 2013 owa

Upon checking the event logs, noticed the following error –

exchg 2013 2

The reason for the error was later found that the new SSL certificate was not bound to the Exchange backend website. This is a new website created during the Exchange 2013 installation along with the Default website and has all the virtual directories of the Exchange services.


Steps to resolve the error :-

  • Login to IIS Manager
  • Select the Exchange Backend Website and click on Properties
  • Select Edit Bindings
  • Select https binding and click on Edit


  • Bind the SSL certificate to the https binding and click OK


Confirm that you are able to login to OWA successfully and that EMS works fine.


Updating GAL entries forcefully on Exchange Server 2010 using EMS

Recently I had come up with an issue as mentioned below :

A new email alias was added for a domain mailbox in an Exchange 2010 environment. On one of the users Outlook 2010, whenever the user sends an email to this new address [be it], the email is being rejected reporting that such an email address does not exist. I initially tried the following troubleshooting methods :

  1. Tried downloading OAB manually on the workstation from Outlook -> Account Settings
  2. Compared the GUID of the OAB on the Exchange Server location ‘C:\Program Files\Microsoft\Exchange Server\V14\ExchangeOAB’ and the GUID of the OAB present in the outlook [this can be found out by pressing CTRL key + Right click on Outlook icon present in notification area to get Test E-mail AutoConfiguration. Test the setting and note the OAB GUID] and confirmed both are the same
  3. Tried updating OAB in the Exchange Server but resulted in the below error

OAB update

The above issue was resolved by removing the distribution of OAB using ‘Public Folder Distribution‘. It is safe to perform this step in an environment with no Outlook 2003 or earlier clients, as they are the one who access OAB using public folders. Once this step is performed, OAB will use Web Based Distribution.

Even after performing the above steps the issues still persisted. After searching a couple of links online, found out a thread which suggested on performing the following :

  • Update Global Address List on the Exchange Server using the command ‘Get-GlobalAddressList | Update-GlobalAddressList
  • Update Address List using the command ‘Get-AddressList | Update-AddressList
  • Update OAB using the command ‘Get-OfflineAddressBook | Update-OfflineAddressBook
  • Execute the shell command ‘Get-Mailbox | Set-Mailbox -ApplyMandatoryProperties
  • Restart the following MS Exchange services ‘Microsoft Exchange System Attendant Service‘ & ‘Microsoft Exchange File Distribution Service
  • Download the address book manually to your email client without enabling the option ‘download changes since last send/receive

Check and confirm whether the newly added email alias is updated in GAL.


Reference : Technet forums.