Home > Ask the Microsoft Exchange Experts > Richard Luckett: Spam and Security Questions & Answers > Using certificates with Outlook Web Access
Ask The Exchange Expert: Questions & Answers
EMAIL THIS

Using certificates with Outlook Web Access

Richard Luckett EXPERT RESPONSE FROM: Richard Luckett

Pose a Question
Other Exchange Categories
Meet all Exchange Experts
Become an Expert for this site


Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


>
QUESTION POSED ON: 02 March 2005
I have a small company with two sites; each one has an Exchange 2000 server. Is it possible to get Outlook Web Access working for both servers using a single SSL certificate without a "front-end server," which would mean additional hardware and licensing costs?

It's a Windows 2000 single forest domain and all users have e-mail addresses of username@companyname.com. Apparently, this was doable with Exchange 5.5, but not with Exchange 2000. I installed a certificate on the "master" Exchange 2000 server and it works fine, but users whose mailboxes reside on the second server can't use it.



Digg This!    StumbleUpon Toolbar StumbleUpon    Bookmark with Delicious Del.icio.us   


RELATED CONTENT
Richard Luckett: Spam and Security
How effective is tracking the IP address of an email hacker?
Why can't I grant users permissions to an Exchange public folder?
How can I configure Exchange IMF to allow an IP address or DNS?
Tool helps identify inbound Exchange Server email flow issues
Configure SMTP relay restrictions in Exchange Server 2003 to stop spam
How to lock down an SMTP relay to prevent spam in Exchange Server 2003
Connecting an Apple iPhone to Exchange Server on Windows SBS 2003
Why does a security alert pop up when accessing Outlook Web Access?
Exchange email sent to a domain using SPF authentication is returned
Selectively set email permissions for Exchange groups

Outlook Web Access
Troubleshoot 'System Attendant' error messages in OWA
Troubleshoot Microsoft Outlook Web Access problems
Detecting update rollup and patch failures in OWA
Troubleshoot IIS metabase corruption in Outlook Web Access
Fix 'Service unavailable' errors and other common OWA login problems
Troubleshooting Microsoft Outlook Web Access logon issues
Tools to report on Outlook Mobile Access usage
Outlook Web Access issues after an Exchange 2003 migration
Top 5 Outlook Web Access (OWA) tips of 2008
Troubleshooting Outlook Web Access issues on a 64-bit system

Microsoft Exchange Server Hardware Management
Microsoft Exchange Server virtualization tutorial
Troubleshooting a 64-bit Exchange Server 2007 installation
How to move Exchange 2000 to new server hardware
Considerations for virtualizing Exchange 2007 mailbox servers
Can't create mailboxes after virtualizing Microsoft Exchange Server
How to virtualize Exchange Server 2003
Three hardware don'ts when optimizing Exchange Server performance
How Microsoft's new support policy for virtualized Exchange will affect you
Why too much memory can hurt Exchange Server 2007 performance
Virtualizing Exchange Server 2007 with Microsoft's Hyper-V
Microsoft Exchange Server Hardware Management Research

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


What you have described is by design. As you have determined, without a front-end server, you can not centralize the SSL access to all mailboxes. It is a give and take scenario.

There are two pieces of good news I can give you. One is that certificates for your Exchange servers do not have to cost a fortune. You can shop around for cheaper third-party certificate authorities (CA), or you can even configure one of your existing servers in your domain as a Windows CA. The other good news is that the Standard Edition of Exchange Server 2003 can be used as front-end servers. This is significantly cheaper then the Enterprise Edition that we were required to use with Exchange 2000 Server. And, front-end server hardware generally does not cost nearly has much as back-end servers, because there are virtually no disk storage requirements beyond the OS and the Exchange application. Finally, Exchange 2003 front-end servers are backwards compatible with Exchange 2000 back-end servers.

Do you have comments on this Ask the Expert question and response? Let us know.




Search and Browse the Expert Answer Center
Search and browse more than 25,000 question and answer pairs from more than 250 TechTarget industry experts.
Browse our Expert Advice



Outlook Web Access (OWA) Tips and Advice
HomeNewsTopicsITKnowledge ExchangeTipsAsk the ExpertsMultimediaWhite PapersIT Downloads
About Us  |  Contact Us  |  For Advertisers  |  For Business Partners  |  Site Index  |  RSS
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 		  TechTarget - The IT Media ROI Experts