[chef] Re: Re: Re: Re: Re: Server 2012/WinRM3 uses different security?

[Adam Edwards < >]

Your patch trick is cool. I just wrote a similar thing that uses _vbscript_ to patch boxes built from an iso using peewee. I start a scheduled task, though after that, it copies the patching script into the startup folder (was easier for me to watch it in VirtualBox). Once it hits 0 updates to install, it then syspreps and shuts the box down.

If enough people are doing this it should probably make it into veewee, bento, chef cookbook, or other automation.

-Adam

From: David Petzel < "> >
Reply-To: " "> " < "> >
Date: Friday, May 24, 2013 8:56 AM
To: " "> " < "> >
Subject: [chef] Re: Re: Re: Re: Server 2012/WinRM3 uses different security?

On Fri, May 24, 2013 at 11:50 AM, Adam Edwards < " target="_blank"> > wrote:

Question: has anyone actually repro'd this outside of Win2k12?

Yes, I ran into this on Windows 2008R2 

One workaround is to use scheduled tasks, another is to use psexec — see http://tickets.opscode.com/browse/COOK-1172.

Agreed, the schedule task trick also works. We actually use this trickery to "fully patch" a box. When we bootstrap a new node, The first thing we do is created a schedule task, and then append our patching recipe recipe, so that the schedule task will then fire off the next run including the patching recipe. We do this because we have some unknown number of reboots required to fully patch a new node. We use the schedule task to do the install/reboot/check if more are needed loop.  Once no more patches are needed, the patching recipe is removed from the run_list