Wyse Datacenter Appliance XC for vWorkspace Deployment Guide Dell Wyse Solutions Engineering November 2014 A Dell Deployment and Configuration Guide
Revisions Date Description November 2014 Initial release © 2014 Dell Inc. All rights reserved. Reproduction of this material in any manner whatsoever without the express written permission of Dell Inc. is strictly forbidden. For more information, contact Dell. Performance of network reference architectures discussed in this document may vary with differing deployment conditions, network loads, and the like.
Corporation. Other trademarks and trade names may be used in this document to refer to either the entities claiming the marks and/or names or their products and are the property of their respective owners. Dell disclaims proprietary interest in the marks and names of others.
Contents Revisions ............................................................................................................................................................................................. 2 1 Introduction ................................................................................................................................................................................ 7 2 System Requirements ..................................................................................
7 8 9 6.2 Performance Tuning..................................................................................................................................................... 49 6.3 Integrating SCVMM, Nutanix, and Microsoft Failover Cluster ............................................................................... 50 6.4 Integrating vWorkspace with SCVMM .......................................................................................................................
12.2.1 Configuring Web Access and Secure Gateway ....................................................................................................... 79 12.2.2 Installing vWorkspace Client (Connector) ............................................................................................................... 80 12.3 Using Foglight for Virtual Desktops .......................................................................................................................... 80 13 Adding Hosts ..........
1 Introduction The Wyse Datacenter Appliance XC utilizes Dell PowerEdge R720xd servers, the Nutanix software-defined storage (SDS) application, and VDI components to deliver an out-of-the-box infrastructure solution for virtual desktops and shared desktop sessions. This document provides the tasks required to install and configure the Dell vWorkspace VDI components on to a Wyse Datacenter Appliance XC cluster.
2 System Requirements Before proceeding with the Wyse Datacenter Appliance XC for vWorkspace setup, ensure the following requirements are met. To successfully complete the setup, you must be familiar with the following technologies: Active Directory Windows Server 2012 (or higher) Supplemental Documentation Some sections in this guide refer to the following documentation for additional details. 2.
2.3 Supported Hypervisor Platforms The hypervisor used in this solution can be Microsoft Windows Server 2012 R2 with Hyper-V role or VMware vSphere 5.5 GA (not Update 1 or Update 2). 2.4 Active Directory (AD) Active Directory is required for this solution; however, configuration of AD is beyond the scope of this document except where noted. DNS is required for name resolution. All Windows servers must belong to the same AD domain. 2.4.
Figure 1 3. 4. 5. 6. 7. 10 ADSI Edit Application Right-click and select New Object. Select Container from the object class and click Next. Enter a value for the object class. For example, VMMDKM. Click Next. To create the new container, click Finish. Make sure that the new container object now appears in AD.
Figure 2 11 ADSI Edit Wyse Datacenter Appliance XC for vWorkspace
8. Make note of the distinguished name for the container for later use in the installation. Rightclick the container and select Properties. Select the distinguishedName attribute in the list, double-click the attribute, and then copy the value. Figure 3 ADSI String Attribute Editor 9. Click the Security tab and add the VMM service account that you created in the earlier section by granting full control to this object and all descendant objects of the container.
3 Configuring Nutanix Storage Pool and Containers To use the cluster storage, you must configure a storage pool and containers within the pool. Create only one pool consisting of all the disks in the cluster. Within the storage pool, we recommend creating multiple containers for a logical distinction between the compute and management storage layers. 1. Figure 4 To configure the storage pool and containers, log in to the Nutanix Web Console. From the Home drop-down menu, select Storage.
Figure 6 Creating Storage Pool 3. Provide a name for the pool (for example, SP1) and use all unallocated disk space. Click Save. On the Create Container page, to view additional settings, click the Advanced Settings button.
Hyper-V Hypervisor and SMB Shares While using Hyper-V for the hypervisor, SMB shares are used to store the virtual machine disks and settings files. The cluster name is the “host” portion of the SMB share name. If not created during the Nutanix cluster setup, add a DNS entry for this name and point it to the cluster IP address. The container names that you created earlier are used as the share names. The resulting share name will be \\{clustername}\{container-name}. For example, \\cluster\ds_mgmt.
4 Configuring Hypervisor 4.1 Setting up Windows host Joining Hyper-V Hosts to the Active Directory Domain If using Windows 2012 R2 with Hyper-V role as the hypervisor, the hosts must have already been joined to the AD domain as part of the initial Nutanix cluster setup. 4.2 Hyper-V Virtual Switches and NICs The Nutanix cluster setup process will create a network team using the 10 GB NICs. This team is associated with a virtual switch named “ExternalSwitch” for all external traffic to the host and VMs.
In the following example, the management VLAN uses 177 as the ID and is added to the ExternalSwitch vSwitch (this should be changed to the ID used for your management network). Figure 9 Virtual Switch VLAN ID Adding Virtual NICs Using PowerShell, you can run the Get-VMNetworkAdapterVlan command to view current virtual NICs and VLAN assignments. Figure 10 View Virtual NIC VLAN Assignments using PowerShell The following PowerShell commands can be run to create additional vNICs and corresponding VLANs.
Set-VMNetworkAdapterVlan -ManagementOS -VMNetworkAdapterName "LiveMigration" Access -VlanId 50 Make sure the corresponding VLAN tagging is configured on the physical switches that the hosts are connected to. NOTE: It is not necessary to create a virtual NIC and VLAN assignment for the desktops. Network Traffic for the desktop VMs will pass through the ExternalSwitch virtual switch, but the Hyper-V host OS does not need a connection on that network or VLAN.
Jumbo Frames The Nutanix cluster setup should have configured the NICs to the largest supported MTU size (jumbo frames). This can be verified in Network Connections. Go to the properties of the NICs for the ExternalSwitch, Cluster, and LiveMigration, and then click Configure. Click the Advanced tab and verify that Jumbo Packet value is set to the highest value (typically, 9014 bytes) and modify if not currently set to the highest value.
5 Setting up Management VMs The table here summarizes all of the management VM specifications for the vWorkspace and Hyper-V configuration. Figure 13 Hyper-V Management VM Table This table summarizes all of the management VM specifications for the vWorkspace and vSphere hypervisor configuration. Role OS vDisk vRAM (GB) vCPU NIC Size (GB) Nutanix CVM 8 32 2 N/A C: (rear) Broker + Licensing 4 8 1 40 ds_mgmt WebAccess + SGW 2 6 1 40 ds_mgmt SQL Server Std.
The SQL and SCVMM VMs are created first for the Hyper-V configuration followed by the remaining management VMs. Similarly, the SQL and vCenter VMs are created first for the vSphere configuration. 5.1 Creating Management VMs To create VMs for Hyper-V configuration: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 13. 21 Log in to any of the hosts in the cluster and start Server Manager. Any host can be logged in to because the VMs will eventually be added as roles to a Microsoft Failover Cluster.
Figure 14 Network Adapter External Switch 14. For the SQL VM, we recommend creating four additional virtual disks: two for database and database log files, and two for tempdb and tempdb logs. To create four additional drives, rightclick SQL VM in the Virtual Machines pane and select Settings. 15. Click the SCSI controller in the hardware pane, select Hard Drive in the right pane (under SCSI Controller), and then click Add. Repeat the task until you have four more virtual disks.
17. Windows Server 2012 R2 must be installed on each of the management VMs. You can install Windows Server 2012 R2 by attaching an .iso file to the virtual DVD or by using existing OS deployment applications. If installing by ISO file, add a DVD Drive first by clicking SCSI Controller in the VM Settings, highlighting DVD Drive, and clicking Add. 18. After installing the OS and applying your Windows license key, configure an IP address for the VM. 19.
Figure 16 Formatting Virtual Drives 2. SQL service accounts created as outlined in the System Requirements section. 5.2.2 SQL Server Installation SQL Server Installation: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 24 While logged in to the SQL VM, access the SQL setup files (go to file share, copy locally, insert DVD, download, etc.) Run Setup.exe, in the left pane, click Installation, and then select new stand-alone installation. Click OK to continue past the discovery operation.
12. Change the SQL service accounts to the desired domain user accounts. Make sure to specify the domain account and password. Click Next to continue. Figure 17 Server Configuration 13. Set to mixed mode authentication, specify a password for the SA account, and add domain user(s) or group(s) to be used for SQL administration. 14. On the DataBase Engine Configuration page, click the Data Directories tab.
5.3 Installing System Center VMM Software NOTE: SCVMM is only required when the hypervisor is Hyper-V. Log in to the SCVMM VM to perform the SCVMM prerequisites and installation tasks here. 5.3.1 SCVMM Software Prerequisites Windows ADK for Windows 8.1 Download the Windows ADK for Windows 8.1 installation file available at Microsoft website: http://www.microsoft.com/en-US/download/details.aspx?id=39982 1. 2. 3. 4. 5. Run adksetup.exe and accept the default location.
.NET Framework 3.5 .NET Framework 3.5 is required for the vWorkspace Broker Helper service. 1. In Server Manager, click Manage and select Add Roles and Features. 2. On the Before You Begin page, click Next, select Role-based or feature-based installation, and then click Next. 3. The local server should be selected as the destination. Click Next. 4. Click Next on server roles without selecting any roles. 5. Select .NET Framework 3.5 and click Next. 6.
15. If you left the checkmark next to Open the VMM console check box, the Connect to Server window is displayed. Otherwise, click the Console icon on the desktop. Connect to the VMM Console. Figure 19 SCVMM Installation Screen vWorkspace Broker Helper Service for SCVMM: 1. For vWorkspace 8.5 and later, use the Broker Helper Service (BHS) installer included with the vWorkspace installation files. For vWorkspace 8.0 MR1, download the Broker Helper Service (hotfix ID #412931) from : https://support.software.
This computer is configured to receive credentials from a remote client computer. 3. On the SCVMM VM, enter the following from at an administrator PowerShell command prompt. The computer names must be the FQDN of each Nutanix or Hyper-V separated by commas along with the Microsoft Failover Cluster (MFC) name associated with the cluster: Enable-WSManCredSSP –Role Client –DelegateComputer Host1.domain,Host2.domain,Host3.domain,MFC_name.domain When prompted, select Y and press Enter.
Figure 20 Deploy OVF Template 3. In the OVF deployment wizard, click Browse, select the vCenter Appliance OVF template file, and then click Next. 4. Confirm the template details and click Next. 5. Specify a name for the vCenter Server Appliance VM and click Next. 6. Select the datastore you created for your management VMs as the storage location and click Next. 7. Select Thin Provision for disk format and click Next. 8. Review the settings and click Finish to deploy.
Figure 22 vCenter Appliance VM Console 11. Open a web browser window to the URL indicated in the Quick Start Guide (displayed on the console screen) and type the User Name root and Password vmware, and then click Login. Figure 23 vCenter Appliance login screen 12. Accept the EULA and click Next. 13. Click Next to skip the Customer Experience Improvement Program page. 14. If using a static IP address, you must close the wizard and set a hostname. In this guide, a static IP address will be used.
Figure 24 Static IP Address 16. Set the Hostname and IPv4 address settings. Click Save Settings. Note: The fully qualified domain name (FQDN) format must be used for the host name. 17. When the network settings have saved, change the URL on the web browser to the static IP address you just set, and log in again using the login ‘root’ and password ‘vmware’, and then click the Network tab to verify your IPv4 settings. 18.
19. Do not change selections on the Customer Experience Improvement Program page, click Next. 20. Select the Set custom configuration check box and click Next. 21. For this solution, the embedded database option will be used. Accept the default database settings and click Next. 22. Select embedded for the SSO deployment type, type a password for the administrator@vsphere.local user, and then click Next. 23.
5.5 Installing vWorkspace Broker The following tasks describes the process of installing the vWorkspace broker components: 1. Log in to the vWorkspace broker VM. 2. In Server Manager, click Manage Add Roles and Features, click Next and select Role-based or Feature-based installation. Click Next. Make sure the broker VM is the selected server and click Next. 3. In the left pane, click Remote Desktop Services, and click Next until you see the Role services page. 4.
8. 9. 10. 11. 12. 13. 14. Right-click the start.exe file, and then run as an administrator. Click the Install button to begin. Click Yes in the .NET Framework dialog box, and then click Next. Accept the license agreement and click Next. Type your user name and organization information and click Next. Select Advanced setup type and click Next. Select only Connection Broker Role and vWorkspace Management Console Role (Management Console on version 8.5 and later) features and click Next. 15.
342720 (vSphere configuration only) 5.5.1 Applying vWorkspace Licenses To apply your vWorkspace license: 1. 2. 3. 4. 5. 6. 7. 8. 5.6 Open the vWorkspace Management Console. From the File menu, select Licensing. Select the Licenses option. Click the Add License button. Browse to the location of your ASC license file (provided by Dell Licensing team). Select the file and click Open. On the message window stating the license has been added, click OK. Click Close.
5.7 Installing Foglight for Virtual Desktops Foglight account requirements: Administrator access to all machines requiring a Foglight agent. An administrator password for Foglight. The user name foglight and the default password for this account can initially be used to log in to the browser interface and to use command line interface options with administrator privileges. It is recommended that you change the default password for this account.
13. The main installer extracts files and spawns another installation process. Click Next on the Foglight for Virtual Desktops introduction window. 14. Accept the license agreement and click Next. 15. Select Custom Install and click Next. 16. Select the location where you want to install Foglight. You can accept the default location C:\Quest_Software\Foglight or click the Browse button to navigate to another location. Click Next. 17. Select the location where you want to create product icons.
37. 38. 39. 40. 41. 42. 43. 44. 45. 46. A list of the Foglight services that are starting. Services listed in grey have not yet started, services listed next to a blue circle are starting, and services listed next to a green square with a check mark have started. The information on the page is updated as Foglight starts. The page also includes a link that allows you to refresh the page. When the server startup is complete, a link to the Foglight login page appears. Close the browser window.
Figure 30 Discovery Setup 50. Click the Configure Database Details button and type the information to connect to the vWorkspace database. Make sure to change the database instance from “VWORKSPACE” to “MSSQLSERVER” (default instance) or type port as 1433. You can click the Test button to ensure the details are correct, and then click OK. Click Next to continue. Figure 31 Set Database Details 51. Click the Add button to enter information about your Web Access and Secure Gateway servers if necessary. 52.
Figure 32 Foglight Configuration Screen 57. Verify your broker and click Next. 58. Verify your database and click Next. 59. Click Next until the Hyper-V Configuration page is displayed. The Hyper-V hosts should have been discovered but you must specify credentials to connect to the servers. Select the check box to select all of the hosts and click the Credentials button. Type the credentials in the dialog box and click OK. Click Next to continue.
60. Click Next on the App-V Configuration page. 61. Click Finish. Apply the following vWorkspace hotfixes: 331043 The following procedure describes the process of installing the Foglight for Virtual Desktops component for vWorkspace 8.5 and later: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. Log in to the vWorkspace Foglight for Virtual Desktops VM. Access the vWorkspace setup files (go to file share, copy locally, insert DVD, download, etc.). Right-click the start.exe file and run as administrator.
15. Select Custom Install and click Next. 16. Select the location where you want to install Foglight. You can accept the default location C:\Quest_Software\FoglightvDesktops or click the Browse button to navigate to another location. Click Next. 17. Select the location where you want to create product icons. Select the Create Icons for all Users option to create shortcuts for all Foglight users. Click Next. 18. Select Enable to enable as a service and click Next. 19. Review the installation information.
40. The system will log you in automatically using the user name and password that you specified. 41. If you did not perform a discovery during installation, click the link Discover and Configure Foglight for My Virtual Desktop Environment. 42. Click the Manage Credentials link to specify the Windows domain credentials to access components in your virtual desktop environment. 43. Under Managing Credentials, click the Add button to enter the credentials. Figure 35 Managing Credentials 44.
Figure 37 Set Database Details 48. Click the Add button to enter information about your Web Access and Secure Gateway servers if necessary. 49. Click the Discover Environment button to begin discovery. If a discovery has already been completed (that is during installation) then click Next. 50. After discovery is completed, click OK, and then click Next to view different wizards and fine tune the settings. 51. The Discovered Environment to be Monitored page displays components that were discovered.
Figure 38 Foglight Configuration Screen 54. Verify your broker and click Next. 55. Verify your database and click Next. 56. Click Next until the Hyper-V Configuration page is displayed. The Hyper-V hosts should have been discovered but you must specify credentials to connect to the servers. Select the check box to select all of the hosts and click the Credentials button. Type the credentials in the dialog box and click OK. Click Next to continue.
57. Click Next on the App-V Configuration page. 58. Click Finish. 5.7.1 Applying Foglight License If you did not specify the Foglight license during installation, perform the following tasks to apply. 1. 2. 3. 4. 5. 6. 5.8 Log in to the vWorkspace Broker VM, start the vWorkspace Management Console, and then click the Diagnostics & Monitoring link under vWorkspace Farm in the upper-left corner.
10. 11. 12. 13. 14. Monitoring link under vWorkspace Farm in the upper left corner. After you have specified the required connection options, click OK. To test the connection between the Agent Manager and the Management Server, click Test. A URL for which the connection has not been tested appears next to an orange-colored exclamation mark icon. URLs that fail the connectivity test displays a red-colored x icon. When you complete adding Management Server URLs, click Next.
6 Configuring SCVMM The following sections describe the tasks that must be completed to configure SCVMM for integration with the Nutanix cluster and vWorkspace broker. NOTE: SCVMM is required only when the hypervisor is Hyper-V. 6.1 Run As Account Log in to the VMM host and start the Virtual Machine Manager Console and do the following: 1. 2. 3. 4. Click Settings in the lower right pane of the console. Click the Create Run As Account button from the Home menu. Type a name and description.
After changing the registry settings, reset the VMM service. For explanations and more information about System Center performance planning, refer to the article: http://social.technet.microsoft.com/wiki/contents/articles/18059.planning-capacity-and-performancefor-system-center-2012.aspx 6.
Failover Cluster Manager. You can also verify by accessing the VMM console, select Fabric, and then click Servers. Placement Paths on Hosts in SCVMM 1. In the VMM console, select Fabric in the bottom left pane, and then click Servers. 2. Expand the All Hosts folder under Servers to view the Microsoft Failover Cluster that you previously added. Click the Microsoft Failover Cluster object. Figure 40 Microsoft Failover Cluster 3. Under the Hosts pane, right-click the first host and select Properties.
5. In the Specify the default parent disk paths to be used for the virtual machines section, remove all existing paths (if present) by selecting them, and then clicking Remove. When finished, click OK. Figure 42 Placement Paths 6. Repeat tasks 3–5 for all hosts in the cluster. 7. Right-click the MS Failover Cluster and select Properties. 8. In the Properties window, click File Share Storage in the left pane.
9. By default, the containers you created in the Configuring Nutanix Storage Pool and Containers section will be present. Select each file share path listed and click Remove to remove file shares. Figure 43 Remove File Shares 10. Also, by default, the file share path will contain the FQDN of the host. Because of an apparent bug in SCVMM, you must specify a placement path on each host that contains only the host name in order for ODX Fast File Copy to work properly.
Figure 44 Specify SMB Share Path 12. Click OK in the Add File Share window. The share will be listed on the File Share Storage page of the Properties window until you click OK. After you click OK and view the properties of the Failover Cluster again. The original FQDN path will be listed. This is the expected behavior. 13. Click OK to close the Properties window. Right-click the Failover Cluster and select Refresh. 14.
15. In the host Properties window, click Placement Paths in the left pane. The Specify the default parent disk paths to be used for the virtual machines section will now display the UNC share that contains the host name instead of the FQDN.
16. If any other file paths are listed, select them and click Remove. Only the file path to your compute container that is not using the FQDN of your host must be present. Figure 47 Remove File Paths 17. Click OK. Repeat tasks 14–17 for all hosts in the cluster. NOTE: If the FQDN of the host is used in the placement path, SCVMM will use BITS instead of Fast File Copy to copy the virtual disk files resulting in much slower provisioning times.
7. 8. 9. 10. 57 On the Other Settings page, adjust the concurrency settings to 10 and click OK. On the Management Servers window, click OK. To select Host Groups & Clusters, click Next. The SCVMM server should appear in the Host Groups & Clusters pane. Expand the SCVMM server until the Microsoft Failover Cluster name is displayed and click the name to select the cluster. Click Finish.
7 Configuring Microsoft Failover Cluster Perform the following tasks to complete the configuration of the Microsoft Failover Cluster. NOTE: Microsoft Failover Cluster is required only when the hypervisor is Hyper-V. 7.1 MS Failover Cluster Quorum The Microsoft Failover Cluster does not use any of the host drives for its configuration. For quorum, configure a file share witness using the ds_mgmt container. 1. 2. 3. 4. 5. 6. 7.2 Log in to one of the Hyper-V hosts.
Figure 48 Cluster Network 1 Properties NOTE: Clients should not be allowed to connect through the Cluster or Live Migration networks. After configuring the properties for each of your networks, click Live Migration Settings under the Actions pane. Specify that only the Live Migration network be used for this purpose. 7.3 Adding Management VMs as Highly Available VMs Now that the Microsoft Failover Cluster is created, the Management VMs should be added to the cluster.
8 Configuring vCenter The following sections describe the tasks that must be completed to configure vCenter for integration with the Nutanix cluster and vWorkspace broker. NOTE: vCenter is required only when the hypervisor is vSphere. 8.1 Integrating vCenter and Nutanix The Nutanix cluster and nodes must be added to vCenter. To add the Nutanix configured ESXi hosts to vCenter: 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. 8.
5. Type a name for the vCenter server (this can be the actual host name or whatever you want as it applies only to what is displayed in the console). Select VMware vCenter Server as the system type and click Next. 6. Type the vCenter server name along with the credentials to access. Click the Test connection to server button to verify connectivity, and then click Next. 7. On the Other Settings page, click Finish. 8. On the Datacenter Wizard page, click Next. 9.
9 Floating vs Dedicated Management If your cluster is running more than 1000 desktops or contains 10 or more nodes, we recommend that the management VMs reside on dedicated hosts (Dedicated Management model). For environments smaller than this, the management VMs will be spread evenly across the cluster nodes (Floating Management model). For example, if your cluster consists of three Hyper-V nodes, two of the management VMs will be configured to run on each node.
10 Deploying Virtual Desktops The process for deploying virtual desktops consists of creating a desktop template, importing the template to SCVMM or vCenter (depending on the hypervisor used), and adding the template to a provisioning group in vWorkspace. The vWorkspace broker will create the specified number of desktops from the template to be used in the virtual desktop deployment. To provision virtual desktops, perform the following tasks. 10.1 Desktop Template (Gold Image) Setup 10.1.
10.1.2 Creating VHDX for Hyper-V NOTE: Solution is provided on the basis of using full clones for persistence (Standard provisioning) and recommended disk format is VHDX. If using linked clones and rapid provisioning is necessary, you must use VHD format with this version of vWorkspace. 1. Open PowerShell and go to the path where you want the template VM to be stored. 2. Run the following command to create a VHDX file for the template VM using the following necessary specifications. Replace “VMName.
10.1.3 Creating Desktop VMs for the vSphere hypervisor configuration For equivalent steps to create desktop VMs for vSphere, see the vSphere Virtual Machine Administration Guide (ESXi 5.5). For example specifications to use for the desktop VMs, refer to the vSphere Desktop VM Example Configuration Table earlier in this guide. NOTE: Solution is provided on the basis of using full clones for persistence (Standard provisioning) and recommended disk format is VMDK.
4. Select Complete installation type and click Next. 5. To complete the installation, click Install, and then click Finish. 6. To restart the system, click Yes. 10.1.6 Optimizing Desktop OS vWorkspace includes an application called Desktop Optimizer that can be used to optimize desktop settings for a VDI environment including disabling unnecessary services. The vWorkspace Desktop Optimizer is installed with the Instant Provisioning Tools and can be opened from C:\Program Files\Quest Software\vWorkspace\De
10.2 Adding Desktop Template to SCVMM NOTE: SCVMM is only required when the hypervisor is Hyper-V. The desktop template must first be added to SCVMM as a VM template and then imported to vWorkspace as a template while creating a computer group. After creating a desktop VM on one of the Hyper-V hosts, log in to the SCVMM server to add it as a template. 1. Shut down the desktop VM that you want to use as your template before you begin. 2.
14. Click Availability under the Advanced section and select the Make this virtual machine highly available check box. The default Medium priority is sufficient. Figure 49 VM Template Properties 15. Click OK to exit and save. 10.3 Adding Desktop Template to vCenter NOTE: vCenter is required only when the hypervisor is vSphere. The desktop template must first be added to vCenter as a VM template, and then imported to vWorkspace as a template while creating a computer group.
Figure 50 vWorkspace New Computer Group Wizard 4. Type name of the computer group in the Group Name box on the Group Name page, and then click Next. 5. Select Microsoft SCVMM on the System Type page, and then click Next. 6. On the Administrative Account page, type information about the domain account that will be used as an administrative account. Select the password check box to validate the credentials. Click Next. 7.
15. Click Next on the Session Protocol page for RDP protocol. NOTE: This page does not appear in vWorkspace 8.5 and later. 16. 17. 18. 19. 20. 21. 22. 23. 24. 25. 26. 27. 28. 29. 30. 31. 32. Click Next to accept defaults on the Experience Optimization page. Enable support for EOP Audio on the EOP Audio page if necessary and click Next. Click Next on the Task Automation page. Click Next on the Permissions page. Select Create new computers from a master template and click Finish.
Refer to the vWorkspace Administration Guide for the equivalent steps for provisioning persistent desktops using standard provisioning.
11 Deploying Shared Sessions (RDSH) The process for deploying RDSH is similar to deploying virtual desktops. A template VM for RDSH is first created and then imported to SCVMM or vCenter (depending on the hypervisor used) and added to a provisioning group in vWorkspace. The vWorkspace broker will create the specified number of RDSH VMs from the template to be used in the shared session deployment. To provision shared sessions, perform the following tasks. 11.1 Setting up Shared Session (RDSH) 11.1.
5. 6. 7. 8. 9. 10. 11. 12. 13. 14. 15. 16. 11.1.2 On the Specify Name and Location page of the New Virtual Machine wizard, type the name and location of the VM. The location is the Nutanix SMB share for your RDSH container (for example, \\nutanix-cluster\ds_rdsh). On the Specify Generation page, specify Generation 2 and click Next.
Application Installation The RD Session Hosts require the user software installed locally as this is the OS that it is being used by the users connected using the Remote Desktop Session. The requirement is customer specific but includes your standard office type applications. vWorkspace Terminal Server Role 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11. 12. Access the vWorkspace setup files (go to file share, copy locally, insert DVD, download, etc.). Right-click start.exe and run as administrator.
11.2 Adding RDSH Template to SCVMM NOTE: SCVMM is required only when the hypervisor is Hyper-V. The RDSH template must first be added to SCVMM as a VM template and then imported to vWorkspace as a template while creating a Session Host provisioning group. After creating a RDSH VM on one of the Hyper-V hosts, log in to the SCVMM server to add it as a template. 1. Shut down the RDSH VM that you want to use as your template before you begin. 2.
Figure 51 VM Template Properties 15. Click OK to exit and save. 11.3 Adding RDSH Template to vCenter NOTE: vCenter is only required when the hypervisor is vSphere. The RDSH template must first be added to vCenter as a VM template, and then imported to vWorkspace as a template while creating a Session Host provisioning group. Refer to the vSphere Virtual Machine Administration Guide (ESXi 5.5) for steps on cloning a RDSH VM to a template. 11.
6. On the Administrative Account page, type information about the domain account that will be used as an administrative account. Select the password check box to validate the credentials. 7. Click Next. 8. Click Next on the Task Automation page. 9. Click Next on the Permissions page. 10. On the Finish page, select Create new computers from a master template check box, and then click Finish. The Add Computers wizard is displayed. 11. Click Next on the Welcome page for the Add Computers wizard. 12.
12 Using the VDI Environment To connect to the provisioned desktops or shared sessions, you must first create a Managed Application, publish it to the corresponding desktop computer group or RDSH hosts, and assign it to the entitled users or user groups. You must then allow access by using web browsers or installed client or both. 12.
17. After clicking OK on the Select Targets window, the Select Folder(s) window is displayed. Select the desired folder location and click OK to proceed 18. Repeat the tasks 16–17 to add more users or groups. When finished, click OK. 19. On the Target Assignments page, click Next. 20. On the Permissions page, adjust permissions as necessary. Permissions here are for the group that has access to modify the Managed Application. Click Finish. 12.2 Connecting to vWorkspace 12.2.
The remaining settings will vary depending on your network environment and needs. For help determining what is appropriate, refer to the Using Web Access and Secure Gateway sections of the vWorkspace Administration Guide. 12.2.2 Installing vWorkspace Client (Connector) The vWorkspace Connector allows users to establish a connection to the vWorkspace farm and receive a list of authorized desktops and applications.
13 Adding Hosts This section describes the tasks to add hosts to the cluster. 13.1 Adding Nutanix Nodes Refer to the Nutanix Web Console Guide for the procedure to expand an existing cluster. 13.2 Adding MS Failover Cluster Nodes To add nodes to an existing failover cluster: NOTE: Microsoft Failover Cluster is required only when the hypervisor is Hyper-V. 1. Start Failover Cluster Manager on an existing node. 2. Right-click Nodes Add Nodes. 3.
