How many websites on IIs 6.0 on XP Pro 64?

IIS on XP limits you to one active website.

Some options:
a) create a new directory to house the root of your CMS, and change the home
directory of your default website to point ot that
OR
b) you can create additional websites using adsutil.vbs, IIS ADSI provider
or Metabase Explorer. However only one site can be started at any one time.
So you can manually create the additional website in the metabase, and then
decide which website you want to have running at any one time. This works
for IIS 5.1 on x86 - I haven't tested on IIS 6 on x64

Cheers
Ken

"pauld" <pauld581.RemoveThis@hotmail.com> wrote in message
news:fdadeb1c-8e3e-49e9-b0c6-ed5a399bd083@i7g2000prf.googlegroups.com...
> Hi -
> I am trying to do some testing on a CMS that a client is considering
> using. In order to test it I need to create a new website in
> IIS...When I right-click on "Web Sites" in IIS manager I do not get
> the New>Web Site in the menu, so obviously I cannot get to the Web
> Site Creation Wizard. I believe this is because IIS is limiting me to
> one web site, but I had thought that XP Pro x64 did not have this
> limitation. I should note that up until now I create new directories
> in the inetpub/wwwroot to do web testing, but for this CMS I seem to
> need to create a new site entirely.
>
> Any help with this would be greatly appreciated. Obviously I am not an
> IIS pro.
>
> TIA,
> Paul
>
> System: MS Windows XP
> Professional x64 Edition
> Version 2003
> Service Pack 2
>
> AMD Athlon 64 X2 Dual-core 5600+
> 6 GB RAM
 >> Stay informed about: How many websites on IIs 6.0 on XP Pro 64? 

Hello,

Yes, it is Server 2003 in design, but the same "consumer level" restrictions
apply to it that apply to Windows 32 bit, for the obvious reason MS would
want you to buy the SERVER OS if you need to use server-like features. The
limit is 100% artificial.

You can also try making Virtual Directories - of those you can have
multiples.
Each such directory has its own sessions and application settings (to some
degree)

W

"pauld" <pauld581 DeleteThis @hotmail.com> wrote in message
news:e9c3b4d1-96e4-4bb9-825e-e0fe274de665@d21g2000prf.googlegroups.com...
> On Feb 20, 5:47 pm, "Ken Schaefer" <kenREM... DeleteThis @THISadOpenStatic.com>
> wrote:
>> IIS on XP limits you to one active website.
>>
>> Some options:
>> a) create a new directory to house the root of your CMS, and change the
>> home
>> directory of your default website to point ot that
>> OR
>> b) you can create additional websites using adsutil.vbs, IIS ADSI
>> provider
>> or Metabase Explorer. However only one site can be started at any one
>> time.
>> So you can manually create the additional website in the metabase, and
>> then
>> decide which website you want to have running at any one time. This works
>> for IIS 5.1 on x86 - I haven't tested on IIS 6 on x64
>>
>
> Thank you for your fast reply, Ken. I can do what you suggest, and I
> suppose it's not that big of a deal to start and stop sites, but I was
> surprised that my version of Windows does not allow multiple sites to
> run. Everything I've read about XP Pro x64 indicates that it is
> essentially Windows Server 2003 with an XP badge slapped on it. I've
> not found anything authoritative on this matter anywhere else, so I am
> hoping someone here knows the answer.
>
> In the meantime I'm doing basically your second suggestion (using the
> freeware XP Pro IIS Admin, which incidentally warns me that I don't
> need to use it since I am on Windows Server 2003!).
>
> Thanks again,
> Paul
>
>
>
>> Cheers
>> Ken
>>
>> "pauld" <pauld... DeleteThis @hotmail.com> wrote in message
>>
>> news:fdadeb1c-8e3e-49e9-b0c6-ed5a399bd083@i7g2000prf.googlegroups.com...
>>
>> > Hi -
>> > I am trying to do some testing on a CMS that a client is considering
>> > using. In order to test it I need to create a new website in
>> > IIS...When I right-click on "Web Sites" in IIS manager I do not get
>> > the New>Web Site in the menu, so obviously I cannot get to the Web
>> > Site Creation Wizard. I believe this is because IIS is limiting me to
>> > one web site, but I had thought that XP Pro x64 did not have this
>> > limitation. I should note that up until now I create new directories
>> > in the inetpub/wwwroot to do web testing, but for this CMS I seem to
>> > need to create a new site entirely.
>>
>> > Any help with this would be greatly appreciated. Obviously I am not an
>> > IIS pro.
>>
>> > TIA,
>> > Paul
>>
>> > System: MS Windows XP
>> > Professional x64 Edition
>> > Version 2003
>> > Service Pack 2
>>
>> > AMD Athlon 64 X2 Dual-core 5600+
>> > 6 GB RAM
>
 >> Stay informed about: How many websites on IIs 6.0 on XP Pro 64? 

"Irresistance" <woy.TakeThisOut@irresistance.com> wrote in message
news:47bcd1ea$1@dnews.tpgi.com.au...
> You can also try making Virtual Directories - of those you can have
> multiples.
> Each such directory has its own sessions and application settings (to some
> degree)

Actually, this is slightly incorrect.

Whether or not a folder is a virtual directory has nothing to do with
whether it has it's own application settings and sessions.

What determines this is whether the folder is marked as an "application
root" or not. You can make any arbitrary folder (whether it's a virtual
directory or not) an application root. In IIS Manager, go to the Directory's
properties and click the "Create" button.

By default, when you add a virtual directory an application root is also,
automatically, created for that folder. This leads to people confusing
virtual directories with application roots. There is no need to create a
virtual directory. You can just create another folder in c:\inetpub\wwwroot
and mark it as an appRoot in IIS Manager.

Cheers
Ken
 >> Stay informed about: How many websites on IIs 6.0 on XP Pro 64? 

Ahhh ok - although what exactly is then the benefit of making a virtual
directory, if ANY directory can be an "application"

Only reason I can think of is that you can access it more easily like
http://IPAddress/VirtualDirectoryName without having to worry about its
physical location on the disk drive(s)? I normally leave c:\inetpup\wwwroot
for what it is and have all virtual directories on a different, more
secure/RAIDed drive...

W

"Ken Schaefer" <kenREMOVE RemoveThis @THISadOpenStatic.com> wrote in message
news:uDQpYvCdIHA.2268@TK2MSFTNGP02.phx.gbl...
>
> "Irresistance" <woy RemoveThis @irresistance.com> wrote in message
> news:47bcd1ea$1@dnews.tpgi.com.au...
>> You can also try making Virtual Directories - of those you can have
>> multiples.
>> Each such directory has its own sessions and application settings (to
>> some degree)
>
> Actually, this is slightly incorrect.
>
> Whether or not a folder is a virtual directory has nothing to do with
> whether it has it's own application settings and sessions.
>
> What determines this is whether the folder is marked as an "application
> root" or not. You can make any arbitrary folder (whether it's a virtual
> directory or not) an application root. In IIS Manager, go to the
> Directory's properties and click the "Create" button.
>
> By default, when you add a virtual directory an application root is also,
> automatically, created for that folder. This leads to people confusing
> virtual directories with application roots. There is no need to create a
> virtual directory. You can just create another folder in
> c:\inetpub\wwwroot and mark it as an appRoot in IIS Manager.
>
> Cheers
> Ken
 >> Stay informed about: How many websites on IIs 6.0 on XP Pro 64? 

The purpose of a "virtual directory" is to add a folder to the virtual
path/URI (e.g. http://servername/foldername) where "foldername" does not
exist under the physical path.

Cheers
Ken


"Irresistance" <woy.RemoveThis@irresistance.com> wrote in message
news:47bcded6@dnews.tpgi.com.au...
> Ahhh ok - although what exactly is then the benefit of making a virtual
> directory, if ANY directory can be an "application"
>
> Only reason I can think of is that you can access it more easily like
> http://IPAddress/VirtualDirectoryName without having to worry about its
> physical location on the disk drive(s)? I normally leave
> c:\inetpup\wwwroot for what it is and have all virtual directories on a
> different, more secure/RAIDed drive...
>
> W
>
> "Ken Schaefer" <kenREMOVE.RemoveThis@THISadOpenStatic.com> wrote in message
> news:uDQpYvCdIHA.2268@TK2MSFTNGP02.phx.gbl...
>>
>> "Irresistance" <woy.RemoveThis@irresistance.com> wrote in message
>> news:47bcd1ea$1@dnews.tpgi.com.au...
>>> You can also try making Virtual Directories - of those you can have
>>> multiples.
>>> Each such directory has its own sessions and application settings (to
>>> some degree)
>>
>> Actually, this is slightly incorrect.
>>
>> Whether or not a folder is a virtual directory has nothing to do with
>> whether it has it's own application settings and sessions.
>>
>> What determines this is whether the folder is marked as an "application
>> root" or not. You can make any arbitrary folder (whether it's a virtual
>> directory or not) an application root. In IIS Manager, go to the
>> Directory's properties and click the "Create" button.
>>
>> By default, when you add a virtual directory an application root is also,
>> automatically, created for that folder. This leads to people confusing
>> virtual directories with application roots. There is no need to create a
>> virtual directory. You can just create another folder in
>> c:\inetpub\wwwroot and mark it as an appRoot in IIS Manager.
>>
>> Cheers
>> Ken
>
 >> Stay informed about: How many websites on IIs 6.0 on XP Pro 64? 

On Feb 20, 7:56 pm, "Ken Schaefer" <kenREM....RemoveThis@THISadOpenStatic.com>
wrote:
> The purpose of a "virtual directory" is to add a folder to the virtual
> path/URI (e.g.http://servername/foldername) where "foldername" does not
> exist under the physical path.
>
> Cheers
> Ken
>
> "Irresistance" <w....RemoveThis@irresistance.com> wrote in message
>
> news:47bcded6@dnews.tpgi.com.au...
>
>
>
> > Ahhh ok - although what exactly is then the benefit of making a virtual
> > directory, if ANY directory can be an "application"
>
> > Only reason I can think of is that you can access it more easily like
> >http://IPAddress/VirtualDirectoryNamewithout having to worry about its
> > physical location on the disk drive(s)? I normally leave
> > c:\inetpup\wwwroot for what it is and have all virtual directories on a
> > different, more secure/RAIDed drive...
>
> > W
>
> > "Ken Schaefer" <kenREM....RemoveThis@THISadOpenStatic.com> wrote in message
> >news:uDQpYvCdIHA.2268@TK2MSFTNGP02.phx.gbl...
>
> >> "Irresistance" <w....RemoveThis@irresistance.com> wrote in message
> >>news:47bcd1ea$1@dnews.tpgi.com.au...
> >>> You can also try making Virtual Directories - of those you can have
> >>> multiples.
> >>> Each such directory has its own sessions and application settings (to
> >>> some degree)
>
> >> Actually, this is slightly incorrect.
>
> >> Whether or not a folder is a virtual directory has nothing to do with
> >> whether it has it's own application settings and sessions.
>
> >> What determines this is whether the folder is marked as an "application
> >> root" or not. You can make any arbitrary folder (whether it's a virtual
> >> directory or not) an application root. In IIS Manager, go to the
> >> Directory's properties and click the "Create" button.
>
> >> By default, when you add a virtual directory an application root is also,
> >> automatically, created for that folder. This leads to people confusing
> >> virtual directories with application roots. There is no need to create a
> >> virtual directory. You can just create another folder in
> >> c:\inetpub\wwwroot and mark it as an appRoot in IIS Manager.
>
> >> Cheers
> >> Ken- Hide quoted text -
>
> - Show quoted text -


Actually, we went and put back the XP Pro restrictions on IIS6 in XP
Pro 64bit before it shipped. But there was a time when IIS6 ran full-
blown in XP Pro 64bit -- you just don't have those internal bits.

I see no reason why you shouldn't just download and use Virtual PC
2007 or Virtual Server 2005 SP2 as well as Windows Server 2003 180
Evaluation CD/ISO and just install it in the Virtual Machine for
testing -- this is exactly what that software makes easy to do.



//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//
 >> Stay informed about: How many websites on IIs 6.0 on XP Pro 64?