What the hell is that..
I could be a Nubbut I couldn't find anything on Google or on the forums on the subject. Is there a way to edit the default start-up state of a windows service in backtrack? Thanks heaps in advance
![]()
What the hell is that..
If you can't explain it simply, you don't understand it well enough -- Albert Einstein
I assume you mean "Is there a way to boot a Windows machine using BackTrack and then change the startup state of a Windows service?"
Its a fairly simple registry change, by editing the DWORD "Start" value under the following path in the SYSTEM hive
The SYSTEM hive file itself is stored under %SystemRoot%\system32\config\systemCode:\ControlSet<controlset#>\Services\<service_name>\
This tool can do the registry modification under Linux
Offline NT Password & Registry Editor
Capitalisation is important. It's the difference between "Helping your brother Jack off a horse" and "Helping your brother jack off a horse".
The Forum Rules, Forum FAQ and the BackTrack Wiki... learn them, love them, live them.
or you cann use sc.exe that is in windows
DESCRIPTION:
SC is a command line program used for communicating with the
NT Service Controller and services.
USAGE:
sc <server> [command] [service name] <option1> <option2>...
The option <server> has the form "\\ServerName"
Further help on commands can be obtained by typing: "sc [command]"
Commands:
ozzy
Yeah, that was the way I'd read it, too. Apparently, the others had not.
I still maintain that the person doing this had better have a damned good idea of what they're doing with the registry. One "simple" change can leave a Windows machine unbootable, if it's done in the wrong spot, or to the wrong entry.
Thorn
Stop the TSA now! Boycott the airlines.
Yes.... I had to think for a bit before I came to that conclusion though.
True, it is possible to hose windows by changing the wrong registry key. However as registry changes go, this particular one is fairly simple.
Of course that doesnt mean that the potential consequences will be any less severe if the person making the change stuffs up.
The System hive would be a particularly bad one to corrupt for example, it would be bad to accidentally delete some of the services keys or set them to disabled (some relate to system drivers), etc, etc. It comes with the territory when editing the registry though. Hopefully the OP is aware of that.
I assume that if someone asks for a way to do something they are aware of the potential consequences of getting it wrong. That assumption may not be warranted for some people, but if the only potential downside is of them breaking their Windows machine then I generally wont go out of my way to provide a warning or otherwise baby-sit them. (Especially considering that Windows systems are quite capable of breaking all on their own anyway).
That experience may even provide someone a valuable life lesson on taking backups before making important system changes.![]()
Capitalisation is important. It's the difference between "Helping your brother Jack off a horse" and "Helping your brother jack off a horse".
The Forum Rules, Forum FAQ and the BackTrack Wiki... learn them, love them, live them.