Platform Requirements

This section serves as a checklist to make sure your Horizon DaaS 9.2.x platform has everything necessary for a successful deployment.

• Required Files

  • Automation Appliances

    • Horizon Version Manager (HVM):

      Horizon-Version-Manager-22.1.0.0-21662925_OVF10.ova

    • Horizon Air Link (HAL)

      horizon-air-link-22.1.0.0-21661035_OVF10.ova

  • Appliance Template

    `ApplianceTemplate_22_1_0_20230409_signed.ova```

    Note: If you want to change the default password on the template, perform the following steps:

    1. Deploy ApplianceTemplate_22_1_0_20230409_signed.ova in vCenter.
    2. Power on the VM and change the appliance password to the password you want to use.
    3. Export and download to a new OVA file. Use this file for all future deployments.

  • Platform

    • av-manager-2303.0.0-65-airBAT.deb
    • dbmonitor_22.1.0.deb
    • dt-aux-22_1_0.deb
    • dt-platform-22_1_0.deb
    • latest_rev.txt
    • node-manifest.json
    • wem-service-diagnose-19.3.24.deb
    • xmp-2303.0.0-2907-airBAT.deb

  • Agents

    • Latest compatible version of Horizon Agents Installer (HAI). See the Omnissa Product Interoperability Matrices.

      Note: If you are using a “hot patch” style Agent Automatic Update, you also need the related agent.tar file.

    • Latest compatible version of Unified Access Gateway (UAG). See the Omnissa Product Interoperability Matrices.

    • Latest compatible version of Dynamic Environment Manager (DEM). See the Omnissa Product Interoperability Matrices.

  • Utilities

    • WinSCP
    • 7zip or WinZip

• vCenter Server and vSphere Hypervisor (ESXi) Requirements

  • Latest compatible versions of vCenter Server and vSphere. See the Omnissa Product Interoperability Matrices.

  • Distributed Resource Scheduler (DRS) set to off or manual

  • One or more vCenter Server appliances

    Note: To use a single vCenter Server configuration, you must set the allow.shared.hostmanager policy to true. You are prompted to do this at the end of each set of installation and upgrade steps.

  • Individual ESX Host mapping is not supported.

• Networking

  • Front end/management network created and IPs designated to SP appliances.

  • BBLL (Backbone Link Local) network created and IPs designated to SP appliances.

  • IP ranges planned to accommodate your maximum appliance estimate.

    For example, if you plan on accommodating 200 total appliances, a /24 mask gives you a maximum of 254 usable IP addresses. Because you need approximately 400 IPs across 200 appliances (primary/standby), consider using a /23 mask instead.

  • One network type used across all appliances (Standard Switch VLAN, vDS VLAN, or VXLAN)

  • All required network visibility, routing, hardening, and so on, must be configured ahead of time.

  • The gateway used for the Service Provider network must have ICMP echo enabled. This is required for HVM deployment tasks.

• Storage

  • Datastores provisioned and allocated for service providers and tenants
  • All platform files and templates available in a file share accessible to the service provider and tenant

• Active Directory

  • Domain Controllers configured to Microsoft Best Practices
    • Domain Controller IP addresses and port requirements
    • NTP is properly configured and time sync is active and current.
    • Domain Controllers are on the same network.
  • Computer and User OUs, Admin Groups, User Groups, Computer/User GPOs
    • Permissions configured
    • Password never expires account option selected
    • Domain Bind account with adequate permissions
      • Full Distinguished Name
  • DNS
    • Hostnames, IPs, and open ports
    • Scavenging settings
    • Conditional Forwarding (for proper communication between service providers and data centers)
  • DHCP (static IP addressing- DHCP not required)

• Service Provider Requirements

  Note: All platform appliances must set the timezone to UTC only.

  • Horizon DaaS version required for upgrade to Horizon DaaS 9.2.0

    Service provider must be running Horizon DaaS 9.0.x or 9.1.x.

• Tenant Requirements

  • Horizon DaaS version required for upgrade to Horizon DaaS 9.2.0

    All tenants must be running Horizon DaaS 9.0.x or 9.1.x.

    Note: All Debian packages for the version you are running must be available in the service provider appliance's /data/repo folder.

  • Appliance Location in vCenter for upgrade to Horizon DaaS 9.2.0

    For upgrade to Horizon DaaS 9.2.0, all appliances must be in the root folder of vCenter.

    Note: If appliances are not in the root folder, you might need to move them there.

  • Network

    • If you are using Instant Clone desktops, you cannot use VLANs. IC desktops require DVS port groups or VXLANs to function properly.
    • All virtual machines (appliances, utility servers, images, and so on) must be using VMXNET3 network adapters. E1000 network adapters are not supported.

  • VPN

    • Bandwidth requirements
    • PSK, endpoint IPs

  • UAG

    See information in the Tenant Installation Worksheet.

  • Active Directory

    • Domain Controller IP addresses, port requirements

    • Computer and User OUs, Admin Groups, User Groups, Computer/User GPOs created

      • Horizon View, UEM, *.admx, and *.adml files downloaded
      • Import procedure
      • Service Accounts have Password never expires account option selected

    • Domain Join account with adequate permissions

      • Full Distinguished Name

    • Domain Bind account with adequate permissions

      • Full Distinguished Name

    • NTP properly configured and time sync active and current

      Note: Sysprep/Generalize cloned server images each time to avoid domain join issues.

  • DHCP Server

    • Defined Scopes, reservations, and so on
    • Lease time for scopes set at eight hours instead of the default eight days

  • DNS Server

    • Hostname, IPs
    • Proper DNS record scavenging configuration

  • File Server

    • General File sharing and permissions configured
    • HAI installer and Agent.tar file accessible on the file share

  • Images

    • VM hardware version up to date
    • VMware Tools up to date
    • Proper agent versions for this version of Horizon DaaS (Horizon Agent Integrated Agent, UEM, and so on)
    • Image optimized (OptimizeanImage.md))

  • Workspace ONE UEM

    • Workspace ONE UEM shares created and configured
    • Workspace ONE UEM installed and configured on the designated server
    • Workspace ONE UEM initial configuration complete
    • GPO configuration and linking to Computer OUs complete

• Compute Resources

  • If you are upgrading an existing environment, confirm that each desktop manager is configured with only one compute resource. Multiple compute resources per desktop manager are not supported.

    Note: Any offline or deactivated tenant organizations must be deleted from the platform or reconfigured with a single compute pool.

  • No stand-alone ESXi hosts in the existing compute pools.

• File Integrity Verification

  To ensure a successful, issue-free installation, verify that the core installation files have the correct checksum before you start. See Verify File Integrity.