How to Brand OWA 2007 and 2010 with the Server Name

Wednesday, March 31, 2010
If your Exchange 2007 or Exchange 2010 environment includes more that one CAS server, it's sometimes helpful to know which one a client is connecting to.  Environments with more that one CAS usually use some form of hardware or software load balancing, making it difficult to troubleshoot OWA issues.

A relatively easy way to do this is to brand each CAS server's OWA logon page with the server name.  This way, end-users are able to provide the server name if they run into problems.

For Exchange 2007, navigate to C:\Program Files\Microsoft\Exchange Server\ClientAccess\owa\auth folder and open the logon.aspx file using Notepad.

Add either of the two edits shown in the screenshot below:

Adding the server name as highlighted above in red will visibly add the server name to the logon screen, as shown below:

Adding the server name as highlighted above in blue will add the server name "invisibly" below the logon screen.  To view the server name, click anywhere on the screen and press CTRL-A to select all.  You can then see the server name, as shown below:

For Exchange 2010, navigate to the C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess\Owa\auth folder and open the logon.aspx file using Notepad.

Add the server name, as shown in the screenshot below:

This will add the server name to the logon screen, as shown below:

Important Note: These edits are overwritten anytime an Exchange Server update is applied to the CAS servers.  This is because every update includes a complete reinstallation of the Exchange binaries, and the logon.aspx file you edited will be overwritten.

Typically, the logon.aspx page rarely changes, so you can usually make a copy of it after you've made your edits and copy it back after the update.  However, there are no guarantees that the file will not be changed by an update.  If so, you will need to re-edit the logon.aspx file.


  1. Great Post Jeff.

    I always been interested to use the screen around the OWA logon screen. Any idea how to do that ?

  2. Thanks for simply explaining something that Microsoft should have helped us do, oh, 10 years ago...

  3. I'll look into that when I get back from vacation. The background color or add graphics?

  4. The user can also simply pull up the appropriate Help/About page which tells you a lot more information, including what server(s) they're using. Mind you, they have to be logged in first...

  5. Where are the langauge files stored? I want to edit the pre-existing test, but want to allow the multi-language functionality that Exchange 2010 provides. I want to edit the source language files for the different languages our international organization uses. I could hard-code the login.aspx file that lot of people recommend, but then it is only in one language.

  6. Superb article. Just what I was looking for. I have two load-balanced CAS servers and needed to know which server I was authenticating against. Many thanks!


Thank you for your comment! It is my hope that you find the information here useful. Let others know if this post helped you out, or if you have a comment or further information.