I havent replied but i hope you all enjoyed my tutorial. Its very indepth and covers some basic shit.
|
Shell
CLI(Command Line Interface) In-Depth/Easy To Follow/Detailed |
  (Jul 27, 2017 10:41 AM)x4x552 Wrote: You should focus on PowerShell as it's far more powerful. Just cause it says "power" doesnt mean ifs powerful xD  (Jul 28, 2017 02:28 PM)Dеath Wrote: Just cause it says "power" doesnt mean ifs powerful xD I beg to differ. Powershell IS much more powerful than Batch.  (Jul 28, 2017 02:28 PM)Dеath Wrote: Just cause it says "power" doesnt mean ifs powerful xD Batch is good if you don't know what PowerShell is. As soon as you get a real job managing multiple systems, batch quickly becomes irrelevant. Even PsExec is waning, as PowerShell can handle more with less, again, across multiple systems. ![[Image: pia_banner_3.png]](https://www.privateinternetaccess.com/affiliates/banners/pia_banner_3.png) 
Jul 30, 2017 06:01 PM
(This post was last modified: Jul 30, 2017 06:06 PM by motherfawker666.)
On accessing the Command Prompt:
You can use the 'WinKey + R' method on any Windows machine since XP. On Windows 8 and up you can use '[WinKey + X] A' to open an Admin prompt and '[WinKey + X] C' to open a non-elevated prompt. Also, the people here are right about PowerShell. In a real world job managing Windows machines you aren't really going to use Command Prompt. CMD is decent for doing some basic stuff on your own machine but its really not scalable. |
|
|
