Create a Platform Layer (XenServer Connector)

In this article:

A Platform Layer should include the platform software and settings required to deploy images in your environment, given your choice of hypervisor, provisioning service, and connection broker.

You can create two kinds of Platform Layers:

• Platform Layers for publishing Layered Images (Required) - A Platform Layer for publishing is used in Image Templates to ensure that your published Layered Images include the software and settings required to run flawlessly in your environment.

• Platform Layers for packaging Layers (Required in some cases) - A Platform Layer for packaging is used for creating App Layers and OS Layer Versions in your hypervisor environment. This Layer includes the hypervisor software and settings required to easily install the app or OS update on a VM in the selected hypervisor.

Prerequisites

When creating a Platform Layer, the software installers for your platform must be available in a location that's accessible to the Packaging Machine VM where you are going to create the Layer. As summarized in the following table, the prerequisites vary based on the type of Platform Layer you choose to create.

Citrix XenServer prerequisites

• XenServer account and privileges

  • A XenServer account (new or existing) to use for Unidesk.
  • The account must have XenServer privileges to:
    • Create and remove virtual disks.
    • Copy and delete layers on virtual disks using XenServer file APIs.

• Citrix XenServer software and settings

  Access to the XenServer Tools to install on the layer.

• XenServer resource information

  The XenServer info listed in Citrix XenServer Connector Configuration.

• Network access to Unidesk OS Machine Tools

  When you create Layer or add a Version to it, the Unidesk Management Console (UMC) uses a Connector Configuration to create a VM called a Packaging Machine for the Layer you are building. The Packaging Machine must have access to the Unidesk OS Machine Tools download, which is available on the Unidesk Download page.

Prepare a new Platform Layer

1. Select Layers > Platform Layers and select Create Platform Layer in the Action bar. This opens the Create Platform Layer wizard.

2. In the Layer Details tab, enter a Layer Name and Version, both required values. Optionally, you can also enter other values.

3. In the OS Layer tab, select the OS Layer you want to associate with this Platform Layer.

4. In the Connector tab, choose a Connector Configuration for the platform where you are creating this layer. If the configuration you need isn't listed, Click New, select your platform from this list, and Add a Configuration for it.

   Example: If you are creating the layer in a XenServer environment, select the XenServer connector with the information needed to access the location where you will package this layer.

5. In the Platform Types tab, select the radio button that describes the purpose of this Platform Layer: to create and update layers, or to publish Layered Images. For more about these choices, see Platform Layers.

6. From the dropdown menus, select the platform(s) you are using.

7. In the Packaging Disk tab, enter a file name for the Packaging Disk, and select the disk format. This disk will be used for the Packaging Machine (the VM) where you will install the tools, as described in the next two sections.

8. In the Icon Assignment tab, select an icon to assign to the layer. This icon represents the layer in the Layers Module.

   • To use an existing image, select an image in the image box.
   • To import a new image, click Browse and select an image in PNG or JPG format.

9. In the Confirm and Complete tab, review the details of the Layer, enter a comment if required, and click Create Layer. Any comments you enter will appear in the Information view Audit History.

10. At the bottom of the UI, expand the Tasks bar and double-click the task to show the full task description.

    Once the task is complete, the location of the Packaging Disk is shown (example task message shown below).

    

Next, you can deploy the Packaging Machine for your Layer. The Packaging Machine is a temporary virtual machine where you install the software to include in the Layer being created.

Power on the Packaging Machine in Citrix XenServer

1. Log into your XenServer client.

2. Back in the Unidesk Management Console (UMC), expand the Tasks bar at the bottom of the UI, and double-click the Create Platform Layer task to see the full Task Description (example below).

   

3. Use the instructions in the Task Description to navigate to the Packaging Machine in your XenCenter client.
4. While in the Infrastructure View, select your Packaging Machine's VM from the list of machines.

5. In the XenCenter UI in the panel on the right, choose the Console option for the VM.

6. Power on the VM.
7. Select the Click here to create a DVD drive link.
8. Power cycle the VM (yes, you have to in order to get the DVD Drive).
9. At the top of the console window, click the DVD Drive 1 drop down menu and select the xs-tools.iso.

10. Install the XenTools. This will require multiple reboots as part of the tools installation. Once complete, you should see that you have access to all XenTools, as well as all of the data available under the Performance tab for your VM.

    Note: The XenCenter console uses RFB for it's console connection, which uses Port 5900. On Windows 2008 and Windows 7, this port is closed in the Firewall by default and should be opened so you can use the console to access any VMs

Install the platform tools on the Packaging Machine

Whether you are creating a Platform Layer or adding a version to it:

1. Remote log in to the Packaging Machine. Be sure to log in using the User account you used to create the OS.

2. Install the platform software and tools, along with any drivers, boot-level applications, or files needed. Keep in mind that the state of the software before you finalize the layer is what the image will use.

   • If this Platform Layer is going to be used for packaging new layers, install and configure your hypervisor tools and settings.
   • If this Platform Layer is going to be used for publishing Layered Images, install and configure your hypervisor, provisioning service, and connection broker tools and settings.
   • If a software installation requires a system restart, restart it manually. The Packaging Machine does not restart automatically.

3. Make sure the Packaging Machine is in the state you want it to be in for users:

   • If the tools you install require any post-installation setup or registration, complete those steps now.
   • Remove any settings, configurations, files, mapped drives, or applications that you do not want to include on the Packaging Machine.

   • When using PVS, if your OS image was activated using KMS, rearm KMS just before you shut down

     1. Verify the Rearm count on the OS by running slmgr /dlv from a command prompt. The Rearm count must not be zero.

        slmgr /dlv

     2. Rearm KMS:

        slmgr /rearm

Verify the Layer and shut down the Packaging Machine

Once the software is installed on the Packaging Machine, it is important to verify that the Layer is ready to be finalized. To be ready for finalization, any required post-installation processing needs to be completed. For example, a reboot may be required, or a Microsoft NGen process may need to complete.

To verify that any outstanding processes are complete, you can run the Shutdown For Finalize tool (icon below), which appears on the Packaging Machine's desktop.

To use the Shutdown For Finalize tool:

1. If you are not logged into the Packaging Machine, remote log in as the user who created the machine.
2. Double-click the Shutdown For Finalize icon. A command line window displays messages detailing the layer verification process.
3. If there is an outstanding operation that must be completed before the Layer can be finalized, you are prompted to complete the process. For example, if a Microsoft NGen operation needs to complete, you may be able to expedite the NGen operation. For details, see Verifying Layers.

4. If you are using KMS licensing, once any pending operations are complete, be sure to rearm KMS yet again just before you shutdown. First, enter this command to verify that the Rearm count is > 0:

   slmgr /dlv

   Then, rearm KMS:

   slmgr /rearm

5. Double-click the Shutdown For Finalize icon again to shut down the Packaging Machine.

The Layer should be ready to finalize.

During the shutdown for finalization

Layer integrity messages let you know what queued tasks must be completed before a Layer is finalized.

The new Layer or Version can only be finalized when the following conditions have been addressed:

• A reboot is pending to update drivers on the boot disk - please check and reboot the Packaging Machine.
• A post-installation reboot is pending - please check and reboot the Packaging Machine.
• An MSI install operation is in progress - please check the Packaging Machine.

• A Microsoft NGen operation is in progress in the background.

  Note: If a Microsoft NGen operation is in progress, you may be able to expedite it, as described in the next section.

Expediting a Microsoft NGen operation

NGen is the Microsoft Native Image Generator. It is part of the .NET system, and basically re-compiles .NET byte code into native images and constructs the registry entries to manage them. Windows will decide when to run NGen, based on what is being installed and what Windows detects in the configuration. When NGen is running, you must let it complete. An interrupted NGen operation can leave you with non-functioning .NET assemblies or other problems in the .NET system.

You have the choice of waiting for the NGen to complete in the background, or you can force the NGen to the foreground. You can also check the status of the NGen operation, as described below. However, every time you check the queue status, you are creating foreground activity, which might cause the background processing to temporarily pause.

Forcing the NGen to the foreground will allow you to view the progress and once the output has completed, you should be able to finalize the layer.

1. Force an NGen operation to the foreground.

   Normally, NGen is a background operation and will pause if there is foreground activity. Bringing the task into the foreground can help the task to complete as quickly as possible. To do this:

   1. Open a command prompt as Administrator.

   2. Go to the Microsoft .NET Framework directory for the version currently in use:

      cd C:\Windows\Microsoft.NET\FrameworkNN\vX.X.XXXXX

   3. Enter the NGen command to execute the queued items:

      ngen update /force

      This brings the NGen task to the foreground in the command prompt, and lists the assemblies being compiled.

      Note: It’s okay if you see several compilation failed messages!

   4. Look in the Task Manager to see if an instance of MSCORSVW.EXE is running. If it is, you must allow it to complete, or re-run ngen update /force. Do not reboot to stop the task. You must allow it to complete.

2. Check the status of an NGen operation

   1. Open a command prompt as Administrator.

   2. Check status by running this command:

      ngen queue status

   3. When you receive the following status, the NGen is complete, and you can finalize the Layer.

      The .NET Runtime Optimization Service is stopped

Finalize the Layer

To finalize the Layer, you import the installed software into the Platform Layer you prepared in the Unidesk Management Console (UMC).

1. Return to the UMC.
2. Select Layers > Platform Layers.
3. Select Finalize in the Action bar.
4. Monitor the Task bar to verify that the action completes successfully and that the layer is deployable.