setting a service to disabled

[Bill Uyer]

Is it possible to set a service to to be disabled from the command prompt
similar to the disable command from the recovery console? I am looking to
be able to change a service's startup type from the command prompt from
automatic to disabled and back. Thanks.

 

[Ray at]

Do you have the W2K Resource Kit? If so, take a look at sc.exe. If not,
post back.

Ray at work

 

[Matthias Tacke]

Is it possible to set a service to to be disabled from the command prompt
similar to the disable command from the recovery console? I am looking to
be able to change a service's startup type from the command prompt from
automatic to disabled and back. Thanks.

Have a look at psservice out of pstools from sysinternals

http://www.sysinternals.com/ntw2k/freeware/psservice.shtml

hth
Matthias

 

[Bill Uyer]

Ray

I do not have the Resource Kit can you help with sc.exe file. Thanks.

 

[Matthias Tacke]

Ray

I do not have the Resource Kit can you help with sc.exe file. Thanks.

http://www.dynawell.com/reskit/microsoft/win2000/sc.zip

Why don't you try the freeware from sysinternals?

Matthias

 

[Ray at]

I suggest not using a third party application for something that Microsoft
has a solution for. Download sc.exe and put it in one of your %path% paths,
and then enter a command as such:

sc \\remotemachine config browser start= disabled

Ray at work

 

[Mark V]

I suggest not using a third party application for something that
Microsoft has a solution for. Download sc.exe and put it in one
of your %path% paths, and then enter a command as such:

Item: The Resource Kit utilities are "disavowed" by MS anyway. And
are essentially "3rd-party tools". They do have that "MS" associated
with them though FWIW.

Item: Mark Russinovich and SysInternals have been around for ages and
have an excellent reputation.

PSSERVICE.EXE 2.1 is 4 years fresher than a freely downloadable
SC.EXE (NT4) and IMO works better.

Conclusion: Except for ignorant "house rules" in a corporate
setting, I can see no reason not to use the Sysinternals tool(s)
which are more frequently updated, free, easier to locate. and often
have greater capabilty. Not that owning the Resource Kits isn't a
good thing, just expensive.

sc \\remotemachine config browser start= disabled

 

[Ray at]

Item: The Resource Kit utilities are "disavowed" by MS anyway. And
are essentially "3rd-party tools". They do have that "MS" associated
with them though FWIW.

Yes, that is a very valid point. Remapkey.exe is a very good sample of
something that is obviously not a Microsoft creation... :]

Item: Mark Russinovich and SysInternals have been around for ages and
have an excellent reputation.

PSSERVICE.EXE 2.1 is 4 years fresher than a freely downloadable
SC.EXE (NT4) and IMO works better.

Conclusion: Except for ignorant "house rules" in a corporate
setting, I can see no reason not to use the Sysinternals tool(s)
which are more frequently updated, free, easier to locate. and often
have greater capabilty. Not that owning the Resource Kits isn't a
good thing, just expensive.

Sometimes this is true, and sometimes it isn't. I've just seen way too much
waste where I work where instead of taking the time to learn how to use
Windows tools to perform an action, we will go blow thousands of dollars on
some software package that basically just throws a GUI on top of some
Windows functionality.

Ray at work

 

[Mark V]

Item: The Resource Kit utilities are "disavowed" by MS anyway.
And are essentially "3rd-party tools". They do have that "MS"
associated with them though FWIW.

Yes, that is a very valid point. Remapkey.exe is a very good
sample of something that is obviously not a Microsoft creation...
:]

Item: Mark Russinovich and SysInternals have been around for ages
and have an excellent reputation.

PSSERVICE.EXE 2.1 is 4 years fresher than a freely downloadable
SC.EXE (NT4) and IMO works better.

Conclusion: Except for ignorant "house rules" in a corporate
setting, I can see no reason not to use the Sysinternals tool(s)
which are more frequently updated, free, easier to locate. and
often have greater capabilty. Not that owning the Resource Kits
isn't a good thing, just expensive.

Sometimes this is true, and sometimes it isn't. I've just seen
way too much waste where I work where instead of taking the time
to learn how to use Windows tools to perform an action, we will go
blow thousands of dollars on some software package that basically
just throws a GUI on top of some Windows functionality.

Too true and I've seen that as well. I guess my argument was too
focused on SC vs. PSSERVICE, ResKit vs. SysInternals quality
freeware. At least these days we get _some_ tools in the Support
Tool Pack.
Your point is well taken. ;-)