Niklas Aldergren wrote:
On 31 Jan 2007 03:34:29 -0000, Greg Ercolano <erco@(email surpressed)> wrote:
[posted to rush.general]
The downside here is that the password is in clear-text in install.bat
so protect the installation point appropriately.
The problem I recall with instsrv is that if you supply
the -a/-p flags, they'll only work if the service is not
currently installed.
So to make a /change/, you must first remove the service
with 'instsrv Rushd remove', then re-create it with
'instsrv Rushd c:\rush\etc\bin\srvany.exe -a .\render -p render',
and then re-apply the registry settings for the command line
arguments.
I think an approach I can take is to make the install.bat
take optional <USERNAME> and <PASSWORD> settings on the
command line, eg:
install.bat -user .\render -pass render
So that if those flags are specified, the script will pass
the -a/-p flags to instsrv.
I'll do some tests.
Either that, or I can have the script call SC.EXE to do
the job more easily.
Be aware that the account you specify must have the 'log on as a
service' right.
Both the SC command (if available), and the instsrv command
will do this automagically. In the case of instsrv, it seems
you must first remove then re-create the service and re-apply
the registry settings, eg:
instsrv Rushd remove
instsrv Rushd c:\rush\etc\bin\srvany.exe -a .\render -p render
reg add HKLM\System\CurrentControlSet\Services\rushd\Parameters
reg add HKLM\System\CurrentControlSet\Services\rushd\Parameters\Application=c:\rush\bin\rushd.exe
..which would set up the rushd service to run as 'render',
password 'render'.
SC is a little bit easier if all you want to do is change
the username/password.
I'll follow up to this thread if I find this works well across
all the windows platforms.
|