(My experience with PHP under IIS)
I believe that you should configure PHP as a FastCGI module - I do not think that you can configure PHP as an ISAPI extension. You can configure PHP either using FastCGI or from ISAPI - ISAPI may be faster than FastCGI. There is a guide to configure IIS using ISAPI:
A google search shows many pages discussing the issue of safe vs vs stream, which does not require a stream argument if you want to know the details, however the short version is that the non-streaming safe version is faster, but the thread-safe version is more is safe. You should choose the version with streaming security at the moment , if you do not have a performance problem, and be aware that your application will work correctly in unsafe binary files.
Finally, there is no need for x64 binaries when running PHP as a FastCGI application - php works as a separate process, so x86 binaries will work fine on the x64 web server, and most ordinary php applications will have no need for the address space above 4 GB, as IIS scaling can simply trigger additional php processes.
When setting up the FastCGI extension, you need to specify it in the php-cgi.exe executable file in the php-cgi.exe installation directory.
Justin
source share