
	Home > Microsoft Exchange Tips > Exchange Server Administration Tips > Proper patching for both front-end and back-end Exchange Server setups

Exchange Tips:

EMAIL THIS

TIPS & NEWSLETTERS TOPICS

EXCHANGE SERVER ADMINISTRATION TIPS

Proper patching for both front-end and back-end Exchange Server setups

Serdar Yegulalp
06.22.2006
Rating: -4.75- (out of 5)

Exchange Server tips, tutorials and expert advice

Digg This! StumbleUpon Del.icio.us

Outlook Web Access (OWA) works in front-end/back-end Exchange Server deployments, but you need to pay extra attention to maintenance if you're running this setup. This is doubly important for updates and service packs, which should always be applied to front-end servers and back-end servers in synchrony. Otherwise, you could run into OWA performance and availability problems.

If you improperly or inconsistently update your front-end and back-end servers, OWA users may receive a "Loading" message when they try to access their mailboxes from the front-end server -- but no messages will ever actually display, and reloading will not help.

This problem typically arises when the back-end server is updated without the front-end server also being patched. It is also important to note that the proper order of operations is to always upgrade your front-end servers before your back-end servers. See Microsoft TechNet article, Service Packs: Upgrading front-end and back-end servers.

A quick way to bring your front-end and back-end servers into synchrony is to examine the contents of the \Program Files\Exchsrvr\exchweb folder on each of them. Usually, the directory will have a few folders with revision numbers in them, such as 6.5.6944.0 and 6.5.7226.0. The most recent updates are in the highest numbered folders.

You can then copy the folders from the back-end server and paste them into the exchweb folder on the front-end server. If you have more than one front-end server, make sure you do this for all of them....

Digg This!

StumbleUpon

Del.icio.us

RELATED CONTENT

	Outlook Web Access
	Block Web beacons and protect OWA users from spam
	OWA 2007 configuration tricks to boost performance
	Top 5 Exchange ActiveSync tips
	Lock down direct file access and protect OWA users
	Simplify an OWA URL on Windows Server 2008
	Windows Mobile 6.5 touts Internet Explorer, OWA improvements
	When OWA's default configurations aren't good enough
	Digging deeper into Exchange Server 2010
	Troubleshoot 'System Attendant' error messages in OWA
	Troubleshoot Microsoft Outlook Web Access problems

Exchange Server Administration Tips

Remove Exchange 2003 objects from AD to install Exchange 2010

Don'ts for optimal Exchange 2007 mailbox server efficiency

Is your Exchange 2007 hub transport server healthy?

Avoid Outlook 2007 performance issues during repairs

Developing an Exchange 2007 server role DR plan

How DSAccess service improves Exchange Server 2007 reliability

An introduction to the Exchange Remote Connectivity Analyzer tool

Monitor Exchange 2007 with disk- and RPC-related counters

DPM 2007 replica inconsistencies in Exchange databases

Track Exchange 2007 mailbox server health using database counters

Outlook and Outlook Web Access Tips

Block Web beacons and protect OWA users from spam

Outlook 2007 shut-down problems and fixes

OWA 2007 configuration tricks to boost performance

Pros and cons of Outlook 2007's storage engine redesign

Lock down direct file access and protect OWA users

Simplify an OWA URL on Windows Server 2008

Windows Mobile 6.5 touts Internet Explorer, OWA improvements

Custom error message redirects OWA users

When OWA's default configurations aren't good enough

Save time typing Outlook 2007 messages with Quick Parts

RELATED RESOURCES

2020software.com, trial software downloads for accounting software, ERP software, CRM software and business software systems

Search Bitpipe.com for the latest white papers and business webcasts

Whatis.com, the online computer dictionary

(You do not need to restart Exchange Server when you're done.)

The best long-term solution is, of course, to patch both machines, but the above workaround is useful if you want to get things working without going through the downtime required to patch Exchange Server.

About the author: Serdar Yegulalp is editor of the Windows Power Users Newsletter.

Do you have comments on this tip? Let us know.

Related information from SearchExchange.com:

Tutorial: How to set up a front-end Exchange Server cluster

Expert Advice: Deciding between a front-end and back-end Exchange server

FAQ: Outlook Web Access administration

Learning Center: Troubleshooting Outlook Web Access

Reference Center: Outlook Web Access tips and resources

Please let others know how useful this tip is via the rating scale below. Do you have a useful Lotus Notes, Domino, Workplace or WebSphere tip or code snippet to share? Submit it to our tip contest and you could win a prize.

Rate this Tip

To rate tips, you must be a member of SearchExchange.com.
Register now to start rating these tips. Log in if you are already a member.

Submit a Tip

DISCLAIMER: Our Tips Exchange is a forum for you to share technical advice and expertise with your peers and to learn from other enterprise IT professionals. TechTarget provides the infrastructure to facilitate this sharing of information. However, we cannot guarantee the accuracy or validity of the material submitted. You agree that your use of the Ask The Expert services and your reliance on any questions, answers, information or other materials received through this Web site is at your own risk.

Email Server Solutions: Exchange 2007, Exchange 2003, Exchange 2000, SharePoint

SEARCH

TechTarget provides technology professionals with the information they need to perform their jobs - from developing strategy, to making cost-effective purchase decisions and managing their organizations' technology projects - with its network of technology-specific websites, events and online magazines.


TechTarget Corporate Web Site \| Media Kits \| Site Map All Rights Reserved, Copyright 2004 - 2009, TechTarget \| Read our Privacy Policy