Windows bootstrap should run in a local Elevated session under System account

[Annih]

Hello,

As cookbook maintainer I receive more and more issues because people are unable to test or bootstrap Windows nodes using the recipes I provide.
Most of the time, this is related to WinRM remote limitation, resulting in an Access denied error.
This issue is clearly related to test-kitchen#876.

And again I think knife bootstrap should use winrm-elevated to apply the recipes under a local session with SYSTEM account.

What do you think @mwrock?

cc: @aboten

[jvogt]

Just curious if anyone has a workaround for this, short of running chef client while logged into the machine?

[jdpc02]

We have our chef client installed as a service. It checks back with the master server every half an hour.

[mwrock]

once WinRb/WinRM#191 is merged, I'd like to do some winrm refactoring here to atleast add a flag to knife winrm that will run commands through winrm-elevated.

[SolverDude]

@mwrock SWEET! Is this imminent? Can I help?

[mwrock]

Just waiting on a green light from @sneal. It's quite a bit to review.

[jptoto]

@mwrock did this or something like it ever get merged? Sure would be handy to have a flag for knife bootstrap to run as elevated.

[mwrock]

you can now run ad hoc knife winrm commands elevated using --winrm-shell elevated but bootstrap continues on in cmd.exe because we share the same scripts for knife bootstrap ssh.

[jptoto]

That'll work for now. Thanks @mwrock much appreciated 👍

[tas50]

Hey there. In Chef Infra Client 15 we completely rewrote the bootstrap functionality of Chef to use train engine. That rewrite fixed a large number of long standing issues and moves us to a much more robust connection method for bootstrapping. There is high likelihood that this issue has been resolved with that rewrite. I'm going to close this out at this point, but if you encounter the problem with Chef Infra Client 15 please open it up again.