| EXCHANGE RANGER

How to customize Exchange Server 2013 OWA Log In Page

By Gulab Prasad | Thursday, January 1, 2015 | Exchange Server 2013 Leave a comment

I have been asked to customize Outlook Web App page several time in past by some of my clients.

Customizing Outlook Web App (OWA) page in Exchange 2013 is easy as compare to other previous versions.

Default OWA login page is regular Blue and White theme.

You will have change few file to make Log In page the way you want it to look.

On Client Access Server you will have to browse the location where all the theme files are store.
C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\owa\auth\15.0.995\themes

Note: Before you make any changes to the existing files, make sure you take a backup of all the files by copying and pasting it some where on the server or on the network.

For this article I am making changes on 2 files which are highlighted olk_logo_white and owa_text_blue

Copy and paste the file and click on replace button once get the pop after pasting the file.

There's one more location you can make the changes. In IIS you can do the same thing.

After making the changes you can login to the owa URL in my case its https://webmail.exchangeranger.net/owa and you should see the new owa login page.

Cheers,
Gulab Prasad

Exchange Server 2010 To 2013 Migration Guide

By Gulab Prasad | Sunday, December 28, 2014 | Exchange Server 2013 2 Comments

Ending my year with Exchange Server 2010 To 2013 Migration Guide. I hope it helps to accomplish your migration project.

Signing out from year 2014. Wish you all very happy and prosperous year 2015.

Cheers,
Gulab Prasad

How to Request and Configure Exchange Server 2013 Certificate

By Gulab Prasad | Thursday, December 11, 2014 | Exchange Server 2013 Leave a comment

I wrote one small guide on "How to Request and Configure Exchange Server 2013 Certificate".
You can download this guide from the below link.

Cheers,

Cannot access LcsCDR or QoEMetricson Monitoring back-end database.Verify that these databases has been deployed, and that access to the Monitoring back-end database is not blocked by firewall.

By Gulab Prasad | Saturday, December 6, 2014 | Lync Server 2013 Leave a comment

While deploying Lync Server 2013 Archiving and Monitoring role, I ran into the below error message.

Check your SQL Server which will be used for Archiving and Monitoring for Lync Server 2013. I found that databases were not created.

Resolution:
Login to your SQL Server and open SQL Server Management Studio and connect to the SQL Server. Create LcsCDR and QoEMetrics database manually.

Rerun the deployment again and it will complete successfully.

Cheers,

How to Install and Configure Exchange 2013 Edge Server

By Gulab Prasad | Saturday, October 11, 2014 | Exchange Server 2013 Leave a comment

It's been long time I wrote any articles, but it's good to be back. In this article we will learn how to install and configure Exchange Server 2013 Edge Transport Role.
LAB environment:

2 Windows Server 2008 R2 Domain Controller
1 Exchange Server 2013 CU5 with Mailbox and CAS Server Role on Windows Server 2012 R2
1 Exchange Server 2013 CU5 Edge Server Role on Windows Server 2012 R2
2 NIC Card, 1 Internal and 1 External

The Edge Transport Server is not an Active Directory domain joined server, but it should have a normal FQDN which should be resolvable from the Internet. In the lab I am using exch03.exchangeranger.net for the server FQDN.

After installing the Windows Server 2012 R2 rename the server as per your requirement and add the Suffix, in my case it's exchangeranger.net

As the Edge Transport server is using the internal DNS servers for name resolution this should not be a problem on the Edge Transport Server, but on the internal network you have to add the Edge Transport server manually to the internal DNS servers. Create Host record in DNS for Edge Server.

First we will have to install prerequisites for Exchange 2013 Edge Transport Server by running the below commands:

Install-WindowsFeature RSAT-ADDS

Install-WindowsFeature ADLDS

Start the installation of Edge Transport Server 2013.

Next part is to make sure that Edge Server is able to ping the Mailbox Server and vise versa.

When I pinged the Mailbox Server from Edge Server it failed.

Make sure you disable the Windows Firewall on both Mailbox and Edge Server.

After disabling the Firewall you can ping the server both way.

Now the next part is to create the Edge Subscription.

To create the Edge Subscription file open the Exchange Management Shell and enter the following command:

New-EdgeSubscription –FileName C:\EdgeSubscription\Edge01.xml

Copy the XML file from Edge Transport to Mailbox Server to a location on the local disk in my case it's C:\EdgeSubscription drive of the Exchange 2013 Mailbox server. To import the XML file open the Exchange Management Shell and enter the following command:

New-EdgeSubscription -FileData ([byte[]]$(Get-Content -Path “C:\EdgeSubscription\Edge01.xml” -Encoding Byte -ReadCount 0)) -Site “Default-First-Site-Name”

Once you are done with Importing XML file on Mailbox Server successfully you need to start the Edge Synchronization, to start it we need run Start-EdgeSynchronization on Mailbox Server.

In the output above you see Result: CouldNotConnect and FailureDetails: The LDAP server is unavailable, don't panic give this process sometime and you will see Result: Success and FailureType: None as shown in below image.

Now it's time to get this newly installed Edge Server to work specifying it in a Smart Host on existing Send Connector on Mailbox Server or creating the new Send Connector all together. We are going to create new Send Connector named Internet.