horizon daas 9.0.x installation and upgrade - vmware ...€¦ · horizon daas worksheets in...

Horizon DaaS 9.0.x Installation and Upgrade

VMware Horizon DaaS

You can find the most up-to-date technical documentation on the VMware website at:

https://docs.vmware.com/

VMware, Inc.3401 Hillview Ave.Palo Alto, CA 94304www.vmware.com

Copyright ©

2020 VMware, Inc. All rights reserved. Copyright and trademark information.


VMware, Inc. 2

https://docs.vmware.com/https://docs.vmware.com/copyright-trademark.html

Contents

1 About this Document 5

2 Before You Begin 6Platform Requirements 6

Horizon DaaS Worksheets in Microsoft Excel Format 10

3 Install Horizon Version Manager 12

4 Install the Service Provider 21Set Up vCloud Usage Meter Integration 28

5 Upgrade the Service Provider 31Set Up vCloud Usage Meter Integration 36

6 Installing a Tenant 38Deploy a Tenant 38

Provision a Tenant 46

Install Unified Access Gateway 51

7 Upgrading a Tenant 56Run the Upgrade Task 56

Run the Migrate Task 58

Install Unified Access Gateway 60

8 Hotfix Management 65

9 Instant Clone Image Management 69

10 Agent Installation 70Configure Automatic Agent Updates Without Internet Access 70

Install Agents Manually 75

Optimize an Image 76

11 Import an Image 78Troubleshooting Agent Pairing 82

12 Roll Back an Upgrade 84

VMware, Inc. 3

13 Additional Information 87

14 Additional Tasks 88Configure NTP on Windows Server 88

Verify File Integrity 89


VMware, Inc. 4

About this Document 1This document provides instructions for performing an upgrade or new installation of a VMware Horizon DaaS environment.

Note For information about upgrading from Horizon DaaS 9.0.0 to Horizon DaaS 9.0.1, see the Horizon DaaS 9.0.x Release Notes.

VMware, Inc. 5

https://docs.vmware.com/en/VMware-Horizon-DaaS/services/rn/Horizon-DaaS-900-Release-Notes.html#901

Before You Begin 2This section provides access to information you need before you perform an installation or upgrade.

This chapter includes the following topics:

n Platform Requirements

n Horizon DaaS Worksheets in Microsoft Excel Format

Platform Requirements

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

n Required Files

n Automation Appliances

n Horizon-Version-Manager-1.0.0.0-16097526_OVF10.ova (1,119 MB)

n horizon-air-link-vcpp-2.1.0.0-16064524_OVF10.ova (605 MB)

n Appliance Template

ApplianceTemplate_20_2_0_20200319_signed.ova

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

1 Deploy ApplianceTemplate_20_2_0_20200319_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.

n Platform

n av-manager-23.1.0-4299-airBAT.deb

n cloud-connector-client_3.1.0.deb

n dbmonitor_20.2.0.deb

VMware, Inc. 6

n dt-aux-20_2_0.deb

n dt-keybox_2.85.01.15712778.deb

n dt-platform-20_2_0.deb

n latest_rev.txt

n node-manifest.json

n wem-service-diagnose-19.3.24.deb

n xmp-23.1.0-2660-airBAT.deb

n Agents

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

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

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

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

n Utilities

n WinSCP

n 7zip or WinZip

n vCenter Server and vSphere Hypervisor (ESXi) Requirements

n Latest compatible versions of vCenter Server and vSphere. See the VMware Product Interoperability Matrices.

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

n 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.

n Individual ESX Host mapping is not supported.

n Networking

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

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

n IP ranges planned to accommodate your maximum appliance estimate.


VMware, Inc. 7

https://www.vmware.com/resources/compatibility/sim/interop_matrix.phphttps://www.vmware.com/resources/compatibility/sim/interop_matrix.phphttps://www.vmware.com/resources/compatibility/sim/interop_matrix.phphttps://www.vmware.com/resources/compatibility/sim/interop_matrix.phphttps://www.vmware.com/resources/compatibility/sim/interop_matrix.phphttps://www.vmware.com/resources/compatibility/sim/interop_matrix.phphttps://www.vmware.com/resources/compatibility/sim/interop_matrix.phphttps://www.vmware.com/resources/compatibility/sim/interop_matrix.php

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.

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

n All required network visibility, routing, hardening, and so on, configured ahead of time

n Storage

n Datastores provisioned and allocated for service providers and tenants

n All platform files and templates available in a file share accessible to the service provider and tenant

n Active Directory

n Domain Controllers configured to Microsoft Best Practices

n Domain Controller IP addresses and port requirements

n NTP is properly configured and time sync is active and current.

n Domain Controllers are on the same network.

n Computer and User OUs, Admin Groups, User Groups, Computer/User GPOs

n Permissions configured

n Password never expires account option selected

n Domain Bind account with adequate permissions

n Full Distinguished Name

n DNS

n Hostnames, IPs, and open ports

n Scavenging settings

n Conditional Forwarding (for proper communication between service providers and data centers)

n DHCP (static IP addressing- DHCP not required)

n Tenant Requirements

n Horizon DaaS version

All tenants must be running Horizon DaaS 8.0.1.

Note All 8.0.0 and 8.0.1 debian packages must be available in the service provider appliance's /data/repo folder.

n Appliance Location in vCenter


VMware, Inc. 8

For upgrade, 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.

n Network

n If you are using Instant Clone desktops, you cannot use VLANs. IC desktops require DVS port groups or VXLANs to function properly.

n All virtual machines (appliances, utility servers, images, and so on) must be using VMXNET3 network adapters. E1000 network adapters are not supported.

n VPN

n Bandwidth requirements

n PSK, endpoint IPs

n UAG

See information in the Tenant Installation Worksheet.

n Active Directory

n Domain Controller IP addresses, port requirements

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

n VMware View, UEM, *.admx, and *.adml files downloaded

n Import procedure

n Service Accounts have Password never expires account option selected

n Domain Join account with adequate permissions


n Domain Bind account with adequate permissions


n NTP properly configured and time sync active and current

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

n DHCP Server

n Defined Scopes, reservations, and so on

n Lease time for scopes set at eight hours instead of the default eight days

n DNS Server

n Hostname, IPs

n Proper DNS record scavenging configuration


VMware, Inc. 9

n File Server

n General File sharing and permissions configured

n HAI installer and Agent.tar file accessible on the file share

n Images

n VM hardware version up to date

n VMware Tools up to date

n Proper agent versions for this version of Horizon DaaS (Horizon Agent Integrated Agent, UEM, and so on)

n Image optimized (see Optimize an Image)

n Workspace ONE UEM

n Workspace ONE UEM shares created and configured

n Workspace ONE UEM installed and configured on the designated server

n Workspace ONE UEM initial configuration complete

n GPO configuration and linking to Computer OUs complete

n Compute Resources

n 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.

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

n 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.

Horizon DaaS Worksheets in Microsoft Excel Format

To simplify planning and ensure all information needed to install or upgrade Horizon DaaS is available, download and fill out the Horizon DaaS 9.0.0 Worksheets in Microsoft Excel Format, which help you gather the inputs required provide additional guidance.

In addition to reading the Platform Requirements checklist, you should also download the Horizon DaaS 9.0.0 Worksheets in Microsoft Excel Format. You can download these documents by clicking the link in the left navigation panel on the VMware Horizon DaaS Documentation page or by clicking this link: Horizon DaaS 9.0.0 Worksheets in Microsoft Excel Format.


VMware, Inc. 10

https://docs.vmware.com/en/VMware-Horizon-DaaS/index.htmlhttps://docs.vmware.com/en/VMware-Horizon-DaaS/9.0.0/horizon-daas-worksheets.zip

This ZIP file contains two Microsoft Excel workbooks: Service Provider Worksheets and Tenant Worksheets.

n Service Provider Worksheets contains the Service Provider Installation Worksheet, the Service Provider Upgrade Worksheet, and a Blue-Green IP Planning worksheet.

n Tenant Worksheets contains the Tenant Installation Worksheet, the Tenant Upgrade Worksheet, and a Blue-Green IP Planning worksheet.

These worksheets are referred to in the installation and upgrade procedures.


VMware, Inc. 11

Install Horizon Version Manager 3This task describes how to install Horizon Version Manager (HVM)

VMware, Inc. 12

Procedure

1 Deploy the Horizon Version Manager OVA in vCenter.

a Open a browser and log into your management vCenter.

b Right click the cluster and click Deploy OVF Template…

c Select the VM folder to which to deploy the appliance and name the appliance according to the details in the Service Provider Installation Worksheet.

d Select the cluster, click Next, and wait for the validation to be finished.

e Click Next on the Review details screen.


VMware, Inc. 13

f Select the datastore and click Next.

g Select the destination network and click Next.


VMware, Inc. 14

h On the Customize template screen, fill out the four Root and Rundeck UI password text boxes, expand the Networking drop-down, fill out the four remaining text boxes, and click Next.

i On the Ready to complete screen, click Finish to begin the deployment.

2 Power on VM and wait a few minutes.

3 Copy platform files to appliance.

a Start WinSCP and log into the newly deployed HVM appliance through its IP address using protocol type SCP and user name root.

b Accept all certificates.

c Transfer all Debian files, JSON, latest_rev.txt, and appliance template OVA from the folder in your file share to /opt/vmware/hvm/install-upgrade. There are 11 files in total.


VMware, Inc. 15

4 Change the permissions on the JSON manifest.

a Right click the node-manifest.json file in WinSCP, click Properties, and change the permissions so that Owner, Group, and Others have full Read/Write/Execute.

b Click OK.

5 Close WinSCP.


VMware, Inc. 16

6 Log into Horizon Version Manager RunDeck, proceeding past any SSL warnings.

a In a browser, navigate to https://HVM_IPADDRESS:4443/

b Log in with user name rundeck and the password you set previously.

7 Click Projects > Horizon-DaaS.


VMware, Inc. 17

8 Click Jobs > Horizon-Air-Link Installer.

9 Fill out information based on the details in the Service Provider Installation Worksheet. All text boxes are case-sensitive

Note the following:

n Make sure to select the HAL OVA, not HVM.

n You can skip the Route-Gateway, Webproxy-Server, and Webproxy-Port text boxes.

n If you are reattempting this step, you must change the Force-Deploy text box to Yes to overwrite the previous failed appliance deployment.

n For VXLAN, use the full network name that displays in vCenter/Networking.


VMware, Inc. 18

10 Scroll back to the top and click Run Job Now.

11 Monitor the upload status in the bottom left of the browser window.

12 On the next screen, click the Log Output button and monitor progress.

13 If you must stop a job for any reason, scroll to the top of the page and click the Kill Job X button in the top right.

14 If the job fails and you must rerun it for any reason, scroll to the top of the page and click the Run Again… button and click Run Again. This action takes you back to the previous page so you can make corrections.

15 Once the upgrade is finished, the following appears in the log output:


VMware, Inc. 19

You can also scroll to the top of the page and verify that the job has a green check next to the job name.

16 You can now use Horizon Version Manager to deploy new service providers, upgrade existing service providers from Horizon DaaS 8.0.1, or upgrade and migrate existing tenants.


VMware, Inc. 20

Install the Service Provider 4This topic describes how to deploy a new service provider.

Procedure

1 Log into the Horizon Version Manager portal.

Rundeck opens in your browser.

2 Click Projects > Horizon-DaaS.

VMware, Inc. 21

3 Click Jobs > Horizon DaaS Install Management Appliances.

4 Fill out the information based on the details in the Service Provider Installation Worksheet and click Run Job Now.

Note the following:

n VXLAN networks need the full network name as is displayed in vCenter. For example, vxw-dvs-14-universalwire-33-sid-12345-NSX-U-NETWORK-NAME-01

n If you did not change the Template OVA password, the value in the Default-Template-Password text box must be Desktone1.

Click the top left Log Output button and monitor upload status on the bottom left of the browser window.

5 HVM deploys the SP1, SP2, RM1, and RM2 appliances concurrently.

6 After the appliances are deployed and powered on, click Jobs > Horizon DaaS SP Domain Bind.


VMware, Inc. 22

7 Fill out the domain bind information based on the values in the Service Provider Installation Worksheet, and then click Run Job Now.

8 Click Jobs > Horizon DaaS SP Compute Assignment.

9 Enter information for your Service Provider appliance and vCenter Server.

10 Enter cluster information as described below.

Option Description

Cluster-Name Enter a unique name for the compute.

Cluster-Usage Select one or more of the three options (Service, Tenant, Network).

n Select Service to install Service Provider and Resource Manager appliances on the cluster.

n Select Tenant to install Tenant and additional Desktop Manager appliances on the cluster.

n Select Network to install Network appliances like Unified Access Gateway and NSX Edge Gateway on the cluster.

If you only have one cluster, select all three options.

Cluster-Resource-Ratios Make any desired changes to the default values.

n Memory Over allocation Ratio - This ratio determines the amount of virtual machine memory that the compute resource can allocate. For example, if the ratio is 4.0 and the memory capacity of the compute resource is 64 GB, then it supports up to 256 GB of virtual machine memory. The default value is 1.0.

n Virtual to Physical CPU Ratio - This ratio determines the number of virtual machine CPUs that the compute resource can allocate. For example, if the ratio is 8.0 and the number of physical CPU cores on the compute resource is 8, then it supports up to 64 virtual machine CPU cores. The default value is 12.

11 Click Run Job Now.

12 Open a browser and navigate to the SP IP address using https://. For example: https:///service.


VMware, Inc. 23

13 Log into Service Center.


VMware, Inc. 24

14 Check the cluster resource ratios you set for the new cluster.

a Click Service Grid > Resources.

b Click Compute Resources, navigate to the new cluster, and then click Edit Compute Resource.


VMware, Inc. 25

A dialog box displays showing the current settings for the compute. If any of the ratios is invalid, the text box is outlined in red. If all ratios are valid, then none of them are outlined in red, as in the example below.

c If you see a value outlined in red, correct that value and click Save. Otherwise click Cancel.

15 (Optional) Rename the appliance groups.

a Select Service grid > Resources

b Click a BBLL IP address link.


VMware, Inc. 26

c Determine whether the appliance group is a Service Provider group or a Resource Manager group by looking at the appliance shown in the Hostname field.

This is an example of a Service Provider group:

This is an example of a Resource Manager group:

d Double-click the Name text box, enter a new user-friendly name such as Service Providers or Resource Managers, and click OK.

e Repeat the steps above for the other appliance group.

16 Upload certificates (this task can be done later if necessary).

a Select Configuration > General.

b Click the Click here link under Other Configuration.


VMware, Inc. 27

c Click the Certificates tab.

d Select the CA, SSL cert, and SSL key files, then click Submit.

e Click the Click here link on the same page to initiate a rolling reboot on the appliances to finish the certificate installation.

17 (Optional) Capacity Model Collections and Desktop Models. If you want to define additional collections or change the default model, perform the following steps.

a Select Configuration > Desktop Capacity.

b Add new collection definitions by clicking the + sign.

18 If you are using a single vCenter Server configuration, set the allow.shared.hostmanager policy to true.

Important Using a single vCenter Server configuration is not considered a best practice for production environments. Use this configuration for demonstration or limited-use environments only.

a In Service Center, click tenants > policy.

The Policy configuration page displays.

b Select an organization from the Organization drop-down menu.

c Click an empty area of the page to the right or left of the policy list.

d Type dtpolicy.

Additional hidden policies display in the list.

e If allow.shared.hostmanager is set to false (the default value), double-click on the word false to edit the value.

f Enter true and click OK.

Set Up vCloud Usage Meter Integration

On your new or upgraded tenant, you can configure integration with VMware vCloud® Usage Meter.

Attention This procedure requires vCloud Usage Meter 4.2, which has a release date of May 21, 2020.


VMware, Inc. 28

Procedure

1 In Service Center, add a user account with the Read-only mode - View all/No Saving role.

a Click configuration > domain.

b Click on the name of the domain on the left side of the screen, then click Edit.

c Click the Group Info tab and then click the Add Admin Group hyperlink.

d 4. Select the role on the right and begin typing the name of the AD group name you want to add using distinguished name format. The system provides a dropdown of all available group names starting with the text you typed. Click it, then click the Save button.


VMware, Inc. 29

2 Install vCloud Usage Meter following the steps in the Deploying and Configuring vCloud Usage Meter guide on the vCloud Usage Meter documentation page.

3 Using the read-only account you have created, follow the instructions for adding Horizon DaaS in the Using and Managing vCloud Usage Meter guide on the vCloud Usage Meter documentation page.

Attention Horizon DaaS 9.0.0 and Horizon Cloud on IBM Cloud 20.2.0 are the same release. As a result, when you are setting up vCloud Usage Meter integration, you might see the 20.2.0 product version instead of 9.0.0. If you see this, it does not indicate a problem of any kind, so you can still proceed with the setup.


VMware, Inc. 30

https://docs.vmware.com/en/vCloud-Usage-Meter/index.htmlhttps://docs.vmware.com/en/vCloud-Usage-Meter/index.htmlhttps://docs.vmware.com/en/vCloud-Usage-Meter/index.html

Upgrade the Service Provider 5This topic describes the procedure for upgrading your service provider appliance.


Procedure


VMware, Inc. 31


2 Click Jobs > Horizon DaaS Upgrade Management Appliances.

Note Appliances must be in the root folder in vCenter. If not, the system cannot find the specified VMs and the job fails.

3 Fill out the info based on the details in the Service Provider Upgrade Worksheet and click Run Job Now.

Note If you did not change the Template OVA password, the value in the Default-Template-Password text box must be Desktone1.

4 Click the top left Log Output button and monitor the upload status on the bottom left of the browser page.

If your job fails at this point with error:

Appliance# already exists

then delete from the disk the VMs in the vCenter folder named 20.2.0.x.x.

5 The following output appears in the log when the job has finished successfully:

You can also scroll to the top of the page and verify that the job has a green check next to the job name.


VMware, Inc. 32


VMware, Inc. 33

6 Verify the new version:

a Log into Service Center using the new IP address.

b Click the Version hyperlink at the bottom of the page.

You can also click appliances and see the updated versions.


VMware, Inc. 34

7 Update DNS records so that the records for Service Provider appliance A point to the new IP addresses.

Note If you have any bookmarks pointing to the old vCenter IP, you must update them.

8 If you are using a single vCenter Server configuration, after the tenant appliances are deployed you must set the allow.shared.hostmanager policy to true.




b Click an empty area of the page to the right or left of the policy list.

c Type dtpolicy.



VMware, Inc. 35

d If allow.shared.hostmanager is set to false (the default value), double-click on the word false to edit the value.

e Enter true and click OK.

Set Up vCloud Usage Meter Integration

On your new or upgraded tenant, you can configure integration with VMware vCloud® Usage Meter.

Attention This procedure requires vCloud Usage Meter 4.2, which has a release date of May 21, 2020.

Procedure

1 In Service Center, add a user account with the Read-only mode - View all/No Saving role.

a Click configuration > domain.

b Click on the name of the domain on the left side of the screen, then click Edit.


VMware, Inc. 36

c Click the Group Info tab and then click the Add Admin Group hyperlink.

d 4. Select the role on the right and begin typing the name of the AD group name you want to add using distinguished name format. The system provides a dropdown of all available group names starting with the text you typed. Click it, then click the Save button.

2 Install vCloud Usage Meter following the steps in the Deploying and Configuring vCloud Usage Meter guide on the vCloud Usage Meter documentation page.

3 Using the read-only account you have created, follow the instructions for adding Horizon DaaS in the Using and Managing vCloud Usage Meter guide on the vCloud Usage Meter documentation page.

Attention Horizon DaaS 9.0.0 and Horizon Cloud on IBM Cloud 20.2.0 are the same release. As a result, when you are setting up vCloud Usage Meter integration, you might see the 20.2.0 product version instead of 9.0.0. If you see this, it does not indicate a problem of any kind, so you can still proceed with the setup.


VMware, Inc. 37

https://docs.vmware.com/en/vCloud-Usage-Meter/index.htmlhttps://docs.vmware.com/en/vCloud-Usage-Meter/index.htmlhttps://docs.vmware.com/en/vCloud-Usage-Meter/index.html

Installing a Tenant 6You can install a tenant in Service Center.

You install a tenant by first deploying the tenant and then provisioning the tenant.

Important You can only have three tenants deployed simultaneously. Attempting to deploy more than three tenants can cause deployment problems.


n Deploy a Tenant

n Provision a Tenant

n Install Unified Access Gateway

Deploy a Tenant

You can deploy a tenant using Service Center.

Prerequisites

Confirm that the Domain Join and Domain Bind accounts have been created, permissions are properly assigned, accounts are located in the proper OUs, and static DNS A records have been created.

Procedure

1 On the Tenants tab in Service Center, click register a tenant.

VMware, Inc. 38

2 Fill out the General Info tab.

3 On the Networks tab, click the Add button next to the data center name.

4 Enter the network information from the Tenant Installation Worksheet.

n For standard VLANs, use the VLAN ID in the Network ID text box. For example, 1027.

n For DVS Port Groups, use the Port Group Name in the Network ID text box. For example, dvs-TenantA-Desktops-01.

n For VXLANs, truncate the beginning of the VXLAN name up to the SID and keep the rest when entering the name into the Network ID text box. For example:

n Name in vCenter: vxw-dvs-100-universalwire-24-sid-50017-NSX-U-VCAN-DEMO-DESKTOP-01

n Truncated name to use in Service Center: 50017-NSX-U-VCAN-DEMO-DESKTOP-01


VMware, Inc. 39

5 Click Save and Create Appliances.

6 On the next page, fill out the tenant appliance information and click Create Appliances.

7 To monitor appliance reservations, click appliances > reservations.

Note Wait until the tenant appliances have deployed before proceeding.

8 If you are using a single vCenter Server configuration and you have not already made this setting, you must set the allow.shared.hostmanager policy to true.





c Type dtpolicy.





VMware, Inc. 40

9 Add a Tenant-dedicated vCenter to the Compute Resources.

a Select service grid > resources.

b Click the Compute Resources tab, then the Add Host Manager tab.


VMware, Inc. 41

c Enter the FQDN and credentials of the vCenter Server you want to add, select resource managers from the drop-down menu, then click Add.

d Accept the certificate.

10 Assign resources by performing the following steps.

a Click service grid > resources.

b On the Desktop Managers tab, click the Tenant name and then click the Compute Resources tab.

c Select the appropriate vCenter Server and click Assign.


VMware, Inc. 42

d Select the cluster.

e Select the tenant and network under Usage.

f To dedicate this cluster to a single tenant, confirm that the Share this Compute Resource check box is not selected, then click Save.

g To share this cluster across multiple tenants, confirm that the Share this Compute Resource check box is selected, then click Save.

h On the following page, select the required Memory Partition and CPU Partition and click Save.

i On the Desktop Managers tab, click the Networks tab, then click the Assign button next to the network resource designated for this tenant.


VMware, Inc. 43

j Click service grid > resources, click the Desktop Managers tab, and then click the Datastores tab.

k Enter the Datastore name as seen in vCenter, then click Submit.

n Because this is a regex text box, you can enter more complex strings, such as:

n Tenant1-SSD-01 | Tenant2-SSD-02

n Tenant1-SSD-*

n Use the Datastore name as seen in vCenter Datastores and Datastore Clusters.

11 Configure User Licenses and Desktop Capacity.

a In Service Center, click tenants > browse tenants.

b Click the Edit button next to the appropriate tenant.

c Select the Quotas tab.


VMware, Inc. 44

d Modify the User License text box.

e Click that section’s Update button.

f Select the data center from the drop-down menu under Desktop Capacity, then assign the desired desktop capacity.

g Click that section’s Update button.

h Select the data center from the drop-down menu under Template Quota, then assign the desired template quota.

i Click that section’s Update button.


VMware, Inc. 45

12 Apply Certificates (this step can be performed at another time).

a In Service Center, click Tenants > Browse Tenants, then click the Edit button next to the appropriate tenant.

b Click the Certificates tab.

c Browse and select the appropriate files for the CA Certificate, SSL Certificate, and SSL Key, then click Submit.

d Click the Click here link on the same page to initiate a rolling reboot on the appliances to finish the certificate installation.

What to do next

Provision a Tenant.

Provision a Tenant

After you have finished deploying a tenant, you can provision the tenant in the Administration Console.


VMware, Inc. 46

Procedure

1 On the Tenants tab in Service Center, click Edit next to the tenant and click the Show Info button to display the default local login credentials. Make a note of these credentials.


VMware, Inc. 47

2 In your browser, navigate to the tenant appliance’s floating IP address (https://10.1.1.12/admin) and log in with the local credentials shown in Service Center.

3 Update the password and continue to the next screen.


VMware, Inc. 48

4 Configure Active Directory.

a Click Configure next to Active Directory in the Getting Started wizard.

b Enter the domain bind info based on the Tenant Installation Worksheet, and then click Domain Bind.


VMware, Inc. 49

c Enter the domain join info based on the Tenant Installation Worksheet, and then click Save.

d Enter administrator group information and click Save.


VMware, Inc. 50

5 Log in with Domain Admin credentials.

What to do next

After you have finished provisioning the new tenant, you must set up Unified Access Gateway (UAG). See Install Unified Access Gateway.

Install Unified Access Gateway

You can install VMware Unified Access Gateway (UAG) in your environment.

Procedure

1 In vCenter, navigate to the VM folder where you want to install the Unified Access Gateway appliance, right click, and select Deploy OVF Template.

2 Using the information in the Tenant Installation Worksheet, fill out the text boxes and click Finish to deploy.

#-NIC deployment options are 1-NIC, 2-NIC, and 3-NIC

Note You must enter passwords in the OVF deployment forms.


VMware, Inc. 51

3 Power on the VM. This process might take over five minutes. Once the VM is fully started up, the following screen displays in the console:

4 If you are missing Unified Access Gateway configurations, run the apsetup script.

a Log into the Tenant appliance using one of the following methods:

n Console to the Tenant appliance and log in with user desktone.

n Start a PuTTY session to the Service Provider appliance, log in with user desktone, and SSH to the BBLL IP of the Tenant appliance.

b Navigate to the directory shown and run the apsetup script:

sudo /usr/local/desktone/scripts/apsetup.sh

c Respond to the prompts according to the information in the Tenant Installation Worksheet. If the setup was successful, the script exits with Response status: 200.


VMware, Inc. 52

5 Update the certificates (this task can be done later).

If you are using a 3-NIC configuration, you must perform the following steps from a desktop with access to the UAG management network and the network with the share containing the SSL certificates.

a Open a browser and log into the UAG appliance at https://UAG-IP:9443/admin with the user name admin.

b Click Select under Configure Manually.


VMware, Inc. 53

c Under Advanced Settings, click the gear icon next to TLS Server Certificate Settings.

d Select the Internet Interface check box.


VMware, Inc. 54

e Next to Private Key, click the hyperlink to browse to the folder containing your certificates.

Note You might have to click All Files in the file type drop-down menu in the File Open dialog box that pops up.

f Do the same for Certificate Chain, then click the blue Save button.

The text Server Certificate Uploaded Successfully displays in green at the top right of the browser frame.

6 Wait for the UAG services to restart and configuration to complete. This can take 5–10 minutes.

7 Validate configuration success by checking external connectivity.

What to do next

Chapter 10 Agent Installation.


VMware, Inc. 55

Upgrading a Tenant 7You can upgrade a tenant from Horizon DaaS 8.0.1 to Horizon DaaS 9.0.0.


There are four tasks required to upgrade a tenant.

n Running an Upgrade task in RunDeck, which stages the new “Blue” tenant appliances and prepares them for cut-over.

n Running a Migrate task in RunDeck on the day of your maintenance window, which powers off the old tenants and cuts over to the new appliances.

n Setting up Unified Access Gateway (UAG)

n Configuring automatic agent upgrades.

After these steps have been performed, you can start migrating and updating images, desktops, pools, and farms.

Note the following:

n Your tenant assignments still work even though they are on DaaS Agent 8.0.x.

n You can only update and migrate one tenant at a time.

n Downloading usage reports on a tenant that has been upgraded but not migrated will not work until after migration.


n Run the Upgrade Task

n Run the Migrate Task

n Install Unified Access Gateway

Run the Upgrade Task

The first task for upgrading a tenant is running the Upgrade task in RunDeck.

VMware, Inc. 56


Procedure


2 Click Jobs > Horizon DaaS Upgrade Tenant Appliances.

3 Fill out the information, then click Run Job Now.

Note The value for Default-Template-Password is Desktone1 unless you have previously changed it.

4 Click the top left Log Output >> button and monitor upload status on the bottom left of the browser window.


VMware, Inc. 57

Results

After the job has finished successfully, the following output displays in the log:

What to do next

After the appliances have been staged, the next step is to migrate from the old appliances to the new appliances. See Run the Migrate Task.

Run the Migrate Task

After you have finished running the Upgrade task, you must run the Migrate task in RunDeck.

Prerequisites

Before you can run the Migrate task, you must first finish running the Upgrade task.

Procedure

1 Get the tenant OrgID from Service Center.

a Log into vCenter.

b Find the Id text box to the left of the tenant name.

2 Click Jobs > Horizon DaaS Migrate Tenant Appliances.

3 Fill out the information, then click Run Job Now.


VMware, Inc. 58

4 Click the Log Output button and monitor upload status on the bottom left of the browser window.

After the job has finished successfully, the following output displays in the log:

5 To verify the new version, log into the Administration Console, click the ? icon, and select About.

A dialog appears showing the version number.


VMware, Inc. 59

6 If you are using a single vCenter Server configuration, set the allow.shared.hostmanager policy to true.





c Type dtpolicy.




What to do next

After you have finished running the Migrate task for the new tenant, you must set up Unified Access Gateway (UAG). See Install Unified Access Gateway.

Install Unified Access Gateway

You can install VMware Unified Access Gateway (UAG) in your environment.

Procedure

1 In vCenter, navigate to the VM folder where you want to install the Unified Access Gateway appliance, right click, and select Deploy OVF Template.

2 Using the information in the Tenant Installation Worksheet, fill out the text boxes and click Finish to deploy.

#-NIC deployment options are 1-NIC, 2-NIC, and 3-NIC

Note You must enter passwords in the OVF deployment forms.


VMware, Inc. 60

3 Power on the VM. This process might take over five minutes. Once the VM is fully started up, the following screen displays in the console:

4 If you are missing Unified Access Gateway configurations, run the apsetup script.

a Log into the Tenant appliance using one of the following methods:

n Console to the Tenant appliance and log in with user desktone.

n Start a PuTTY session to the Service Provider appliance, log in with user desktone, and SSH to the BBLL IP of the Tenant appliance.

b Navigate to the directory shown and run the apsetup script:

sudo /usr/local/desktone/scripts/apsetup.sh

c Respond to the prompts according to the information in the Tenant Installation Worksheet. If the setup was successful, the script exits with Response status: 200.


VMware, Inc. 61

5 Update the certificates (this task can be done later).

If you are using a 3-NIC configuration, you must perform the following steps from a desktop with access to the UAG management network and the network with the share containing the SSL certificates.

a Open a browser and log into the UAG appliance at https://UAG-IP:9443/admin with the user name admin.

b Click Select under Configure Manually.


VMware, Inc. 62

c Under Advanced Settings, click the gear icon next to TLS Server Certificate Settings.

d Select the Internet Interface check box.


VMware, Inc. 63

e Next to Private Key, click the hyperlink to browse to the folder containing your certificates.

Note You might have to click All Files in the file type drop-down menu in the File Open dialog box that pops up.

f Do the same for Certificate Chain, then click the blue Save button.

The text Server Certificate Uploaded Successfully displays in green at the top right of the browser frame.

6 Wait for the UAG services to restart and configuration to complete. This can take 5–10 minutes.

7 Validate configuration success by checking external connectivity.

What to do next

Chapter 10 Agent Installation.


VMware, Inc. 64

Hotfix Management 8Hotfix deployment and management for Horizon DaaS 9.0.0 (and 8.0.0) has been streamlined by combining multiple hotfixes into a single package, called an update. For example, a Horizon DaaS 9.0.0 Update 2 package would contain all fixes from Horizon DaaS 9.0.0 Update 1, along with additional fixes found only in Update 2.

Horizon DaaS 9.0.0 hotfixes and updates are deployed using Horizon Version Manager (HVM), and it is advised to use the latest HVM version available on My VMware. HVM hotfix management includes uploading the updates, refreshing the list of available hotfixes and updates, applying them to appliances, detecting the presence of previously deployed updates on appliances, and reverting appliances to a previous state.

Upload Hotfix Artifacts

Refresh the Hotfix List

Apply a Hotfix

Detect Hotfixes on DaaS Appliances

Revert Appliances to a Pre-Hotfix State

Upload Hotfix Artifacts

Note Hotfixes are uploaded to the Horizon Version Manager appliance, not to a DaaS appliance.

There are two different procedures for uploading artifacts, depending on the source machine from which you are performing the upload.

n To upload hotfix artifacts from a jump host or local UNIX machine:

a Log into the Horizon Version Manager portal.

b Click Projects > Horizon-DaaS-Artifact-Upload.

c Click Jobs > Upload Artifacts to Horizon Version Manager.

VMware, Inc. 65

https://my.vmware.com/

d Enter information as described in the following table.

Field Description

Artifact-Type Select hotfixes.

File Click New Value + and paste the UNIX absolute path of the file to upload. For example, /home/guest/file1.tgz.

Repeat for each hotfix file you want to upload.

IP-Address IP address of the machine where the file is located.

User-Name User name for the machine where the file is located.

User-Password User password for the machine where the file is located.

e Click the Run Job Now button on the top right of the page.

Rundeck shows the progress of the file transfer, followed by a message indicating that the transfer has been successful.

n To upload hotfix artifacts from a Microsoft Windows or Mac machine:

a Upload the file to your Horizon Version Manager appliance using a file transfer client such as WinSCP for Microsoft Windows or Filezilla for Mac.

b Change permissions for the file. For example:

chmod 744 file1.tgz

c Change ownership for the file.

$ chown -R rundeck:rundeck file1.tgz

Refresh the Hotfix List

If you have uploaded hotfix artifacts since the last time you ran the Refresh Hotfix List job, run that job now. Running the Refresh Hotfix List job makes your recently uploaded hotfixes available when you want to apply them to your appliances.

1 In Rundeck, click Projects > Horizon-DaaS-HotFix-Management.

2 Click Jobs > Refresh Hotfix List.

3 Click the Run Job Now button.

Rundeck shows the progress of the refresh, followed by a message in the top right of the page indicating that the refresh has been successful.


VMware, Inc. 66

Apply a Hotfix

There are two different jobs for applying hotfixes to appliances. The job you use depends on whether you are applying hotfixes to Tenant appliances in a "pre-migrated" state. These are Tenants for which you have run the Upgrade task but not yet run the Migrate task. For more information on this distinction, see Chapter 7 Upgrading a Tenant.

n To apply hotfixes to Tenant appliances that have been upgraded but not yet migrated:

a In Rundeck, click Projects > Horizon-DaaS-HotFix-Management.

b Click Jobs > Apply Hotfix to Pre-Migrated Tenant Appliances.

c For Org-DaaS-Version, select the current version of Horizon DaaS that is running on the appliances.

Available hotfixes for that version appear next to Hotfix.

Note If you see hotfixes marked as only applying to certain types of appliances, it is not something with which you need to be concerned. The system applies all hotfixes to the appropriate appliances without any additional action on your part.

d Select hotfixes to install.

e Fill in the rest of the required information and click Run Job Now.

Rundeck shows the progress of the job, followed by a message in the top right of the page indicating that the hotfix has been successful.

n To apply a hotfix to DaaS management (Service Provider and Resource Manager) appliances and to Tenant appliances that are not in the "pre-migrated" state described above

a In Rundeck, click Projects > Horizon-DaaS-HotFix-Management.

b Click Jobs > Apply Hotfix to DaaS Appliances.

c For Org-DaaS-Version, select the current version of Horizon DaaS that is running on the appliances.

Available hotfixes for that version appear next to Hotfix.

Note If you see hotfixes marked as only applying to certain types of appliances, it is not something with which you must be concerned. The system applies all hotfixes to the appropriate appliances without any additional action on your part.

d Select hotfixes to install.

e If you are reapplying hotfixes following a previous failed attempt, select Yes in the Force drop-down menu. Otherwise, leave the default value of No.

f Fill in the rest of the required information and click Run Job Now.

Rundeck shows the progress of the job, followed by a message in the top right of the page indicating that the hotfix has been successful.


VMware, Inc. 67

Detect Hotfixes on DaaS Appliances

1 In Rundeck, click Projects > Horizon-DaaS-HotFix-Management.

2 Click Jobs > Detect Hotfixes on DaaS Appliances.

3 Fill in the required information and click Run Job Now.

When the job is finished, you can view the output on the Activity page. The output includes a list of all appliances in the organizations you selected and the hotfixes installed on each appliance.

Revert Appliances to a Pre-Hotfix State

Horizon Version Manager automatically takes snapshots of your appliances before and after you apply a hotfix. To revert an appliance, navigate to it in your vCenter Server and select the desired snapshot.


VMware, Inc. 68

Instant Clone Image Management 9Instant Clone images are managed differently than traditional full clone desktops.

To edit the image and publish the changes to an assignment, you must:

n Duplicate the image.

n Perform modifications to the image.

n Import the image as an Instant Clone desktop.

n Assign the image to the assignment of your choice.

When you manage images this way, there is an inherent “versioning” of the image due to copies being made. If an image update is problematic for any reason, you can assign the old image to the pool to revert to a known good image state.

VMware, Inc. 69

Agent Installation 10You can install agents either automatically or manually.


n Configure Automatic Agent Updates Without Internet Access

n Install Agents Manually

n Optimize an Image

Configure Automatic Agent Updates Without Internet Access

This topic describes the process for setting up automatic agent updates for your environment when your datacenter does not have external internet access.

If your datacenter does not have external internet access, you must perform the steps below to set up automatic agent updates. When this process is complete, your system indicates available agent updates on the Assignments and Images pages of the tenant administrator's console. See the Tenant Administration guide for more information.

Note If you configured automatic agent updates in Horizon DaaS 8.0.1, the file locations you set are not migrated and must be configured again on the upgraded tenant.

Procedure

1 Create a directory called C:\WinFileShare\hotpatch.

VMware, Inc. 70

2 Download the agent tarball file from the My VMware site and extract it into the hotpatch directory, as shown in the example below.

3 Navigate to the subfolder called files, which contains a number of files as shown in the example below.


VMware, Inc. 71

4 Get the SHA256 value of the supportingFiles.tar file.

a Start PowerShell and navigate to the folder containing the newly extracted supportingFiles.tar file.

b Enter the following command:

Get-FileHash supportingFiles.tar -Algorithm SHA256 >SHA256.txt

Note the hash value that is returned, because you will use it in the Administration Console later.

Note If you are using Linux, you can use the following command instead:

openssl dgst -sha256 supportingFiles.tar

5 In Service Center, click tenants > policy, and select your tenant.

6 Update policies as shown in the following table.

Policy New Value

agentupdate.cachePath /mnt/wem/___

n is the IP address of the file server

n is the name of the share.

For example: /mnt/wem/__192_168_1_100_My_Share

agentupdate.cipherList AES256-GCM-SHA384

agentupdate.enable true

agentupdate.enablehotpatch true

agentupdate.job.repeatInterval 3600000

agentupdate.job.startDelay 30000


VMware, Inc. 72

7 In the Administration Console, click Settings > File Share.

8 Click New.


VMware, Inc. 73

9 Fill out details for file share.

Note If you have not created a file server, assign a server to host your agent file share, create a file share, and configure share and NTFS permissions (read/write, and so on) before proceeding with next steps.

10 Select the check box on the new file share in the console then click More > Import.

11 Open the SHA256.txt file created previously, copy the checksum, paste it into the File Hash text box, and click Validate.

The following success message displays:

You can now begin updating images and assignments with the latest agent using the Update Agent feature.


VMware, Inc. 74

Install Agents Manually

You can install agents using the manual procedure described below. Previous versions of Horizon DaaS required multiple agents to be installed separately, but Horizon DaaS 9.0.0 supports the unified Horizon Agents Installer (HAI), which installs all agents at the same time.

Prerequisites

The following prerequisites must be met:

n VMware Tools must be up to date.

n VM hardware version must be up to date (for example, vm-13 for ESXi 6.5).

n The VM name inside vCenter must match what is specified in the Guest OS and must be 15 characters or less.

n The image must have the VNIC connected at the VM level.

n The VNIC must be VMXNET3.

n The VNIC must be assigned to the correct network/port group and the domain controller must have open communication with the VM.

n The VM OS type in vCenter VM Options must match the actual OS installed.

Procedure

1 Run the appropriate version HAI executable.

2 Click the Configure button under Horizon Cloud Endpoint Desktop.


VMware, Inc. 75

3 Select whether this desktop will be used for Instant Clone or not, then select the rest of the options you need for this image.

Deselect Horizon 7 Persona Management.

Note Previous Horizon DaaS versions required that the DaaS Health Agent be installed in addition to the other agents. That has been replaced by the Help Desk Plugin option in the HAI installer. You are presented with a command-line equivalent of the options selected.

4 Verify that the options are correct and click Proceed with installation.

A screen displays showing the installation status

When the installation has finished, a window displays indicating that the installation was successful.

5 Click Finish.

You are prompted for a reboot.

6 Click Restart Now to finalize the installation.

What to do next

It is recommended that you optimize the image before proceeding with image import. See Optimize an Image.

Optimize an Image

You can optimize an image using the VMware OS Optimization tool.

To optimize the image for best performance, we recommend downloading and using the VMware OS Optimization tool. This is not normally required if you are using a VMware-provided image that has already been optimized.


VMware, Inc. 76

Procedure

1 Download the tool from https://labs.vmware.com/flings/vmware-os-optimization-tool onto the image you want to optimize.

2 Open the ZIP file and extract the two files onto the desktop.

3 Run VMwareOSOptimizationTool.exe.

4 On the Analyze tab, click the Template drop-down menu, and select the correct template. For example, Windows 7 (Horizon Cloud) or Windows 10 (Horizon Cloud).

5 Click Analyze > Optimize.

6 Reboot the machine.

7 Delete the downloaded ZIP file and the extracted files.

What to do next

You are now ready to import your image for use in assignments. See Chapter 11 Import an Image.


VMware, Inc. 77

Import an Image 11You can import an image into a tenant.

Prerequisites

Check the video settings for each virtual machine that you are going to use as an image. The minimum video settings are two monitors and 128 MB video memory.

Procedure

1 Log into the Administration Console and click Inventory > Images.

2 Click the New button.

VMware, Inc. 78

3 Select the desktop to import. When you start entering the name of the image you want to import, the Desktop text box populates with the image name. Click the populated name to select it. After selecting the image, the system begins performing the agent pairing process. When the agent pairing process has finished, Agent Status changes to Active.

4 Fill out all required text boxes, and click Publish.

Here is an example of the required text boxes for an Instant Clone image.


VMware, Inc. 79

Here is an example of the required text boxes for a Traditional Clone image.

Note Traditional Clone images require local admin credentials to be entered. Image import status changes from In Transition to Published.


VMware, Inc. 80

5 If the import fails, return to Inventory > Images, select the image, then click More > Convert to Desktop.

You can also look at Monitor > Activity to identify what caused the failure. In this example, the image failed to convert because it was set to import as an Instant Clone image without the Instant Clone feature enabled in the Horizon Agent.

Resolve any issues preventing the image conversion process, then try the import process again.


VMware, Inc. 81

Troubleshooting Agent Pairing

If the DaaS Agent fails to pair during the image import process, use the following instructions to help troubleshoot and resolve the issue.

Check Configuration

Confirm that all the following items are configured correctly:

n VMware Tools is up to date.

n VM hardware version is up to date.

n Guest OS and VM names match.

n Correct Horizon Agent Installer version is installed.

n VNIC adapter type is VMXNET3.

n VNIC is assigned to the correct port group and connected in the VM properties in vCenter.

n Domain Controller is reachable from the VM.

n Firewall is turned off (not only that the firewall service is deactivated).

Re-Enable Agent Pairing

If you are installing the Horizon Agent Installer on an image that has already had the DaaS Agent installed, requires an agent reinstall, or is being upgraded from a previous version, you must update some registry values after installing the DaaS Agent. The previous install has left some registry settings behind and must be reset. When the platform initiates the pairing process with the DaaS Agent, it updates the registry to deactivate the agent from continuing further attempts of re-pairing. As a result, if the pairing process fails for a valid reason, further attempts to reinstall the agent fail because this registry key is stopping the process.

To re-enable agent pairing:

1 Stop the VMware DaaS Agent service in services.msc.

2 Open regedit and navigate to:

Computer\HKLM\SOFTWARE\Wow6432Node\VMware, Inc.\VMware DaaS Agent

3 Edit the EnableBootstrap REG_DWORD key and change the value from 0 to 1.


VMware, Inc. 82

4 Clear the vmid REG_SZ value of any text.

5 On the tenant appliance:

a Log into the tenant appliance element database:

psql -Uadmin edb

b Turn on extended display:

\x

c Run the following commands:

select * from t_general_machine where name=’VMNAME’;

Note the tools_state, agent_version, and is_agent_pairing_acknowledged fields in the table.

update t_general_machine set is_agent_pairing_acknowledged=’f’ where name=’VMNAME’;

6 Switch back to the desktop and start the DaaS Agent service.

7 Log into the Administration Console and reinitiate the DaaS Agent pairing process by importing it as a new image. You might have to convert it back to a desktop first before you can try importing it again.


VMware, Inc. 83

Roll Back an Upgrade 12If you have completed an upgrade or had an upgrade fail, you can roll back your environment to the previous version.

The steps below are for performing a manual rollback. This is only necessary in cases where automated rollback fails.

Note There are known issues related to this procedure. See the Known Issues section of the release notes for more information.

Procedure

1 Roll back service provider (SP) appliances.

a Power off all appliances running the new version ('green' appliances).

b Power on all appliance running the old version ('blue' appliances).

c Reset database on both appliances.

n If the 'blue' SP appliances are running version 8.0.1, run the following commands as root on both appliances:

DB_NAME='fdb'; PGPASSWORD=$(sed -n 1p /root/.pgpass | cut -d: -f5) psql -U admin $

{DB_NAME} -c "BEGIN;SET TRANSACTION read write; ALTER DATABASE ${DB_NAME} SET

default_transaction_read_only='off'; COMMIT;"

service dtService restart

n If the 'blue' SP appliances are running version 18.1 or later, run the following command as root on both appliances:

/usr/local/desktone/scripts/reset_db_access_mode.sh 1000 'restart'

2 Roll back resource manager (RM) appliances.



VMware, Inc. 84

3 Roll back tenant (TA) and desktop manager (DM) appliances.



c Reset database on appliances.

n If the 'blue' SP appliances are running version 8.0.1, run the following command as root on all TA and DM appliances. Run once for each database, replacing XXX with the name of the database (fdb, edb, and avdb for TA appliances; edb and avdb for DM appliances).

DB_NAME='XXX'; PGPASSWORD=$(sed -n 1p /root/.pgpass | cut -d: -f5) psql -U admin $

{DB_NAME} -c "BEGIN;SET TRANSACTION read write; ALTER DATABASE ${DB_NAME} SET

default_transaction_read_only='off'; COMMIT;"

n If the 'blue' SP appliances are running version 18.1 or later, run the following command as root on the primary SP appliance with the appropriate tenant OrgId:

/usr/local/desktone/scripts/reset_db_access_mode.sh 'TENANT_ORG_ID'

d Restore the 'blue' appliance eth1 IP by running the following command as root on the primary SP appliance. Run once for each TA or DM appliance, replacing BACKBONE_IP with the backbone IP of the appliance.

BLUE_APPLIANCE_ETH1='BACKBONE_IP'; export PGPASSWORD=$(sed -n 1p /root/.pgpass | cut -d: -

f5); BLUE_APPLIANCE_ID=$(psql -U admin fdb -t --no-align -c "select appliance_id from

network_interface where ip_address='${BLUE_APPLIANCE_ETH1}'"); psql -U admin fdb -c "WITH

NIC_IDS AS (select id from network_interface where adapter_name IN ('eth1', 'standby') and

appliance_id= '${BLUE_APPLIANCE_ID}') UPDATE network_interface SET adapter_name=(CASE

ip_address WHEN '${BLUE_APPLIANCE_ETH1}' THEN 'eth1' ELSE 'standby' END) WHERE id IN (SELECT

id from NIC_IDS)"

e Restore the platform version and manifest version for the tenant organization by running the following command as root on the primary SP appliance with the appropriate values for TENANT_ORG_ID, BLUE_PLATFORM_VERSION, and BLUE_MANIFEST_VERSION.

n If the 'blue' SP appliances are running version 8.0.1, run the following command:

TENANT_ORG_ID='XXXX' BLUE_PLATFORM_VERSION=‘X.X.X'; PGPASSWORD=$(sed -n 1p /root/.pgpass

| cut -d: -f5) psql -U admin fdb -c "UPDATE appliance SET version='$

{BLUE_PLATFORM_VERSION}' WHERE org_id=${TENANT_ORG_ID}"

n If the 'blue' SP appliances are not running version 8.0.1, run the following command:

TENANT_ORG_ID='XXXX' BLUE_PLATFORM_VERSION=‘X.X.X' BLUE_MANIFEST_VERSION='X.X.X.XXXX.X';

PGPASSWORD=$(sed -n 1p /root/.pgpass | cut -d: -f5) psql -U admin fdb -c "UPDATE

appliance SET version='${BLUE_PLATFORM_VERSION}', manifest_version='$

{BLUE_MANIFEST_VERSION}' WHERE org_id=${TENANT_ORG_ID}”


VMware, Inc. 85

f If you had the App Volumes Manager console enabled before the upgrade, re-enable it by running the following command as root on the primary SP appliance with the appropriate value for ORG_ID.

PGPASSWORD=$(sed -n 1p /root/.pgpass | cut -d: -f5) psql -U admin fdb -c "UPDATE organization

SET avmui_enabled='t' where id='ORG_ID’"

g Restart dtService by running the following on each TA and DM appliance.

service dtService restart


VMware, Inc. 86

Additional Information 13The following information is helpful to know as you set up your environment.

n It is a good practice to set the DHCP lease duration for your tenant DHCP scope to eight hours and not the default of eight days. This setting prevents issues from happening down the road.

n Although skinned server operating systems are supported for traditional clone pools, Instant Clone pools are not supported for server operating systems at this time.

n Desktop hard drive size is based on the size of the image being used for the pool, so size the image disk size accordingly. Some administrators have used an image naming convention that makes it easy to identify what size disk is being used and help identify the right model to use when creating assignments.

VMware, Inc. 87

Additional Tasks 14This section describes additional tasks you might want to perform.


n Configure NTP on Windows Server

n Verify File Integrity

Configure NTP on Windows Server

You can configure Network Time Protocol (NTP) on Windows Server.

Procedure

1 Open a command prompt.

2 Check time sync:

w32tm /query /source

If the output says Free-running System Clock or Local CMOS Clock, the server is not using NTP.

3 List NTP server list:

w32tm /query /peers

If the output shows that the peer list is empty and state pending, the server is not using NTP.

4 Update the peer list:

w32tm /config /update /manualpeerlist:SPACE_LIMITED_NTP_SERVERS /syncfromflags:manual /

reliable:yes

5 Force sync:

w32tm /resync /rediscover

6 Check if the server is now using NTP:

w32tm /query /source

VMware, Inc. 88

If the output shows one of the servers in your peer list, the server is now using NTP.

Verify File Integrity

Before you install or upgrade any application, it is a good practice to verify the file integrity for all files. This topic describes the process for performing an MD5 hash comparison using PowerShell and a free utility called WinMD5.

Procedure

1 Open the file containing the correct MD5 checksum.

2 Start PowerShell and enter the following command:

Get-FileHash -Algorithm MD5

Example:

Alternatively, start a third-party hash tool of your choice, such as WinMD5, and browse to the file for which you must calculate the hash.

Important If the hash tool you are using is a freeware application, validate the legitimacy of the tool before using it.


VMware, Inc. 89

3 Copy the command output and paste it underneath the file’s hash in the hash document.

n If the two values match, then you can know with certainty that the file was properly downloaded and not modified.

n If the two values do not match, you might have to redownload the file or check with the software provider to validate the file.


VMware, Inc. 90

Horizon DaaS 9.0.x Installation and UpgradeContentsAbout this DocumentBefore You BeginPlatform RequirementsHorizon DaaS Worksheets in Microsoft Excel Format

Install Horizon Version ManagerInstall the Service ProviderSet Up vCloud Usage Meter Integration

Upgrade the Service ProviderSet Up vCloud Usage Meter Integration

Installing a TenantDeploy a TenantProvision a TenantInstall Unified Access Gateway

Upgrading a TenantRun the Upgrade TaskRun the Migrate TaskInstall Unified Access Gateway

Hotfix ManagementInstant Clone Image ManagementAgent InstallationConfigure Automatic Agent Updates Without Internet AccessInstall Agents ManuallyOptimize an Image

Import an ImageTroubleshooting Agent Pairing

Roll Back an UpgradeAdditional InformationAdditional TasksConfigure NTP on Windows ServerVerify File Integrity

horizon daas 9.0.x installation and upgrade - vmware ...€¦ · horizon daas worksheets in...

Documents