
Seems that Redmond forgot to include most crucial tool in sysadmin’s job – a simple text mode editor. This overall is good news and great improvement since previous generations of Windows, but what if you need to create or edit a PowerShell, CMD script or some config file? Nowadays everything seems to be text mode.

Even System Center is a front end for PowerShell.

Just take a look at Server Core, WinPE, Nano, PS Remoting, Windows SSH server, Recovery Console and Emergency Management Services. No more wizards and forms, MMC and GUI based administration is suddenly thing of a past. I remember sitting through countless TechEd / Ignite sessions year after year and all I could see were blue PowerShell command prompts everywhere. Since 2012 or so Microsoft is pushing concept of running Windows Server headless without GUI and administering everything through PowerShell. (This is a guest post by Antoni Sawicki aka Tenox)
