By default an App layering packaging machine will use DHCP to assign an IP address. There is no built in mechanism to change this behavior to use a statically assigned IP.

To work around this, a manually assigned MAC address can be set on a VM Template in your hypervisor. Then an IP address can be assigned to this specific MAC address within the network or the MAC can be added to an allowed list for DHCP assignment.

---

Instructions

If you do not already have a VM template assigned to your App layering connector, then please do the following. Otherwise you can skip to "Set a Static MAC Address".

Create VM Template:

• Create a new virtual machine in your hypervisor
  • Do not add any disks
  • Be sure to configure BIOS or UEFI as needed.

Set a Static MAC Address:

VMware:

1. On your VM template machine go to Edit Settings.
2. Expand the Network adapter.
3. Copy the existing MAC shown and then select Manual.
4. Paste in the MAC address you copied.

Please Note: If you are running vSphere 8.x, you won't be able to save the MAC and you will see it switch back to Automatic. Please change the MAC on the template using the ESXi host web interface per https://kb.vmware.com/s/article/95189

Hyper-V:

1. Right click the VM template and select Settings.
2. Expand the Network adapter and go to "Advanced Features"
3. Under MAC address select Static.

XenServer:

1. Click on the VM's Networking tab for your VM template and go to Properties.
2. Set a manual MAC address.

Set the VM Template on the connector:

1. From the App Layering Web Console go to Connectors.
2. Select a connector and click Edit or create a new one by clicking Add Connector Configuration.
3. Under Virtual Machine Clone Settings, go to Virtual Machine Template and select Browse.
4. Select your VM Template with the static MAC set.

Limitations:

Normally App Layering will allow four simultaneous layering tasks with Offload Compositing disabled, or a virtually unlimited number (within reason) with Offload enabled. Using a static MAC on your template will force every packaging machine created with that connector and template to have the same MAC and IP.

If you need to run multiple operations at the same time, you will need to create multiple templates each with their own MAC and assign each template to a unique connector. Then start each task with a different connector. Once the task has finished you may reuse that connector. If a task is in an idle state but otherwise still active, you cannot reuse the connector yet. The layer must be finished finalizing or the image must finish being published first.

Citrix is not responsible for and does not endorse or accept any responsibility for the contents or your use of these third party Web sites. Citrix is providing these links to you only as a convenience, and the inclusion of any link does not imply endorsement by Citrix of the linked Web site. It is your responsibility to take precautions to ensure that whatever Web site you use is free of viruses or other harmful items.