thanks for responding, here is my build.json I’m running for the Packer build:
{
"builders": [
{
"type": "virtualbox-iso",
"format": "{{user `vm_image_format`}}",
"guest_os_type": "Windows11_64",
"iso_url": "{{user `iso_url`}}",
"iso_checksum": "{{user `iso_checksum`}}",
"iso_interface": "sata",
"vm_name": "{{user `vm_name`}}",
"disk_size": "{{user `vm_disk_size`}}",
"hard_drive_interface": "sata",
"headless": "false",
"guest_additions_mode": "disable",
"shutdown_command": "{{user `shutdown_command`}}",
"shutdown_timeout": "10m",
"disable_shutdown": "true",
"post_shutdown_delay": "30s",
"boot_wait": "3s",
"gfx_controller": "vboxsvga",
"gfx_vram_size": "128",
"gfx_accelerate_3d": "true",
"boot_command": [
"<spacebar><spacebar>"
],
"floppy_files": [
"floppy/auto_winrm.ps1",
"floppy/Autounattend.xml"
],
"vboxmanage": [
[
"modifyvm",
"{{.Name}}",
"--memory",
"{{user `vm_memory`}}"
],
[
"modifyvm",
"{{.Name}}",
"--cpus",
"{{user `vm_cpus`}}"
],
[
"modifyvm",
"{{.Name}}",
"--firmware",
"EFI"
]
],
"export_opts": [
"--manifest",
"--vsys",
"0",
"--description",
"{{user `vm_description`}}",
"--version",
"{{user `vm_version`}}"
],
"communicator": "winrm",
"winrm_host": "5985",
"winrm_username": "{{user `admin_user`}}",
"winrm_password": "{{user `admin_pass`}}",
"winrm_timeout": "6h",
"skip_nat_mapping": "true",
"pause_before_connecting": "20s"
}
]
}
I have a autounattend.xml that I built in WSIM matched to the Windows 11 Enterprise install.wim in the ISO that I’m using.
Even still, I still cannot get it to run unattended, it won’t step past the first screen.
I’m building this image using the virtualbox-iso type to get an OVA output.
I’ve been looking at a lot of examples online of autounattend.xml files, and the matching of Images to WSIM answer file. I’ve been reading that if the Image is listed as Windows 10 Enterprise you need to specify that, even if it is Windows 11 Enterprise you are trying to install, but I’m not sure because even when I try this it still does not start:
I’ve also noted that the language has to match exactly, which I am also ensuring. I’m Running everything as standard en-US and keyboard input as standard US (Which I understand is still also en-US?):
Again, still cannot get past the intial screen and WinRM connector reports no connection to 127.0.0.1:
