[no subject]
1996-04-17 14:28:38
OPTIONS: NOACK LOG SHORT NOTEBOOK ALL
Date: 17 April 1996, 13:47:20 EDT
From: Pete Tanenhaus, ADSM Client Development TANENHAU at GDLVM7
To: ADSM-L at VM.MARIST.EDU
Subject: srvinst utility
This utility eliminates the need to manually update the registry.
Installing the service creates the following registry entry in
the HKEY_LOCAL_MACHINE subtree:
System
CurrentControlSet
Services
ServiceName
where ServiceName is the name of the installed service.
SRVANY requires an addition key named Parameters to be added under
the ServiceNameKey with the REG_SZ values AppDirectory, Application,
and AppParameters.
The SRVINST utility should be used in place of (not in addition to)
the manual installation instructions specified in the readme file.
I apoligize if I didn't make this clear.
Before installing the service with SRVINST you should have the
following information:
- Fully qualified directory path of the ADSM NT (32-Bit Windows)
client. The default assumed by the utility is adsm32 on the
system partition. Note that if you are installing the service
on a remote machine the path should be in relative to that
machine.
If this is not correctly specified the service will be installed
but it will not start.
It can be corrected after the service has been installed by
changing a registry value (see below).
- Fully qualified path of the SRVANY.EXE utility. The default
taken is the NT System32 directory. See above note if the
service is being installed on a remote machine.
If this is not correctly specified the service will not
install.
- The name you want to use when installing the service. The
default is Adsm Scheduler Service.
- The ADSM node password. If this is not correct the service will
be installed and will start but the scheduler client will never
execute any schedules unless the ADSM server has authentication
turned off.
Use the SRVINST utility to install the service as follows:
1. Install the service (Option I).
- If the machine is remote, enter the remote machine
at the prompt. If it isn't, take the default.
- Specify the Service Name to install if something other
than the default is desired.
- Specify the fully qualified path of SRVANY.EXE relative
to the machine where the service is being installed.
- Specified (Yes or No) if you want the service to start when
the machine boots.
- Confirm that you want to install the service.
2. Update the SRVANY registry entries (option U)
- Confirm the name of the machine and the service name
that was just installed. These will already be set
to the values used in step 1.
- The registry values should now be displayed. Except for
the ImagePath values none of them should be set.
- Confirm that you want to update the registry entries
for this service.
- You will be prompted for the ADSM NT client directory.
Enter the fully qualified path relative to the machine on
which the service is being installed.
- You will be prompted for the ADSM password. Enter this value.
- Do not update the ImagePath value unless the location of the
SRVANY.EXE file has changed since the service was installed.
The service should now be correctly installed and ready to start.
It may now be started via the Services Control Panel or the NET START
command.
I hope this answers your questions and clarifies the use of this utility.
Pete Tanenhaus
ADSM Client Development
-------------------------------Original Append-------------------
From: Rusty Wright <rusty AT GROAN.BERKELEY DOT EDU>
Subject: adsm windows nt version 2r1m3 client install
To: Multiple recipients of list ADSM-L <ADSM-L AT VM.MARIST DOT EDU>
In the README file, under "running the nt scheduler as an nt service"
the instructions are a bit vague; they say that the utility
srvinst.exe is included to "aid in installing the client as a service"
but the instructions don't say just what "aid" srvinst.exe provides.
So I ran srvinst.exe and what it does conflicts with the instructions
that follow for manually installing adsm as a service; the manual
instructions say to edit the registry and add a Parameters key under
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/ADSM Scheduler
but the srvinst.exe program created the key "ADSM Scheduler Service"
(not "ADSM Scheduler"), and it placed it under
HKEY_LOCAL_MACHINE/SYSTEM/CurrentControlSet/Services
Also, srvinst.exe didn't create the Parameters key, so I had to go in
and manually add it and the three values as per the manual
installation instructions.
|
<Prev in Thread] |
Current Thread |
[Next in Thread> |
- [no subject],
Pete Tanenhaus, ADSM Client Development <=
|
|
|