This project is read-only.

Need help installing Orchard on Windows 2003 IIS 6.0 Production Web Server

Topics: Administration, Installing Orchard, Troubleshooting
May 17, 2012 at 9:42 PM

We have an old web-facing Windows Server 2003 Standard SP2 + IIS 6.0 production web server running a few classic ASP websites, including our main company website and multiple micro-sites. What would be the easiest and "safest" way to install Orchard on this web server without impacting the production websites that are currently running?

Our goal is to create a basic "Default Recipe" Orchard site in a IIS 6.0 "Virtual Directory". We understand that Orchard may require some underlying dependencies that are not currently installed on this web server. Is there a chance that the installation of Orchard and its underlying dependencies may cripple the existing functioning ASP websites?

Thank you in advance,


May 18, 2012 at 12:47 AM

Do it in a different app pool and you'll be safe.

May 18, 2012 at 2:12 AM

bertrandleroy, our concern is 1) how to install the Orchard's necessary dependencies in the production web server and 2) that those dependencies won't brake the existing production websites that are running (i.e. the existing company web site).

If we were to use the Web Platform installed on the web server to install Orchard, would the existing (classic ASP) web sites break?

May 18, 2012 at 2:14 AM

As I said, deploy it into an application that is configured to use a distinct application pool and you'll be fine. Classic ASP and ASP.NET run fine side-by-side, this is a scenario that is fully supported by Microsoft.