Exchange 2007 Sp1 Installation Killed My Webservice

[Brotschaden]

Heyho,

 

Today I installed Exchange Server 2007 SP1 for the first time on my Windows Server 2008 R2. The installation went fine (with Vista SP2 compatibility mode), but suddenly my coworkers complained that my website was unreachable. What a mess.

 

Suddenly I got a nasty http:500 error that some plugin for my OWA service was unable to load instead of my homepage. I was pretty much angry, because Exchange installed all those webservice without asking me in critical regions. I deinstalled my exchange server and had to make a new IIS entry for my website on my server, because I was not able to rescue my old set up (which was build on the default IIS entry).

 

Okay some data about my network:

Windows Server 2008 which runs DHCP, is the Active Directory Domain Controller, is a IIS webserver, DNS and routs the inner network. A lot of tasks for a server, but that's okay, because it's a extremly small firm with 3 laptops and two printers to manage.

 

I would like to know from you a way to make the Exchange Server and the website cooperate on one server without virtualisation. I just don't want the exchange server to stand in the way of my webservice.

 

I have a domain URL which points to my ip. So you can reach over http://MY IP ADRESS/ the main.html of my website.

 

Thanks in advice!

[gchq]

Have never used or set-up MS Exchange - but have many Lotus Notes Domino applications running with IIS (from 5 to 7). The trick is to change the default http address (Notes in my case, MS Exhange in yours) from the default (80) to some other not in use port (like 84), and https 443 to say 446

 

Your IIS web service will run without any problems, and if MS has web admin/email (like Notes) then users can access it by typing http://YourDomain.com:84 or https://YourDomain.com:446