Group Policy perhaps?
"You can give users access to the command line without giving them privileges to run amok. I confess to not remembering exactly how, but it can indeed be done."
I know that in W7, there is a "Run as administrator" option in the context menu (I have mine set to open as administrator by default).
I assume you can remove that using Group Policies.
I was responding to apotheon's post:
"Ultimately, "regular" users should probably learn the CLI as well, because otherwise they're missing out on a lot of functionality ..."
I personally think that regular users should be able to perform all of their tasks using simple GUI tools.
That said, there is probably some value in showing people how to use "ping" to test their network connectivity (for example) since MS didn't provide a simple GUI tool for it.
My Sys Tray network icon seems to have no idea about the actual network status (when I run VMware Workstation, it indicates that the network has failed).
The Windows "Network and Sharing Center" doesn't show any useful information on it's default page (you have to burrow into it, to find out the basic information that "ipconfig" would show you).
Why doesn't "Network Connections" show that information by default?
Who needs room to display >50 network adapters on an home/office PC?
Why isn't there a simple, easy to access GUI tool for that?
It could show you the default "ipconfig" information.
The "ping" section would only need a few buttons (e.g. "Local Host - your PC", "Gateway", etc.) and a field to enter network/website names.
The Gnome Network Manager (in Ubuntu 10.04) trumps W7 in this case.
It has a "Connection Information" option in its context menu, which displays the basic information.
