I came over this great checklist from Stackoverflow on how to configure windows to run old asp applications.


(1) Under Server Manager, go to "Manage" and "Add Roles". Look for Web Server (IIS) --> Application Development --> check ASP and Server Side Includes. Add IIS 6 Management Compatibility.

(2) Do not name site folders with .com, .net, etc at the end.

(3) Create NEW user account: - [app pool user identity] is user: app_pool_blahblahblah, pw: xxxxxx

(4) In Application Pool, advanced settings: - set .Net Framework version to "v2.0" <-- fixed issue with default asp doc not working!

- set "Enable 32-bit applications" to TRUE.

- under Process Model, change Identity to "[app pool user identity]" account we created above.

- This is default: be sure "load user profile" is set to FALSE.

- This is default: be sure "maximum worker processes" is "1".

(5) In Server Manager under features add SMTP server. Install IIS6 Resource Kit so you can use Metabase Explorer. Grant the [app pool user identity] user read access to the /Local Machine/SmtpSvc/ in the IIS Metabase Mail: In IIS 6 Management Console: - Under SMTP Virtual Server Properties: -- "Access" Tab --> Relay: add IPs of this server, including -- "Delivery" Tab --> Advanced: for "fully qualified domain name" put name of server -- "Delivery" Tab --> Advanced: for "smart host", for Godaddy, put "" -- "Delivery" Tab --> Outbound connections: Make sure limits are set to 100. -- "Security" Tab --> add "[app pool user identity]" and IIS_IUSRS


(6) In IIS 7 and 8 under web site:

- Under ASP:

-- under limits change max req entity and buffering limit to 1024000000

-- set script language to "vbscript"

-- set "send errors to browser" to true

-- set "Enable Parent Paths" to true -- ONLY IF PROBLEM: set enable buffering to "false" - Authentication --> edit "Anonymous Authentication" and set to app pool identity.

- under Management (at bottom) go into "Configuration Editor".

-- In the dropdown go to System.web --> http runtime and change maxRequestLength to 1024000000

-- In the dropdown go to System.webserver/security/requestFiltering --> chg allowDoubleEscaping=true

-- In the dropdown go to System.webserver/security/authentication/anonymousAuthentication --> chg userName to blank.

 - ONLY IF PROBLEM: under error pages: under 404 set to "/home.asp" and "execute URL" - ONLY IF PROBLEM: edit c:\windows\system32\inetsrv\config\applicationHost.config: change to "Allow"

(9) Set "Modify" Permissions for [app pool user identity] for the following folders: - your web site - windows\temp - inetpub\temp - inetpub\mailroot - ONLY IF PROBLEM: windows\serviceprofiles\networkservice\AppData\Local\Temp?

AND Set Permissions in registry: - ONLY IF PROBLEM: HKeyLocalMachine\Software\Wow6432Node\Microsoft\Jet\4.0\Engines? FOR THESE USER ACCOUNTS: - IIS_IUSRS - [app pool user identity] - NETWORK SERVICE

(10) For your FTP site, go to FTP Authorization Rules and add a rule to allow your specific user(s) or group(s).

(11) Install and Use Process Monitor to find permissions issues - filter

(12) Make sure SSL v2 and v3 are not being used: Click Start, click Run, type regedit, and then click OK. In Registry Editor, locate the following registry key/folder: HKey_Local_Machine\System\CurrentControlSet\Control\SecurityProviders \SCHANNEL\Protocols\SSL 2.0 Right-click on the SSL 2.0 folder and select New and then click Key. Name the new folder Server. Inside the Server folder, click the Edit menu, select New, and click DWORD (32-bit) Value. Enter Enabled as the name and hit Enter. Ensure that it shows 0x00000000 (0) under the Data column (it should by default). If it doesn't, right-click and select Modify and enter 0 as the Value data. Do the same with SSL 3.0. Restart the computer. Verify that no SSL 2.0 or 3.0 ciphers are available at or the Public SSL Server Database.

(13) SSL issue where Safari tells client that it needs a certificate. - Go into IIS settings for the SSL-protected site. - Click on "SSL Settings" - Choose "ignore".