OWA Not on an Exchange Server

In my experience you need to install IIS on the Exchange server and install IIS on a separate box. Make the IIS on the second box secondary IIS server by creating an alias on on the primary to point at the secondary. This way the secondary IIS server takes all the throtting and answer all the client requests via OWA.

Yes it is possible and I also recommend it..Just set up a server and put iis 4 or 5 on it and then run the exchange setup and do a custom setup. Select just owa to install and that will just install the owa components. You also will want to load theexchange service packs even though you are just loading the owa component. If you are going to load owa on a 2000 server, there are a couple of issues in installing owa, but they are documented in microsofts web site.

I am assuming that you are using Ex 5.5 - generally I would say that depending on the size of your user base it is better to set OWA up on a seperate IIS box.
Main reasons for this being that in OWA 5.5 each user session is a CDO MAPI session held in memory - which is a load you don't need on your Exchange server.
All you need to do is put the Exchange disk in the IIS server and choose a custom install - deselect everything apart from IIS and then just follow the onscreen prompts. - There is a good OWA white paper on the Microsoft 5.5 site for firwall configurations.

Exchange 2000 can do accomplish your ideal situation. The OWA is a front-end server that can be located in a DMZ and the actual 2000 Exchange server is the back-end server. Do a search on Microsoft's website for a document called E2KFBTop.doc. This goes into detail about front-end back-end scenarios. An excerpt from the document:
The front-end and back-end server topology is recommended for multiple-server organizations that use Microsoft Outlook Web Access (HTTP), POP, or IMAP and for organizations that want to provide HTTP, POP, or IMAP access to their employees over the Internet. After receiving a request, the front-end server uses Lightweight Directory Access Protocol (LDAP) to query the Windows 2000 Active Directory? directory service and determine which back-end server holds the requested resource.
Note: A front-end server is a specially configured server running Exchange 2000. A back-end server is a server with a standard configuration running Exchange 2000. There is no configuration option to designate a server as a back-end server. The term ?back-end server? refers to all servers in an organization that are not front-end servers after a front-end server is introduced into the organization.

This question was closed by the author