IIS 7 Detection and Automating Some Tasks

We have some IIS prerequisites to our web application installation...

First, we check the following registry entry to see that IIS is
installed: HKEY_LOCAL_MACHINE, "Software\\Microsoft\\InetStp",
"MajorVersion" .

This appears to be OK for detecting if IIS 7 is insttalled during
initial testing. ??

If installed, we check to see that the 2.0 ASP.NET Web Service
Extension is present and enabled. This I do not know how to make
changes for to have proper functionality in IIS 7. ??

If we detect that that IIS is not installed, we open the Add Windows
Components applet (appwiz.cpl,,2) and instruct to install the Internet
Information Services. This, of course, is for pre Longhorn OSs.

If I simply use appwiz in this environment, that will open the
Programs and Features applet. From there, the user could select 'Turn
Windows Features on or off'. This will then start the Server Manager
where the Role (Web Server (IIS)) could be added along with any sub
services.

Question: Is there a way that I can simply start the Server Manager
via a shortcut akin to appwiz?
Question: If I add ASP.NET in this manner (sub service of IIS), will
this be the same as adding and enabling the pre-Longhorn Web Service
Extension?

Also, is there a programmatic way I can determine if the ASP.NET
extension is present/enabled? This would be needed for a check if IIS
is installed at the onset of our processes.

Any help GREATLY APPRECIATED!

Re: IIS 7 Detection and Automating Some Tasks

On Aug 31, 8:15 am, Superfreak3 wrote:
> We have some IIS prerequisites to our web application installation...
>
> First, we check the following registry entry to see that IIS is
> installed: HKEY_LOCAL_MACHINE, "Software\\Microsoft\\InetStp",
> "MajorVersion" .
>
> This appears to be OK for detecting if IIS 7 is insttalled during
> initial testing. ??
>
> If installed, we check to see that the 2.0 ASP.NET Web Service
> Extension is present and enabled. This I do not know how to make
> changes for to have proper functionality in IIS 7. ??
>
> If we detect that that IIS is not installed, we open the Add Windows
> Components applet (appwiz.cpl,,2) and instruct to install the Internet
> Information Services. This, of course, is for pre Longhorn OSs.
>
> If I simply use appwiz in this environment, that will open the
> Programs and Features applet. From there, the user could select 'Turn
> Windows Features on or off'. This will then start the Server Manager
> where the Role (Web Server (IIS)) could be added along with any sub
> services.
>
> Question: Is there a way that I can simply start the Server Manager
> via a shortcut akin to appwiz?
> Question: If I add ASP.NET in this manner (sub service of IIS), will
> this be the same as adding and enabling the pre-Longhorn Web Service
> Extension?
>
> Also, is there a programmatic way I can determine if the ASP.NET
> extension is present/enabled? This would be needed for a check if IIS
> is installed at the onset of our processes.
>
> Any help GREATLY APPRECIATED!


Yes, you can unattend install IIS and its components, including
ASP.Net. You can do this for all IIS versions, though the instructions
can differ. appwiz.cpl is not a good solution; it is just slightly
better than doing nothing about pre-requisites. There is a single
magic command to unattend install IIS6, and there is another magic
command to unattend install IIS7. Both commands are publicly
documented on MSDN.

Determining ASP.Net Web Service Extension is not required on IIS7. It
is required only if you run ASP.Net pages in "Classic" Managed
Pipeline Mode. That mode is not the default, so you need to rethink
your requirement to always enable ASP.Net Web Service Extension.

There is no documented way to detect the selection status of various
Windows Features of IIS7. There is an undocumented backdoor way.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: IIS 7 Detection and Automating Some Tasks

On Aug 31, 6:06 pm, David Wang wrote:
> On Aug 31, 8:15 am,Superfreak3 wrote:
>
>
>
>
>
> > We have some IIS prerequisites to our web application installation...
>
> > First, we check the following registry entry to see that IIS is
> > installed: HKEY_LOCAL_MACHINE, "Software\\Microsoft\\InetStp",
> > "MajorVersion" .
>
> > This appears to be OK for detecting if IIS 7 is insttalled during
> > initial testing. ??
>
> > If installed, we check to see that the 2.0 ASP.NET Web Service
> > Extension is present and enabled. This I do not know how to make
> > changes for to have proper functionality in IIS 7. ??
>
> > If we detect that that IIS is not installed, we open the Add Windows
> > Components applet (appwiz.cpl,,2) and instruct to install the Internet
> > Information Services. This, of course, is for pre Longhorn OSs.
>
> > If I simply use appwiz in this environment, that will open the
> > Programs and Features applet. From there, the user could select 'Turn
> > Windows Features on or off'. This will then start the Server Manager
> > where the Role (Web Server (IIS)) could be added along with any sub
> > services.
>
> > Question: Is there a way that I can simply start the Server Manager
> > via a shortcut akin to appwiz?
> > Question: If I add ASP.NET in this manner (sub service of IIS), will
> > this be the same as adding and enabling the pre-Longhorn Web Service
> > Extension?
>
> > Also, is there a programmatic way I can determine if the ASP.NET
> > extension is present/enabled? This would be needed for a check if IIS
> > is installed at the onset of our processes.
>
> > Any help GREATLY APPRECIATED!
>
> Yes, you can unattend install IIS and its components, including
> ASP.Net. You can do this for all IIS versions, though the instructions
> can differ. appwiz.cpl is not a good solution; it is just slightly
> better than doing nothing about pre-requisites. There is a single
> magic command to unattend install IIS6, and there is another magic
> command to unattend install IIS7. Both commands are publicly
> documented on MSDN.
>
> Determining ASP.Net Web Service Extension is not required on IIS7. It
> is required only if you run ASP.Net pages in "Classic" Managed
> Pipeline Mode. That mode is not the default, so you need to rethink
> your requirement to always enable ASP.Net Web Service Extension.
>
> There is no documented way to detect the selection status of various
> Windows Features of IIS7. There is an undocumented backdoor way.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //- Hide quoted text -
>
> - Show quoted text -

For the unattended processes involving IIS 7, are you referring to
Pkgmgr.exe? If so, I guess I would have to formulate and use an .xml
file with this, similar to that shown here...

http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=959 (Longhorn
Server example).

I guess what I would like to have happen is to check for IIS 5, 6, or
7. If none exist (IIS 7 on Longhorn) on Windows Server 2008
(Longhorn), it would be nice if I could fire off the IIS setup, which
would have to include any ASP.NET 'Features', I guess.

The only problem is I don't know how to ensure the .xml file will take
care of all this. In looking at the example for Longhorn server at
the above link, I see that is appears that ASP.NET will be installed.

I guess I'll give this a shot on a Virtual Image I have for testing
and take a look.

Just let me know if this is the unattended path you were hinting
at. ;)

THANKS FOR THE HELP (so far, as I'm sure I'll need more).

Re: IIS 7 Detection and Automating Some Tasks

On Sep 4, 10:32 am, Superfreak3 wrote:
> On Aug 31, 6:06 pm, David Wang wrote:
>
>
>
>
>
> > On Aug 31, 8:15 am,Superfreak3 wrote:
>
> > > We have some IIS prerequisites to our web application installation...
>
> > > First, we check the following registry entry to see that IIS is
> > > installed: HKEY_LOCAL_MACHINE, "Software\\Microsoft\\InetStp",
> > > "MajorVersion" .
>
> > > This appears to be OK for detecting if IIS 7 is insttalled during
> > > initial testing. ??
>
> > > If installed, we check to see that the 2.0 ASP.NET Web Service
> > > Extension is present and enabled. This I do not know how to make
> > > changes for to have proper functionality in IIS 7. ??
>
> > > If we detect that that IIS is not installed, we open the Add Windows
> > > Components applet (appwiz.cpl,,2) and instruct to install the Internet
> > > Information Services. This, of course, is for pre Longhorn OSs.
>
> > > If I simply use appwiz in this environment, that will open the
> > > Programs and Features applet. From there, the user could select 'Turn
> > > Windows Features on or off'. This will then start the Server Manager
> > > where the Role (Web Server (IIS)) could be added along with any sub
> > > services.
>
> > > Question: Is there a way that I can simply start the Server Manager
> > > via a shortcut akin to appwiz?
> > > Question: If I add ASP.NET in this manner (sub service of IIS), will
> > > this be the same as adding and enabling the pre-Longhorn Web Service
> > > Extension?
>
> > > Also, is there a programmatic way I can determine if the ASP.NET
> > > extension is present/enabled? This would be needed for a check if IIS
> > > is installed at the onset of our processes.
>
> > > Any help GREATLY APPRECIATED!
>
> > Yes, you can unattend install IIS and its components, including
> > ASP.Net. You can do this for all IIS versions, though the instructions
> > can differ. appwiz.cpl is not a good solution; it is just slightly
> > better than doing nothing about pre-requisites. There is a single
> > magic command to unattend install IIS6, and there is another magic
> > command to unattend install IIS7. Both commands are publicly
> > documented on MSDN.
>
> > Determining ASP.Net Web Service Extension is not required on IIS7. It
> > is required only if you run ASP.Net pages in "Classic" Managed
> > Pipeline Mode. That mode is not the default, so you need to rethink
> > your requirement to always enable ASP.Net Web Service Extension.
>
> > There is no documented way to detect the selection status of various
> > Windows Features of IIS7. There is an undocumented backdoor way.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //- Hide quoted text -
>
> > - Show quoted text -
>
> For the unattended processes involving IIS 7, are you referring to
> Pkgmgr.exe? If so, I guess I would have to formulate and use an .xml
> file with this, similar to that shown here...
>
> http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=959(Lo nghorn
> Server example).
>
> I guess what I would like to have happen is to check for IIS 5, 6, or
> 7. If none exist (IIS 7 on Longhorn) on Windows Server 2008
> (Longhorn), it would be nice if I could fire off the IIS setup, which
> would have to include any ASP.NET 'Features', I guess.
>
> The only problem is I don't know how to ensure the .xml file will take
> care of all this. In looking at the example for Longhorn server at
> the above link, I see that is appears that ASP.NET will be installed.
>
> I guess I'll give this a shot on a Virtual Image I have for testing
> and take a look.
>
> Just let me know if this is the unattended path you were hinting
> at. ;)
>
> THANKS FOR THE HELP (so far, as I'm sure I'll need more).- Hide quoted text -
>
> - Show quoted text -

If this pkgmgr.exe is the method to which you refer, I have another
question regarding the use of the .xml file. From the link provided,
it is documented that the version entry must be changed to match the
target machine....

name="Microsoft-Windows-Foundation-Package"
version="6.0.6001.16510"
language="neutral"
processorArchitecture="x86"
publicKeyToken="31bf3856ad364e35"
versionScope="nonSxS"
/>

My question then, would be how could I make the use of the .xml file
universal, if it is possible at all. If not, how could I use pkgmgr
to simply install IIS 7 with ASP.NET? I'm not sure of the command
line to use as a minimum for our purposes, I guess is what it really
boils down to. This is, of course, if we can't use the .xml file
universally for VISTA Longhorn.

THANKS AGAIN!

Re: IIS 7 Detection and Automating Some Tasks

On Sep 4, 1:29 pm, Superfreak3 wrote:
> On Sep 4, 10:32 am, Superfreak3 wrote:
>
>
>
>
>
> > On Aug 31, 6:06 pm, David Wang wrote:
>
> > > On Aug 31, 8:15 am,Superfreak3 wrote:
>
> > > > We have some IIS prerequisites to our web application installation...
>
> > > > First, we check the following registry entry to see that IIS is
> > > > installed: HKEY_LOCAL_MACHINE, "Software\\Microsoft\\InetStp",
> > > > "MajorVersion" .
>
> > > > This appears to be OK for detecting if IIS 7 is insttalled during
> > > > initial testing. ??
>
> > > > If installed, we check to see that the 2.0 ASP.NET Web Service
> > > > Extension is present and enabled. This I do not know how to make
> > > > changes for to have proper functionality in IIS 7. ??
>
> > > > If we detect that that IIS is not installed, we open the Add Windows
> > > > Components applet (appwiz.cpl,,2) and instruct to install the Internet
> > > > Information Services. This, of course, is for pre Longhorn OSs.
>
> > > > If I simply use appwiz in this environment, that will open the
> > > > Programs and Features applet. From there, the user could select 'Turn
> > > > Windows Features on or off'. This will then start the Server Manager
> > > > where the Role (Web Server (IIS)) could be added along with any sub
> > > > services.
>
> > > > Question: Is there a way that I can simply start the Server Manager
> > > > via a shortcut akin to appwiz?
> > > > Question: If I add ASP.NET in this manner (sub service of IIS), will
> > > > this be the same as adding and enabling the pre-Longhorn Web Service
> > > > Extension?
>
> > > > Also, is there a programmatic way I can determine if the ASP.NET
> > > > extension is present/enabled? This would be needed for a check if IIS
> > > > is installed at the onset of our processes.
>
> > > > Any help GREATLY APPRECIATED!
>
> > > Yes, you can unattend install IIS and its components, including
> > > ASP.Net. You can do this for all IIS versions, though the instructions
> > > can differ. appwiz.cpl is not a good solution; it is just slightly
> > > better than doing nothing about pre-requisites. There is a single
> > > magic command to unattend install IIS6, and there is another magic
> > > command to unattend install IIS7. Both commands are publicly
> > > documented on MSDN.
>
> > > Determining ASP.Net Web Service Extension is not required on IIS7. It
> > > is required only if you run ASP.Net pages in "Classic" Managed
> > > Pipeline Mode. That mode is not the default, so you need to rethink
> > > your requirement to always enable ASP.Net Web Service Extension.
>
> > > There is no documented way to detect the selection status of various
> > > Windows Features of IIS7. There is an undocumented backdoor way.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > //- Hide quoted text -
>
> > > - Show quoted text -
>
> > For the unattended processes involving IIS 7, are you referring to
> > Pkgmgr.exe? If so, I guess I would have to formulate and use an .xml
> > file with this, similar to that shown here...
>
> >http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=959(L onghorn
> > Server example).
>
> > I guess what I would like to have happen is to check for IIS 5, 6, or
> > 7. If none exist (IIS 7 on Longhorn) on Windows Server 2008
> > (Longhorn), it would be nice if I could fire off the IIS setup, which
> > would have to include any ASP.NET 'Features', I guess.
>
> > The only problem is I don't know how to ensure the .xml file will take
> > care of all this. In looking at the example for Longhorn server at
> > the above link, I see that is appears that ASP.NET will be installed.
>
> > I guess I'll give this a shot on a Virtual Image I have for testing
> > and take a look.
>
> > Just let me know if this is the unattended path you were hinting
> > at. ;)
>
> > THANKS FOR THE HELP (so far, as I'm sure I'll need more).- Hide quoted text -
>
> > - Show quoted text -
>
> If this pkgmgr.exe is the method to which you refer, I have another
> question regarding the use of the .xml file. From the link provided,
> it is documented that the version entry must be changed to match the
> target machine....
>
> > name="Microsoft-Windows-Foundation-Package"
> version="6.0.6001.16510"
> language="neutral"
> processorArchitecture="x86"
> publicKeyToken="31bf3856ad364e35"
> versionScope="nonSxS"
> />
>
> My question then, would be how could I make the use of the .xml file
> universal, if it is possible at all. If not, how could I use pkgmgr
> to simply install IIS 7 with ASP.NET? I'm not sure of the command
> line to use as a minimum for our purposes, I guess is what it really
> boils down to. This is, of course, if we can't use the .xml file
> universally for VISTA Longhorn.
>
> THANKS AGAIN!- Hide quoted text -
>
> - Show quoted text -


To keep things interesting, instructions are totally different and
incompatible between IIS7 and IIS6/IIS5. And you don't want to use the
XML file because it needs the perfect version number.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: IIS 7 Detection and Automating Some Tasks

On Sep 4, 9:28 pm, David Wang wrote:
> On Sep 4, 1:29 pm,Superfreak3 wrote:
>
>
>
>
>
> > On Sep 4, 10:32 am,Superfreak3 wrote:
>
> > > On Aug 31, 6:06 pm, David Wang wrote:
>
> > > > On Aug 31, 8:15 am,Superfreak3 wrote:
>
> > > > > We have some IIS prerequisites to our web application installation...
>
> > > > > First, we check the following registry entry to see that IIS is
> > > > > installed: HKEY_LOCAL_MACHINE, "Software\\Microsoft\\InetStp",
> > > > > "MajorVersion" .
>
> > > > > This appears to be OK for detecting if IIS 7 is insttalled during
> > > > > initial testing. ??
>
> > > > > If installed, we check to see that the 2.0 ASP.NET Web Service
> > > > > Extension is present and enabled. This I do not know how to make
> > > > > changes for to have proper functionality in IIS 7. ??
>
> > > > > If we detect that that IIS is not installed, we open the Add Windows
> > > > > Components applet (appwiz.cpl,,2) and instruct to install the Internet
> > > > > Information Services. This, of course, is for pre Longhorn OSs.
>
> > > > > If I simply use appwiz in this environment, that will open the
> > > > > Programs and Features applet. From there, the user could select 'Turn
> > > > > Windows Features on or off'. This will then start the Server Manager
> > > > > where the Role (Web Server (IIS)) could be added along with any sub
> > > > > services.
>
> > > > > Question: Is there a way that I can simply start the Server Manager
> > > > > via a shortcut akin to appwiz?
> > > > > Question: If I add ASP.NET in this manner (sub service of IIS), will
> > > > > this be the same as adding and enabling the pre-Longhorn Web Service
> > > > > Extension?
>
> > > > > Also, is there a programmatic way I can determine if the ASP.NET
> > > > > extension is present/enabled? This would be needed for a check if IIS
> > > > > is installed at the onset of our processes.
>
> > > > > Any help GREATLY APPRECIATED!
>
> > > > Yes, you can unattend install IIS and its components, including
> > > > ASP.Net. You can do this for all IIS versions, though the instructions
> > > > can differ. appwiz.cpl is not a good solution; it is just slightly
> > > > better than doing nothing about pre-requisites. There is a single
> > > > magic command to unattend install IIS6, and there is another magic
> > > > command to unattend install IIS7. Both commands are publicly
> > > > documented on MSDN.
>
> > > > Determining ASP.Net Web Service Extension is not required on IIS7. It
> > > > is required only if you run ASP.Net pages in "Classic" Managed
> > > > Pipeline Mode. That mode is not the default, so you need to rethink
> > > > your requirement to always enable ASP.Net Web Service Extension.
>
> > > > There is no documented way to detect the selection status of various
> > > > Windows Features of IIS7. There is an undocumented backdoor way.
>
> > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > //- Hide quoted text -
>
> > > > - Show quoted text -
>
> > > For the unattended processes involving IIS 7, are you referring to
> > > Pkgmgr.exe? If so, I guess I would have to formulate and use an .xml
> > > file with this, similar to that shown here...
>
> > >http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=959(L onghorn
> > > Server example).
>
> > > I guess what I would like to have happen is to check for IIS 5, 6, or
> > > 7. If none exist (IIS 7 on Longhorn) on Windows Server 2008
> > > (Longhorn), it would be nice if I could fire off the IIS setup, which
> > > would have to include any ASP.NET 'Features', I guess.
>
> > > The only problem is I don't know how to ensure the .xml file will take
> > > care of all this. In looking at the example for Longhorn server at
> > > the above link, I see that is appears that ASP.NET will be installed.
>
> > > I guess I'll give this a shot on a Virtual Image I have for testing
> > > and take a look.
>
> > > Just let me know if this is the unattended path you were hinting
> > > at. ;)
>
> > > THANKS FOR THE HELP (so far, as I'm sure I'll need more).- Hide quoted text -
>
> > > - Show quoted text -
>
> > If this pkgmgr.exe is the method to which you refer, I have another
> > question regarding the use of the .xml file. From the link provided,
> > it is documented that the version entry must be changed to match the
> > target machine....
>
> > > > name="Microsoft-Windows-Foundation-Package"
> > version="6.0.6001.16510"
> > language="neutral"
> > processorArchitecture="x86"
> > publicKeyToken="31bf3856ad364e35"
> > versionScope="nonSxS"
> > />
>
> > My question then, would be how could I make the use of the .xml file
> > universal, if it is possible at all. If not, how could I use pkgmgr
> > to simply install IIS 7 with ASP.NET? I'm not sure of the command
> > line to use as a minimum for our purposes, I guess is what it really
> > boils down to. This is, of course, if we can't use the .xml file
> > universally for VISTA Longhorn.
>
> > THANKS AGAIN!- Hide quoted text -
>
> > - Show quoted text -
>
> To keep things interesting, instructions are totally different and
> incompatible between IIS7 and IIS6/IIS5. And you don't want to use the
> XML file because it needs the perfect version number.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //- Hide quoted text -
>
> - Show quoted text -

So, I guess I would have to use the pkgmgr.exe and the exact
Windows_Feature_Name from the command line then. ??

If this is the case, is there anything special I have to do to ensure
ASP.NET and any pre-requisites (for ASP.NET) are installed as well?

THANKS FOR THE INFO! :)

Re: IIS 7 Detection and Automating Some Tasks

On Sep 5, 5:39 am, Superfreak3 wrote:
> On Sep 4, 9:28 pm, David Wang wrote:
>
>
>
>
>
> > On Sep 4, 1:29 pm,Superfreak3 wrote:
>
> > > On Sep 4, 10:32 am,Superfreak3 wrote:
>
> > > > On Aug 31, 6:06 pm, David Wang wrote:
>
> > > > > On Aug 31, 8:15 am,Superfreak3 wrote:
>
> > > > > > We have some IIS prerequisites to our web application installation...
>
> > > > > > First, we check the following registry entry to see that IIS is
> > > > > > installed: HKEY_LOCAL_MACHINE, "Software\\Microsoft\\InetStp",
> > > > > > "MajorVersion" .
>
> > > > > > This appears to be OK for detecting if IIS 7 is insttalled during
> > > > > > initial testing. ??
>
> > > > > > If installed, we check to see that the 2.0 ASP.NET Web Service
> > > > > > Extension is present and enabled. This I do not know how to make
> > > > > > changes for to have proper functionality in IIS 7. ??
>
> > > > > > If we detect that that IIS is not installed, we open the Add Windows
> > > > > > Components applet (appwiz.cpl,,2) and instruct to install the Internet
> > > > > > Information Services. This, of course, is for pre Longhorn OSs.
>
> > > > > > If I simply use appwiz in this environment, that will open the
> > > > > > Programs and Features applet. From there, the user could select 'Turn
> > > > > > Windows Features on or off'. This will then start the Server Manager
> > > > > > where the Role (Web Server (IIS)) could be added along with any sub
> > > > > > services.
>
> > > > > > Question: Is there a way that I can simply start the Server Manager
> > > > > > via a shortcut akin to appwiz?
> > > > > > Question: If I add ASP.NET in this manner (sub service of IIS), will
> > > > > > this be the same as adding and enabling the pre-Longhorn Web Service
> > > > > > Extension?
>
> > > > > > Also, is there a programmatic way I can determine if the ASP.NET
> > > > > > extension is present/enabled? This would be needed for a check if IIS
> > > > > > is installed at the onset of our processes.
>
> > > > > > Any help GREATLY APPRECIATED!
>
> > > > > Yes, you can unattend install IIS and its components, including
> > > > > ASP.Net. You can do this for all IIS versions, though the instructions
> > > > > can differ. appwiz.cpl is not a good solution; it is just slightly
> > > > > better than doing nothing about pre-requisites. There is a single
> > > > > magic command to unattend install IIS6, and there is another magic
> > > > > command to unattend install IIS7. Both commands are publicly
> > > > > documented on MSDN.
>
> > > > > Determining ASP.Net Web Service Extension is not required on IIS7. It
> > > > > is required only if you run ASP.Net pages in "Classic" Managed
> > > > > Pipeline Mode. That mode is not the default, so you need to rethink
> > > > > your requirement to always enable ASP.Net Web Service Extension.
>
> > > > > There is no documented way to detect the selection status of various
> > > > > Windows Features of IIS7. There is an undocumented backdoor way.
>
> > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > //- Hide quoted text -
>
> > > > > - Show quoted text -
>
> > > > For the unattended processes involving IIS 7, are you referring to
> > > > Pkgmgr.exe? If so, I guess I would have to formulate and use an .xml
> > > > file with this, similar to that shown here...
>
> > > >http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=959(L onghorn
> > > > Server example).
>
> > > > I guess what I would like to have happen is to check for IIS 5, 6, or
> > > > 7. If none exist (IIS 7 on Longhorn) on Windows Server 2008
> > > > (Longhorn), it would be nice if I could fire off the IIS setup, which
> > > > would have to include any ASP.NET 'Features', I guess.
>
> > > > The only problem is I don't know how to ensure the .xml file will take
> > > > care of all this. In looking at the example for Longhorn server at
> > > > the above link, I see that is appears that ASP.NET will be installed.
>
> > > > I guess I'll give this a shot on a Virtual Image I have for testing
> > > > and take a look.
>
> > > > Just let me know if this is the unattended path you were hinting
> > > > at. ;)
>
> > > > THANKS FOR THE HELP (so far, as I'm sure I'll need more).- Hide quoted text -
>
> > > > - Show quoted text -
>
> > > If this pkgmgr.exe is the method to which you refer, I have another
> > > question regarding the use of the .xml file. From the link provided,
> > > it is documented that the version entry must be changed to match the
> > > target machine....
>
> > > > > > name="Microsoft-Windows-Foundation-Package"
> > > version="6.0.6001.16510"
> > > language="neutral"
> > > processorArchitecture="x86"
> > > publicKeyToken="31bf3856ad364e35"
> > > versionScope="nonSxS"
> > > />
>
> > > My question then, would be how could I make the use of the .xml file
> > > universal, if it is possible at all. If not, how could I use pkgmgr
> > > to simply install IIS 7 with ASP.NET? I'm not sure of the command
> > > line to use as a minimum for our purposes, I guess is what it really
> > > boils down to. This is, of course, if we can't use the .xml file
> > > universally for VISTA Longhorn.
>
> > > THANKS AGAIN!- Hide quoted text -
>
> > > - Show quoted text -
>
> > To keep things interesting, instructions are totally different and
> > incompatible between IIS7 and IIS6/IIS5. And you don't want to use the
> > XML file because it needs the perfect version number.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //- Hide quoted text -
>
> > - Show quoted text -
>
> So, I guess I would have to use the pkgmgr.exe and the exact
> Windows_Feature_Name from the command line then. ??
>
> If this is the case, is there anything special I have to do to ensure
> ASP.NET and any pre-requisites (for ASP.NET) are installed as well?
>
> THANKS FOR THE INFO! :)- Hide quoted text -
>
> - Show quoted text -


ASP.Net 1.1 is preinstalled on Windows Server 2003, and ASP.Net 2.0 is
preinstalled on Vista. Unattend installation mechanism for both IIS6
and IIS7 will be able to deal with ASP.Net, and you don't need to do
anything special.


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: IIS 7 Detection and Automating Some Tasks

On Sep 6, 7:28 am, David Wang wrote:
> On Sep 5, 5:39 am,Superfreak3 wrote:
>
>
>
>
>
> > On Sep 4, 9:28 pm, David Wang wrote:
>
> > > On Sep 4, 1:29 pm,Superfreak3 wrote:
>
> > > > On Sep 4, 10:32 am,Superfreak3 wrote:
>
> > > > > On Aug 31, 6:06 pm, David Wang wrote:
>
> > > > > > On Aug 31, 8:15 am,Superfreak3 wrote:
>
> > > > > > > We have some IIS prerequisites to our web application installation...
>
> > > > > > > First, we check the following registry entry to see that IIS is
> > > > > > > installed: HKEY_LOCAL_MACHINE, "Software\\Microsoft\\InetStp",
> > > > > > > "MajorVersion" .
>
> > > > > > > This appears to be OK for detecting if IIS 7 is insttalled during
> > > > > > > initial testing. ??
>
> > > > > > > If installed, we check to see that the 2.0 ASP.NET Web Service
> > > > > > > Extension is present and enabled. This I do not know how to make
> > > > > > > changes for to have proper functionality in IIS 7. ??
>
> > > > > > > If we detect that that IIS is not installed, we open the Add Windows
> > > > > > > Components applet (appwiz.cpl,,2) and instruct to install the Internet
> > > > > > > Information Services. This, of course, is for pre Longhorn OSs.
>
> > > > > > > If I simply use appwiz in this environment, that will open the
> > > > > > > Programs and Features applet. From there, the user could select 'Turn
> > > > > > > Windows Features on or off'. This will then start the Server Manager
> > > > > > > where the Role (Web Server (IIS)) could be added along with any sub
> > > > > > > services.
>
> > > > > > > Question: Is there a way that I can simply start the Server Manager
> > > > > > > via a shortcut akin to appwiz?
> > > > > > > Question: If I add ASP.NET in this manner (sub service of IIS), will
> > > > > > > this be the same as adding and enabling the pre-Longhorn Web Service
> > > > > > > Extension?
>
> > > > > > > Also, is there a programmatic way I can determine if the ASP.NET
> > > > > > > extension is present/enabled? This would be needed for a check if IIS
> > > > > > > is installed at the onset of our processes.
>
> > > > > > > Any help GREATLY APPRECIATED!
>
> > > > > > Yes, you can unattend install IIS and its components, including
> > > > > > ASP.Net. You can do this for all IIS versions, though the instructions
> > > > > > can differ. appwiz.cpl is not a good solution; it is just slightly
> > > > > > better than doing nothing about pre-requisites. There is a single
> > > > > > magic command to unattend install IIS6, and there is another magic
> > > > > > command to unattend install IIS7. Both commands are publicly
> > > > > > documented on MSDN.
>
> > > > > > Determining ASP.Net Web Service Extension is not required on IIS7. It
> > > > > > is required only if you run ASP.Net pages in "Classic" Managed
> > > > > > Pipeline Mode. That mode is not the default, so you need to rethink
> > > > > > your requirement to always enable ASP.Net Web Service Extension.
>
> > > > > > There is no documented way to detect the selection status of various
> > > > > > Windows Features of IIS7. There is an undocumented backdoor way.
>
> > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > > //- Hide quoted text -
>
> > > > > > - Show quoted text -
>
> > > > > For the unattended processes involving IIS 7, are you referring to
> > > > > Pkgmgr.exe? If so, I guess I would have to formulate and use an .xml
> > > > > file with this, similar to that shown here...
>
> > > > >http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=959(L onghorn
> > > > > Server example).
>
> > > > > I guess what I would like to have happen is to check for IIS 5, 6, or
> > > > > 7. If none exist (IIS 7 on Longhorn) on Windows Server 2008
> > > > > (Longhorn), it would be nice if I could fire off the IIS setup, which
> > > > > would have to include any ASP.NET 'Features', I guess.
>
> > > > > The only problem is I don't know how to ensure the .xml file will take
> > > > > care of all this. In looking at the example for Longhorn server at
> > > > > the above link, I see that is appears that ASP.NET will be installed.
>
> > > > > I guess I'll give this a shot on a Virtual Image I have for testing
> > > > > and take a look.
>
> > > > > Just let me know if this is the unattended path you were hinting
> > > > > at. ;)
>
> > > > > THANKS FOR THE HELP (so far, as I'm sure I'll need more).- Hide quoted text -
>
> > > > > - Show quoted text -
>
> > > > If this pkgmgr.exe is the method to which you refer, I have another
> > > > question regarding the use of the .xml file. From the link provided,
> > > > it is documented that the version entry must be changed to match the
> > > > target machine....
>
> > > > > > > > name="Microsoft-Windows-Foundation-Package"
> > > > version="6.0.6001.16510"
> > > > language="neutral"
> > > > processorArchitecture="x86"
> > > > publicKeyToken="31bf3856ad364e35"
> > > > versionScope="nonSxS"
> > > > />
>
> > > > My question then, would be how could I make the use of the .xml file
> > > > universal, if it is possible at all. If not, how could I use pkgmgr
> > > > to simply install IIS 7 with ASP.NET? I'm not sure of the command
> > > > line to use as a minimum for our purposes, I guess is what it really
> > > > boils down to. This is, of course, if we can't use the .xml file
> > > > universally for VISTA Longhorn.
>
> > > > THANKS AGAIN!- Hide quoted text -
>
> > > > - Show quoted text -
>
> > > To keep things interesting, instructions are totally different and
> > > incompatible between IIS7 and IIS6/IIS5. And you don't want to use the
> > > XML file because it needs the perfect version number.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > //- Hide quoted text -
>
> > > - Show quoted text -
>
> > So, I guess I would have to use the pkgmgr.exe and the exact
> > Windows_Feature_Name from the command line then. ??
>
> > If this is the case, is there anything special I have to do to ensure
> > ASP.NET and any pre-requisites (for ASP.NET) are installed as well?
>
> > THANKS FOR THE INFO! :)- Hide quoted text -
>
> > - Show quoted text -
>
> ASP.Net 1.1 is preinstalled on Windows Server 2003, and ASP.Net 2.0 is
> preinstalled on Vista. Unattend installation mechanism for both IIS6
> and IIS7 will be able to deal with ASP.Net, and you don't need to do
> anything special.
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //- Hide quoted text -
>
> - Show quoted text -

I came across ServerManagerCmd.exe to accomplish what I need, I think.

What I'll do from our install wrapper is to fire a little utility I
made to execute this .exe with the -query parameter to dump the
current Role/Role Services configuration to an .xml file. I'll then
check the state of each of my requirements (Web Server (IIS), ASP.NET,
and IIS 6 Mgmt Compatibility) by reading through the various entries.

I believe I can even install any missing components via
ServiceManagerCmd as well. Currently, if something is missing I'm
just going to fire CmpMgmtLauncher and have the user double check the
requirements. Eventually we may change to the automated approach, but
that's not my call at this point.

Let me know what you think of this approach of detecting inadequacies
in IIS 7.

THANKS!!

Re: IIS 7 Detection and Automating Some Tasks

On Sep 6, 10:25 am, Superfreak3 wrote:
> On Sep 6, 7:28 am, David Wang wrote:
>
>
>
>
>
> > On Sep 5, 5:39 am,Superfreak3 wrote:
>
> > > On Sep 4, 9:28 pm, David Wang wrote:
>
> > > > On Sep 4, 1:29 pm,Superfreak3 wrote:
>
> > > > > On Sep 4, 10:32 am,Superfreak3 wrote:
>
> > > > > > On Aug 31, 6:06 pm, David Wang wrote:
>
> > > > > > > On Aug 31, 8:15 am,Superfreak3 wrote:
>
> > > > > > > > We have some IIS prerequisites to our web application installation...
>
> > > > > > > > First, we check the following registry entry to see that IIS is
> > > > > > > > installed: HKEY_LOCAL_MACHINE, "Software\\Microsoft\\InetStp",
> > > > > > > > "MajorVersion" .
>
> > > > > > > > This appears to be OK for detecting if IIS 7 is insttalled during
> > > > > > > > initial testing. ??
>
> > > > > > > > If installed, we check to see that the 2.0 ASP.NET Web Service
> > > > > > > > Extension is present and enabled. This I do not know how to make
> > > > > > > > changes for to have proper functionality in IIS 7. ??
>
> > > > > > > > If we detect that that IIS is not installed, we open the Add Windows
> > > > > > > > Components applet (appwiz.cpl,,2) and instruct to install the Internet
> > > > > > > > Information Services. This, of course, is for pre Longhorn OSs.
>
> > > > > > > > If I simply use appwiz in this environment, that will open the
> > > > > > > > Programs and Features applet. From there, the user could select 'Turn
> > > > > > > > Windows Features on or off'. This will then start the Server Manager
> > > > > > > > where the Role (Web Server (IIS)) could be added along with any sub
> > > > > > > > services.
>
> > > > > > > > Question: Is there a way that I can simply start the Server Manager
> > > > > > > > via a shortcut akin to appwiz?
> > > > > > > > Question: If I add ASP.NET in this manner (sub service of IIS), will
> > > > > > > > this be the same as adding and enabling the pre-Longhorn Web Service
> > > > > > > > Extension?
>
> > > > > > > > Also, is there a programmatic way I can determine if the ASP.NET
> > > > > > > > extension is present/enabled? This would be needed for a check if IIS
> > > > > > > > is installed at the onset of our processes.
>
> > > > > > > > Any help GREATLY APPRECIATED!
>
> > > > > > > Yes, you can unattend install IIS and its components, including
> > > > > > > ASP.Net. You can do this for all IIS versions, though the instructions
> > > > > > > can differ. appwiz.cpl is not a good solution; it is just slightly
> > > > > > > better than doing nothing about pre-requisites. There is a single
> > > > > > > magic command to unattend install IIS6, and there is another magic
> > > > > > > command to unattend install IIS7. Both commands are publicly
> > > > > > > documented on MSDN.
>
> > > > > > > Determining ASP.Net Web Service Extension is not required on IIS7. It
> > > > > > > is required only if you run ASP.Net pages in "Classic" Managed
> > > > > > > Pipeline Mode. That mode is not the default, so you need to rethink
> > > > > > > your requirement to always enable ASP.Net Web Service Extension.
>
> > > > > > > There is no documented way to detect the selection status of various
> > > > > > > Windows Features of IIS7. There is an undocumented backdoor way.
>
> > > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > > > //- Hide quoted text -
>
> > > > > > > - Show quoted text -
>
> > > > > > For the unattended processes involving IIS 7, are you referring to
> > > > > > Pkgmgr.exe? If so, I guess I would have to formulate and use an .xml
> > > > > > file with this, similar to that shown here...
>
> > > > > >http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=959(L onghorn
> > > > > > Server example).
>
> > > > > > I guess what I would like to have happen is to check for IIS 5, 6, or
> > > > > > 7. If none exist (IIS 7 on Longhorn) on Windows Server 2008
> > > > > > (Longhorn), it would be nice if I could fire off the IIS setup, which
> > > > > > would have to include any ASP.NET 'Features', I guess.
>
> > > > > > The only problem is I don't know how to ensure the .xml file will take
> > > > > > care of all this. In looking at the example for Longhorn server at
> > > > > > the above link, I see that is appears that ASP.NET will be installed.
>
> > > > > > I guess I'll give this a shot on a Virtual Image I have for testing
> > > > > > and take a look.
>
> > > > > > Just let me know if this is the unattended path you were hinting
> > > > > > at. ;)
>
> > > > > > THANKS FOR THE HELP (so far, as I'm sure I'll need more).- Hide quoted text -
>
> > > > > > - Show quoted text -
>
> > > > > If this pkgmgr.exe is the method to which you refer, I have another
> > > > > question regarding the use of the .xml file. From the link provided,
> > > > > it is documented that the version entry must be changed to match the
> > > > > target machine....
>
> > > > > > > > > > name="Microsoft-Windows-Foundation-Package"
> > > > > version="6.0.6001.16510"
> > > > > language="neutral"
> > > > > processorArchitecture="x86"
> > > > > publicKeyToken="31bf3856ad364e35"
> > > > > versionScope="nonSxS"
> > > > > />
>
> > > > > My question then, would be how could I make the use of the .xml file
> > > > > universal, if it is possible at all. If not, how could I use pkgmgr
> > > > > to simply install IIS 7 with ASP.NET? I'm not sure of the command
> > > > > line to use as a minimum for our purposes, I guess is what it really
> > > > > boils down to. This is, of course, if we can't use the .xml file
> > > > > universally for VISTA Longhorn.
>
> > > > > THANKS AGAIN!- Hide quoted text -
>
> > > > > - Show quoted text -
>
> > > > To keep things interesting, instructions are totally different and
> > > > incompatible between IIS7 and IIS6/IIS5. And you don't want to use the
> > > > XML file because it needs the perfect version number.
>
> > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > //- Hide quoted text -
>
> > > > - Show quoted text -
>
> > > So, I guess I would have to use the pkgmgr.exe and the exact
> > > Windows_Feature_Name from the command line then. ??
>
> > > If this is the case, is there anything special I have to do to ensure
> > > ASP.NET and any pre-requisites (for ASP.NET) are installed as well?
>
> > > THANKS FOR THE INFO! :)- Hide quoted text -
>
> > > - Show quoted text -
>
> > ASP.Net 1.1 is preinstalled on Windows Server 2003, and ASP.Net 2.0 is
> > preinstalled on Vista. Unattend installation mechanism for both IIS6
> > and IIS7 will be able to deal with ASP.Net, and you don't need to do
> > anything special.
>
> > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > //- Hide quoted text -
>
> > - Show quoted text -
>
> I came across ServerManagerCmd.exe to accomplish what I need, I think.
>
> What I'll do from our install wrapper is to fire a little utility I
> made to execute this .exe with the -query parameter to dump the
> current Role/Role Services configuration to an .xml file. I'll then
> check the state of each of my requirements (Web Server (IIS), ASP.NET,
> and IIS 6 Mgmt Compatibility) by reading through the various entries.
>
> I believe I can even install any missing components via
> ServiceManagerCmd as well. Currently, if something is missing I'm
> just going to fire CmpMgmtLauncher and have the user double check the
> requirements. Eventually we may change to the automated approach, but
> that's not my call at this point.
>
> Let me know what you think of this approach of detecting inadequacies
> in IIS 7.
>
> THANKS!!- Hide quoted text -
>
> - Show quoted text -


That should be sufficient for IIS7. A similar trick works for IIS6
with sysocmgr.exe


//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//

Re: IIS 7 Detection and Automating Some Tasks

On Sep 7, 4:49 am, David Wang wrote:
> On Sep 6, 10:25 am,Superfreak3 wrote:
>
>
>
>
>
> > On Sep 6, 7:28 am, David Wang wrote:
>
> > > On Sep 5, 5:39 am,Superfreak3 wrote:
>
> > > > On Sep 4, 9:28 pm, David Wang wrote:
>
> > > > > On Sep 4, 1:29 pm,Superfreak3 wrote:
>
> > > > > > On Sep 4, 10:32 am,Superfreak3 wrote:
>
> > > > > > > On Aug 31, 6:06 pm, David Wang wrote:
>
> > > > > > > > On Aug 31, 8:15 am,Superfreak3 wrote:
>
> > > > > > > > > We have some IIS prerequisites to our web application installation...
>
> > > > > > > > > First, we check the following registry entry to see that IIS is
> > > > > > > > > installed: HKEY_LOCAL_MACHINE, "Software\\Microsoft\\InetStp",
> > > > > > > > > "MajorVersion" .
>
> > > > > > > > > This appears to be OK for detecting if IIS 7 is insttalled during
> > > > > > > > > initial testing. ??
>
> > > > > > > > > If installed, we check to see that the 2.0 ASP.NET Web Service
> > > > > > > > > Extension is present and enabled. This I do not know how to make
> > > > > > > > > changes for to have proper functionality in IIS 7. ??
>
> > > > > > > > > If we detect that that IIS is not installed, we open the Add Windows
> > > > > > > > > Components applet (appwiz.cpl,,2) and instruct to install the Internet
> > > > > > > > > Information Services. This, of course, is for pre Longhorn OSs.
>
> > > > > > > > > If I simply use appwiz in this environment, that will open the
> > > > > > > > > Programs and Features applet. From there, the user could select 'Turn
> > > > > > > > > Windows Features on or off'. This will then start the Server Manager
> > > > > > > > > where the Role (Web Server (IIS)) could be added along with any sub
> > > > > > > > > services.
>
> > > > > > > > > Question: Is there a way that I can simply start the Server Manager
> > > > > > > > > via a shortcut akin to appwiz?
> > > > > > > > > Question: If I add ASP.NET in this manner (sub service of IIS), will
> > > > > > > > > this be the same as adding and enabling the pre-Longhorn Web Service
> > > > > > > > > Extension?
>
> > > > > > > > > Also, is there a programmatic way I can determine if the ASP.NET
> > > > > > > > > extension is present/enabled? This would be needed for a check if IIS
> > > > > > > > > is installed at the onset of our processes.
>
> > > > > > > > > Any help GREATLY APPRECIATED!
>
> > > > > > > > Yes, you can unattend install IIS and its components, including
> > > > > > > > ASP.Net. You can do this for all IIS versions, though the instructions
> > > > > > > > can differ. appwiz.cpl is not a good solution; it is just slightly
> > > > > > > > better than doing nothing about pre-requisites. There is a single
> > > > > > > > magic command to unattend install IIS6, and there is another magic
> > > > > > > > command to unattend install IIS7. Both commands are publicly
> > > > > > > > documented on MSDN.
>
> > > > > > > > Determining ASP.Net Web Service Extension is not required on IIS7. It
> > > > > > > > is required only if you run ASP.Net pages in "Classic" Managed
> > > > > > > > Pipeline Mode. That mode is not the default, so you need to rethink
> > > > > > > > your requirement to always enable ASP.Net Web Service Extension.
>
> > > > > > > > There is no documented way to detect the selection status of various
> > > > > > > > Windows Features of IIS7. There is an undocumented backdoor way.
>
> > > > > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > > > > //- Hide quoted text -
>
> > > > > > > > - Show quoted text -
>
> > > > > > > For the unattended processes involving IIS 7, are you referring to
> > > > > > > Pkgmgr.exe? If so, I guess I would have to formulate and use an .xml
> > > > > > > file with this, similar to that shown here...
>
> > > > > > >http://www.iis.net/default.aspx?tabid=2&subtabid=25&i=959(L onghorn
> > > > > > > Server example).
>
> > > > > > > I guess what I would like to have happen is to check for IIS 5, 6, or
> > > > > > > 7. If none exist (IIS 7 on Longhorn) on Windows Server 2008
> > > > > > > (Longhorn), it would be nice if I could fire off the IIS setup, which
> > > > > > > would have to include any ASP.NET 'Features', I guess.
>
> > > > > > > The only problem is I don't know how to ensure the .xml file will take
> > > > > > > care of all this. In looking at the example for Longhorn server at
> > > > > > > the above link, I see that is appears that ASP.NET will be installed.
>
> > > > > > > I guess I'll give this a shot on a Virtual Image I have for testing
> > > > > > > and take a look.
>
> > > > > > > Just let me know if this is the unattended path you were hinting
> > > > > > > at. ;)
>
> > > > > > > THANKS FOR THE HELP (so far, as I'm sure I'll need more).- Hide quoted text -
>
> > > > > > > - Show quoted text -
>
> > > > > > If this pkgmgr.exe is the method to which you refer, I have another
> > > > > > question regarding the use of the .xml file. From the link provided,
> > > > > > it is documented that the version entry must be changed to match the
> > > > > > target machine....
>
> > > > > > > > > > > > name="Microsoft-Windows-Foundation-Package"
> > > > > > version="6.0.6001.16510"
> > > > > > language="neutral"
> > > > > > processorArchitecture="x86"
> > > > > > publicKeyToken="31bf3856ad364e35"
> > > > > > versionScope="nonSxS"
> > > > > > />
>
> > > > > > My question then, would be how could I make the use of the .xml file
> > > > > > universal, if it is possible at all. If not, how could I use pkgmgr
> > > > > > to simply install IIS 7 with ASP.NET? I'm not sure of the command
> > > > > > line to use as a minimum for our purposes, I guess is what it really
> > > > > > boils down to. This is, of course, if we can't use the .xml file
> > > > > > universally for VISTA Longhorn.
>
> > > > > > THANKS AGAIN!- Hide quoted text -
>
> > > > > > - Show quoted text -
>
> > > > > To keep things interesting, instructions are totally different and
> > > > > incompatible between IIS7 and IIS6/IIS5. And you don't want to use the
> > > > > XML file because it needs the perfect version number.
>
> > > > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > > > //- Hide quoted text -
>
> > > > > - Show quoted text -
>
> > > > So, I guess I would have to use the pkgmgr.exe and the exact
> > > > Windows_Feature_Name from the command line then. ??
>
> > > > If this is the case, is there anything special I have to do to ensure
> > > > ASP.NET and any pre-requisites (for ASP.NET) are installed as well?
>
> > > > THANKS FOR THE INFO! :)- Hide quoted text -
>
> > > > - Show quoted text -
>
> > > ASP.Net 1.1 is preinstalled on Windows Server 2003, and ASP.Net 2.0 is
> > > preinstalled on Vista. Unattend installation mechanism for both IIS6
> > > and IIS7 will be able to deal with ASP.Net, and you don't need to do
> > > anything special.
>
> > > //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> > > //- Hide quoted text -
>
> > > - Show quoted text -
>
> > I came across ServerManagerCmd.exe to accomplish what I need, I think.
>
> > What I'll do from our install wrapper is to fire a little utility I
> > made to execute this .exe with the -query parameter to dump the
> > current Role/Role Services configuration to an .xml file. I'll then
> > check the state of each of my requirements (Web Server (IIS), ASP.NET,
> > and IIS 6 Mgmt Compatibility) by reading through the various entries.
>
> > I believe I can even install any missing components via
> > ServiceManagerCmd as well. Currently, if something is missing I'm
> > just going to fire CmpMgmtLauncher and have the user double check the
> > requirements. Eventually we may change to the automated approach, but
> > that's not my call at this point.
>
> > Let me know what you think of this approach of detecting inadequacies
> > in IIS 7.
>
> > THANKS!!- Hide quoted text -
>
> > - Show quoted text -
>
> That should be sufficient for IIS7. A similar trick works for IIS6
> with sysocmgr.exe
>
> //Davidhttp://w3-4u.blogspot.comhttp://blogs.msdn.com/David. Wang
> //- Hide quoted text -
>
> - Show quoted text -

Ah, similar of 6. NICE. Thanks!