RunServices doesn't work

[Guest]

Hi,

I want to execute a command line when the computer has finished booting.
I formerly used a scheduled task, but for deployment purposes I would prefer
using the RunServices registry key.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunServices

I put the same command line in the the Run key and it does work each time
someone logs on :
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run

I had to create the RunServices key myself because it wasn't there, I also
checked access rights with regedt32, they are the same for both keys.

Why is RunServices apparently not triggered, is there any log somewhere ?

thanks for any help...

 

[Mark V]

Hi,

I want to execute a command line when the computer has finished
booting. I formerly used a scheduled task, but for deployment
purposes I would prefer using the RunServices registry key.

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\RunS
ervices

I put the same command line in the the Run key and it does work
each time someone logs on :
HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Run

I had to create the RunServices key myself because it wasn't
there, I also checked access rights with regedt32, they are the
same for both keys.

Why is RunServices apparently not triggered, is there any log
somewhere ?

What OS?

\RunServices\ is not used in NTx operating systems.

Your application would need to actually be a Service and
"installed" (or wrapped (SvrAny)). This does not sound like the
case there.

Say more about the application purpose and when is needs to run.
Possibly a System Startup Script start method would be appropriate?

 

[Guest]

It's on Windows 2000

I'm surprised it's not supposed to work for this OS because according to
this article it supposed to :
http://support.microsoft.com/?scid=kb;en-us;179365&x=9&y=5

My command line is :
"C:\Program Files\Bginfo\Bginfo.exe" /timer:0 "C:\Program
Files\BgInfo\myinfo.bgi"

BgInfo changes the desktop wallpaper and displays usefull info on it.
On servers, it is very cool to have it updated at boot time, and at each
user logon (including terminal services). I previously use a scheduled task,
but for ease of deployment I thought registry keys were better. BTW, a
scheduled task with double schedule (at startup and at logon would not
suffice when connecting from terminal services).

 

[David H. Lipman]

From: "vLabz" <[email protected]>

| It's on Windows 2000
|
| I'm surprised it's not supposed to work for this OS because according to
| this article it supposed to :
| http://support.microsoft.com/?scid=kb;en-us;179365&x=9&y=5
|
| My command line is :
| "C:\Program Files\Bginfo\Bginfo.exe" /timer:0 "C:\Program
| Files\BgInfo\myinfo.bgi"
|
| BgInfo changes the desktop wallpaper and displays usefull info on it.
| On servers, it is very cool to have it updated at boot time, and at each
| user logon (including terminal services). I previously use a scheduled task,
| but for ease of deployment I thought registry keys were better. BTW, a
| scheduled task with double schedule (at startup and at logon would not
| suffice when connecting from terminal services).
|


Use the SC command to create an actuall NT Service.

sc create /?
Creates a service entry in the registry and Service Database.
SYNTAX:
sc create [service name] [binPath= ] <option1> <option2>...
CREATE OPTIONS:
NOTE: The option name includes the equal sign.
type= <own|share|interact|kernel|filesys|rec|error>
(default = own)
start= <boot|system|auto|demand|disabled|error>
(default = demand)
error= <normal|severe|critical|error|ignore>
(default = normal)
binPath= <BinaryPathName>
group= <LoadOrderGroup>
tag= <yes|no>
depend= <Dependencies(separated by / (forward slash))>
obj= <AccountName|ObjectName>
(default = LocalSystem)
DisplayName= <display name>
password= <password>

 

[Mark V]

It's on Windows 2000

I'm surprised it's not supposed to work for this OS because
according to this article it supposed to :
http://support.microsoft.com/?scid=kb;en-us;179365&x=9&y=5

Hmmm. Well, NTx has a Service Control Manager... I think that KB
article is deficient FWIW.

My command line is :
"C:\Program Files\Bginfo\Bginfo.exe" /timer:0 "C:\Program
Files\BgInfo\myinfo.bgi"

Okay, the Sysinternals site
http://www.sysinternals.com/utilities/bginfo.html
suggests STARTUP folder (per user) for automated per-user startup.
Is that not a feasible option?

I guess I am wondering why you want to make it more difficult and
complex than this basic usage. BGINFO.EXE is not a Service and not
a System utility in the sense that it starts once per boot-up. As
I read it, this is a User-mode executable that should start per-
user when each account logs on. The user profile STARTUP location
would be my first choice. Otherwise the per-user (HKCU) \RUN\
registry location might be used, (or local or domain User Logon
Script perhaps).

BgInfo changes the desktop wallpaper and displays usefull info
on it. On servers, it is very cool to have it updated at boot
time, and at each user logon (including terminal services). I
previously use a scheduled task, but for ease of deployment I
thought registry keys were better. BTW, a scheduled task with
double schedule (at startup and at logon would not suffice when
connecting from terminal services).

I apologize in advance if I am missing something simply because I
have not used BGINFO in many years or on a TS system. Would a TS
user really need to update more than "at logon"?

I'll suggest the forum:
http://www.sysinternals.com/Forum/forum_topics.asp?FID=5
for more help on BGINFO specifics.