Using winrm for bootstrapping windows via chef-provisioning, knife bootstrap, and test-kitchen seems to be the norm, but it also seems to be the wrong way to run chef on windows.
It's been heavily suggested that we run chef-client as a schtask and not via winrm. (or even as a windows service)
I'd like to utilize all of our existing toolchain if possible, and one thought I had was to:
1. create a schtask for chef-client
2. find a way to run the schtask immediately, grab the output, and exit code
3. wrap all that up in a command to run via winrm, call it chef-client-task.bat
4. ????
5. Profit for our existing chef tooling!!!
I'm going to start looking into this approach, but I suspect there may be better alternative and would love to hear how other windows chef users do their day to day development and production work.
Thanks,
@hippiehacker
(from an RV in Burlington Vermont this week)