Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.
By luckysmack on
I was unable to find any information on this elsewhere, But i have a site with a decent amount of users on it. But the company is switching from an Apache server to an IIS server. both have (will have) the most recent versions of PHP and MySQL. I want to know if there is anything that has to be prepared. we will be making the switch within 2 - 3 weeks
Comments
I don't consider myself an
I don't consider myself an expert in this, but for sure you will need to deal with:
impacting clean urls. See here and here, for example.
--
Joe Kyle
--jjkd--
I would switch hosting
I would switch hosting companies, besides the list above you lose cron and depending on the hosting company abilityto set/change diirectory permission.
the site is still pretty
the site is still pretty fresh. but nonetheless some are still using the live site. If i started over and reinstalled from scratch would be more of a pain in the @ss than impossible.
As with hosting companies the site is on a local intranet server with no direct web access. I have to update manually for all the mods (i have a seperate version running on a seperate local testing server that has net access to update, but when i upload the changes to the intranet server, that doesnt have the net access.
I can deal with the clean urls but what about the .htaccess? how will that change? i dont believe i have any mods that have an individual .htaccess. so when transferred is it just not used or do I set that up seperatley/differently. Im not very familiar with IIS yet (they just told me today about the switch to IIS).
...
No clean URLs. And setting up PHP on IIS is a serious pain. Once you get it working it works fine, but the setup is touchy. In all probability all your URLs will now be sample.com/index.php?q=node/1
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide
What about running both
What about running both simultaneously? Keep apache for your drupal site and use IIS for your other stuff (I'm guessing ASP.NET?) Either have separate machines and addresses for them (if it's an intranet why not?) Or have if you don't mind specifying a port have them both on the same machine and listen on different ports. Or use apache as the front end reverse proxy and serve requests from apache or forward to IIS depending on the address.
You can run Both?
Wel currently im not the server guy at the company. Im not sure how to do that honestly. But i can email a link to this thread to him and he can take care of it. I didnt even realize you could do both at once. Im trying to convince him to stay with apache but its a corporate thing (BS and red tape) so good luck there. But either way i will be able to get it up. Its just a little dissapointing not being able to use clean urls since it is a community based intranet. All of the members will be able to post thier own information to the site (almost like a think tank in a way) and others will be able to comment and add to a given node. Which is why i wanted clean urls so searching is easier and for people who would already know the exact address of a page and could just type it in. But somewhere somebody (different post) said clean urls is possible with IIS so im trying to find that post and look more into it. I apparently didnt bookmark it. I need to reinstall delicious in my firefox (just installed FF3 beta, gotta re-download the addons).
....
Well, technically it is possible. Just not a good idea. They will have to assign a second IP Address. Setup and configure Apache, then Setup and configure IIS. Make sure Apache is OFF when they configure IIS. Set the httpd.conf for one IP Address and make sure it works. Setup Apache and assign it it's separate IP Address.
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide -|- Black Mountain
-Steven Peck
---------
Test site, always start with a test site.
Drupal Best Practices Guide