Moving from Apache to IIS

[lovelldr]

Hi guys.

I've just installed a new server at a school, and the server previously used Apache to host a web site, written with PHP and MySQL. Now, the server is using Exchange Server and they want Web Access for Exchange server, so IIS has been set up on the server.

I was wondering whether it was worth using IIS as the main web server and basically host the files through that, or whether to re-install apache and run it through there and just have the IIS installation on a non-standard port for the email. What would your recommendations be?

Another thing which I'm not too sure about, is how easy it is to integrate MySQL and PHP into IIS? With Apache, I know it is a doddle, as I have done it many times. But with IIS is it a different kettle of fish?

Also, would there be much of an impact on the server running IIS, Apache, MySQL, PHP, Exchange? Or would Apache be a minimal impact on the server?

Feedback much appreciated guys

[webman]

PHP performance in IIS sucks. I'd use apache and a reverse proxy configuration for the OWA.

[Geoff]

Exchange doesn't like sharing servers either.

[lovelldr]

PHP performance in IIS sucks. I'd use apache and a reverse proxy configuration for the OWA.

Hmm, I have no idea about wth that is, and how to set it up. Had a quick looksie on google, but couldn't find much info...

You able to pass some links/info my way pls?

Would it be worth doing this reverse proxy? Or would I be better offer just setting the web on "www.thisserver.co.uk" and the owa on "www.thisserver.co.uk:923/owa" or something along those lines?

Cheers

[webman]

There's some information here.

You could go the different port method, but like Geoff said, Exchange doesn't like sharing things in the first place so it's worth testing it first. Also, if somebody wants access OWA from somewhere on a restrictive firewall/proxy that only permits port 80 outbound - they're screwed.

[ChrisH]

Ive got a few things on my exchange box. It's not ideal but it works fine.

[lovelldr]

There's some information here.

You could go the different port method, but like Geoff said, Exchange doesn't like sharing things in the first place so it's worth testing it first. Also, if somebody wants access OWA from somewhere on a restrictive firewall/proxy that only permits port 80 outbound - they're screwed.

lol, that's gone right over my head looking at that. I could probably get to grips with it if I sat down and read through it more and at other stuff to do with it, but I think I might just go the other port route, and see how that goes...

[Joedetic]

I know someone that's run a reverse proxy from apache so that their exchange installation was available to the web via apache.

So you still have it running on IIS but then you setup apache with the reverse proxy so that there's a vhost of exchange.domain.tld/exchange is pointing to the IIS installation that is running on a different port of the same server or something like that.

Just an idea.