21–30 of 118 posts
--92 percent fewer critical bulletins
--80 percent fewer reboots
I can easily shut off a service in Linux. And I can turn it on. The only reboot needed is for the Kernel itself, and that is soon changing.
What I'm reading here is that MS is most of the way there to Linux.
92 % fewer security bulletins and 80% fewer reboots. One can hope that's not just promise.
Microsoft has a real hole in their stack in my opinion... So on Linux you have SSH (for shell) and X11 Forwarding/VNC for GUI remoting. On Windows you have RDP for GUI and nothing for remote shell. Now, I know what you're going to say, "WMI" but WMI was never designed for use over the internet. You have to forward two fixed ports and a dynamic range (shudder). Plus it isn't security hardened either by design or throu…
> We are improving remote manageability via PowerShell with Desired State Configuration as well as remote file transfer, remote script authoring and remote debugging Is PowerShell not what you're looking for, or is it not implemented similar to SSH?
Also setting it up to work over the internet securely is, a touch complicated: http://blogs.technet.com/b/askpfeplat/archive/2012/09/17/wan...
It is a cool party trick that it can work via a web-browser and IIS. But if that's what it takes to make Powershell remoting secure without a VPN then it isn't workable.
Microsoft has a real hole in their stack in my opinion... So on Linux you have SSH (for shell) and X11 Forwarding/VNC for GUI remoting. On Windows you have RDP for GUI and nothing for remote shell. Now, I know what you're going to say, "WMI" but WMI was never designed for use over the internet. You have to forward two fixed ports and a dynamic range (shudder). Plus it isn't security hardened either by design or throu…
Earlier quoted context omitted.
PowerShell web access might be a good alternative: http://blogs.technet.com/b/askperf/archive/2012/11/05/window...
You don't need this. You just need Enter-PSSession [ipaddress], which allows you to interact with it like ssh. You need to enable powershell remoting first though.
Earlier quoted context omitted.
PowerShell web access might be a good alternative: http://blogs.technet.com/b/askperf/archive/2012/11/05/window...
You don't need this. You just need Enter-PSSession [ipaddress], which allows you to interact with it like ssh. You need to enable powershell remoting first though.
Microsoft has a real hole in their stack in my opinion... So on Linux you have SSH (for shell) and X11 Forwarding/VNC for GUI remoting. On Windows you have RDP for GUI and nothing for remote shell. Now, I know what you're going to say, "WMI" but WMI was never designed for use over the internet. You have to forward two fixed ports and a dynamic range (shudder). Plus it isn't security hardened either by design or throu…
SSH access to PowerShell would be a game changer IMHO for Microsoft. Also, have you seen this? http://www.powershellserver.com/download/
Happy to see Microsoft is evolving. Let's hope it will be for everyone's best.
Earlier quoted context omitted.
You don't need this. You just need Enter-PSSession [ipaddress], which allows you to interact with it like ssh. You need to enable powershell remoting first though.
That's not true. I had it working over the internet, separate domains with public/private certs fairly easily.
Guides like https://wprogramming.wordpress.com/2011/07/11/remote-pssessi... don't seem "fairly easy" to me (that's why I said it requires a lot more configuration compared to Enter-PSSession when both parties are in the same domain).
Earlier quoted context omitted.
That's not true. I had it working over the internet, separate domains with public/private certs fairly easily.
I'd be interested in how you set it up, can you maybe share it somewhere? Guides like https://wprogramming.wordpress.com/2011/07/11/remote-pssessi... don't seem "fairly easy" to me (that's why I said it requires a lot more configuration compared to Enter-PSSession when both parties are in the same domain).
It's essentially, Enable-PSRemoting
And commands 1 to 3 in the following guide after Enable-PSRemoting. Try to ignore the waffle. You probably do want to to disable HTTP though.
http://www.sirchristian.net/blog/2013/03/11/using-powershell...
Trying to get SSH to work with certs can involve just as much or more stuff than that.
Maybe i'll write a super simple guide, just listing the bare commands, since the documentation/tutorials for powershell seem non-existent despite being pretty powerful..