On the Existence of net.exe
For years I have been bitching that Windows doesn't have an easy way to control services shy of opening up the control panel and going to "Administrative Tools" (or in any of a number of ways of using the GUI called "services.msc"). Years.
So why is it no one has ever told me about net.exe having a "start" option?
According to the MSDN Library, sc.exe is a much better tool for manipulating Windows services, and I agree. But I am talking about the merest of service control options: "stop" and "start", and you can do this with net.exe, which has been around since forever and which has had this functionality built into it for eons and I didn't know about this until last month.
Criminy. You'd think that with all my naying and braying about how miserable the command-line features in Windows are that someone would make a show of knocking me down off my high horse with the merest of "Try net stop service_name, dumbass" comments. You don't need sc.exe, you don't need "sasv" and "spsv" cmdlets. Now I feel like a total jackass.
Which is actually pretty normal for me.
No comments:
Post a Comment