![]() In my experience these are the primary hurdles to WinRM sweet success. I'll address cross platform scenarios using plain WinRM, powershell remoting from windows and some Chef specific tooling using the knife-windows gem. I'd like to lay out in this post some of the fundamental moving parts as well as the troubleshooting decision tree I often use to figure out where things are wrong and how to get connected. I started working for Chef about six weeks ago and it is not at all uncommon to find customers and fellow employees struggling with failure to talk to a remote windows node. Now armed with 2012R2 and more knowledge its simpler but lets say you are trying to connect from a linux box using one of the open source WinRM ports, there are several gotchas. It wasn't simple at all and took a few hours to finally succeed. I had been using powershell for about a year at the time and thought I'd give it a go. At the time, powershell 2 was the hotness and many were talking up its remoting capabilities. This was my experience years ago when I made my first attempt to use powershell remoting to connect to an Azure VM. ![]() Connecting to a remote windows machine is often far more difficult than one would have expected.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |