App Layering

MS Hyper-V

March 24, 2021

Contributed by:

E C

This section describes considerations and requirements when creating layers or publishing images in Hyper-V.

Platform layer

Configure the Hyper-V settings on the platform layer so that your other layered applications run seamlessly in Hyper-V.

You need a platform layer if the OS image used to create your OS layer originated in a different hypervisor. If the OS image originated in Hyper-V, you do not need a platform layer. The Hyper-V settings are already configured on your OS layer.

You also need a platform layer if you start using Generation 2 machines, as explained in the following section.

Generation 2 machines

To start using Generation 2 machines in Hyper-V when your existing machines are Generation 1:

Create a Hyper-V connector configuration with the Offload compositing feature enabled and Generation 2 selected.
Create a Generation 2 platform layer.
Publish Generation 2 images using this platform layer and your existing Generation 1 app layers.

If you are starting with a fresh deployment in Hyper-V, you can create a Generation 2 OS layer using either of the following approaches:

Create the OS layer from a Generation 1 OS image. Then:
- Create a Hyper-V connector configuration with the Offload compositing feature enabled and Generation 2 selected.
- Add a Generation 2 version to the OS layer.
- Create Generation 2 app layers.
- Create an image template with the new connector selected, and publish the images.
Create the OS layer from a Generation 2 OS image, by bypassing the management console and using the OS import script:
- Locate the ImportOSLayer.ps1 script included in the OS Machine Tools download.
- Import the OS using the script. The script supports the import of UEFI machines and completes the import faster than the management console.

The official version of this content is in English. Some of the Cloud Software Group documentation content is machine translated for your convenience only. Cloud Software Group has no control over machine-translated content, which may contain errors, inaccuracies or unsuitable language. No warranty of any kind, either expressed or implied, is made as to the accuracy, reliability, suitability, or correctness of any translations made from the English original into any other language, or that your Cloud Software Group product or service conforms to any machine translated content, and any warranty provided under the applicable end user license agreement or terms of service, or any other agreement with Cloud Software Group, that the product or service conforms with any documentation shall not apply to the extent that such documentation has been machine translated. Cloud Software Group will not be held responsible for any damage or issues that may arise from using machine-translated content.

Was this helpful

MS Hyper-V

March 24, 2021

Contributed by:

E C

March 24, 2021

Contributed by:

E C

MS Hyper-V

Platform layer

Generation 2 machines

In this article