Changing how ITs done


Praising CLI (Command Line Interface)

Posted by Sean McCall on June 23, 2011 at 2:18 PM

Nothing beats being able to fully script exactly what you want to do, and that’s what the CLI is good for. A lot of the time it also lets you view things a GUI wouldn’t (Although should in a lot of cases). Running something via CLI usually has performance advantages as well, and unlike some GUIs (e.g. Explorer.exe) one hose up doesn’t prevent you from using everything else (e.g. A locked up file copy). One of the first things I do personally on a Windows box is force cmd.exe to open with Administrative credentials. This is both a convenience & prevents limited users from fooling around. I also like to run a .reg with the following:

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\Environment]
“Prompt”=[%computername%\%username%] $_$p$g

That way I know when I’m executing a command on my local machine or remotely. There are so many useful commands, a good handful for networking are:

getmac /S (Find out the MAC address of a remote machine)

net time /domain:domain.name.com /set (Sync system time with the DC)

ping -a ::1 (Ping & attempt to resolve host name (Using IP6 localhost since it’s super short))

pathping (Basically see where hose ups are when trying to connect to a host)

ipconfig /displaydns (See what sites users may have been going to, even if they delete there history)

arp -d (Good to run on all clients if a NIC was just switched out on a server, etc.)

            server serverIP
            settype=SRV (Standard probe for DNS server info)

netsh wlan show networks interface=”Wireless Network Connection” mode=bssid (CLI version of nearby wireless networks, it tells a whole lot more than the GUI)

Categories: None

Post a Comment


Oops, you forgot something.


The words you entered did not match the given text. Please try again.

Already a member? Sign In