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.
Sort of. Enter-PSSession is backed by http or https [1] and is not as good as ssh. You can interact with PowerShell, but you can't interact with command-line programs launched from PS. [1] Grep for "http" on this page: http://ss64.com/ps/enter-pssession.html
Microsoft Announces Nano Server
51–60 of 118 posts
Re: Microsoft Announces Nano Server
#52From this announcement: http://azure.microsoft.com/blog/2015/04/08/microsoft-unveils... I read: > Nano Server provides just the components you need – nothing else And that's exactly what I do not trust MS with. With a well documented history of backdoor ridden bloat ware products it is not quite the company that I accept any non-opensource release to have "just what I need and nothing else". Though I must admit that…
But some enterprises use MS software, and this is a much needed option.
ObVote: I downvoted your complaint imaginary internet points has no bearing on the discussion at hand.
Re: Microsoft Announces Nano Server
#53Microsoft 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…
MS should really include something like this in Windows.
Hell, I (or you) should find the time and write it ourselves, node.js has great TLS support and has a Windows port.
Re: Microsoft Announces Nano Server
#54What is the use-case for this? Modern Linux distros have all the tooling, libraries, utilities already - is the idea to use this for hosting .Net stuff?
Running stuff that requires Windows.
Re: Microsoft Announces Nano Server
#55Microsoft 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…
You are ignoring Windows Remote Management, Microsofts implementation of the WBEM standard protocol for remote management of devices. https://msdn.microsoft.com/en-us/library/aa384426(v=vs.85).a... "Windows Remote Management (WinRM) is the Microsoft implementation of WS-Management Protocol, a standard Simple Object Access Protocol (SOAP)-based, firewall-friendly protocol that allows hardware and operating systems, fr…
And, being SOAP-based, it's certainly nothing like a command-line.
But most of all, it's not fun.
Re: Microsoft Announces Nano Server
#56From this announcement: http://azure.microsoft.com/blog/2015/04/08/microsoft-unveils... I read: > Nano Server provides just the components you need – nothing else And that's exactly what I do not trust MS with. With a well documented history of backdoor ridden bloat ware products it is not quite the company that I accept any non-opensource release to have "just what I need and nothing else". Though I must admit that…
That's fine. Then this release (and frankly, any MS product) is not for you. But some enterprises use MS software, and this is a much needed option. ObVote: I downvoted your complaint imaginary internet points has no bearing on the discussion at hand.
I've certainly re-considered dotNet after it got open sourced recently! It (finally) seemed like a reasonable proposition -- as I explain in my post BTW.
But indeed, Windows, and especially Windows-closed-source-on-a-server, is not my cup of tea. And I don't understand how it could be anyone's tea.
> But some enterprises use MS software
Sure, and this is a start-up forum. :)
Anyway, I upvoted your post for taking the trouble to explain your downvote. Thanks.
Re: Microsoft Announces Nano Server
#57Earlier quoted context omitted.
Yeah, I believe their RPi version is a lightweight consumer-facing version of Windows 8, not intended for use as a server.
No, there's a lot of confusion from bad messaging with the Pi 2 and Windows 10 announcement. By all reports Win 10 on the Pi 2 is a system to run services that have no GUI, desktop, or other UI.
Take a look on Don Box's presentation at WinHEC from last month. Device talk stats about ~40 mins, device demo starts at ~44 mins.
http://channel9.msdn.com/Events/WinHEC/2015/Developing-for-t...
Re: Microsoft Announces Nano Server
#58From this announcement: http://azure.microsoft.com/blog/2015/04/08/microsoft-unveils... I read: > Nano Server provides just the components you need – nothing else And that's exactly what I do not trust MS with. With a well documented history of backdoor ridden bloat ware products it is not quite the company that I accept any non-opensource release to have "just what I need and nothing else". Though I must admit that…
Please down voter(s), leave a note.. :)
Re: Microsoft Announces Nano Server
#59Earlier quoted context omitted.
You are ignoring Windows Remote Management, Microsofts implementation of the WBEM standard protocol for remote management of devices. https://msdn.microsoft.com/en-us/library/aa384426(v=vs.85).a... "Windows Remote Management (WinRM) is the Microsoft implementation of WS-Management Protocol, a standard Simple Object Access Protocol (SOAP)-based, firewall-friendly protocol that allows hardware and operating systems, fr…
Have you ever tried using wsman? It is not fun. And, being SOAP-based, it's certainly nothing like a command-line. But most of all, it's not fun.
It was a bit arcane to set up but mainly it was slow, like, really slow. All the SOAP serialization is terrible for performance but it is flexible and it did work.
Re: Microsoft Announces Nano Server
#60Earlier quoted context omitted.
I hope it will cost a lot less. Might interesting for the C# people to use non-Azure clouds more if the costs are more inline with Linux based systems.
With MVC moving to a Linux compatible infrastructure in the next version, it may be too little too late, and C# people might just use Linux for real. Literally the only C# "thing" which won't run on Linux is Visual Studio itself. Heck we might even see a Linux Powershell version here in the next few years.
But for sever-side code, .net core + asp.net will get the job done.