In my current project, I am doing a lot of Ansible coding. However, they have chosen to install an agent on Windows, which makes executing code a lot easier. They are now releasing statement after statement and new modules to support Windows. This is why, for example, Chef and Puppet started partnering with Microsoft (or the other way around?). This recently changed quite a bit, and the industry found itself in a position where it needed to act. It was also needed more because most huge installations were run on Linux servers that somehow needed to be managed. Why all on Linux? Because it’s easier (document-based configuration management on Linux vs API-based configuration management on Windows). It is so similar to all that’s already out there and it made my transition so much easier!Īll of the traditional (read older, mature, already present at most companies) configuration management tools were born in the Linux universe-none of them on Windows, except maybe System Center Configuration Manager, but I am not going to get into that. Microsoft did a great job with PowerShell. All I knew was PowerShell and Windows and I was wondering how I would cope. This was very scary in the beginning-everything is so different. I am now not only managing and implementing the Windows operating system, but I also have to manage Linux machines, mostly through tools like Puppet, or in this case, Ansible.
Sure, cool idea! If you want to read more from me, head over to my personal blog or follow me on Twitter recently changed jobs. I’m David O’Brien, Microsoft MVP for Windows PowerShell, and I was asked by Ed if I wanted to share some of my knowledge on his blog. Today Windows PowerShell MVP, David O’Brien, talks about executing Windows PowerShell on Linux.
Microsoft Scripting Guy, Ed Wilson, is here. Summary : Microsoft MVP, David O’Brien, talks about using the pywinrm module to execute Windows PowerShell from Linux.
0 kommentar(er)
