If the entire Windows is based from PowerShell...


Recommended Posts

Sorry if this has been posted, I've read somewhere about this. It's said if the entire Windows is based from PowerShell, then Windows will be reimagined, from the way its work, there would be dramatical improvement, is that true?

Link to comment
Share on other sites

trying not to laugh.... you know they tried that with exchange already and only made things harder to do in a lot of respects only to add back in UI's for a lot of stuff to simplify it... sure powershell command for everything would be nice for automation but it does add a lot of complexity

Link to comment
Share on other sites

trying not to laugh.... you know they tried that with exchange already and only made things harder to do in a lot of respects only to add back in UI's for a lot of stuff to simplify it... sure powershell command for everything would be nice for automation but it does add a lot of complexity

 I'm really glad I didn't have to do much work with Exchange 2007, doing some of the things that was dead easy by Gui you'd have to look up the powershell commands for.  There are still things in powershell that I wish they'd put into Exchange's ECP.

Link to comment
Share on other sites

With SCCM there is supposed to be an alternative for everything that can be done in the GUI for automation, as mentioned already.

Most things are done MUCH easier in the GUI, though. We use it for importing users and creating accounts, passwords, etc., automatically, but that's about it.

Link to comment
Share on other sites

Sorry if this has been posted, I've read somewhere about this. It's said if the entire Windows is based from PowerShell, then Windows will be reimagined, from the way its work, there would be dramatical improvement, is that true?

Actually, you COULD (theoretically) run all of Windows from either sort of command line *today* - that is, in fact, how Hyper-V Server Core works (it has no GUI at all by default).  PowerShell has been part of both sides of Windows since the infamous XP Service Pack 2 - it was designed to be a unified scripting language across all of Windows.  You can launch PSE scripts and standard Windows executables from either a standard command line or a PSE shell - they are designed to be interchangeable (the same way that old-school third-party utilities TakeCommand and 4NT were interchangeable).

 

There are two problems with that approach - first, PowerShell is not well documented outside of servers (rather embarrassing for an all-around scripting language, which it is designed to be).  While core common commands (like DISM) are getting more and more documented with each release, they are treated like last-resort commands, even by Microsoft.  Second is the practicality side, and especially outside of servers - anyone with more than a passing interest in PowerShell documentation is lumped in with the old-school Runbox "gearheads" - all too many users would rather stick with what is comfortable - even IF it smacks of complacency.

Link to comment
Share on other sites

No thanks - would rather stick with the GUI. While Powershell would be indeed nice and powerful, it does add a lot of complexity though.

 

I'd still use the GUI interface, even in Windows Server.

Link to comment
Share on other sites

Having no gui is bad. Its like having your hands tied behind your back to your feet, while being blind folded underwater, while being upside down. Sure its possible to swim but why kill yourself trying to do it? Its just like with Ubuntu server, the first thing I do is install the damn gui. I hate being crippled when I should not have to be.

Link to comment
Share on other sites

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.