Re: WSUS interference with OWA

"David Kerber" <ns_dkerber@ns_WarrenRogersAssociates.com> wrote in message
news: t...
>I had installed WSUS on our exchange server, hoping to reduce network
> bandwidth on our smallish (25 machine) internal network. However, I
> discovered that WSUS killed Outlook Web Access operation, and I could
> never figure out why: they use different ports, IIS seemed to be set up
> correctly for each of them, but I could never get it to work. Once I
> removed WSUS, OWA started working again.

It's likely the co-existence of SSL situation. OWA requires SSL.
WSUS requires that SSL be only required for certain virtual directories.
WSUS shares the Default Web Site virtual server with OWA.

Your installation should have placed WSUS on the alternate virtual server
"WSUS Administration". If it did not, then force it to the alternate virtual
server at installation. Based on your comments about "different ports" I'm
assuming that it did.

From there (and this is exactly the same scenario that SBS2003 uses, so we
know it works), you'll need to manually modify the Default Web Site, to
*exclude* SSL requirements on the /selfupdate virtual directory.

Beyond that, WSUS should not interfere with any other functionality on the
Default Web Site unless you've implemented host headers on the Default Web
Site. Both the D.W.S. and WSUS Administration sites need to be assigned the
same host header(s).

--
Lawrence Garvin, M.S., MCITP:EA, MCDBA
Principal/CTO, Onsite Technology Solutions, Houston, Texas
Microsoft MVP - Software Distribution (2005-2009)

MS WSUS Website: http://www.microsoft.com/wsus
My MVP Profile: http://mvp.support.microsoft.com/pro...awrence.Garvin