Novell Doc: PlateSpin Orchestrate 2.0 Virtual Machine Management Guide

5.3 Known Autoprep Limitations

There are some limitations that you need to be aware of when you use Autoprep:

Currently, the Gateway IP Address setting under the Autoprep Network Adapter 0 and the Autoprep Network Adapter 1 sections of the Info/Groups tab for a VM object and VM template object is available in a list box.

Because the Linux VM OS accepts only one default gateway, it accepts only the first setting in the list as the actual gateway IP address. The other settings are ignored.
The hostname setting is required when you use the VCenter Provisioning Adapter to do any autoprepping of Linux VMs. Use the following syntax to supply the hostname setting: resource.provisioner.autoprep.linuxglobal.ComputerName
If you have a VM template with two network cards, only the first card is considered active and therefore it is the only card configured with Autoprep.

To work around this issue, set the fact manually in the Facts/Constraints editor or associate a new policy on the template with the following syntax:
```
<policy>
<resource>
<fact name="provisioner.autoprep.adapters[1].Active" value="true"
type="Boolean" />
</resource>
</policy>
```
The Personalize action is not supported for vCenter VMs, but it does work for VMs created with the vSphere Provisioning Adapter Add-on for PlateSpin Orchestrate 2.0.2.