Customize OWA logon page in Exchange 2013

The Outlook Web App sign-in, language selection, and error pages are created based on graphics and .css files in the themes resources folder in the Client Access Server.

Any modifications to those pages will be seen by all users.

Here you have an example about what you can do.

Browse to the Following Location in your Client Access Server


and modify the following files to customize Web form.

  • owa_text_blue.png
  • olk_logo_white.png
  • Sign_in_arrow.png
  • Favicon_ico.png
  • logon.css


Redirect Owa in Exchange 2013

May you want to configure OWA to automatically redirect users from top level directory to /owa virtual directory and force redirection to SSL, here you have what you need to do.
This procedure has been tested under IIS 8.5 with Exchange 2013 CU8.
1.Open IIS manager in Exchange server.
2.Open “SSL settings” feature under “Default Web Site” and “Exchange Back End” website.

3.Uncheck  “Require SSL” checkbox on both websites and click Apply to save changes

4.Then, open “Http Redirect” feature under “Default Web Site” and “Exchange Back End” web Site.

5. Ensure “Redirect request to this destination” checkBox is marked and type your redirect url.
6.Ensure “Only redirect request to content in this directory “ checkbox is also marked and “Status code found (302)” is also selected.
7.Click on “Apply” to save changes.

8.As we don´t need to redirect sub folders to /owa directory we should uncheck the HTTP Redirect option from all the sub directories under “Default Web Site” and “Exchange Back End” Website.

9.If you want to access to ExchangeControl Panel (ecp) only from a secure connection ensure to set SSL settings on /ecp virtual directory only.

Can’t login to Exchange Admin Center after a clean Exchange 2013 installation

Yesterday, after a clean installation of MS Exchange 2013 RU7 i have some problems to login to the Exchange Admin Center using Exchange administrative credentials

I can successfully connect to the Exchange Power Shell but something seems to be wrong with FormsAuthentication,

IIS log is registering error code “302 0” every time I try to login to the url: https://myservername/ecp/?exchclientver=15

Here is what I did:

I ran the following cmdlet to check ecp virtualdirectory authentication:

Get-Ecpvirtualdirectory -server MYSERVER | fl identity,*auth*

I ran the following cmdlet to change Windows Authentication and Forms Authentication

Set-EcpVirtualDirectory -Identity “MYSERVER\ecp (default web site)” -windowsauthentication $true -formsauthentication $false

Then IISreset to apply changes, 

Then I was able to login successfully to Exchange Admin Center on https://servername/ecp/?exchclientver=15 and I was ready to migrate the Exchange Admin mailbox to a new Exchange 2013 Database.

Once the Exchange Admin mailbox have been migrated, I ran the following cmdlet to enable  Forms Authentication and disable Windows Authentication, as default setting.

Set-EcpVirtualDirectory -Identity “MYSERVER\ecp (default web site)” -windowsauthentication $false -formsauthentication $true


Your Exchange Server administrator has blocked the version of Outlook that you are using. Contact your administrator for assistance.

This morning I have noticed about an issue with Outlook 2003,

No user can connect to Exchange 2010 from Outlook 2003 version, but users affected by this incident are able to connect to their mailbox using OWA , mobile phones ,Outlook 2010 or 2013 version.

All Mailboxes have been migrated from Exchange 2003 to Exchange 2010 and legacy Servers have been decommissioned from the Organization a few days ago.

A user with Outlook 2003 get the following error when he try to connect to his own mailbox.

Your Exchange Server administrator has blocked the version of Outlook that you are using. Contact your administrator for assistance.

I ran the following cmdlets to check for any blocked parameters enabled on CAS Servers, but I didn´t found anything about.

  • Get-CasMailbox | Ft, name, MAPI*
  • Get-RpcClientAccess –server  “myExchangeserver” | fl blocked*,encryption*

After a while I found the solution,

Public Folder hierarchy and database have been removed yesterday because is not used anymore by the Organization.

Note: Remove Public Folders is not a recommended practice if you still have Outlook 2003 clients in your Organization. Outlook 2003 has some dependencies with Public Folders, especially for free busy and OAB.

Creating a new Public Folder Database on Exchange 2010 the problem was solved. I forced OAB to be published in the new Public Folder Database  and forced also to be assigned to each Mailbox Database.

Quick and Simple way to migrate DHCP Scope from W2008 to W2012

Windows Server 2012 and Windows Server 2012 R2 has new DHCP cmdlets which include export and import tasks based on PowerShell.

  • Export-DhcpServer
  • Import-DhcpServer

To export the DHCP server configuration, scopes and leases from a Windows Server 2008, Windows Server 2008 R2 or Windows Server 2012 to Windows Server 2012 R2, run the following command from the Windows Server 2012 R2 powershell console.

Export-DhcpServer –ComputerName “” -Leases -File C:dhcpexp.xml -verbose

If you do not want export lease information, do not include –Leases switch.

Once the export task is finish Stop the DHCP service in the current DHCP server (

Net stop dhcpserver

Install DHCP Server role on your NEW Windows Server 2012 R2.

Install-WindowsFeature -IncludeManagementTools dhcp

To import DHCP server configuration to Windows Server 2012 R2, run the following command from the Windows Server 2012 R2 powershell console.

Import-DhcpServer –ComputerName “” -Leases –File C:dhcpexp.xml -BackupPath D:dhcpbackup -Verbose

Delivery report issues with attachments in Exchange 2010

I am involved in a email migration project from  Exchange 2003 to Exchange 2010.This morning I have been warned about an issue with a migrated mailbox in Exchange 2010 related to Delivery Receipt .
A user request a delivery receipt from a Mailbox Stored in Exchange 2010 server ,and  he receive it but without the original email (attached).
Users with mailbox stored in Exchange 2003 are still receiving  this attachment.
After Reviewing so many parameters in the Exchange server  I found the root cause of this behaviour.
I found a paramater in the transport global settings that control how Exchange handles delivery status notifications (DSNs) that are generated by earlier versions of Exchange or non-Exchange messaging systems.
Yo can get the value for this parameter running the following cmdlet:

Get-TransportConfig  | fl DSNConversionMode
The values for this parameter are the following:

  •     UseExchangeDSNs
  •     PreserveDSNBody
  •     DoNotConvert

You can change the value for this parameter running the following cmdlet:

Set-TransportConfig  -DSNConversionMode (value)
By default, this parameter is set to UseExchangeDSNs and Exchange converts the DSNs to the Exchange 2010 DSN format. Any customized text or attachments that were associated with the original DSN are overwritten.
If you set this parameter to PreserveDSNBody, Exchange converts the DSNs to Exchange 2010 DSN format but any customized text or attachments of the DSN message is retained.
If you set this parameter to DoNotConvert, Exchange does not modify the DSN message. Instead, Exchange 2010 delivers the message as a standard message.
for more info:

Can not synchronize email with smartphone after migrating the mailbox to Exchange 2013

Some users can not synchronize email with mobile devices  after migrating the mailbox to Exchange 2013.

The following error is registered in the event viewer : “Exchange ActiveSync returned an HTTP 500 response.”

Make sure that the check box for “Include inheritable permissions from this object’s parent” is selected in the security tab on the user object in Active Directory