eaksel / packer-win2019 Goto Github PK

Hi, i'm reusing parts of your project to create a template with vsphere-iso.
Everything seems to work fine, i just do not undestand how the network card is being set up.
Shouldn't i put a network conf in te autounattend.xml ?

Is there a reason for win2019-gui_uefi.json to call win-update.ps1 script twice?

      {
        "type": "powershell",
        "scripts": ["scripts/win-update.ps1"]
      },
      {
        "type": "windows-restart",
        "restart_timeout": "30m"
      },
      {
        "type": "powershell",
        "scripts": ["scripts/win-update.ps1"]
      },
      {
        "type": "windows-restart",
        "restart_timeout": "30m"
      }

Thanks otherwise for this repo!

I was able to use this great tool on my Mac OS, with Fusion, and generated teh output-vmware-iso/* files. Which file(s) do I port over to VCenter? Perhaps add the instructions to the README.md file? Or do I run yet another program to generate an ISO file from these files?

Hi

Thanks for the awesome project and for your work

I am trying to build ServerStandard edition instead of Datacenter one so I changed the scripts/bios/gui/autounattend.xml file like below :

<SynchronousCommand wcm:action="add">
                 <CommandLine>%SystemRoot%\system32\WindowsPowerShell\v1.0\powershell.exe -Command dism /online /quiet /set-edition:ServerStandard /productkey:N69G4-B89J2-4G8F4-WWYCC-J464C /accepteula</CommandLine>
                 <Order>7</Order>
                 <Description>Switch from EVAL to VL</Description>
  </SynchronousCommand>

When I try to build the image, it gets stuck waiting for WinRM to become available and never proceeds further.

I got the product key from Microsoft's official KSM activation page for Win2k19 StandardServer Edition.

https://docs.microsoft.com/en-us/windows-server/get-started/kmsclientkeys

I am using VMWare Workstation PRO to build the image via below command

packer build -only=vmware-iso win2019-gui.json
Do you have any insights what might be the culprit or what should I change else in the configuration files to make this work?

Thank you

Great job !

Have you try with 2022 server ?

Thank you for a very useful project, I was able to use it as a great source of information to build Windows 2019 images using the hyperv-iso and hyperv-vmcx builders.

Packer 1.6.3 added support for the cd_files token to a number of builders, including the virtualbox-iso one.
This allows you to specify a list of files which Packer will package up as an ISO and attach to the booting VM. For instance it can make it more convenient to make changes to autounattend.xml without having to rewrap it into an ISO, and is an alternative to the floppy_files token on platforms where a virtual floppy drive is no longer supported (for instance Generation 2 VMs on Hyper-V).

The drawback is that you need one of the supported command line ISO authoring utilities in the path, oscdimg.exe can be extracted from the Windows 10 ADK.