Building server 2012, I get a "Language to install" dialog about packer-templates HOT 6 CLOSED

I've never encountered this before, but I always use the eval ISO and stick with the default locale/timezone. I'd be fairly certain this is either due to your specific ISO or the locale/timezone settings. I'm sure the product key is unrelated.

What I'd do is revert your locale/timezone changes and just see if that fixes it to isolate the settings from the ISO. I'm not sure what the fix would be other than it is somewhere in the autounattend.xml.

from packer-templates.

OK, thanks. I'll try that (so I just have my own ISO, but everything else unchanged) and see if that fixes it. If it does, I'll see if I can work out another way of making the changes I want post-install.

BTW, if I want to disable the windows update step (so I can run some tests in a reasonable length of time!) can I do that just by commenting out the Install-WindowsUpdate -AcceptEula line in scripts/package.ps1?

from packer-templates.

Yeah that should cut out about 6 hours :)

from packer-templates.

Sigh. Looks like it was from putting the language in autounattend.xml. Off to do some research on autounattend then...

Thanks for your help, and apologies for not researching more fully before raising the issue here.

from packer-templates.

no worries. The autounattend can be pretty cryptic indeed.

from packer-templates.

Looks like Windows these days comes without language packs included by default. If you change language manually, I guess it installs what it needs.

For information, should anyone else find this thread, the following powershell code can change the language:

Set-WinSystemLocale -SystemLocale en-GB
Set-WinSystemLocale en-GB 
Set-Culture en-GB
Set-WinUserLanguageList en-GB -force
Set-WinHomeLocation 242 # UK, US is 244

There's more (you need to download and install the language pack, and you need to somehow copy the current user values to the welcome screen and new user accounts (there's a GUI for that in the control panel, but I don't know what the powershell commands would be, yet), but the basic answer is that you can do it.

Add to that the fact that with DISM it appears you can activate an evaluation version with a full product key, and it looks like I can do all I need in a vagrant provisioning script from your base box (and then repackage the box for further customisation, if needed). Which is really cool.

from packer-templates.