I’ve just got myself an evaluation copy of Windows 2008 Server out of curiosity. I’ve installed it on VMware Workstation 6 running on a Windows Vista computer. While a virtualized Windows 2008 Server is a sucker on resource, it’s performance is still acceptable for those who just want to try it out like me.
Let’s see how to install PHP5 and MySQL5.1 on Windows 2008 Server.
IIS 7 is now a server role in Windows 2008 Server as opposed to previous versions of Windows Server (2000 and 2003) where IIS was installed as a component.
To add the IIS7 server role, launch the Server Manager: Start => Programs => Administrative Tools => Server Manager
Right-click on Role from the left panel and select Add Roles from the contextual menu. From the Add Roles Wizard, check the Web Server (IIS 7) checkbox. Click on Next until the Roles Services screen.

Here are the options I’ve selected:
Click on Next again and then on Install. When the installation is completed, you can now access your new IIS 7 web server.

Stay tuned as I’ll post how to install PHP5 and MySQL Server 5.1 on Windows 2008.
Posted in IIS · MySQL · PHP · Tutorials · Virtualization · Windows Server | 3 Comments
3 responses so far ↓
1. Response by : WordPress on Server 2008 « Everything I write on Mar 14, 2008 at 10:05 pm
[...] WordPress on Server 2008 15 03 2008 After spending way to much time on my dilemma, I was finally able to install WordPress on Windows Server 2008. I spent a lot of time searching the Internet and despite all the tutorials out there, none of them helped except one fluke web site which happened to work. First I will tell you do not attempt to use isapi but instead use fastcgi. The tutorial I found is located at thewebhostinghero.com. [...]
2. Response by : How To Install IIS 7, PHP5 and MySQL 5.1 on Windows Server 2008 - Part 2 on Sep 25, 2008 at 8:06 am
[...] 12th, 2008 · 18 Comments Following up on my last post, I’ve now got a working IIS 7 web server running on Windows 2008. We’re now going to [...]
3. Response by : George Gruber on Apr 6, 2009 at 12:59 am
I would like to point out that FastCGI, as profound as it may seem, has some limitations. I had inadvertently inserted a UNICODE character at the end of the first line of an included .php5 file. I knew what the problem was but the character was represented in such a way that it was very difficult to see. I had been configured and running PHP using FastCGI as outlined (and it did work) but it produced no HTML output whatsoever. It took me a couple of hours to find it. I reconfigured IIS to use the ISAPI interface with the same error and not only did it throw an error message but it also rendered the page (albeit with an error message). Had I been using ISAPI all along, I would have seen the error, had the line number identified and fixed in about 30 seconds. As it was, I only had a blank browser window to work from. If you have ever had a working web site all of a sudden reduced to absolutely no output, you would understand that your heart just stops and you think WTF?
IMHO, if you are using PHP and MySQL, the thread safe issue isn’t an issue. Perhaps a good compromise is use FastCGI on production and ISAPI on development servers. It doesn’t mean that there aren’t bugs that would crop up on the production server but 99% will be dealt with in an environment that is kinder to the programmer.
Leave a Comment