What are the limitations of running Expression Engine on an IIS server? This would of course be assuming that it was running PHP and mySQL. So for example, do captchas work? email notifications? etc.
This is an archived forum and the content is probably no longer relevant, but is provided here for posterity.
The active forums are here.
November 15, 2007 2:57pm
Subscribe [0]#1 / Nov 15, 2007 2:57pm
What are the limitations of running Expression Engine on an IIS server? This would of course be assuming that it was running PHP and mySQL. So for example, do captchas work? email notifications? etc.
#2 / Nov 15, 2007 3:37pm
The only universal thing I’ve seen is that force query strings must be on.
The rest, however, is all reliant on the server being set up correctly. Permissions can be difficult since those can’t seem to be set by FTP, but only by an administrator.
You can always run the server check wizard =)
#3 / Nov 15, 2007 4:51pm
Is it still possible to remove the index.php? on a Windows server? I know nothing about Windows based servers, but have a client that needs an install on one.
#4 / Nov 15, 2007 4:55pm
Ah, that depends on if ISAPI is available. There’s information in the wiki on that; but it’s not as easy, I believe.
#5 / Nov 16, 2007 11:09am
Not specific limitations regarding features, but I figured this might be helpful. We installed EE on a shared Windows host - web.com (formerly Interland) - and it ran SUPER slow. Now, I suspect this had more to do with the host server configuration, RAM allotment, etc. than anything with EE. We moved this exact same site over to a new host running Linux and it ran perfectly - just as fast as the many other EE sites we have running on Linux hosts. From then on, we strongly recommend to all our clients to go with a Linux box for their EE sites.
#6 / Nov 16, 2007 12:19pm
yea, so do i. it’s just this oe particular client. i hate windows servers!
#7 / Nov 16, 2007 1:20pm
The only universal thing I’ve seen is that force query strings must be on.
I use IIS and have this set as no.
I don’t think there are any limitations with EE due to IIS. I’ve seen it run both fast and slow, so it’s probably like anything else: just depends on server config, and what else is running.
#8 / Nov 17, 2007 12:02am
We are redoing our company site and originally had EE on an IIS server and it just wasn’t working out. removing index.php wasn’t working correctly and for some reason the permissions were not working right. Moved to Apache and all is fine now. 😊
#9 / Nov 17, 2007 12:19pm
The only universal thing I’ve seen is that force query strings must be on.
The rest, however, is all reliant on the server being set up correctly. Permissions can be difficult since those can’t seem to be set by FTP, but only by an administrator.
You can always run the server check wizard =)
In case you didn’t know turning on force query string is no big deal because it is in the EE control panel.
If you would be on a host where you don’t have a control panel to set permissions, that could be a big problem.
I used to use a host where that was a support ticket issue, sucked to be me.
Is the Windows host admin knowledgeable, that’s going to make all the difference.