How to create a VDI Windows 11 Gold Image with proper vTPM for Omnissa Horizon

 Omnissa, Omnissa Horizon, VDI  4 Responses »
Sep 292025
 
How to create a VDI Windows 11 Gold Image with proper vTPM for Omnissa Horizon

In this video, I’ll show you how to properly create a Windows 11 gold image, for use with Omnissa Horizon VDI (both persistent VM template full-clones, and non-persistent Instant Clones).

We’ll be using the manual process to create the VDI Golden Image.

In this video, I’ll show you how to:

  • Use Windows ADK and WinPE add-on to create a WinPE ISO to pre-boot the Windows 11 Installer
  • Use the WinPE ISO to pre-boot and install Windows 11, without a vTPM
  • Prepare the Windows 11 image for deployment
    • Install Omnissa Horizon agent
    • Install Microsoft 365 using the ODT (Office Deployment Toolkit)
  • Use the Omnissa Operating System Optimization Tool (OSOT)
    • Optimize the image using OSOT
    • Generalize the image using OSOT
    • Finalize the image using OSOT

Note on VDI (Virtual Desktop Infrastrucutre), TPM and vTPM devices

When deploying Windows 11 in VDI environments there are special considerations due to Windows 11 TPM requirements. Windows 11 Golden images should not have a vTPM, nor should they ever have a vTPM attached and then removed. Attaching and removing a vTPM or TPM from Windows 11 is considered data loss, and can cause issues with the image.

If you are deploying persistent full-clones, after the cloning process you can add a vTPM to the persistent VM.

If you are deploying non-persistent Instant Clones, the desktop pool in Horizon should be configured to add a vTPM to Instant Clones on provisioning.

References

A big thank you goes out to Graeme Gordon and Hilko Lantinga for their documentation and techzone articles providing this information for Partners, Customers, and Community!

Refernced Links and Documents:

Update the Omnissa UAG IP Configuration via Shell or Console

 Omnissa Horizon, Omnissa Unified Access Gateway  1 Response »
Sep 242025
 
Update Omnissa Unified Access Gateway Network Configuration via SSH or Console

So you’re in a situation where you need to update the Omnissa UAG IP Configuration via Shell or Console.

Your Omnissa UAG (Unified Access Gateway) network configuration usually takes place on deployment, or can be modified via the Web Admin interface running on port 9443.

In some scenarios you may lose access, or have to change the networking configuration when you don’t have access to the web administration GUI. This could be because of firewall rules, network changes, or troubleshooting.

PLEASE NOTE: Normally it is considered best practice to deploy new UAGs if an IP change is required. UAG deployment should be automated (using the powershell scripts from Omnissa). This post is for informational purposes only for special situations, troubleshooting, or in scenarios where deploying a new UAG, isn’t possible.

Updating your UAG IP Network Configuration

If you need to update or change your network configuration on your UAG, via console or SSH, you can run the following command:

/opt/omnissa/root/scripts/scripts/configureNetwork.sh

After executing this command, you’ll be presented with these options:

You can note numerous options for network configuration of the UAG appliance.

You can then select option “1” to view your configuration, or option “6” to configure your IP, subnet, gateway, etc.