4 ms·

I'd be happy to see Edit come back, but honestly I think MS wants people doing as little commandline as possible. In fact, there newest tactic is to hide confi

I'd be happy to see Edit come back, but honestly I think MS wants people doing as little commandline as possible. In fact, there newest tactic is to hide configuration changes they don't want users to mess with in commandline only powershell options that are typically poorly documented, and have odd syntax. maybe isn't malicious, but it feels like it.

pjmlp 3y ago
Not at all, that is Microsoft appealing to the UNIX culture, that everything should be headless on a server. Hence Windows Nano Server, and everything configuration setting being available via scripting. I thought HN would appreciate that.
- anthk 3y ago
  More than scripts, an hybrid web/scripting approach. You set up the settings in a web panel, and then you should be able to export the cfg/scripts to a zip file to be scripted/applied afterwards.
  - pjmlp 3y ago
    Like IIS used to have in the old days, ActiveX/ASP managed. Nowadays the new Windows Admin Center, https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/understand/what-is https://learn.microsoft.com/en-us/windows-server/manage/wind...
- bonton89 3y ago
  I personally have little interest in Windows servers these days. I'm more interested in automating painful settings and actions on my remaining Windows VMs that I use for some desktop applications or maintain just in case I need one in a pinch. One task I wanted to do was have my Windows VM boot in the night and install all updates before shutting down and creating a snapshot. Windows has a pretty jank update system but I was kind of shocked there is no command line way built into windows to trigger "run all the updates now". Despite their obsession with preventing people turning updates off and rebooting against user wishes they didn't build in a way to actually just run them on a controlled schedule. I ended up needing to install a 3rd party powershell package some one made to get this functionality which is ridiculous and arguably somewhat of a security risk.
conor- 3y ago
I think it feels like the inverse. It seems like MS wants people to use more CLI and has been retrofitting PowerShell as a full-fledged Windows administration layer. But the problem with it being retrofitted is it feels very clunky and difficult to explore. There's also Windows Terminal which seems like a genuine attempt at making interacting with shells in Windows less painful in general.
- Meph504 3y ago
  At a server side I would agree but from windows desktop it feels different, I should have clarified that.

pjmlp 3y ago

Not at all, that is Microsoft appealing to the UNIX culture, that everything should be headless on a server. Hence Windows Nano Server, and everything configuration setting being available via scripting. I thought HN would appreciate that.

anthk 3y ago
More than scripts, an hybrid web/scripting approach. You set up the settings in a web panel, and then you should be able to export the cfg/scripts to a zip file to be scripted/applied afterwards.
- pjmlp 3y ago
  Like IIS used to have in the old days, ActiveX/ASP managed. Nowadays the new Windows Admin Center, https://learn.microsoft.com/en-us/windows-server/manage/windows-admin-center/understand/what-is https://learn.microsoft.com/en-us/windows-server/manage/wind...
bonton89 3y ago
I personally have little interest in Windows servers these days. I'm more interested in automating painful settings and actions on my remaining Windows VMs that I use for some desktop applications or maintain just in case I need one in a pinch. One task I wanted to do was have my Windows VM boot in the night and install all updates before shutting down and creating a snapshot. Windows has a pretty jank update system but I was kind of shocked there is no command line way built into windows to trigger "run all the updates now". Despite their obsession with preventing people turning updates off and rebooting against user wishes they didn't build in a way to actually just run them on a controlled schedule. I ended up needing to install a 3rd party powershell package some one made to get this functionality which is ridiculous and arguably somewhat of a security risk.

conor- 3y ago

I think it feels like the inverse. It seems like MS wants people to use more CLI and has been retrofitting PowerShell as a full-fledged Windows administration layer. But the problem with it being retrofitted is it feels very clunky and difficult to explore. There's also Windows Terminal which seems like a genuine attempt at making interacting with shells in Windows less painful in general.

Meph504 3y ago
At a server side I would agree but from windows desktop it feels different, I should have clarified that.