Guy Recommends
Beat spammers with anti-spam software for Exchange
Server – GFI MailEssentials.
Download FREE
trial
Introduction to Exchange 2003 HTTPMon
HTTPMon has been around for a while. This pages explains how to setup and install HTTPMon. Get your copy from the Windows Server Resource Kit.
Topics
for Exchange 2003 HTTPMon
HTTPMon is not a pure Exchange 2003 utility. In fact HTTPMon's main job is to target IIS's Web sites. The link is that Exchange uses IIS, particularly for OWA (Outlook Web Access).
The most likely reason for installing HTTPMon is to troubleshoot problems with OWA, particularly with a network load balancing a cluster.
- Real-time - A service which samples in real-time
- Reporting Server - Gathers data from monitor servers and loads it into SQL Server
- Client Monitor - Outputs to a set of Web pages that displays the results from the SQL Server database
 Exchange Server 2007 is a complex topic, do you need practical hands on training? As an MCT trainer, I can thoroughly recommend
TrainSignal. In particular, I like the way
that TrainSignal cover all learning methods, instructor lead, video and of course text
material. You can either take one module, for example Exchange 2007 or go for a combination of modules.
Learn more about Microsoft Exchange Server 2007 here
HTTPMon is setup from the \apps\httpmon folder of the Windows (not Exchange) Server Resource Kit. Next HTTPMon is a bit quirky, you run the Configuration Manager to configure the service.
The information to add is the name of your Exchange Organization, and the OWA servers that you wish to monitor.
I have never got any joy from HTTPMon, perhaps I should have persevered,
perhaps I should have got it 'hooked up' to SQL. Another reason I have not got the best out of HTTPMon is that I have not tested it in a NLB cluster.
If you have had great success with HTTPMon, write in and I will publish your information here. Meanwhile I put HTTPMon in that category yes I have seen it, but not for me. (Not every tool
can be fantastic! I feel that I am allowed to dismiss one utility as mediocre)
Mission to configure HTTPMon to check connections in a NLB (Network Load Balancing Cluster).
Stage 1 - Setting up Monitoring with HTTPMon
1. Right-click Global Settings, and then click Properties.
2. Under Source Server Computername, and the name of your NLB_Cluster.
3.
EnableSingleIP, click TRUE, Stage 2 - Adding a Cluster to HTTPMon
1. Right-click Web Clusters, click Add cluster 2. click the Cluster tab. Under Cluster name, type NLB_Cluster.
3. In the Single IP Settings section, Configure Virtual IP: Virtual IP
Port: 2504
Password: password
Waterlevel: leave this field blank Stage 3 Adding your Servers to the Cluster
1. On the Web Clusters dialog box, right-click NLB_Cluster, click Add Server..., and then click the Server tab.
2. For Server name, type YourServerName, and then under Accessed by, enter the
following values, and then click OK:
IP Address: YourServerName's Dedicated Network card
Host Name: YourServerName's host name.
NOTE: The Host Name field relies DNS
3. Repeat for each
server in your NLB_cluster.
HTTPMon may not be the most exiting tool in the Windows Resource Kit, however it may be your answer for troubleshooting OWA in a NLB cluster.
Download your Exchange 2003 Migration eBook for only $6.25
 The
extra features you get in your eBook include: 20 checklists to
plan your migration. Detailed instructions and advice on the best
strategy for your organization.
Lots of tips, recommendations and troubleshooting advice. Problem
solving section. Active Directory explained. Printer friendly
pages.
See Also
| 
