/
Customize the Windows unattend file
Customize the Windows unattend file
For guest tools with Windows, the platform default is to use a Windows unattend file. Guest setup with a Windows unattend file runs the first time you deploy a VM. If the guest setup is not successful, the VM deploy or reconfigure will fail and roll back.
Using the Windows unattend file, Abiquo sets:
- Fully qualified domain name (FQDN)
- Guest password at deploy time
The Abiquo default Windows unattend file also includes these static settings:
- TimeZone with default W. Europe Standard Time
- JoinWorkgroup with default WORKGROUP
To configure a custom Windows unattend file for a datacenter
- Log in to the Remote Services server as an administrator
- Create your own custom unattend file and make the tomcat user the owner of the file
By default Abiquo will replace the following variables:
- $adminPassword
- $domain
- $hostName
Edit the abiquo.properties file and set the location of your custom unattend file. For example:
// Path to Windows unattend file com.abiquo.esxi.experimental.customize.win.unattendfile=/root/windows_unattend.xml
, multiple selections available,
Related content
Customize the Windows unattend file
Customize the Windows unattend file
More like this
Prepare for guest setup with hypervisor tools
Prepare for guest setup with hypervisor tools
More like this
Use a Windows unattend file with vCenter 7.0.3 U3
Use a Windows unattend file with vCenter 7.0.3 U3
More like this
Use a Windows unattend file with vCenter 7.0.3 U3
Use a Windows unattend file with vCenter 7.0.3 U3
More like this
Prepare for guest setup with hypervisor tools
Prepare for guest setup with hypervisor tools
More like this
Prepare for guest setup with hypervisor tools
Prepare for guest setup with hypervisor tools
More like this
Copyright © 2006-2022, Abiquo Holdings SL. All rights reserved