Windows automation kinda died when system admins stopped needing to know how to work with JET DB when needing to do one serious ad work.
I don't can't think of a single CI or automation thing that works with Linux that you can't do in Windows if pushed I can probably come with considerably more things which are opposite.
Licensing is the only thing really that makes windows machines a pain to work with unless you are big enough for a sell reporting volume licensing scheme.
In an ideal world you wouldn't have to deal with 32-bit versions of Windows, or EOL'd 64-bit versions. The real world with lots of legacy stuff doesn't work that way. Meanwhile EOL'd versions of Linux chugged away just fine.
Iteration on the Windows instances was also quite a bit slower than with the Linux ones. Applying all the requisite compliance stuff resulted in a number of additional reboot cycles. I could get a Linux instance bootstrapped in half the time, without having to bake a custom image.
This is a tooling issue, dont expect to use a tool that was hacked together for all intents a purposes rather than a native solution and get good results.
https://www.reddit.com/r/sysadmin/comments/21z62d/sccm_2012_...
And this:
https://www.windows-noob.com/forums/topic/9357-how-can-you-m...
And I'm seeing three things:
1.) SCCM is not nearly as easy to automate as the alternatives.
2.) SCCM is expensive.
3.) SCCM has mediocre support for Linux.
And there ya go. Meanwhile things like Ansible, Chef, and Puppet can handle your Linux, BSD, and OSX servers with aplomb. Where Ansible, Chef, and Puppet use mature, cross-platform scripting languages SCCM uses Powershell. Windows is the odd man out here, and skills from nearly every other OS don't really transfer well to dealing with Windows. That's why Windows is seen as more tedious.
And, sure, our Windows guys were dropping to Powershell constantly from their Chef cookbooks. But then you get to deal with maintaining PS 2 and PS 4 scripts. The versions of Ruby and Python you'll find with Ansible/Chef/Puppet are significantly better with backwards compatibility in this regard.
But, let's say that we had bought into SCCM. That doesn't really fix the problems with the other parts of the stack, nor does it fix the inconsistencies across Windows versions.
And you got this from what exactly?
Windows does automation just fine, you are throwing this word around without even trying to explain what is it you want to automate.
SCCM has ok to decent support for Linux; again depending on your use cases and distro.
I don't understand why are you even bringing random Reddit and forum posts for a 5 year old version of SCCM.
SCCM isn't expensive it's usually "free" when you buy enough licenses.
Also you missed a very critical point; Chef, Puppet and Ansible can invoke the SCCM agent.
Their built-in agents for Windows suck, so you either write your own automation (e.g. Powershell) and invoke it via Chef/Puppet/w/e or you use a decent agent that was actually built for purpose.
You are constantly complaining about things that at the end stem from a single source; incorrect tooling.
> It's really not, it's that most devops engineers don't want to learn or even bother and most windows sysadmins simply don't know how.
From a hiring/project/management perspective, this is my definition of "hard".
From a sysadmin perspective, a huge problem is the amount of knowledge needed to be an effective windows sysadmin absolutely dwarfs -- by several orders of magnitude -- the amount of knowledge needed to be effective on Linux.
How many sysadmins have you heard suggest, with all credulity that the solution is downtime and a reinstall on Windows? on Linux? Once a sysadmin knows how to move files around, run strace and grep, there is very little hidden from them on Linux, while on Windows they still don't even know how to take a backup, which is helped less by Microsoft refusing to publish any documentation that makes them look stupid -- like it being impossible to take an on-line backup of a server running Microsoft Exchange 2007 prior to SP2.
> I don't can't think of a single CI or automation thing that works with Linux that you can't do in Windows if pushed I can probably come with considerably more things which are opposite.
I agree wholeheartedly with that statement.
I hope that UNIX sysadmins want to learn, and bother to learn well the Windows environment better: UNIX sysadmins already know how a system is supposed to work, and it is by large the sheer number of inexperienced Windows sysadmins that make Windows look stupid. UNIX sysadmins have a better chance of running Windows well simply because they won't put up with "have you tried reinstalling everything"?
There's also some really good ideas in the Windows ecosystem that Linux (and even OSX) could really benefit from.
> Licensing is the only thing really that makes windows machines a pain to work with unless you are big enough for a sell reporting volume licensing scheme.
An aside: I'm not so sure this is true anymore, at least not with Azure for infrastructure, and Open programs for desktops/laptops.
I agree wholeheartedly with that statement.
I hope that UNIX sysadmins want to learn, and bother to learn well the Windows environment better: UNIX sysadmins already know how a system is supposed to work, and it is by large the sheer number of inexperienced Windows sysadmins that make Windows look stupid. UNIX sysadmins have a better chance of running Windows well simply because they won't put up with "have you tried reinstalling everything"?"
Powershell is the key that unlocks Windows administration, I think. Certainly, as somebody that does both platforms, learning Powershell made a big difference to how I work and think when using Windows.
Having said that, Windows Server is still fundamentally bad. The logging is a mess, remote access is awkward compared to SSH on Linux, the failure to properly integrate package management hurts every day, the Registry is still...there, and the list goes on. The disparity of DevOps tooling is another issue. I would agree with the comment that automating Windows takes several times as long as Linux. It's just not happy fun.
At this point, Windows is probably not retrievable. The Windows Server folks will keep improving it bit by bit, but I can't see an argument for continuing to flog the horse and use Windows Server outside of full-dress Microsoft corporate environments.
Also wmi always worked and still does.
Logging is great you just need to configure it and register your own triggers and monitors really depends on what you want to log.
It's very easy to do logging of every action and even completely custom and send it to the event log, you can also register custom events if you want to add your own application logging or use the stubs and just push the information into the text fields.
Again this simply comes to 2 things tooling and knowing windows internals well, sadly because there are usually very little negative side effects to rebooting a windows machine and that the market is flooded GUI administrators with mcsa/mcse certs gained through memorizing exam dumps it's hard to find people that know or want to know how to administrate windows machines to their full potential.
To me, that's sort of where Windows is now. It has some really impressive stuff: Windows 2000 was an avalanche of innovations, but most of it was built for the corporate LANs of a decade ago. Put Windows Server on a cloud, and most of this stuff is not relevant or useful, and Windows is not great at some fundamentals.
Logging is one of those. If you are interested in this kind of thing, I'd genuinely encourage you to spin up a Fedora or Debian system and look at the thing work. We are currently in transition between logging systems, but the feature sets are impressive and the error messages are useful. Windows logging is even more patchwork, and the (Microsoft) products that bother with the core logging system tend to fill it with chaff. It might get better, one day, but it's not a good experience today, and hasn't ever been.
Another is software management. Package-based software management has to be deeply integrated into the OS for it to provide it's full value. Debian have done this for years, and Red Hat have caught up. Microsoft have a muddle of multiple software management systems, and individual admins can't fix it. We just have to work around it and do the best that we can, or decide that the platform is what it is, and move on.