In June 27, Microsoft released VirtualMachineAdditionsforVistaBeta2. After installing VirtualMachineAdditionsforVistaBeta2 on VirutalServer2005R2SP1Beta1, I can finally play iis7. Before VMAdditions is installed, my LonghornServerBeta2 Virtual Machine always uses forWindows200.
In June 27, Microsoft released Virtual Machine Additions for Vista Beta 2. After installing it on Virutal Server 2005 R2 SP1 Beta 1, I can finally play with IIS 7. Before installing this version of VM Additions, my Longhorn Server Beta 2 virtual machine was always using for Windows 200
In June 27, Microsoft released Virtual Machine Additions for Vista Beta 2. After installing it on Virutal Server 2005 R2 SP1 Beta 1, I can finally play with IIS 7. Before installing this version of VM Additions, my Longhorn Server Beta 2 virtual machine was always using the VM Additions for Windows 2003, which was never too slow. After this version is installed, when the Longhorn Server Beta 2 virtual machine is allocated 480 MB of memory, the speed is very fast and it feels great! So I finally started my journey to IIS 7.
As a PHP player, after IIS 7 is available, the first idea is to install PHP on IIS 7. The following is a diagram of all my installation processes.
First, install IIS 7. I have installed all the features of IIS 7, but I am not going to introduce these features in this article, or it will be too far away. After installation, PHP 5 for Windows's Binary zip package. Decompress it to the C:/PHP Directory, and copy a copy of php. ini-dist and rename it php. ini. Next, choose my computer> Properties> advanced system Settings> environment variables, and add the PATH for the executable files and the phprc path for php. ini ):
Next, configure IIS 7. The following figure shows the Starting Screen after IIS 7 is started. It looks cool:
You can configure a site or the whole server. Of course, the configuration of the whole server may be more convenient in the future, such as creating a site, PHP can be supported, which is very suitable for virtual hosts, so here we configure the entire server. Therefore, first select the server to be configured. The default value is of course your local server. You will see that after the selection, the picture on the right is completely different from that on IIS 6:
Selecting the feature you are looking for from this entire property page is of course quite eye-catching. Therefore, you can select the feature by range (Areas) and category (Categories. Here we need to configure ISAPI and CGI Restrictions, which can be found in the Security category of IIS scope:
Under all installation conditions, the ISAPI and CGI Restrictions page contains ASP and ASP. NET by default:
Select New Restriction… In the rightmost task... To create a Restriction for PHP. The content to be filled in:
Next we can create an application pool for the PHP program:
Add a default index. php document After configuring the default document:
Next, configure the Handler ings option in the Server Components category in the IIS range:
This step is the most important. Here, we want to add a Script Map, the content to be filled in:
After this step is configured, PHP can run. You do not need to configure ISAPI Filters or restart the IIS server. You can create an index directly in the C:/inetpub/wwwroot directory. php, the content is to execute a phpinfo () function, and then input http: // localhost in the browser. If you see it, the configuration is successful:
After installing PHP, the next step is to install an accelerator for it. I usually use Zend Optimizer, because it is best to configure it. You can download it from here: ZendOptimizer-3.0.1-Windows-i386.exe.
During the installation process, we will find that Zend Optimizer can identify IIS 7, which is really amazing:
After the installation is complete, refresh the page and at a location at the bottom of the page, you will find that Zend Optimizer has been started:
Next, we should configure the directory for saving the Session. Otherwise, the Session may not work properly.
First, create a folder for the Session file. Here we take the C:/PHP/sessions directory as an example. After the folder is created, assign permissions to it. here we need to grant the IIS_IUSRS user group full control permissions, IIS_IUSRS user group should be the newly added user group in IIS 7. In earlier versions, I have never seen it:
Then, add the path to php. ini. Remove the semicolon before session. save_path:
Refresh the http: // localhost page again. If you see that the session. save_path item is the directory you configured, this will be successful:
To further confirm that the Session is available, you can directly install a program with a Session. Here I chose PHPRPC. After execution, we can see C: the/PHP/sessions directory contains the session file.
Now, even if this step is complete, you can enable other extensions in php. ini! That's simple. However, to modify php. ini, you still need to restart the IIS server to make the modification take effect.