Skip to content

Archive for September, 2010


Exchange 2010 SP1 Outlook Web App login customizations.

I’m updating the code in this article using BitTrack Decode HTML to provide you with easy to read code.

I needed to add some code to the OWA page to help our Help Desk get people logged on quicker without so much hand holding.

So here are the three changes I did to the file logon.aspx found in the path (if you let the Exchange 2010 installer chose the default path): C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\auth\

Login Domain Reminders

Customize this however you wish with any HTML code you want. I have two domains that log into this interface, and the email addresses only match Domain2’s UPN, so to make it easier for everyone – we’ve standardized on domain\username. But this code will show up above the username login table but below the Public/Private radio buttons and explanations.

Look for the following lines of code:


<input id="username" name="username" type="text" />

Below the

tag but above the

Insert a new line of code (or multiple, you have the entire table width available):

<span style="color: #ff0000;">&#9830</span> Domain1 use: <strong>domain1\user name</strong>
<span style="color: #0000ff;">&#9830</span> Domain2 use: <strong>domain2\user name</strong>


Invalid Credentials

If a user enters incorrect information, the login page will change to display an alert to tell the user why their email hasn’t appeared on the screen. We wanted to make it easy for a user to find our password reset page, so we included some additional html to provide them a link to the page.

Look for <%=LocalizedStrings.GetHtmlEncoded(Strings.IDs.InvalidCredentialsMessage)%>

Insert between %> and the following text:

Visit https://pwreset.domain.tld to reset your password.

Obviously, you could include any other text that is relevant to your environment to assist your users.

Connected to…

I have to client access servers setup using MNLB, so they both respond to requests to our OWA URL. If either one of them is having a server specific problem, it’s a pain typing in each FQDN URL to test, when I can just insert a little text at the bottom to tell me or the user which server is serving them.

Look for (Strings.IDs.ConnectedToExchange)%>

Insert between %> and the following text ”’Client Access Server 1”’ or ”’Client Access Server 2”’ as appropriate.

The finished line of code should look like this:

<%=LocalizedStrings.GetHtmlEncoded(Strings.IDs.ConnectedToExchange)%>Client Access Server 2

%d bloggers like this: