- What's new in App Layering 4.12
- What's new in App Layering 4.11
- What's new in App Layering 4.10
- What's new in App Layering 4.9
- What's new in App Layering 4.8
- What's new in App Layering 4.7
- What's new in App Layering 4.6
- What's new in App Layering 4.5
- What's new in App Layering 4.4
- What's new in App Layering 4.3
- What's new in App Layering 4.2
- What's new in App Layering 4.1
- Known issues and considerations
- Fixed issues
- System requirements
- Plan your deployment
- Install appliance
- Install agent
You can publish layered images to PVS running in the MS Hyper-V, VMware vSphere, Nutanix AHV Acropolis, or Citrix XenServer hypervisor.
When creating the layer, the PVS installer and your hypervisor tools must be available in a location that’s accessible to the packaging machine where you are creating the layer.
If you are using a connection broker, the installer for the broker must also be accessible from the packaging machine.
IPv6 must be disabled on the OS layer.
If IPv6 is not disabled on your OS Layer, add a new Version to the OS Layer and disable IPv6 in the new Version.
IMPORTANT: If you disable IPv6 on the Platform layer instead of on the OS layer, the resulting PVS machines will lose their network connection and hang when they are booted.
App Layering agent
The agent must be installed on each PVS server to which you publish images, and at each location where you will run connector configuration scripts. Each agent must be registered with the App Layering appliance.
PVS servers where the agent is installed
The PVS console must be installed on all PVS servers where the agent is installed.
PVS Target Device Imaging software
The PVS Target Device Imaging software must be available to install on the Platform layer. The version must match the PVS server where the layered image will be published.
PVS resource information
The PVS info listed in this PVS Connector Configuration topic.
Appropriate PowerShell Snap-in must be installed.
Unique CMID for each target device (if using KMS)
When using KMS licensing, PVS requires that each target device has a unique CMID. For the full story, check out this Citrix article, Demystifying KMS and Provisioning Services. Rearming KMS is covered in the steps to Create a Platform layer.
Any additional PVS settings you use in your environment
Any settings you need to configure PVS on your Platform layer so that it matches the environment where the layered image will be used.
Software and settings - Access to the software to install on the layer.
Hypervisor resource information - The hypervisor info listed in the connector configuration you are using.
You need any installers, tools, and settings required to run your connection broker on the hypervisor you are using.
- KMS settings, if using KMS licensing
Once you have the requirements, you are ready to create the Platform layer.