RE: OWA not displaying properly after upgrade- E2K to E2K3

I get to answer my own post...

It was a permissions issue. I had used IIS Lockdown (urlscan is part of IIS
lockdown?) on the Win2K/Exchange 2K installation. IIS Lockdown adds the Iwam
and Iusr accounts to a group named Web Anonymous Users. Removing the Iusr
account from the Anonymous Users group fixed the problem.

A bit of reading on IIS Lockdown tool:
http://www.iisanswers.com/articles/IIS_Lockdown/IISLockdown.htm

I am guessing that the reason I had this particular issue was because of the
way I upgraded (i.e. Exchange 2K to Exchange 2k3, then Win2k to Win2k3)? I
could not find a KB article that addressed problems with an upgrade after IIS
Lockdown had been used on a Win2k box. Can anyone point me to one that
addresses this issue?

--
Ken Rappold


"Ken Rappold" wrote:

> Kinda long post...
>
> Upgraded exchange 2k on win2k sp4 box (single box, one location, one domain,
> one forest). Applied E2k3 sp1, then upgraded win2k sp4 to win2k3.
> Everything appears to work fine except OWA. IE 6 displays OWA with only some
> text and placemarkers for graphics. No background, no graphics, no buttons
> to press, no messages displayed. OWA doesn't work.
> I've searched and performed the applicable tasks from the following KB items
> (I've done more, I just don't remember them all):
> http://support.microsoft.com/?kbid=280823
> http://support.microsoft.com/?kbid=821898
> http://support.microsoft.com/?kbid=883380
>
> I did have this issue from KB280823: "Your Exchange computer was upgraded
> from Microsoft Windows Server 2000 to Microsoft Windows Server 2003 and
> URLScan was installed and configured before the upgrade. URLScan is not
> required for IIS 6.0 and can cause problems that are consistent with these
> symptoms. URLScan 2.5 is the only version that Microsoft supports for use
> with IIS 6.0." I uninstalled URLScan but it had no affect. I've tried
> reinstalling URLScan 2.5 and uninstalling it, no difference.
>
> I've recreated all of the Exchange virtual directories and verified NTFS
> permissions as well as IIS permissions following every KB article I could
> find.
>
> I feel it's a premissions issue because the OWA page is there, but is not
> functional because it doesn't display properly.
> Any help would be appreciated.
>
> --
> Ken Rappold
.