While talking with customers over the past couple of weeks during a multi-country/multi-continent trip, one phrase that kept coming up is “lock-in”, as in “we’re trying to avoid lock-in” or “this approach doesn’t have any lock-in”. While I’m not a huge fan of memes, this phrase always brings to mind The Princess Bride, Vizzini’s use of the word “inconceivable,” and Inigo Montoya’s famous response. C’mon, you know you want to say it: “You keep using that word. I do not think it means what you think it means.” I feel the same way about lock-in, and here’s why.
Lock-in, as I understand how it’s viewed, is an inability to migrate from your current solution to some other solution. For example, you might feel “locked in” to Microsoft (via Office or Windows) or “locked in” to Oracle (via their database platform or applications), or even “locked in” to VMware through vCenter and vSphere. Although these solutions/platforms/products might be the right fit for your particular problem/need, the fact that you can’t migrate is a problem. Here you are, running a product or solution or platform that is the right fit for your needs, but because you may not be able Continue reading

In case you missed it, Ansible 2.0’s Windows support includes a number of improvements and new features that make automating Windows with Ansible easier. Because of Red Hat’s commitment to solid cross-platform management, you’ll also see an acceleration of these kinds of improvements in future Ansible releases. I’ll highlight a few of the items I’m most excited about from 2.0, and give a quick peek at what’s scheduled for future releases.
Update management is a common pain point for Windows administrators. The new win_updates module makes it easy to orchestrate updates during your maintenance windows- no more logging into individual machines to kick off updates or hoping a scheduled update pass actually ran!
2.0 shipped with a suite of modules for managing IIS. From configuring websites, AppPools, virtual directories, and more- now Ansible can deploy and manage your IIS apps with ease.
Since WinRM doesn’t have a built-in file transfer mechanism, Ansible has to jump through some “interesting” hoops to deploy its module code and copy files from the control host to a managed Windows box. Historically, this process was very slow, and could only transfer small Continue reading