[chef] Re: Re: Re: Re: Re: Windows Blues, part 2

[Adam Edwards < >]

I think the issues with winrm involve authentication — right now, ntlm / kerberos support is spotty at best on various operating systems, usually you have to resort to basic to get things to work. There's work going on in Chef and gems used for WinRM to get past this, since the status quo is not acceptable.

Outside of that strange behavior, we're trying to be more WinRM friendly, releasing support for winrm bootstrapping for openstack and ec2 earlier this year, for instance. It's a good path as you say if you want to use "clean" AMI's or you're in a system where you can't customize the image but you can get winrm access.

-Adam

From: Jeppe Nejsum Madsen < "> >
Reply-To: " "> " < "> >
Date: Monday, June 10, 2013 12:56 PM
To: " "> " < "> >
Subject: [chef] Re: Re: Re: Re: Windows Blues, part 2

On Mon, Jun 10, 2013 at 5:53 PM, Adam Edwards < " target="_blank"> > wrote:

Thanks for the details Jeppe. One more question on 2k12: if MSFT gets the quota bug fixed soon, will you be able get back on the wagon using Win2k12?

Actually, the current setup using SSH seems to work even if it takes some extra work. We now have a Win2k12 EC2 AMI that includes FreeSSHD and haven't had any issues (sans the tickets I mentioned ;-)

Winrm does seem like a more natural fit in windows however and would allow us to use clean Amazon AMIs. But to be frank, it also seems like an area that doesn't get so much attention on the chef side ;-(

/Jeppe