Now all they have to do is switch their kernel to linux, their gui to kde and get their office suite to LibreOffice, and Windows will be the perfect computer.
kde and libreoffice are objectively worst though...
Windows Server 2019 Includes OpenSSH
181–190 of 296 posts
Re: Windows Server 2019 Includes OpenSSH
#182Earlier quoted context omitted.
My biggest complaints with Windows are the spying on users, the forced updates on users, the registry still existing, and the NTFS file system still being the primary file system. The kernel is actually likable but would benefit from being open source and the GUI is a horrible blend of touch screen and legacy input hybridness that I wish never existed.
> the registry still existing You know that GNOME also has a registry, right? https://wiki.gnome.org/action/show/Projects/dconf
Based on multiple config files which makes it easier to manage.
Re: Windows Server 2019 Includes OpenSSH
#183Earlier quoted context omitted.
Microsoft has come a really long way recently towards moving to CLI-based management. Starting with Server 2016, the default installation method of Windows Server no longer includes most of the GUI (called the Desktop Experience), leaving you with a command prompt window in the middle of the screen instead. An even thinner version of Windows Server, Nano Server, is also available, and includes even less GUI, being mu…
They started on this in the late 2000s when I was an intern there. But there was a lot to untangle. It’s the biggest refactoring job you can imagine. A decade long effort. Back then they didn’t really understand the point of ssh though. They had a vision of remote management via .net RPC and powershell.
This makes you seem like you don't understand the point of PowerShell remoting.
Passing serialised scriptblocks to the remote host, executing them, and getting serialized objects back. Meaning you can pass serialisable objects around, handle errors, the multiple output streams, etc. over the remoting connection.
Because it's integrated into the language, you can pull PowerShell modules over from the remote host to the local host automatically generating proxy stubs for them ("implicit remoting"). E.g. to manage and Exchange server you can remote to it, and bring the Exchange cmdlets back, and then import them locally as if they were a local module.
It's also able to do that and edit the proxies as it builds them for you, to allow and restrict what commands you get - based on your permissions and perhaps which tier of service you're paying for. And not just allow or restrict commands, but allow or restrict individual parameters on those commands, if desired.
Re: Windows Server 2019 Includes OpenSSH
#184Now all they have to do is switch their kernel to linux, their gui to kde and get their office suite to LibreOffice, and Windows will be the perfect computer.
Windows ux is better out of the box than on any Linux so far, it's really polished. The office suite is also much better than alternatives. So just switching the kernel to Linux would be enough and super winrar.
True, windows is more polished. However with a dozen of devs and Microsoft's q&a facilities, it would not take more than 2 years for linux to get the same level of polish on the GUI side of things.
It has come such a long way in 15 years.
Re: Windows Server 2019 Includes OpenSSH
#185Earlier quoted context omitted.
I’ve been developing on and for Windows for 20 years and just started doing anything with Linux earlier this year. If you told me I had to do anything advanced with Windows using only a CLI, I wouldn’t know where to start. On the other hand, I could maneuver my way around a bash shell. I haven’t thought about that before now.....
I think it's time for MS to develop a new ANSI/VT-compliant, text-oriented shell (to complement PowerShell, which is largely object- and API-oriented). There ought to be a default shell worth using on the other end when you ssh into a Windows server :) cmd.exe and DOS were both text-oriented but extremely buggy and inconsistent. Perhaps MS could just focus on providing a very bash-like language (perhaps even include…
[deleted]
Re: Windows Server 2019 Includes OpenSSH
#186Earlier quoted context omitted.
They started on this in the late 2000s when I was an intern there. But there was a lot to untangle. It’s the biggest refactoring job you can imagine. A decade long effort. Back then they didn’t really understand the point of ssh though. They had a vision of remote management via .net RPC and powershell.
I dont know if that means they didnt understand it. It reads like they were trying to solve the underlying problems with a different approach. SSH is an awesome tool & capability as a relatively high level network channel. The defacto “shell” approach leads to a lot of problems when used as a management device. It encourages adhoc, unstructured, and opaque changes. Managing your hosts via Secure Shell simply leads to…
Where does your opinion on Ansible lie then? It's a systems configuration and orchestration tool that by default, uses SSH as the transport.
For Ansible users, Windows getting OpenSSH is a huge win, since we (presumably) will no longer have to jump through all the hoops WinRM throws you in order to configure Windows machines remotely.
Re: Windows Server 2019 Includes OpenSSH
#187Earlier quoted context omitted.
It's almost 2019. Are we still fighting over this? OTOH, purely from my experience, MS's tools are good for managing a domain, or some computers. When you start to administer hundreds or thousands of servers, scriptability of CLI tools and pliability of text files trumps all computer automation. xCAT and Salt are two tools (that I use regularly) which are built on these properties and can manage thousands of servers…
On that note, these administration issues are why Walmart & Kroger are on SUSE, much of the IT work you see smaller chains employing people to do has been automated away, or reduced to having any available employee follow a (very simple) guide on how to netboot the machine for re-imaging.
A very simple FAI or Kickstart server with small tools to enable provisioning can automate a lot of things in a non-IT oriented workspace.
A simple HTML form to "arm" the installation server, a simple reboot and PXE booting can be much more effective than all the painkillers combined for remedying the headaches of IT people and managers alike.
If you don't roll changes that often, you can distribute emergency USBs to install servers and workstations. Even a single USB can detect and install the system accordingly.
Re: Windows Server 2019 Includes OpenSSH
#188Does anyone know — sorry if I forget the correct terms — whether you can SSH with pub key auth and perform operations that require elevated permissions, such as disk resizing?
I have some vague memory of limitations in earlier versions, with distinct differences between password auth and key auth.
Re: Windows Server 2019 Includes OpenSSH
#189Earlier quoted context omitted.
Because? What advantages does it offer?
Read Windows Internals. It's a very different design from Linux. Worth learning about another approach to operating systems if you're at all interested. WNT evolved (spiritually) from VMS and has a lot of unique things in its structure. Note also that Windows already kind of is a perfectly serviceable Linux kernel through WSL. That's one of the unique things about NT - it was designed for binary compatibility for pro…
> perfectly serviceable Linux kernel through WSL
Namespaces/cgroups?