I have a front end server running Win2k3, IIS 6.0, and OWA in which the defa
ult website quit working. I had to create a new website on this server and r
estore from backup the virtual directories in order to get OWA working again
. Now the http virtual server won't start on this server in ESM, access to O
WA works fine.The http exchange virtual server on the back end cluster is st
arted and running ok. Being that the default http virtual server for the fro
nt end is crippled because it's attached to the default website, will creati
ng a new http virtual server work with the new website or does any http virt
ual server created still revert to the default website? I'm looking for the 
best way to A) either somehow get the default website working again so that 
it and the default http virtual server will actually start and outlook web a
ccess can be accessed from there (I'm thinking now that maybe the virtual di
rectories were the problem and that maybe if I restore them from the new web
site to the default website maybe it will start again) or B) create a new "h
ttp virtual server" in Exchange System Manager under administrative groups, 
protocols, http and see if it will point to the new website I created that i
s working now with OWA. I'd like to do this without bringing down OWA as it 
is working. 

The reason I need to do this is we'll be installing RPC over Http and forms 
based authentication and the http virtual server has to be running on both t
he front end and back end servers.

Any help with this will be greatly appreciated,
Thanks,

[ Post a follow-up to this message ]