Bill Swallow wrote:
> Did I miss something in your reply? It looks like the only thing you sent me
> is a link to an atricle explaining how to run adsutil.vbs, and pointing out
> that I need to be an admin to run it.
>
> Did you even bother READING my question? It doesn't look like it.
>
> LISTEN UP: 1) I installed SP3 (from a local copy on the C: drive) on top of
> XP Pro with SP2. This installation was apparently successful.
>
> 2) I have local copies of the XP Pro/SP2 install kit, and the SP3 install
> kit, on the C: drive. I set the Registry to point to these locations so I
> wouldn't need to find install disks when I made changes.
>
> 3) I (tried to) turn on IIS as part of building the baseline image for my
> software developers.
>
> 4) This attempt failed because it can't find the adsutil.vbs file; it's
> asking for my SP3 CD. That didn't help.
>
> 5) I searched the C: drive, making sure to search *everything* (hidden and
> system files, too). THERE IS NO ADSUTIL.VB* FILE ANYWHERE ON THE C: DRIVE.
>
> 6) I asked you if I did something wrong, or if there was a problem with SP3.
> I did NOT ask you how to run adsutil.vbs.
>
> Please read the question and answer the question that is asked, not give
> some knee-jerk response to the question you think I asked.
>
I installed WinXP from a hard drive (i386 folder), and so my
install files are still around. This is what I found in a
search of those files. The file in question is inside a CAB.
When extracted, this is what I got.
D:\I386\IIS6.CAB
IIS_adsutil.htm 5,547 bytes
IIS_adsutil.vbs 93,538 bytes
My CD is a WinXP SP3 OEM, purchased recently. So SP3
is already integrated.
This is the text copied from the contents of the HTM.
*******
IIS Administration Script Utility (adsutil)
Summary:
This is an IIS administration utility that uses VBScript with
Active Directory Service Interfaces (ADSI) to manipulate the
IIS configuration. This script should be run using CScript,
which is installed with Windows Script Host.
Usage:
Cscript.exe adsutil.vbs COMMAND <path> [<param>...]
Cscript.exe adsutil.vbs COMMAND [<path> [<parameters>...]]
Commands:
GET Path Display chosen parameter.
SET Path Value Assign a new value.
ENUM path "/P" Enumerate all parameters for the path.
/P - Enumerate the paths only (no data).
ENUM_ALL "/P" Enumerate all parameters.
/P - Enumerate the paths only (no data).
DELETE path Delete the path or parameter.
CREATE path [KeyType] Create the path and assign it the KeyType.
APPCREATEINPROC Path Create an in-process application.
APPCREATEOUTPROC Path Create an out-of-process application.
APPDELETE Path Delete the application (if present).
APPUNLOAD Path Unload an out-of-process application.
APPGETSTATUS Path Get status of the application.
FIND Path Find the paths where a parameter is set.
START_SERVER Path Starts the server.
STOP_SERVER Path Stop the Web site.
PAUSE_SERVER Path Pause the Web site.
CONTINUE_SERVER Path Unpauses the Web site.
HELP Prints all available commands.
Notes
* <Path> is the path of the node at which you are setting
the property combined with the name of the property you
are setting. For example, if you want to set the
ServerComment for Web server number 1, the command would
be as follows:
adsutil SET w3svc/1/ServerComment "Web Server Number 1"
The next time the IIS snap-in is opened, it will reflect
the name of the Web server as "Web Server Number 1"
* The switch "-s:server name" can be used after any command
to execute the command on a remote computer. (See first
example below.)
Examples:
Cscript.exe adsutil.vbs GET W3SVC/1/ServerBindings -s:remotecomputer1
Cscript.exe adsutil.vbs SET W3SVC/1/ServerBindings ":81:"
Cscript.exe adsutil.vbs CREATE W3SVC/1/Root/MyVdir "IIsWebVirtualDir"
Cscript.exe adsutil.vbs START_SERVER W3SVC/1
Cscript.exe adsutil.vbs ENUM /P W3SVC
*******
That is all that showed up. It isn't on my C: drive, because
IIS isn't installed as a Windows component.
Paul
Similar Threads
