...or you could just keep your OWA 5.5 box in place, serving up OWA 5.5-style ASP pages as it's always done. There's a whitepaper on Frontend/Backend configuration you'll want to read: http://www.microsoft.com/Exchange/techinfo/deployment/2000/e2kfrontback. asp
> -----Original Message----- > From: Andrew Chan [mailto:[EMAIL PROTECTED]] > Posted At: Monday, November 12, 2001 12:20 AM > Posted To: MSExchange Mailing List > Conversation: OWA on Exchange 2000 > Subject: RE: OWA on Exchange 2000 > > > That is true. In order to put OWA on a separate machine that doesn't > host your mailboxes, you still have to install E2K on that > box (which is > not required in E5.5) and mark that box as FrontEnd Server. > There has > been extensive discussions in recent past on the list. You > should find > many helpful suggestions if you do a little more digging on the list's > archive. > > > Andrew, > MCSE (NT + W2K) + CCNA > > > -----Original Message----- > From: Andy Haigh [mailto:[EMAIL PROTECTED]] > Posted At: Sunday, November 11, 2001 10:18 PM > Posted To: NewsgroupDiscussion > Conversation: OWA on Exchange 2000 > Subject: OWA on Exchange 2000 > > We are looking at upgrading to E2K and currently have OWA > setup on a web > server seperate to our Exchange Server 5.5 machine. One of my > technical > guys > after researching this has said that this configuration is > not possible > in a > E2K enviroment. Is this true. Surely you can have a scenario where web > part > is in the DMZ and the actual exchange server is on the inside network, > although I do realise that OWA is more integrated in E2K but I would > have > thought the web part would be transportable. > > Thanks > > Andy > _________________________________________________________________ List posting FAQ: http://www.swinc.com/resource/exch_faq.htm Archives: http://www.swynk.com/sitesearch/search.asp To unsubscribe: mailto:[EMAIL PROTECTED] Exchange List admin: [EMAIL PROTECTED]
