search

joefitzgerald / packer-windows

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

Explain why openssh and windows updates are mutually exclusive #127

Closed lonniev closed 8 years ago

lonniev commented 9 years ago

Some of us want an updated Windows image WITH openssh installed. Why does Autounattend.xml place its commenting so that one gets one or the other but not both?

If there's an incompatibility here, then document it.

kensykora commented 9 years ago

It's not mutually exclusive, the update script installs open SSH at the end of the run so that Packer can then connect to it and run its own scripts. We don't install Open SSH initially so that packer doesn't attempt to run provisioning during reboot cycles of windows update runs.

lonniev commented 9 years ago

Uh, oh, getting burned by that now during the packer build attempt. Going to look at the update script to confirm that. (Again would be cool if the README or the XML said, "no need to turn these both on". It doesn't say that yet, does it? ;-) )

lonniev commented 9 years ago

Well, gollee, there it is in the update script. Ok, I leave it with the recommendation that the XML indicate that or that the windows update script gets a name like, "update windows and install openssh".

kensykora commented 9 years ago

Reopening to update documentation as suggested. Thanks for the feedback!

icnocop commented 9 years ago

There is a discrepancy (which adds to the confusion) with the autounattend.xml files between windows 7 and windows 2012 r2 for example.

In the Windows 7 Autounattend.xml file, the "" section disables windows updates, but that section in some of the other Autounattend.xml files do not.

I also think that openssh should be installed regardless of windows updates so that packer can actually connect to the vm as part of its build process because packer doesn't support WinRM yet.

Thank you.

sneal commented 8 years ago

200 addresses this issue