Archive for the 'microsoft' Category
How to install php 4.4.1 on iis 6.0
Although this is not as common as installing it on a *nx machine (since I personally use freebsd and linux, im not going to play favorites), there are still a great deal of people out there that for one reason or another, would like to php scripts on a windows 2003 box (the company I worked for would not allow us to run anything but windows machines).
Steps for installing php 4.4.1 on a windows 2003 machine
note: These instructions are for iis 6.0
Step 1: Download php 4.4.1 (get the binary package, not the installer)
Step 2: Extract the .zip file you just downloaded (I usually extract it to the c drive and rename it php, but the name can be anything).
Step 3: Launch the iis (internet information services) manager
Step 4: Click on “web service Extensions” on the left and right-click on the right and pane and go to “add a new web service extension”. There should now be a new window on the screen. for “extention name” use “.php”. Click the add button on the right, and point it to c:\(the php directory from step 2)\sapi\php4isapi.dll. After this is done, check the box that says “set extension status to allowed” and click ok.
Step 5:
a) right-click “web sites” and go to properties.
b) click on the tab “home directory”
c) where it says “execute persmissions” it should state: “scripts and executables”
d) click the “configuration…” button
e) click the “add…” button
f) for executable, use the same one from step 4 (php4isapi.dll).
The extensions should be .php.
Step 6: copy php.ini to c:\windows and php4ts.dll,php4ts.lib to c:\windows\system32
Testing your new installation:
I usually create a file called “info.php” with the following:
If everything has been installed properly, when you go to “info.php”, you should see an information page about php 4.4.1
Successfully Backing up and Restoring IIS 6.0
There comes a time in every system administrator’s life when they must face a harsh reality. Your company’s webserver has had a major harddrive failure and it needs to be running again as quickly as possible because in the business world, time=money.
After personally going through the above scenario a dozen times, I scoured the Internet to
find the best solution for backing up and restoring all of my company’s websites. Microsoft provides a few solutions within their knowlege base, but most require you to restore it on the exact system (hardware) where it was backed up.
I came up with a solution that is fairly simple to execute and is hardware independent.
Disclaimer: I have tried the following and it has worked successfully for me, but use it at your own risk. I am not responsible for any damage you may cause from following this procedure.
Steps for backing up (These steps will be done on the original server)
Step 1: Download and Install the iis 6.0 resource kit (link here)
Step 2: We are first going to backup the metabase files for your server. This is a sort of internal registry designed specifically for IIS.
A) Launch the program called “Metabase Explorer” that came with the resource kit
B) Two items can be seen on the left-hand pane. “Lm” and “Schema”. Both of these need to be saved. To do this, right-click on each one individually and then go to “export to file”. To make it easier for restoring, I prefer to use the exact names of each key: “Lm.mbk” and “Schema.mbk”. If you don’t use this naming convention, just remember the file that is associated with the proper key.
C) Now, the actual websites can be backed up. There is nothing special that needs to be done here. The entire website directory just needs to be copied to your desired location. Also worth noting: remember the exact path of your websites directory. IE: “C:\websites” or “c:\wwwroot”. You will need this when restoring.
Steps for Restoring (These steps will be done on the new/target server)
Step 1: Copy all website files from the backup to the exact filepath as the original server (from step 2 part c from above)
Step 2: install the iis 6.0 resource kit
Step 3: launch the metabase explorer
Step 4: left-click on “LM” on the left-hand pane and go to metabase->import key. Then point it to the LM key file that has been backed up.
Step 5: Follow step 4 for “schema”.
Step 6: This step is important, because without it, your websites will be inaccessible. If this step is forgotton, you will see a username/password authentication box whenever someone tries to visit any of your websites.
A) Open up the IIS manager
B) In the left-hand pane, right-click websites and go to properties.
C) Go to the tab that says “directory security”and under “authentication and access control” click on “edit”.
D) The restore process clears these settings, so make sure “enable anonymous access” is checked and an username/password is set. It will not allow a blank password, so a password will need to be set for the anonymous user account on the system username: IUSER_*MACHINE NAME*. This can be done through the administrative user control panel.
You should now have an exact copy of your websites.