If you find anything more definitive than what I found, let me know. I, too tried to get WinRM set up properly on a couple windows servers at work, and I *think* I got it working, but I did so many things that it probably worked more because the servers felt pity on me than that I knew what I was doing.
On Sat, May 12, 2012 at 2:52 PM, Justin Baker <azolo1...@gmail.com> wrote:
>> This is completely off-topic, but I was wondering if any of you
>> managed to get WinRM running on a Windows 7 box.
>> I've tried to get a dummy worker computer setup with it and
>> encountered several problems with firewall setup and WinRS then not
>> being able to find it (even with ports open)
>> My Google-fu didn't bring a definitive guide on how to get that setup
>> easily, but if any of you guys have some docs or instructions about
>> it, will be much appreciated.
>> I'll test on a VM instead of the real hardware in case I hosed it again
> If your computers are part of a ActiveDirectory Domain, it's cake.
> Setting it up anywhere else, well there's always the same problems. Then
> there's the other 5 problems that come up afterwards. It's traumatic
> experience for me most times I try.
Thanks Justin (and Nick too)
Indeed it was a traumatic experience and can't say I managed to get it to work.
Wonder how veewee does with Vagrant boxes?
> Either way the Powershell remoting scripts are based off winrm and
> are better than 'winrm quickconfig' so you should look at those.
> get-help about_remote_requirements
Will give a whirl on a VM this time, already hosed the worker machine
installation with it. For the time being, Remote Desktop seems to work
just fine :)
> Will give you better information than anything else I've found in the
> winrm documentation itself. Which is sad.
> Otherwise, it's painful. Good luck =)
> You received this message because you are subscribed to the Google Groups
> "RubyInstaller" group.
> To post to this group, send email to firstname.lastname@example.org.
> To unsubscribe from this group, send email to
> For more options, visit this group at
-- Luis Lavena
Perfection in design is achieved not when there is nothing more to add,
but rather when there is nothing more to take away.
Antoine de Saint-Exupéry
> Indeed it was a traumatic experience and can't say I managed to get it to
> Wonder how veewee does with Vagrant boxes?
It installs Cygwin:sshd.
It has a winrm setup script in there, but it's not used in Vagrant.
(They probably couldn't get it working.)
> > Either way the Powershell remoting scripts are based off winrm and
> > are better than 'winrm quickconfig' so you should look at those.
> > get-help about_remote_requirements
> Will give a whirl on a VM this time, already hosed the worker machine
> installation with it. For the time being, Remote Desktop seems to work
> just fine :)
It's *harder* on a virtual machine box. Just a quick couple hints,
unless you're on a Active Directory Domain, winrm *hates* you.
If you want to connect using a non-Kerebos authentication system,
then you need to connect through https:// which means you'll need
a SSL cert. (This is the part I stopped at)
Also you need winrm running on the current computer,
because "knownhosts" are "TrustedHosts" and can only be added
using the winrm service.
Then and only then will you unlock the next problem, because
with winrm solutions are overrated.