Though XP seems quite ancient, there are many folks who still use it, many of which are developers. That said, developing under XP limits one from running multiple websites in IIS. XP does not currently support running multiple websites on a single license, but there is a tool you can use to work around it, IIS Admin.
After looking for a bit, we were able to find a solution to the problem called IIS Admin. IIS Admin allowed for multiple site definitions to be created under Windows XP (with only a single site started at a time). But this only creates empty sites and can’t copy settings from one site to another.
Initial Solution Drawbacks
First, the program did not show up in the taskbar. This meant that if the program lost focus it could be difficult to find again with multiple windows open. Second, if you created a site and failed to start it, the next time you opened IIS it would show up as an error. These among some others, proved to become a problem of its own when it came to introducing new developers to the program.
After dealing with explaining the program over and over, coders at Code Project decided to create IIS Admin in C# (hence IIsAdmin.NET was born) and while re-creating it, correct some of the features we found less then desirable. All of the interfacing with IIS is done via the Active Directory Service Interface (ADSI). Although the IIS ADSI provides much more functionality, programmers decided to keep IIsAdmin.NET’s primary function to creating the web site definition and switching between the active sites. All of the site management such as virtual directory creation can be done via IIS.
Download Source (Requires Login)
Source: Code Project
To be able to add multiple sites we use the adsutil.vbs file.
(the file is located in the folder C:/Inetpub/AdminScripts).
Here’s an overview of its usage:
Show a list of current setups
adsutil.vbs enum w3svc /p
Create a clean setup in a new website (make sure the sitenumber is free!):
adsutil.vbs create_vserv W3SVC/2
Copy an existing setup to a new site (including Virtual Directories!):
adsutil.vbs copy W3SVC/1 W3SVC/2
Delete a setup:
adsutil.vbs delete W3SVC/2
Republished by Blog Post Promoter