search

joefitzgerald / packer-windows

Windows Packer Templates
MIT License
1.63k stars 1.12k forks source link

Switch To WinRM #181

Closed joefitzgerald closed 8 years ago

joefitzgerald commented 8 years ago

Checklist of all templates ported to WinRM

kensykora commented 8 years ago

Wow, is this real life? :+1:

StefanScherer commented 8 years ago

Whoot!

StefanScherer commented 8 years ago

Removing rsync is just a consequence. "Get off of my vCloud ;-)" Internal joke, only needed for vagrant-vcloud plugin, but doesn't make sense here in upstream.

oxypwn commented 8 years ago

Yay!

StefanScherer commented 8 years ago

I'll test the windows_10.json in a few minutes and remove the SSH parts there, too.

StefanScherer commented 8 years ago

@joefitzgerald my first Windows 10 build for Fusion was fine, but I left the Vagrant Post Processor in the json template. What is your reason to switch to the Compress Post Processor? May I push the commit for windows_10.json + answer_files/10/Autounattend.xml into this branch? Starting VirtualBox build now...

joefitzgerald commented 8 years ago

@StefanScherer Of course, feel free to push to that branch.

I decided to switch to the compress post processor because it encourages people to build a single base image (with Windows updates applied) that they can then use to further iterate via the vmware-vmx or virtualbox-ovf builders. I don't think we need to push people straight over to vagrant, particularly with the flux associated with https://ottoproject.io.

StefanScherer commented 8 years ago

OK, I got it. :+1: So I'll adjust the post processor before the push.

Real2014 commented 8 years ago

Seems that the WinRM instead of SSH finally works. Great WORK and thank you to everyone who realized it! I always had the problem that the windows ssh packer scripts didn't work on German ISO. Now with using WinRM the problem should be part of history :+1:

DenverOps commented 8 years ago

I have tested this and everything works great. The only issue is WinRM has slow file transport speeds. I tested this with an ISO and it took > 6hrs to complete. I did some research and others are having the same issues with WinRM. https://github.com/packer-community/winrmcp/pull/6 and https://github.com/mitchellh/packer/issues/2648#issuecomment-170756293. Users beware of slow speeds in WinRM transports.

StefanScherer commented 8 years ago

Worth reading http://www.hurryupandwait.io/blog/whats-new-in-the-ruby-winrm-gem-15 It's Ruby, but someone may have a look at it to do the same in GO. -> PSRP

/cc @mwrock ;-)

sneal commented 8 years ago

Closing in favor of #200

martinmosegaard commented 6 years ago

Can I ask here on the current status of WinRM and packer? I am trying to use the winrm communicator with Windows 2008, but it fails with a wsarecv error. I can see that the templates in this repository still use ssh instead of the winrm communicator, so it is not clear to me what the preferred way is.