Page Comparison

{"diagramDefinition":"flowchart TD\n\n\nA2[<font color=ffffff>Hypervisor</br>tools]-->|Deploy     </br> </br>   Reconfigure: no DHCP|B2{<font color=ffffff>OS}-->|Win|Z-->c2[/<font color=ffffff>Unattend file/]-->D2[<font color=ffffff>Network via </br>DHCP only]\nZ(( ))\nstyle Z fill:#g1g,stroke:#100,stroke-width:2px\nZ-->f2[/<font color=ffffff>Custom</br>specification/]-->G2[<font color=ffffff>Network via DHCP </br>or Static IP injection]  \nB2-->|Linux|h2[/<font color=ffffff>Custom</br>specification/]-->I2[<font color=ffffff>Network via DHCP </br>or Static IP injection]  \n \n    \n    \n\nstyle A2 fill: #ff9f3c,stroke: #ff9f3c\nstyle B2 fill: #ff9f3c,stroke: #ff9f3c\nstyle c2 fill: #ff9f3c,stroke: #ff9f3c\nstyle D2 fill: #ff9f3c,stroke: #ff9f3c\nstyle f2 fill: #ff9f3c,stroke: #ff9f3c\nstyle h2 fill: #ff9f3c,stroke: #ff9f3c\nstyle G2 fill: #ff9f3c,stroke: #ff9f3c\nstyle I2 fill: #ff9f3c,stroke: #ff9f3c"}

...

...

For guest tools with Windows, the platform default is to use a Windows unattend file.

The default unattend file is Abiquo default 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:

...

To configure a custom Windows unattend file for a datacenter

1. Log in to the Remote Services server as an administrator

2. Create your own custom unattend file and make the tomcat user the owner of the file

   1. By default Abiquo will replace the following variables:

      • $adminPassword

      • $domain

      • $hostName

3. Edit the abiquo.properties file and set the location of your custom unattend file. For example:

   Code Block
   // Path to Windows unattend file com.abiquo.esxi.experimental.customize.win.unattendfile=/root/windows_unattend.xml

...

On VMware, to use a custom specification to configure Windows, set the unattend file unattendfile property to false.

com.abiquo.esxi.experimental.customize.win.unattendfile=false

...

Edit a VM template for guest setup

...

To prepare a VM template

...

Go to Catalogue

...

Go to Advanced

...

For Guest setup, select Cloud-Init or Hypervisor tools.

1. For Windows on AWS, you can select from: CLOUDBASE_INIT, EC2LAUNCH_V2, EC2LAUNCH, EC2CONFIG

...

1. For Windows systems we strongly recommend this option

2. The platform will log in with the template User and Password (see below) and change the Password to the guest initial password.
   The platform will send the guest initial password to the user via mail or SMS, and users can display it with the VM key button

...

1. On Windows, enter Administrator

2. On Linux, enter root or another user that can run chpassword, with sudo and by always entering the password

   1. If sudo is not available, please contact Abiquo Support to configure the nosudoerrequiredforuser property

...

1. The platform does not save VM passwords

   1. On Linux, before deploying an instance template, edit the instance template's password to set it to the current VM password.

...

Select the Operating system. If required, enter the OS version. For more details see Set the guest operating system for VMware

...

Optionally, go to Variables and set variables for the VM template. The platform will add these variables to the VM using metadata or user data. See VM variables

...

TipAdd the SSH public key to your user before you deploy VMs. To connect to your VM, you will often require the SSH key pair, for example, to connect to Windows VMs in public cloud via RDP

...

Users can now automate their VMs with guest setup. See Automate first boot of a VM for guest setup

...