231–240 of 296 posts
Thats nice. How about adding it to Windows 10?
The very first sentence of the article is: > The OpenSSH client and server are now available as a supported Feature-on-Demand in Windows Server 2019 and Windows 10 1809!
Earlier quoted context omitted.
Yes and no. Having used DSC and powershell remoting extensively, these create as many problems as they solve. Nothing works smoothly. Not a thing. The saving grace here will be SSH because then at least we can drive all our kit across both platforms from Ansible and be done with the entire MSFT management stack. At the moment we use Ansible but it runs over WinRM which is completely unreliable due to some architectur…
> Really, automation on Windows is extremely costly compared to Linux I'd disagree. I've been managing fleets of Windows machines since NT 3.51 (and fleets of Linux servers since 2003). It's all about knowing the tools well. Whilst I've been using Linux since around 1995 (Slackware!), and prior to that various Unix and Xenix(!) boxes had popped in and out of my IT life, I'd never managed more than one or two machines…
1. Remote management is totally unreliable. If I point DSC at 20 nodes via WinRM, 25% of the time it will fail on one of the nodes.
2. Everything takes glacial amounts of time to happen, from deployment and provisioning to simple cases like restarting processes. This is because Windows is simply so damn large.
3. There are so many edge cases and bits of tribal knowledge dotted all over stackoverflow which is sometimes the only way of finding out what the hell is going on, it's impossible to cover all of them through automation and nigh on impossible to document the rationale behind them.
4. Literally everything is stateful and state is difficult to synchronise and reload.
5. The disparity between major platform releases makes it extremely difficult to develop automation that isn't brittle and can span major windows versions. And because everything has all of the other concerns from coupling to bugs it's impossible to chop big chunks of your infrastructure over to new windows server versions. So you end up in permanent migration mode.
6. The sheer amount of bugs in some of the larger products like SCCM and SCVMM are just unbearable. SCVMM client for linux is a pile of shit and I'm being polite there.
All of these cost immense amount of wall clock time and staff attention which far outweighs the cost benefit of using the platform to start with at least from an application server business.
On the desktop, things are slightly better as it's the least bad desktop platform for corporates but that's changing. Even Microsoft know that which is why they are forcing people down the cloud route and selling subscriptions.
Earlier quoted context omitted.
Yes and no. Having used DSC and powershell remoting extensively, these create as many problems as they solve. Nothing works smoothly. Not a thing. The saving grace here will be SSH because then at least we can drive all our kit across both platforms from Ansible and be done with the entire MSFT management stack. At the moment we use Ansible but it runs over WinRM which is completely unreliable due to some architectur…
For managing desktops and not servers, Group Policy is still unbeaten. I have yet to see a unified strategy on Linux of being able to say, mount these drives on logon, show these applications, don't allow them to do x, change the background to y etc. Sure, managing linux servers is a doddle, but desktop environments are miles harder to get right.
That is what every single Windows environment I've seen turns into, including the SCCM powered and Microsoft direct consultancy managed ones.
Earlier quoted context omitted.
Yes and no. Having used DSC and powershell remoting extensively, these create as many problems as they solve. Nothing works smoothly. Not a thing. The saving grace here will be SSH because then at least we can drive all our kit across both platforms from Ansible and be done with the entire MSFT management stack. At the moment we use Ansible but it runs over WinRM which is completely unreliable due to some architectur…
>I've got to the point I never want to run Windows infrastructure again. Before anyone says "it's getting better". That has been the case from 10 years and it only got different. i know what you mean. It's part of the reason I'm on the cusp of discarding my 20ish years of MS SQL Server experience and going full Postie for the rest of my life. Windows IT infrastructure in most enterprises is a pile of lies. It's parti…
But people are totally 100% happy with that in some circumstances. They are happy with lower mediocrity because simply the vendor in question has got away with it for so many years that it is now the status quo.
If I bought a Tesla and it behaved like the average windows machine I'd drive it back through the fucking dealer's window.
Simply I demand better and I demand what I paid for.
I would be more interested about spying. Does it spy? Call home? How safe is corporate data on that system? Can I audit the source code?
Also people claiming that it does not spy because it open source should read [1]. Source availability does not mean the binary was built from it.
1. You Think the Visual Studio Code Binary You Use Is Open Source? Think Again | Hacker News – https://news.ycombinator.com/item?id=18012301
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.
Earlier quoted context omitted.
Yes and no. Having used DSC and powershell remoting extensively, these create as many problems as they solve. Nothing works smoothly. Not a thing. The saving grace here will be SSH because then at least we can drive all our kit across both platforms from Ansible and be done with the entire MSFT management stack. At the moment we use Ansible but it runs over WinRM which is completely unreliable due to some architectur…
For managing desktops and not servers, Group Policy is still unbeaten. I have yet to see a unified strategy on Linux of being able to say, mount these drives on logon, show these applications, don't allow them to do x, change the background to y etc. Sure, managing linux servers is a doddle, but desktop environments are miles harder to get right.
Earlier quoted context omitted.
> A main criticism of all this is that the usual tools didn't work remotely I can't think of any that I use regularly that don't work remotely. Which snap-ins are you referring to? Most of them you just right-click on the top level object and select "connect to another computer".
Most of Control Panel, such as the network configuration (I realise this isn't a snapin, sorry) A quick check shows the availability of "connect to another computer" is a bit random; I can do it in services.msc and taskschd.msc but not in diskmgmt.msc . Maybe that's why I've never found it before.
Earlier quoted context omitted.
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…
> I think it's time for MS to develop a new ANSI/VT-compliant... They are doing exactly that: https://blogs.msdn.microsoft.com/commandline/2018/08/02/wind...