AdminGuidev5.0

Pano System Administrators Guidev5.0

1.0 December 22, 2011 Copyright Pano Logic, Inc.

Copyrights and TrademarksPano, Pano Logic, Pano Button are registered trademarks of Pano Logic, Inc.Pano System Administrators Guide

Copyrights and Trademarks i

iiPano System Administrators Guide

Table of ContentsPrefaceAbout This Book . . . . . . Who Should Use This Book Related Documentation . . Typographical Conventions Contacting Pano Logic . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1.1 .1 .1 .1 .2

Chapter 1 Pano System OverviewPano Client . . . . . . . . . . . . . . . Pano Device . . . . . . . . . . . . . . Pano Remote. . . . . . . . . . . . . . Pano Gateway . . . . . . . . . . . . . Pano Controller. . . . . . . . . . . . . Pano Controller Roles. . . . . . . . Pano Controller Group Architecture. Pano Maestro . . . . . . . . . . . . . Pano Direct Service . . . . . . . . . . Virtualization Layer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3.4 .4 .5 .6 .6 .7 .8 .9 10 10

Chapter 2 Pano System ConceptsDVMs. . . . . . . . . . . . . . . DVM Collections . . . . . . . . . Types of Collections . . . . . . . User Based Collections . . . . Device Based Collections . . . Automated Deployment Concepts Templates . . . . . . . . . . . . Virtual Desktop Management . . Scalability . . . . . . . . . . . . Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1111 11 12 12 14 16 16 17 17 18

Chapter 3 System RequirementsVirtualization Platform Requirements . . . . . . . . . . . . . . . . . Network Addressing Requirements . . . . . . . . . . . . . . . . . . Hardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . Hardware and Resource Requirements for VMware vSphere . . . Hardware and Resource Requirements for Windows Server 2008 R2 Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . Hardware and Resource Requirements for XenServer . . . . . . . Trial Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . VMware Trial Requirements . . . . . . . . . . . . . . . . . . . . Microsoft Trial Requirements . . . . . . . . . . . . . . . . . . . . Citrix XenServer Trial Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

1313 17 18 18 19 21 22 23 23 24

Chapter 4 SupportPano Controller and Pano Direct Versions. . . . . . . Supported Number of DVMs and Pano Clients . . . . Supported Operating Systems for Pano Direct Service Supported Directory Services . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

2525 25 27 28

Table of Contents iii

Supported Third Party Connection Brokers . . . . Support for USB Devices . . . . . . . . . . . . . Supported Non-Isochronous USB Devices . . Supported Isochronous USB Devices for Pano G2 Supported Monitor Resolutions . . . . . . . . . . Monitor Resolution Support for Pano G2 . . . . Monitor Resolution Support for Pano G1 . . . . Supported Wireless Bridges . . . . . . . . . . . . Supported Third Party Logon Screens . . . . . . . Windows Server Support . . . . . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

. . . . . . . . . .

28 29 29 31 34 34 34 35 35 36

Chapter 5 LimitationsLimitations of Pano Controller without vCenter Server Limitations to Windows 7 Support . . . . . . . . . . . Limitations to Fast User Switching . . . . . . . . . . . Limitations to Sleep and Hibernate . . . . . . . . . . Limitations of Pano Controller without Active Directory Limitations to USB Device Support . . . . . . . . . . (Pano G1) Limitations of Pano Dual Monitor. . . . . . Limitations of VMware View Manager . . . . . . . . . Limitations of XenDesktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

3738 40 41 41 42 42 43 43 44

Chapter 6 The BasicsPano Buttons Light Indicators . . . . . . . . . . . . . Pano Client Login Status Indicators . . . . . . . . . . Power On Pano Controller . . . . . . . . . . . . . . . Power Off Pano Controller . . . . . . . . . . . . . . . Log On To Pano Controller . . . . . . . . . . . . . . Log Off from Pano Controller . . . . . . . . . . . . . Log On To DVMs as End User. . . . . . . . . . . . . Log On To DVMs as Administrator . . . . . . . . . . Log Off from DVMs as Administrator . . . . . . . . . Log Off from DVMs as End User . . . . . . . . . . . Reset DVMs as End User . . . . . . . . . . . . . . . Reset DVMs as Administrator . . . . . . . . . . . . . Restart DVMs as End User . . . . . . . . . . . . . . Restart DVMs as Administrator . . . . . . . . . . . . Shut Down DVMs as Administrator . . . . . . . . . . Suspend DVMs as Administrator . . . . . . . . . . . Power On DVMs as End User . . . . . . . . . . . . . Power Off DVMs as End User . . . . . . . . . . . . . Power On DVMs as Administrator . . . . . . . . . . . Power Off DVMs as Administrator . . . . . . . . . . . Wake Pano Device as End User . . . . . . . . . . . . Put Pano Device into Sleep State as End User . . . . Retrieve IP Address of Pano Controller . . . . . . . . Retrieve IP Address of DVMs . . . . . . . . . . . . . Log OnTo Pano Controller VM . . . . . . . . . . . . . Log Off from Pano Controller VM . . . . . . . . . . . View Pano Device Information as End User . . . . . . View Users DVM Login Status and DVM Assignment Enable Secure Connections . . . . . . . . . . . . . . Initiate Secure Connections . . . . . . . . . . . . . . Secure Pano Devices . . . . . . . . . . . . . . . . . Install Pano Device Mounting Brackets . . . . . . . . Verify vCenter Server Licenses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

4546 47 47 48 48 48 48 52 52 53 53 53 54 54 55 55 55 56 56 56 57 57 59 59 60 60 60 61 61 62 63 64 66

ivPano System Administrators Guide

Filter and Sort in Pano Controller . . . . . . . . . . . . . . . . . . . . . . 66 Reorder and Resize Columns in Pano Controller . . . . . . . . . . . . . . 68

Chapter 7 Deployment PlanningDeployment and Network Terminology . . . . . Planning Your Deployment . . . . . . . . . . . Network Infrastructure Assessment . . . . . Site Assessment . . . . . . . . . . . . . . . User Workload Assessment . . . . . . . . . DVM Collections and Storage Choices . . . . Virtualization Platform Options. . . . . . . . . . Required and Optional Platform Components Pano Controller Resource Requirements . . . . Sizing Server and Storage Requirements . . . . Server Architectures . . . . . . . . . . . . . Allocating Server Resources . . . . . . . . . Storage Capacity Requirements . . . . . . . Storage IOPS Requirements . . . . . . . . . Estimating IOPS Requirements per DVM . . Best Practices for Deploying Pano Zero Clients . DVM Best Practices . . . . . . . . . . . . . Network Best Practices . . . . . . . . . . . . Server/Storage Best Practices . . . . . . . . Deployment Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

7171 72 72 75 76 76 78 79 80 80 80 81 82 84 84 85 85 86 87 87

Chapter 8 Deploy Pano SystemAbout Pano Controller . . . . . . . . . . . . . . . . . . . . . . Deployment Options for Pano Controller . . . . . . . . . . . . Scaling Standalone Full Mode . . . . . . . . . . . . . . . . . . Scaling Full Mode with 3rd Party Connection Broker . . . . . . Scaling Zero Client Controller with 3rd Party Connection Broker Expanded Scalability. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

8989 90 91 91 92 92

Chapter 9 Deployment Scenarios(Overview) Sample Deployment Scenarios . . . 25-Seat Deployment . . . . . . . . . . . . . . . Hardware Sizing and Architecture . . . . . . Pano System Configuration . . . . . . . . . Platform Considerations and Configurations . 500-Seat Deployment . . . . . . . . . . . . . . Hardware Sizing and Architecture . . . . . . Pano System Configuration . . . . . . . . . Platform Considerations and Configurations . 1,000-Seat Deployment . . . . . . . . . . . . . Hardware Sizing and Architecture . . . . . . Pano System Configuration . . . . . . . . . Platform Considerations and Configurations . 10,000-Seat Deployment . . . . . . . . . . . . Hardware Sizing and Architecture . . . . . . Pano System Configuration . . . . . . . . . Platform Considerations and Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

95. 95 . 96 . 96 . 97 . 97 . 98 . 99 . 99 . 99 .100 .101 .101 .101 .102 .103 .103 .103

Table of Contents v

Chapter 10 Pano Controller Setup Overview Chapter 11 (Start Here) Deploy Pano System Chapter 12 Install and Configure Pano Controller

107 109 111

Pano Controller to Virtual Infrastructure Manager . . . . . . . . . . . . . 111 Pano Controller Connection to Directory Services . . . . . . . . . . . . . 111 Pano Client Discovery Method . . . . . . . . . . . . . . . . . . . . . . . 112

Chapter 13 Install, Configure and Integrate Pano Controller on VMware 113Install and Configure Pano Controller on VMware vSphere . . . . . . . . 113 (Overview) Install and Configure Pano Controller on VMware vSphere 113 Choose Your VMware Virtualization Infrastructure . . . . . . . . . . . 114 Deploy without vCenter Server and Active Directory . . . . . . . . . . 115 Choose Your Pano Controller Configuration . . . . . . . . . . . . . . 115 Install Pano Controller VM on ESX/ESXi . . . . . . . . . . . . . . . . 117 Change Pano Controller VMs Port Group . . . . . . . . . . . . . . . 118 Reserve Resources for the PanoVirtualAppliance VM in vCenter Server119 Integrate Pano Controller into Your VMware Environment . . . . . . . . 120 (Overview) Integrate Pano Controller into Your VMware Environment . 120 Configure Pano Controller Appliance Role . . . . . . . . . . . . . . . 121 Determine Access Accounts for Integrating Pano ControllerVMware . 122 Configure the Data Center FirewallVMware . . . . . . . . . . . . . . 122 Connect Pano Controller To Directory ServicesVMware . . . . . . . 122 Connect Pano Controller To vCenter Server . . . . . . . . . . . . . . 124 Choose a Pano Client Discovery MethodVMware . . . . . . . . . . 125 (Broadcast/Probe Methods) Set Up Pano Client DiscoveryVMware . 125 (DHCP Method) Set Up Pano Client DiscoveryVMware . . . . . . . 126 Configure Your Pano System License . . . . . . . . . . . . . . . . . 128

Chapter 14 Install, Configure and Integrate Pano Controller on Hyper-V 131Install and Configure Pano Controller on Hyper-V . . . . . . . . . . . . . (Overview) Install and Configure Pano Controller on Hyper-V . . . . . Choose Your Pano Controller Configuration . . . . . . . . . . . . . . Install the Pano Controller Connector for Microsoft SCVMM . . . . . . Install PanoVirtualAppliance on SCVMM . . . . . . . . . . . . . . . . Create the PanoVirtualAppliance VM . . . . . . . . . . . . . . . . . . Provision PanoVirtualAppliance VM . . . . . . . . . . . . . . . . . . Set Up the PanoVirtualAppliance VM. . . . . . . . . . . . . . . . . . Integrate Pano Controller into Your Hyper-V Environment . . . . . . . . (Overview) Integrate Pano Controller into Your Hyper-V Environment . Configure Your Pano Controller Appliance Role . . . . . . . . . . . . Determine Access Accounts for Integrating Pano ControllerHyper-V . Configure the Data Center FirewallHyper-V . . . . . . . . . . . . . . Connect Pano Controller To Directory ServicesHyper-V . . . . . . . Connect Pano Controller to SCVMM . . . . . . . . . . . . . . . . . . Choose a Pano Client Discovery MethodHyper-V . . . . . . . . . . (Broadcast/Probe Methods) Set Up Pano Client DiscoveryHyper-V . (DHCP Method) Set Up Pano Client DiscoveryHyper-V . . . . . . . Configure Your Pano System License . . . . . . . . . . . . . . . . . 131 131 132 134 134 135 135 136 137 137 138 138 139 139 140 141 141 142 144

viPano System Administrators Guide

Chapter 15 Install, Configure and Integrate Pano Controller on XenServerInstall and Configure Pano Controller on XenServer . . . . . . . . (Overview) Install and Configure Pano Controller on XenServer. Choose Your Pano Controller Configuration . . . . . . . . . . . Install Pano Controller VM on XenServer . . . . . . . . . . . . Integrate Pano Controller into Your XenServer Environment . . . . (Overview) Integrate Pano Controller into Your XenDesktop Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . XenDesktop Architecture . . . . . . . . . . . . . . . . . . . . . XenDesktop Components . . . . . . . . . . . . . . . . . . . . About the Logon Process. . . . . . . . . . . . . . . . . . . . . Configure the Pano Controller Appliance Role . . . . . . . . . . Determine Access Accounts for Integrating Pano Controller XenDesktop . . . . . . . . . . . . . . . . . . . . . . . . . . Configure the Data Center FirewallXenDesktop . . . . . . . . Connect Pano Controller To Directory ServicesXenDesktop . . Connect Pano Controller to XenDesktop Controller . . . . . . . Choose a Pano Client Discovery MethodXenDesktop . . . . . (Broadcast/Probe Methods) Set Up Pano Client Discovery XenDesktop . . . . . . . . . . . . . . . . . . . . . . . . . . (DHCP Method) Set Up Pano Client DiscoveryXenDesktop . . Configure the Pano System License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

147.147 .147 .148 .150 .152 .152 .154 .154 .155 .156 .157 .157 .157 .158 .159

. . . .160 . . . .161 . . . .163

Chapter 16 Prepare Desktops Chapter 17 Prepare for Automated Provisioning on vSphere(Overview) Set Up Desktop Virtual Machines on vSphere Prepare To Create Desktop Virtual Machines . . . . . . . Create Desktop Virtual Machines in vSphere Client . . . . Install Windows . . . . . . . . . . . . . . . . . . . . . . Install VMware Tools on DVMs . . . . . . . . . . . . . . Install Supported Display Driver (Windows 7 only) . . . . Set Hardware Acceleration . . . . . . . . . . . . . . . . Install Pano Direct . . . . . . . . . . . . . . . . . . . . . Verify DVM Connectivity . . . . . . . . . . . . . . . . . . Provide Disposable Desktops . . . . . . . . . . . . . . . Control Session Timeouts . . . . . . . . . . . . . . . . . (Windows 7) Disable Fast User Switching . . . . . . . . . (Windows 7) Disable Sleep and Hibernate . . . . . . . . Create DVM Templates in vSphere Client . . . . . . . . . (Windows XP) Install Sysprep Tools on vCenter Server. . Create Guest Customization Specification . . . . . . . . Test DVM Deployment. . . . . . . . . . . . . . . . . . . Upgrade of Pano Direct Service with View Agent . . . . . Upgrade VMware Tools . . . . . . . . . . . . . . . . . . Upgrade VMware View Agent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

165 167.167 .170 .170 .173 .174 .175 .176 .177 .186 .187 .188 .189 .190 .191 .192 .192 .193 .194 .194 .194

Chapter 18 Prepare for Automated Provisioning on XenDesktop

195

About Provisioning on Pano System with XenDesktop . . . . . . . . . . .195 (Overview) Set Up Desktop Virtual Machines on XenDesktop . . . . . . .196 Install SVGA II Display Driver (Windows 7 only). . . . . . . . . . . . . . .197

Table of Contents vii

Set Hardware Acceleration in Windows . . Install Pano Direct . . . . . . . . . . . . . Control Session Timeouts . . . . . . . . . (Windows 7) Disable Fast User Switching . (Windows 7) Disable Sleep and Hibernate

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

. . . . .

198 198 207 208 209

Chapter 19 Prepare for Automated Provisioning on Hyper-V(Overview) Set Up Desktop Virtual Machines on Hyper-V . Prepare To Create Desktop Virtual Machines . . . . . . . Create Desktop Virtual Machines in SCVMM . . . . . . . Install Windows . . . . . . . . . . . . . . . . . . . . . . Set Hardware Acceleration . . . . . . . . . . . . . . . . Install Pano Direct . . . . . . . . . . . . . . . . . . . . . Verify DVM Connectivity . . . . . . . . . . . . . . . . . . Create DVM Templates in SCVMM . . . . . . . . . . . . Clone with Optional Guest OS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

211211 212 212 212 213 214 223 224 225

Chapter 20 Configure Pano Controller GroupsAbout Pano Controller Redundancy and Scalability . . . About Pano System Scalability . . . . . . . . . . . . Primary and Secondary Pano Controllers . . . . . . Virtual IP Address. . . . . . . . . . . . . . . . . . . Setup and Manage Redundancy. . . . . . . . . . . . . Configure Secondary Pano Controller Instance . . . Add redundancy to your Pano Controller deployment Configure Email Notifications . . . . . . . . . . . . . Disable Email Notifications . . . . . . . . . . . . . . Determine Health of Failover Configuration . . . . . Recover from Degraded or Inactive Configuration . . Switch Active Modes . . . . . . . . . . . . . . . . . Convert Secondary to Primary . . . . . . . . . . . . Remove Failover Configuration . . . . . . . . . . . . Expanding and Managing Scalability . . . . . . . . . . Add an Auxiliary Controller to a Group . . . . . . . . Remove an Auxiliary Controller from a Group . . . . Monitor Client Load Across a Group . . . . . . . . . About Load Balancing XenDesktop Controllers . . . Identify Primary Pano Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

227227 227 228 228 228 229 229 232 233 233 237 237 238 238 238 239 242 242 242 244

Chapter 21 Setup Desktop BrokeringDVM Collections for Pano Virtual Desktop Broker . DVM Collections for Citrix XenDesktop . . . . . . DVM Collections for VMware View . . . . . . . . Remove Broker Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

245245 246 246 247

Chapter 22 Verify Pano System Deployment Chapter 23 Connect Pano Zero Clients

249 251

Connect Pano Devices. . . . . . . . . . . . . . . . . . . . . . . . . . . 251 Pano Buttons Lights . . . . . . . . . . . . . . . . . . . . . . . . . . . . 251

viiiPano System Administrators Guide

Chapter 24 Deploy Pano Remote(Overview) Deploy Pano Remote . . . . . . . . . Set Up Pano Gateway . . . . . . . . . . . . . . . Prepare To Test Pano Remote . . . . . . . . . . Test Pano Remote Connectivity . . . . . . . . . . (Recommended) Add Server String to Executable Remove Server String from Executable . . . . . . Add SSL Certificate To Pano Gateway . . . . . . Upgrade Pano Gateway . . . . . . . . . . . . . . Upgrade Pano Remote . . . . . . . . . . . . . . Configure Pano Remote Access. . . . . . . . . . Configure DVMs for 24-bit Color. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

253.253 .255 .257 .257 .258 .259 .259 .259 .260 .260 .261

Chapter 25 Deploy Pano Maestro Chapter 26 Upgrade Pano System(Overview) Upgrade Pano System to v5.0. . . . . . . . . . . . . . . Get Pano System Upgrade Software . . . . . . . . . . . . . . . . Upgrade Pano Controller . . . . . . . . . . . . . . . . . . . . . . . Upgrade a Single Instance of Pano Controller (Virtual Appliance Upgrade) . . . . . . . . . . . . . . . . . . . . . . . . Upgrade a Single Instance of Pano Controller (Application Upgrade Only) . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade a Group of Pano Controllers (Virtual Appliance Upgrade) Upgrade a Group of Pano Controller (Application Upgrade Only) . Check Status of Pano Controller VMs VMware Tools. . . . . . . . . Update Pano Controller VMs VMware Tools . . . . . . . . . . . . . Upgrade Pano Direct . . . . . . . . . . . . . . . . . . . . . . . . . Check Status of Virtualization Tools on DVMs . . . . . . . . . . . . Upgrade Virtualization Tools on DVMs . . . . . . . . . . . . . . . .

263

Deploying Pano Maestro Virtual Machine . . . . . . . . . . . . . . . . . .263

265. . .265 . . .266 . . .266 . . .267 . . . . . . . . . . . . . . . . .268 .268 .271 .273 .274 .275 .276 .277

Chapter 27 Manage Pano SystemChange Pano Controller VM Network Settings . . . . . Replace Pano Controllers Self-Signed Certificate . . . Restart Pano Controller VM . . . . . . . . . . . . . . . Change Superuser Password . . . . . . . . . . . . . . Provide Users Administrator Access To Pano Controller Change Web Admin Account Password . . . . . . . . . Determine Pano Controller Version . . . . . . . . . . . About Backup Manager . . . . . . . . . . . . . . . . . Configure Backup Manager . . . . . . . . . . . . . . . Backup Retention Policy . . . . . . . . . . . . . . . . . Delete Old Backups . . . . . . . . . . . . . . . . . . . Perform Manual Backups . . . . . . . . . . . . . . . . Restore from Backups . . . . . . . . . . . . . . . . . . Disable Automatic Backups . . . . . . . . . . . . . . . Manage Pano Licenses and Usage (Pano Controller). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

279.279 .280 .281 .281 .282 .283 .283 .283 .284 .286 .286 .287 .288 .289 .289

Chapter 28 Using Pano Maestro

291

Pano Maestro Installation and Setup . . . . . . . . . . . . . . . . . . . .291

Table of Contents ix

Managing Pano Controller Groups . . . . . . . . . . . . . . . . TCP Ports Used by Pano Maestro . . . . . . . . . . . . . . . . . Setting Up Pano Maestro . . . . . . . . . . . . . . . . . . . . . Adding a Pano Controller Group . . . . . . . . . . . . . . . . . . Editing a Pano Controller Group . . . . . . . . . . . . . . . . . . Removing a Pano Controller Group . . . . . . . . . . . . . . . . Configuring Directory Services. . . . . . . . . . . . . . . . . . . Managing Pano Maestro Administrators . . . . . . . . . . . . . . Selecting Pano Maestro Administrators . . . . . . . . . . . . . . Using the Directory Browser . . . . . . . . . . . . . . . . . . . . Backup and Restore Pano Maestro Configurations . . . . . . . . Manage Pano System Licenses and Usage (Pano Maestro) . . . Upgrade Pano Maestro . . . . . . . . . . . . . . . . . . . . . . Setup Secure HTTPS Connection for Pano Maestro Web Access

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

. . . . . . . . . . . . . .

292 292 293 293 294 294 295 296 296 297 297 297 298 298

Chapter 29 Create and Manage DVM CollectionsVMware and Hyper-V 301(Overview) Create DVM CollectionsVMware and Hyper-V . . . . . . . Choose DVM Collection TypeVMware and Hyper-V . . . . . . . . . . Create DVM CollectionsVMware and Hyper-V . . . . . . . . . . . . . Define Collection TypeVMware and Hyper-V . . . . . . . . . . . . Provide Access To DVM CollectionVMware and Hyper-V . . . . . Configure for DVM DeploymentVMware and Hyper-V . . . . . . . Add DesktopsVMware and Hyper-V. . . . . . . . . . . . . . . . . Configure Extra Desktops and Power StateVMware and Hyper-V . Configure for User Control of DesktopsVMware and Hyper-V . . . Set Access Options for Pano Remote UsersVMware and Hyper-V . Assign Pano Clients and Users To DVMsVMware and Hyper-V . . . . User Membership RulesVMware and Hyper-V . . . . . . . . . . . . . Manually Assign Users To DVMs in User Based Collections VMware and Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . Manually Assign Pano Clients To DVMs in Device Based Collections VMware and Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . Verify Newly Created DVMsVMware and Hyper-V . . . . . . . . . . . Deploy ResourcesVMware and Hyper-V . . . . . . . . . . . . . . . . Log Messages for Resource DeploymentVMware and Hyper-V . . . . Use Cases for Device RestrictionsVMware and Hyper-V . . . . . . . Set Up Collections with Device RestrictionsVMware and Hyper-V . . . Update DVM CollectionsVMware and Hyper-V. . . . . . . . . . . . . Delete DVM CollectionsVMware and Hyper-V . . . . . . . . . . . . . Create Virtualization HierarchyVMware . . . . . . . . . . . . . . . . Configure for Concurrent Deployment and Power Operations VMware and Hyper-V . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301 303 305 305 307 310 312 312 314 315 316 317

. 318 . . . . . . . . . 319 320 322 322 322 323 324 324 325

. 327

Chapter 30 Create and Manage DVM CollectionsXen(Overview) Create DVM CollectionsXenServer . . . . . . . Create DVM CollectionsXenDesktop . . . . . . . . . . . . . Define Collection TypeXenDesktop . . . . . . . . . . . . Provide Access To DVM CollectionXenDesktop . . . . . Set Access Options for Pano Remote UsersXenDesktop . Assign Pano Clients and Users To DVMsXenDesktop . . . . User Membership RulesXenDesktop . . . . . . . . . . . . . Manually Assign Users To DVMs in User Based Collections XenDesktop . . . . . . . . . . . . . . . . . . . . . . . . . Use Cases for Device RestrictionsXenDesktop . . . . . . . Update DVM CollectionsXenDesktop . . . . . . . . . . . . Delete DVM CollectionsXenDesktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

329329 330 330 331 331 332 333 333 334 334 335

xPano System Administrators Guide

Set Up Collections with Device RestrictionsXenDesktop. . . . . . . . . .335

Chapter 31 Enable USB Peripheral Support

337

Install Pano Device USB Support . . . . . . . . . . . . . . . . . . . . . .337 Enable Users To Safely Remove USB Mass Storage Devices . . . . . . .338 Restrict or Allow Use of Specific USB Devices . . . . . . . . . . . . . . .339

Chapter 32 Refresh Virtual Machines in Pooled Desktops Chapter 33 Configure and Manage Pano Clients and Desktop Preferences(Overview) Set User Preferences . . . . . . . . . . . . . . . . . . . Retrieve Pano Client Information . . . . . . . . . . . . . . . . . . . Determine Pano Device Model . . . . . . . . . . . . . . . . . . . . Use a Custom Login Image . . . . . . . . . . . . . . . . . . . . . . Reset Pano Client Login Screen Image To Default Image . . . . . . Restart Pano Client Login Screens . . . . . . . . . . . . . . . . . . About Password Changes via Pano Client Login Screen . . . . . . . Configure Pano Devices for Dual-Monitor Use . . . . . . . . . . . . (Pano G1) Verify Pano Dual Monitor Version . . . . . . . . . . . . . (Pano G1) Uninstall Pano Dual Monitor . . . . . . . . . . . . . . . . Manually Add Pano Clients . . . . . . . . . . . . . . . . . . . . . . Create Device-Based DVM Assignments . . . . . . . . . . . . . . . Rename Pano Clients . . . . . . . . . . . . . . . . . . . . . . . . . Change Pano Client MAC Address or IP Address. . . . . . . . . . . Remove Pano Clients . . . . . . . . . . . . . . . . . . . . . . . . . Identify Pano Client Serial Numbers . . . . . . . . . . . . . . . . . . Disable Pano Clients. . . . . . . . . . . . . . . . . . . . . . . . . . Enable Pano Clients . . . . . . . . . . . . . . . . . . . . . . . . . . Default User Login Preferences . . . . . . . . . . . . . . . . . . . . About Pano Control Panel . . . . . . . . . . . . . . . . . . . . . . . Set Keyboard Settings for Specific DVMs . . . . . . . . . . . . . . . Set Audio Settings for Specific DVMs . . . . . . . . . . . . . . . . . Set Default Keyboard Layout and Input Language for Specific DVMs Enable Language Preference for Pano Client Login Screen . . . . . Set Screen Resolution Settings for Specific DVMs . . . . . . . . . . Set Power Save Settings for Specific DVMs as End User. . . . . . . Configure Pano Device Sleep State . . . . . . . . . . . . . . . . . . Disconnect Pano Clients from DVMs . . . . . . . . . . . . . . . . . Unassign Pano Clients from DVMs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

341

343.344 .344 .345 .346 .347 .347 .348 .348 .353 .355 .357 .357 .359 .359 .359 .360 .360 .360 .361 .362 .364 .364 .365 .367 .369 .370 .370 .372 .372

Chapter 34 Pano Controller Network Port UsageInbound Ports Used by Pano Controller . Outbound Ports Used by Pano Controller Internal Ports Used by Pano Controller. . Inbound Ports Used by Pano Direct . . . Outbound Ports Used by Pano Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

373.373 .374 .375 .375 .375

Chapter 35 Monitor and Manage DVMs in Pano Controller

379

Monitor DVM Utilization and State . . . . . . . . . . . . . . . . . . . . . .379 Retrieve DVM Information . . . . . . . . . . . . . . . . . . . . . . . . . .381

Table of Contents xi

Monitor Pano Direct Status . . . . . . . . . Perform Maintenance on DVMs . . . . . . . Determine Pano Direct Version . . . . . . . Determine Whos Logged on To DVMs . . . About User Assignment . . . . . . . . . . . About Device Assignment . . . . . . . . . . Unassign Users from DVMs . . . . . . . . . Move DVMs to Trash . . . . . . . . . . . . Remove DVM from Trash . . . . . . . . . . Delete DVMs from Disk . . . . . . . . . . . Set Power Save Option for All Pano Clients . Replace or Reimage DVMs . . . . . . . . . Expand DVM Hard Drives . . . . . . . . . . Rename DVMs . . . . . . . . . . . . . . . . Launch DVM Console . . . . . . . . . . . . Configure DVM Firewall . . . . . . . . . . . Uninstall Pano Direct. . . . . . . . . . . . . Reuse DVM Names . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

. . . . . . . . . . . . . . . . . .

382 383 384 385 385 385 385 386 387 387 388 388 388 394 394 396 398 399

Chapter 36 Monitor and Manage Sessions in Pano Controller Chapter 37 Optimize DVM PerformanceWays To Optimize DVM Performance . . . . . . . . . . . . . . . . . Windows 7 Optimizations . . . . . . . . . . . . . . . . . . . . . . Windows XP Optimizations . . . . . . . . . . . . . . . . . . . . . Increase VMware ESX Server Service Console Memory . . . . . . . Minimize DVM CPU Consumption . . . . . . . . . . . . . . . . . . . User Group Policy Settings Management with Loopback Processing . . . . . . . . . . . . .

401

Monitor and Manage Sessions. . . . . . . . . . . . . . . . . . . . . . . 401

403403 403 406 411 411 412

Chapter 38 Integrate Pano System with VMware View(Overview) Integrate Pano System with VMware View . . Configure VMware View Agent . . . . . . . . . . . . . . Enable Desktop Connections to VMware View Pools from Pano Zero Clients . . . . . . . . . . . . . . . . . . . . Enable Protocol Choice for VMware View Pools . . . . . Connect Pano Controller To VMware View . . . . . . . . Create VMware View Collection . . . . . . . . . . . . . . Validate Pano Controller-VMware View Configuration. . .

413. . . . . . . . 414 . . . . . . . . 414 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 417 420 420 421 422

Chapter 39 TroubleshootingTroubleshoot Networking Problems . . . . . . . . . . . . . . Troubleshoot DVM Login Problems . . . . . . . . . . . . . . Normal Login Process . . . . . . . . . . . . . . . . . . . DVM Login Error Messages . . . . . . . . . . . . . . . . Troubleshoot Monitor, Mouse, and Keyboard Problems . . . . Troubleshoot USB Device Problems. . . . . . . . . . . . . . Troubleshoot RDP Connection Problems . . . . . . . . . . . Troubleshoot Authentication and Directory Service Problems . Troubleshoot Communication Problems with vCenter Server . Troubleshoot Backup Problems . . . . . . . . . . . . . . . . Troubleshoot Pano Remote Problems . . . . . . . . . . . . . (Pano G1) Troubleshoot Pano Dual Monitor Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

423423 424 424 425 426 428 428 429 431 431 432 434

xiiPano System Administrators Guide

Troubleshooting Group Membership Problems . . . . . . . . . . . . . . .439 Troubleshooting Login Issues . . . . . . . . . . . . . . . . . . . . . . . .439

Chapter 40 Work with Log Files

441

Display and Filter Pano Controllers System Messages . . . . . . . . . . .441 Download Pano Controllers Log Files. . . . . . . . . . . . . . . . . . . .442 Download DVMs Log Files . . . . . . . . . . . . . . . . . . . . . . . . .442

Chapter 41 Pano Device Technical Specification Chapter 42 FAQs Chapter 43 Integrate Pano GINA(Windows XP) Whats a GINA . . . . . . . . . . . . . . . . . . . . (Windows XP) About Pano GINA Provider and Registry Changes . (Windows XP) Reestablish Broken GINA Chain. . . . . . . . . . . (Windows XP) Install Third Party GINA Applications . . . . . . . . (Windows XP) Upgrade or Uninstall Third Party GINA Applications. (Windows XP) Fix Windows GINA State. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

443

Pano G2 Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . .443 Pano G1 Specification . . . . . . . . . . . . . . . . . . . . . . . . . . . .445

447 475.475 .476 .478 .478 .480 .480

Chapter 44 Tech NotesForce Users To Log Off . . . . . . . . . . . . . . . . . . . . . . . . . . Connect Pano Clients To Your Wireless Network . . . . . . . . . . . . . Add Pano Logic Vendor Class for Linux DHCP Server . . . . . . . . . . Add Pano Logic Vendor Class for Netware DHCP Server. . . . . . . . . Add Pano Logic Vendor Class for Cisco IOS DHCP Server. . . . . . . . Add Pano Logic Vendor Class for Alcatel/Lucent VitalQIP DHCP Server . Add Pano Logic Vendor Class for Infoblox DHCP Server . . . . . . . . . Install Pano System with ESXi without vCenter Server . . . . . . . . . . Protect Against Connection Failures To SAN Devices . . . . . . . . . . (RDP Connections Only) Configure Pano Direct for 24-bit Color . . . . . (RDP Connections Only) Enable Remote Desktop and Set Remote Desktop Users . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Microsoft Outlook Nickname and Auto-completion Cache To Desktop Virtual Machines. . . . . . . . . . . . . . . . . . . . . . . Migrate Browser Bookmarks and Cookies To Desktop Virtual Machines . (Less Common) Connect Pano Controller To Directory Services . . . . . Use Pano Direct Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . Enable Silent Installation for Windows XP . . . . . . . . . . . . . . . . . Install Certificate for Pano Direct Drivers . . . . . . . . . . . . . . . . . Change Network Adapter Type . . . . . . . . . . . . . . . . . . . . . . (Windows XP) Disable Network Adapter as Ejectable Device. . . . . . . (XenDesktop Only) Configure Citrix NetScaler to Monitor XenDesktop Controllers . . . . . . . . . . . . . . . . . . . . . . . . . Determine G1 or G2 Device . . . . . . . . . . . . . . . . . . . . . . . . Login Access to Pano Controller Connector for Microsoft SCVMM . . . . Login Access to Pano Gateway . . . . . . . . . . . . . . . . . . . . . . Setup Issues: XenDesktop on VMware ESX Server. . . . . . . . . . . . Windows 7 DVMs are Inaccessible or Windows Does Not Boot . . . . . Help File Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

483.484 .485 .486 .487 .487 .488 .489 .494 .495 .495 .496 .499 .501 .501 .507 .511 .513 .515 .516 .516 .518 .519 .519 .520 .521 .521

Table of Contents xiii

xivPano System Administrators Guide

Chapter0

Preface

About This BookThis book describes the installation and administration of the Pano Virtual Desktop Solution.

Who Should Use This BookThis book is intended to support System Administrators that need to deploy and maintain the Pano System.

Related DocumentationPano System documents contain additional information relevant to installing, maintaining, and The following Administrators Guide administering Pano System.

Pano System Release Notes - This book outlines whats new in the release and what knownissues were fixed in the release. This book is available online at www.panologic.com and through the Pano System Online Help. Pano System Administrators Guide - This book provides step-by-step instructions about how to install and configure the Pano System. This book is available online at www.panologic.com and through the Pano System Online Help. For additional documentation, go to www.panologic.com.

Typographical ConventionsThis document uses different typefaces to indicate different kinds of information. The following table explains these typographical conventions.FontCourierNewBold Italics

Meaning Indicates error messages, file name, or screen output. In a command line, indicates information to be entered exactly as shown. In a command line, indicates a variable for which you should substitute an appropriate value.

About This Book 1

Contacting Pano Logic

Pano Logic Technical Support:

[email protected] or (650) 454-8966

2Pano System Administrators Guide

Pano System Administrators Guide

1Chapter0

Pano System Overview

The Pano System comprises physical client devices, desktop software services, and centralized management software, all running atop a server-based virtualization infrastructure. The Pano System enables organizations to centralize user desktop computers inside the IT Data Center. Instead of having user desktops stationed at each user's desk, you can run these desktops as virtual desktops on a server that is hosted inside your data center. The server can be using the Microsoft, VMware, or Citrix virtualization platform. Users connect to their virtual desktops using Pano clients and Pano System software that runs inside the data center. The Pano System comprises a few main components:

Pano Client - Pano Logic provides clients from which users can connect to their virtualdesktops, and each client has its own set of advantages. You can use one or more of these clients in your environment. Pano Device - A zero client hardware device that enables an end user to connect to the virtual desktop. Zero client means that the Pano device is pure hardware; it does not run any software of any sort. The Pano device has: no CPU no memory no operating system no drivers no software no moving parts The Pano device connects keyboard, mouse, display, audio and USB peripherals over an existing IP network to an instance of Windows 7 or XP running on a virtualized server. Pano Remote - A software solution that allows end users to access their desktop virtual machines from any PC remotely. Pano Remote is commonly used by people who access their virtual desktop in the office, from their home and while on the road. Pano Gateway - Supporting infrastructure for Pano Remote and is an extension of Microsoft Windows Server Terminal Services Gateway. Pano Controller - Pano Logic's centralized service and web-based management interface. Pano Controller lets administrators manage the entire virtual desktop installation by integrating with existing directory services and virtualization platform managers. Pano Controller acts as a connection broker, integrating with your directory service for user authentication. Additionally, Pano Controller supports connecting a Pano client to a user's desktop virtual machine with a 3rd party connection broker such as VMware View and Citrix XenDesktop. Pano Controller architecture of the Pano Manager has been greatly enhanced to role-based functionality and Pano Controller groups for greater scalability and more diverse deployment options. Pano Controller functionality is configured by enabling or disabling Appliance roles: Full Mode is the default configuration and provides full functionality, including both Zero Client Controller and Virtual Desktop Broker functionality. Zero Client Controller (ZCC) role provides support for client discovery, authentication, and login services. Virtual Desktop Broker (VDB) role provides support for Pano connection brokering.

3

While some customers will run Pano Controller in Full Mode using a single Pano Manager instance, customers requiring advanced scalability and deployment options should choose to take advantage of the Zero Client Controller and Virtual Desktop Broker roles for a highly scalable, highly flexible enterprise architecture enabled by Pano Controller groups. Differentiated Pano Controller roles and groups enable flexible 3rd party broker support and enhanced Pano System scalability. Each Pano Controller groups consists of a primary Pano Controller, a secondary Pano Controller and up to four auxiliary Pano Controllers.

Pano Maestro - A centralized management access point to manage the configured PanoController groups. Centralized management includes collecting inventory data from all the devices managed in the groups, integrating with Directory Services (AD) for access authentication, and providing license configuration and enforcement. Pano Maestro is installed on a separate VM. Pano Direct Service - A lightweight service that resides on each desktop virtual machine. This service taps into the Windows drivers and sends the display, keyboard, mouse, audio and USB peripheral data over the network to the Pano device. This service links peripherals attached to the Pano client to the unmodified Windows drivers on the virtual machine. This design guarantees that all existing Windows drivers work without modification. Virtualization Layer - The underlying virtualization platform that allows multiple virtual machines to run on shared server resources. Hypervisors Software that allows multiple virtual machines (VMs) to run concurrently on a host server. Hypervisors host both DVMs running on desktop servers and host system VMs, like Pano Controller, or platform tools on infrastructure servers. DVM Management and Provisioning Tools Various platform-specific tools, often deployed as VMs on infrastructure servers, which are used for automated provisioning, management tasks or optimizing the storage used by DVMs. Client Tools Platform-specific software installed into the DVMs operating system to provide connections to the supporting hypervisor and platform DVM management tools.

Pano ClientPano Clients provide convenient ways for a user to connect to a desktop virtual machine:

Pano Device - Ideal if you want virtual desktops at the lowest total cost of ownership (TCO). Pano Remote - Ideal if you have users who need access to their virtual desktops whenworking from home or on the road. Generally, is used as a complement to the Pano device.

Pano DeviceThe Pano device is specifically designed for server-based desktop virtualization. Because the Pano device is 100% hardware, all software can now in the data center, where all your software can be centrally managed and effectively protected. The Pano device connects to your standard PC peripherals including keyboard, mouse, video monitor, Ethernet network, audio speakers/headphones and a wide variety of USB devices such as thumb drives, CD/DVD drives and additional peripherals. For a list of supported devices, go to Support for USB Devices on page 29. The Pano device is statelessit contains no intelligence or software memoryand is controlled by centralized services such as the Pano Controller and DHCP. The Pano device includes a single buttonthe Pano Buttonthat initiates out-of-band control of a users virtual desktop. By simply pushing the Pano Button, a user can disconnect from the desktop, instantly securing the work environment, while preserving the state and operation of the virtual desktop.


A Pano device consumes only 6.5 watts of power with two monitors connectedaround 5% of the energy consumed by a traditional desktop computerand contains no moving parts or compute resources that would require frequent upgrades or replacement. Also, a Pano device has a configurable sleep mode that consumes less than.2 watts of power. A Pano device provides a desktop experience to the user by communicating with Pano Controller and DVMs (desktop virtual machines), as shown in the following illustration. (The Physical Workspace layer is the only area that is not in the data center; the Virtual Desktop Management and Server Hosted Virtual Desktop layers are hosted in the data center.)

Pano RemotePano Remote is a software solution that allows your always-on-the-go end users to conveniently access their desktop virtual machines from any PC and from a remote location. Pano Remote enables users to reach their Pano desktop virtual machine from a remote location over a wide-area-network like the Internet. Pano Remote enables users to temporarily access their Pano virtual desktops when they are away from the office, whether working in the evening or when travelling. Simply plug a special secure USB key into any Microsoft Windows PC, then log on to the virtual desktop! Pano Remote User Experience Pano Remote provides access to a DVM either in a window or using the full screen. Administrators can set policies in the Pano Controller to allow or restrict access to local printers and drives along with controlling transfer of data on the clipboard between the virtual and host operating systems. Pano Remote is delivered already installed on a secure USB key and can be used with either Microsoft Windows XP, Windows Vista, or Windows 7 on the host desktop computer. Pano Remote vs Pano Device With Pano Remote, your end users can now access their DVMs even when they are not sitting in front of a Pano device. A Pano device is still the primary way of accessing a DVM, but Pano Remote offers a secondary way of gaining access. While in the office your end users have a Pano device at their desks. In addition, they can use Pano Remote to access their DVM from a PC in a conference room, or they can use Pano Remote plus Pano Gateway to access their DVM from a PC at home.

Pano Remote 5

Pano GatewayPano Gateway is a communication mechanism bundled with Pano Remote that provides secure connections from external networks using Microsoft Windows Server 2008 Terminal Services Gateway as supporting infrastructure. Pano Gateway allows your end users to use Pano Remote from outside your firewall without the need for VPN software or hardware. The Gateway uses standard secure protocols (RDP via HTTPS/Secure Sockets Layer) to connect to the Pano Gateway server, and, in turn, to the virtual desktops, simplifying the configuration of firewalls and security policies. Pano Gateway ensures that users get suitable performance in the remote Windows desktop, even over connections like consumer-level DSL or cable modems. Performance is usually better over higher speed connections, however.

Pano ControllerThe Pano Controller is a centrally-hosted server that is delivered as a virtual appliance. Typically, Pano Controller runs as a virtual machine located on the same host servers as your desktop virtual machines. You can add multiple Pano Controllers to your configuration to meet your availability and scalability requirements. The Pano Controller provides secure access to virtual desktops by leveraging services such as Microsoft Active Directory for user authentication. The Pano Controller controls and deploys desktop virtual machines by leveraging virtualization management systems such as Microsoft System Center Virtual Machine Manager (SCVMM) and VMware vCenter Server. The Pano Controller connects end users and Pano devices to desktop virtual machines by integrating with its internal connection broker service, Citrix XenDesktop or VMware View.


Note: In versions prior to Pano System 5.0 this component was called Pano Manager. Starting with Pano System 5.0, this component is called Pano Controller.

The Pano Controller has built-in connection broker functionality. As a connection broker, the Pano Controller uses the Directory Services (typically Microsoft Active Directory) and the management tools provided by the virtualization provider (VMware vCenter Server) to connect a Pano client to a user's DVM. The connection broker is responsible for a couple of important tasks. The connection broker:

Receives the user credentials that users input from the Pano client login screen, and relaysthat information to the directory service for authentication. Communicates with all desktop agents in the DVMs so that the correct virtual desktops can be associated with the correct user. With Pano System 5.0, the Pano Controller supports 3rd party connection brokers and is configured based on appliance functionality or role. The functions and their corresponding roles are:.Appliance Role Zero Client Controller Function Discovery and control of Pano zero clients, including Pano Remote clients Brokering and provisioning of desktop virtual machines Provides both functions listed above.

Virtual Desktop Broker Full Mode

Pano Controller RolesStarting with Pano System 5.0, the administrator can enable or disable these main functions by selecting the appropriate Appliance Role. The Pano Controller must have at least one of these functions enabled. The possible options for the Appliance Role are:

Full Mode - By default the Pano Controller configuration in the PanoVirtualAppliance VMcomes configured in Full Mode. In this configuration, the Pano Controller is able to perform all tasks including discovery and control of Pano clients and brokering and provisioning of desktops. Customers who have deployed earlier versions of Pano System will want to run their Pano Controller in Full Mode because it is functionally equivalent to earlier versions of Pano Manager. In general, Full Mode is the configuration best suited to most environments. Zero Client Controller- As an advanced setting, the administrator may choose to enable only the Zero Client Controller role. In this configuration, the Pano Controller only discovers and controls Pano Zero Clients and Pano Remote clients. A separate connection broker service is

Pano Controller 7

required. This separate connection broker service can be a Pano Virtual Desktop Broker, Citrix XenDesktop or VMware View. Virtual Desktop Broker - As an advanced configuration, the administrator may choose to enable only the Virtual Desktop Broker role. This is valid when you have configured a separate instance of Pano Controller running as a Zero Client Controller. The Appliance Role is configured in the Pano Controller console on the Setup tab:

Pano Controller Group ArchitectureFor scalability with high availability and load balancing, you can add additional Pano Controllers to your configuration to form a Pano Controller group. Each Pano Controller groups consists of a primary Pano Controller, a secondary Pano Controller and up to four auxiliary Pano Controllers to support up to a total of six Pano Controllers. With 3rd party connection brokering, Pano Controller groups can be configured to support up to 10,000 DVMs/clients. Users can roam across Pano Controller groups for flexible DVM access. Note: Scalability and redundancy groups from previous Pano Manager configurations are converted into a Pano Controller group. The table below describes the Pano Controller Group architectures.Appliance Role ConfigurationFull Mode (both ZCC and VDB functionality)

Pano ControllersUp to six per group. Up to five groups.

DescriptionPano Controller running in Full Mode on a single VM. This deployment option is the simplest option to configure and provides the full functionality of the Pano System. This is generally the best option for starting out.

Full Mode


Appliance Role

ConfigurationFull Mode (both ZCC and VDB functionality) with 3rd Party Connection Broker

Pano ControllersUp to six per group. Up to five groups.

DescriptionPano Controller running in Full Mode on a single VM with multiple instances of a 3rd party broker running on separate VMs. This deployment option allows you to use either Citrix XenDesktop or VMware View as the connection broker for user-based assignments. You may also use the Pano Controller's internal connection broker service to support device-based assignments. Choose this option if you want to use a 3rd party connection broker and you also want to use device-based assignments. Pano Controllers running ZCC for discovery, authentication and login services. Requires separate VM for 3rd party connection broker. This deployment option allows you to use either Citrix XenDesktop or VMware View as the exclusive connection broker for your system. With this deployment option you will be limited to user-based assignments only and will not be able to deploy device-based assignments. Choose this option if you want to use a 3rd party connection broker and you do not want to use device-based assignments. Used for special deployment scenarios.

Full Mode

ZCC with 3rd Party Connection Broker ZCC

Up to six per group. Up to five groups.

VDB

VDB Connection Broker

Up to two per group.

See Deployment Planning on page 71.

Pano MaestroPano Maestro provides a centralized management access point to manage Pano Controller groups. Centralized management includes collecting inventory data from all the devices managed in the groups, integrating with Directory Services (AD) for access authentication, and providing license configuration and enforcement. Pano Maestro is installed on a separate VM and manages up to five Pano Controller groups. Pano Maestro features include:

Centralized management, status monitoring, provisioning from single management console location. High-level view and status of Pano Controller Groups and group members. The Pano Controller Group status shows the cumulative status of all group members. Any changes in member status are propagated to the Group status. For example, when one member enters a Warning state, the Pano Controller Group status changes to Warning. Functional interface tabs to manage multiple controllers at the same time. Optional drill down to each of member's Pano Controller console management interface. Management and enforcement of Pano System licenses across Pano Controller groups throughout the customer network. Seamless authentication and access to all the members using Directory Services. Flexible Pano Maestro display and management options.

Pano Maestro 9

Pano Maestro can be setup on same virtualization stack using the same server hardware that is used for setting up the Pano Controller. However, Pano Maestro must be setup on separate virtual machine.

Pano Direct ServiceThis lightweight Pano Direct Service (Pano Direct) runs on each DVM. The Pano Direct is installed on top of your Windows desktop operating system(s) and allows the desktop session and peripheral I/O to be transmitted securely over your standard IP network. The Pano Control Panel, which is part of the Pano Direct, allows individual users to set their personal preferences for keyboard, mouse, display and audio settings.

Virtualization LayerHypervisor (virtualization) software allows multiple virtual machines to run concurrently on a host server. Pano Logics system leverages server-based virtualization platform software to abstract processor, memory, storage and networking resources into multiple virtual machines, to give you greater hardware utilization and flexibility. Hypervisors are used both to host desktop virtual machines (DVMs) running on desktop servers and to host system VMs like Pano Controller or XenDesktop Controller on infrastructure servers. The Pano System plays well with hypervisors, such as vSphere ESX/ESXi, Hyper-V, and XenServer. XenServer and vSphere ESX/ESXi are type 1 or bare metal hypervisors that require no other host operating system (OS). They interact directly with the server hardware rather than relying on the host OS driver stack. Because of this, you need to be sure that your server hardware, including RAID controllers and network interface cards, are on the hardware compatibility list for your selected hypervisor. For a complete list of supported virtualization infrastructure, go to Virtualization Platform Requirements. By having the desktops run on top of a hypervisor such as vSphere ESX/ESXi, for example, you can take advantage of other technologies, such as DRS, VMotion, and HA, to provide a more robust and fault-tolerant desktop delivery mechanism.



2Chapter0

Pano System Concepts

These key concepts introduce the Pano System: DVMs DVM Collections Types of Collections Automated Deployment Concepts Templates Virtual Desktop Management Scalability Licensing

DVMsA desktop virtual machine (DVM) is a virtual machine that runs a desktop operating system such as Windows 7. DVMs run on top of a virtualized infrastructure hosted on one or more servers. From the perspective of a virtualized infrastructure, theres no difference between a DVM and a standard virtual machine. The same types of operations that can be performed on a standard virtual machine can be performed on a DVM. Pano Logic uses the term DVM to specifically refer to virtual machines that are being used as virtual desktops.

When inside the corporate network, users can connect to DVMs through Pano Device or PanoRemote as outlined in Log On To DVMs as End User on page 48. When outside the corporate network, users can connect to DVMs through Pano Remote.

DVM CollectionsThe Pano System manages a set of DVMs called DVM collections, as one logical unit. When you create a collection, you can specify the level of user control and personalization. How you view the collection is the same if you are using VMware vSphere or Microsoft System Center Virtual Machine Manager (SCVMM). DVMs are tracked by GUIs (Globally Unique Identifiers) and not by their location within a folder hierarchy. This design provides a more flexible and reliable method of tracking DVMs that is also platform-independent. This tracking method enables collections to manage lists of DVMs, instead of tracking DVMs by folder membership. To associate DVMs with a new DVM collection, you can pick from various locations. To view the new DVM in the DVMs view, you need to manually associate the new DVM with a collection. When a new DVM is created under a folder that is not managed by any collection, the DVM does not appear on the DVMs view. However, when Pano Controller automatically deploys a new DVM for a managed collection, the DVM relationship to a DVM collection is automatically updated.

DVMs 11

Related Topics Types of Collections on page 12 (Overview) Create DVM CollectionsVMware and Hyper-V on page 301

Types of CollectionsA key characteristic of a DVM collection is the method by which users or devices are mapped to DVMs. There are two basic methods by which mappings are determined: by user and by device. Hence, the following collection types: User Based Collections These DVM assignments are based on the user accessing the system. Use User Based collections if you want users to be able to access their DVMs regardless of location. For instance, if you want your users to be able to roam freely throughout the workplace and always have access to their DVM, use one of the User Based collections. For more information, go to User Based Collections on page 12. Device Based Collections These DVM assignments are based on the device that is being used to access the system. Use Device Based collections if you want a Pano client to always connect to a specific DVM. For more information, go to Device Based Collections on page 14. 3rd Party Connection Broker Collections This special type of collection works in conjunction with VMware View Manager (formerly known as VMware VDM) and Citrix XenDesktop. Use of VMware View and Citrix XenDesktop with Pano System is optional. For details, go to (Overview) Integrate Pano Controller into Your VMware Environment on page 120.and (Overview) Integrate Pano Controller into Your XenDesktop Environment on page 152.

User Based CollectionsWith User Based collections, Pano clients display the Pano client login screen whenever the device is not connected to a DVM. Users simply type their credentials at the Pano client login screen to connect to their assigned DVMs. Note: User Based collections do not support card readers. There are several User Based collections from which you can choose: Pooled Desktops A Pooled Desktops collection type is most appropriate for a set of users that all use the same set of applications. This collection is commonly used in a Call Center environment where there are work shifts and where only a subset of users need a desktop at any given time. The intent of this collection type is to save computing resources by not having each user assigned to a specific desktop. All users would have the same desktop configuration because these desktops are not permanently assigned to these users. However, you can use Windows roaming profiles and document redirection to allow users of a Pooled Desktops collection type to have some degree of personalization. Keep the size of users' profiles small in order to keep login times short. Within a Pooled Desktops collection type, DVMs are created automatically and temporarily allocated to users upon login. DVM are returned to the pool upon logoff.


DVMs can be created automatically from a specified template and assigned to users by the Pano Controller. The set of users that are entitled to use the collection is specified in the collection properties (see Create DVM CollectionsVMware and Hyper-V on page 305). Assignment of DVMs in a Pooled Desktops collection type is on a per session basis: as soon as the users Windows session ends (by logging out of Windows), the DVM becomes available for another user. Permanently Assigned Desktops A Permanently Assigned Desktops collection type is most appropriate for users that require dedicated virtual desktops and that require the ability to customize their virtual desktops or save files locally. This collection type is most commonly used for a typical office environment where users PCs are being replaced by Pano devices. The desktops are created automatically and permanently assigned to users upon first login. After Pano System assigns a DVM to a user, that user retains the same dedicated desktop until it is unassigned by the Administrator. The set of users that are entitled to use the collection is specified in the collection properties (see Create DVM CollectionsVMware and Hyper-V). After the Pano System assigns a user to an available DVM, the Pano System gives that user the same dedicated DVM every time the user logs on with the same credentials. Assignment of the user to the DVM is automatically established the first time the user logs on to the DVM. Alternatively, you can assign a particular DVM to a user through the Management User Interface (MUI). Permanently Assigned Desktops collection types allow you to leverage automated deployment, while providing users a dedicated DVM that they can customize and personalize. Existing Desktops An Existing Desktops collection type is most appropriate when you want to create a one-to-one mapping between a user and a DVM that has been created through some other process other than Pano Controller's automated process. This collection is most commonly used if youre evaluating the Pano system or if you converted a user's physical machine to a virtual machine using VMware Converter, and you want to permanently assign that virtual machine to that user. This collection is the least-used collection type in a production environment. A single Existing Desktops collection type should contain only one DVM; otherwise, the user connects arbitrarily to one virtual machine in the collection. However, you can create multiple Existing Desktops collections. Pano System temporarily allocates the DVM to a user automatically upon login. You can manually assign users to DVMs, if they are part of the vCenter Server inventory. The set of users that are entitled to use the collection is specified in the collection properties (see Create DVM CollectionsVMware and Hyper-V). VMware View When Pano Controller is set up with a VMware View Manager server, any credentials that users input through the Pano client login screens are passed to a VMware View Manager server. VMware View specifies the appropriate desktop virtual machine for the session and the Pano Controller connects the Pano device to the appropriate desktop virtual machine. DVM provisioning is managed through VMware View.

Types of Collections 13

In this scenario, the Pano Controller establishes the connection between the Pano client and the DVM. The Pano Controller does not communicate with vCenter Server to start the DVM; rather, VMware View handles these tasks. Citrix XenDesktop As outlined in Create DVM CollectionsXenDesktop this is the only DVM that is supported for XenDesktop. As implied, this collection does not apply to VMware and Hyper-V.

Device Based CollectionsDevice Based collections allow you to assign Pano clients, rather than users, to specified DVMs. This model is useful if you want to implement special usage scenarios, such as a kiosk or shared computer. A kiosk is commonly defined as a limited purpose computer that supports multiple users. Kiosks are often placed in open locations where users can simply walk up and start using the device, perhaps without providing any credentials. You can find kiosks in public places such as libraries, company break rooms or corporate lobbies. Access without user-supplied credentials is implemented by having the system automatically log on to Windows using credentials that are specified in the collection properties. The user experience is such that the user only sees the Windows desktopnot the Pano client login screen or the Windows login screen. The operating system in a kiosk is generally locked down so that users cannot gain access to applications or networks that are restricted. Creating a Device Based collection is similar to creating a User Based collection. Device Based collections take advantage of the automated deployment features of the Pano Controller, allowing you to create and specify a template, while automating the cloning of new DVMs. Once DVMs have been created, the next step is to assign a device. Device assignment can be performed through the Pano Controller administrator interface or by logging on for the first time from a device through the Pano client login screen. Once assigned, the Pano Controller allows a device to connect to only the designated DVM. If you later want to use that device with a User Based collection, you must first unassign the device from the designated DVM. Note: Device Based collections do not support roaming. There are three types of Device Based collections, and they are very similar and only differ in their process of logging on to Windows: Automatic Login Use this collection if you want the Pano client to automatically log on to the DVMs using the same credentials throughout the collection. DVMs are automatically created from a specified template. Pano clients are assigned to specific DVMs either through the Management User Interface (MUI) or by logging on through the device for the first time. As soon as the Pano client comes up on the network and connects with the Pano Controller, the device automatically connects and logs in to the assigned DVM. The login credentials for the automatic login for Windows are identical for each and every DVM in the collection. The account can be a local account or a domain account.

Different Accounts w/ Automatic Login Use the collection if you want the Pano client to automatically log on to the DVMs using unique credentials for each login device.


A Different Accounts w/ Automatic Login collection type allows you to set up Pano devices and their corresponding DVMs to act like kiosks. This collection type is best when you wish to create a set of kiosks and want to have a unique user name and password for each DVM. Rather than displaying the Pano client login screen, the Pano device automatically connects and logs on to the associated DVM using a specified account name and password. A Different Accounts w/ Automatic Login collection type relies on a user group that has as its members the individual accounts to be used. The user group and the individual accounts must exist in the directory service; local accounts are not supported. DVMs are automatically created from a specified template. Pano clients are assigned to specific DVMs either through the Management User Interface (MUI) or by logging on through the device for the first time. As soon as the Pano client comes up on the network and connects with the Pano Controller, the device automatically connects and logs on to the assigned DVM. Upon automatically logging on to Windows, a unique account name and password will be used for each DVM in the collection. The accounts must be domain accounts and they must be members of the same security group.

Windows Login Use this collection if you only want the Pano client to connect to a DVM, but not log on to the actual DVM (i.e. display the Windows Login screen). A Windows Login collection type allows you to set up a Pano device and a corresponding DVM to act like a general purpose Windows computer. This collection type is useful if:

You require users to use biometric devices (for example, fingerprint scanner to supportfingerprint recognition) for authentication, or You have users that will always connect to a DVM from the same Pano device and desire the same look-and-feel that they experience from a Windows computer, namely a Windows Login screen as opposed to a Pano client login screen. The Pano device automatically connects to the DVM, but does not log on. The user must authenticate to Windows prior to using the DVM. You can assign Pano clients to specific DVMs either through the Management User Interface (MUI) or by logging on through the device for the first time. As soon as the Pano client is discovered on the network and communicates with the Pano Controller, the Pano client automatically connects to the assigned DVM. Users must type their credentials at the Windows login prompt (see Supported Third Party Logon Screens).

Types of Collections 15

Automated Deployment ConceptsAutomated deployment is the ability to configure Pano Controller to automatically create new desktop virtual machines by:

Cloning virtual machines using Templates. Automating Windows Sysprep process using a Customization Specification.You can automatically provision new DVMs by cloning templates. Also, by executing customization specification scripts, you can perform automated sysprep on individual DVMs generated from the template. Note: The template or virtual machine that is used as the source of the cloning should not belong to any domain. Pano Logic designed its solution to run on top of the virtualization platform like VMware vSphere and Microsoft Hyper-V. Therefore, you must integrate with the virtual management component so that the Pano System can have full control of the DVMs that are available in vCenter Server. Automated deployment lessens the resources required to quickly roll out any large size virtual desktop infrastructures. Automated deployment also allows for very flexible desktop deployment models. All collection types, except Existing Desktop, support automated deployment of virtual machines. The conditions under which new DVMs are automatically deployed are based on user demand and the values that you specify when you create the collection or update the collection. (To turn off automated deployment for a collection, uncheck the Deploy Enabled option.) Because deploying a new DVM from a template can take several minutes or more, depending on the size of the template being copied and the performance of the storage sub-system, the Pano System can automatically deploy extra DVMs but not assign them to users right away. When a new user signs into the collection, the Pano System automatically assigns that user to one of the extra DVMs, then deploys a new DVM to replenish the extra DVMs. This way, future users have quick access to a new DVM. You can specify a certain number of extra DVMs that are pre-provisioned. Within this set of extra DVMs, some can be kept powered on for instant access, while others can be powered off to reduce resource utilization, but still provide fast access. The Extra to Keep On and Extra Desktops values in the collection properties dialog determines how many extra DVMs you want the Pano Controller to maintain for the collection, and whether they should be powered on or off. Extra DVMs is the number of additional DVMs that the Pano Controller deploys so that they are quickly available for new users. These extra DVMs are in addition to any assigned or in-use DVMs. Related Topics About Provisioning on Pano System with XenDesktop on page 195

TemplatesThe Pano System connects to a client OS (Windows XP or Windows 7) on desktop virtual machines (DVMs) running on virtualization platform. A template is a VMware vCenter Server concept that refers to a base virtual machine from which you provision DVMs. Templates are key to efficient management of DVMs, and they provide the following benefits:

They save you time by enabling you to automate desktop provisioning and quickly update(manage) virtual machines. They ensure consistency and reduce the risk of human error.


In a Pano System deployment there can be one or more templates. Typically, a template is associated with a specific user type or business unit. It can be customized with specific virtual hardware configuration and installed software to conform to unique requirements and needs. Consider creating a separate template based on one of the following. Choose to create templates based on the method that makes sense for your organization.

Business unit (Finance, Sales, HR, etc). User type (Administrator, Technical Support Engineer, Software Engineer, OfficeAdministrator, etc) where each user might require. Examples of templates might include: Nurse Station Template A Nurse Station template might have 768 MBs of RAM, a single CPU, and an 8GB hard disk. Software installed on this virtual machine template can include Medical Records System client software and Scheduling software. This template is used as base to provision DVMs for nurses stations throughout the hospital. Call Center Template A Call Center template might have 384 MBs of RAM, a single CPU, and a 4GB hard disk. Software installed on this virtual machine template can include Call Answer Magic software. This template is used as base to provision DVMs for all the Call Center Agents. Financial Analyst Template A Financial Analyst template might have 1024GB of RAM, two CPUs, and a 12GB hard disk. Software installed on this virtual machine can include Microsoft Office and decision support software that requires greater processing and memory resources. Help Desk Template A Help Desk template might have 768 MBs of RAM, a single CPU, and a 12GB hard disk. Software installed on this virtual machine template can include MS Office, Helpdesk System ticket tracking and Visio. This template is used as base to provision DVMs for the Help Desk team. System Administrator Template A System Administrator template might have 768 MBs of RAM, a single CPU, and a 10GB hard disk. Software installed on this virtual machine template can include MS Office and all the companys IT system management and administration client software and tools. This template is used as base to provision DVMs for the companys IT administrators.

Virtual Desktop ManagementManage your virtual desktops as you would Windows desktops in a non-virtualized environment. In other words, you can continue to use your Windows administration best practices and tools. For example, to deploy the latest Microsoft product updates to virtual desktops running the Windows operating system use your existing Windows management tools such as Microsoft Windows Server Update Services (WSUS) and Microsoft System Center Operations Manager (SCOM). These tools work just as they would on standalone Windows computers.

ScalabilityThe Pano System provides flexible deployment options to scale from small office architectures to highly scalable, highly flexible enterprise architectures.

Virtual Desktop Management 17

Small office deployments can run a single instance of Pano Controllers can be configured in groups of up to six Pano Controllers for load balancing and client/DVM scalability. A Pano Controller Group can contain from one to six Pano Controllers. Two Pano Controllers can be used to provide Primary and Secondary redundancy. Additional auxiliary Pano Controllers can be added to support up to a total of six Pano Controllers. The Primary/Secondary pair and auxiliary Pano Controllers support up to 2,000 DVMs/clients per group. With 3rd party connection brokering, up to five Pano Controller groups can be configured to support up to highly-scalable deployments of DVMs/clients. Users can roam across Pano Controllers for flexible DVM access.

LicensingWith the Pano System 5.0 release, licensing is introduced for each Pano System. The Pano System license provides license entitlement for Pano System maintenance and upgrades. A Pano System license file (.xml) is provided through an email attachment or downloaded from the Customer Support Center, and is based on the number of installed Pano Zero Clients and the intended license entitlement period, typically 12, 24, or 36 months. Note: Your Pano System license is also available from the Pano Logic Customer Center. After the installation of a Pano System, the Pano System is automatically activated for a 30 day grace period. A warning status appears to indicate the pending license expiration. Additional messages are displayed for license validation and expiration. License expiration does not impact Pano System functionality or operation, but a valid license is required for any device and system upgrade. Pano System licensing involves license service configuration and license key installation. In most deployments, the license service host is set automatically based on the type of configuration. The license service host is set to:

A single a Pano Controller when the controller is setup. The primary Pano Controller when a failover group is configured. Pano Maestro, when a Pano Controller group is added.Note: License service configuration is only necessary if you are configuring a scalability group, multiple Pano Controllers without redundancy. If you are configuring a scalability group, then you need to manually configure the license service on the Pano Controller on which you have setup virtualization configuration. In almost all cases, this is http://localhost. License key installation is done from the License Configuration section in the Setup tab in Pano Controller or from Licenses and Usage in Pano Maestro. To activate the Pano System license key, install the Pano System license file.



3Chapter0

System Requirements

The Pano System has specific hardware and software requirements for each supported platform: Virtualization Platform Requirements Network Addressing Requirements Hardware Requirements Trial Requirements

Virtualization Platform RequirementsThe Pano System supports VMware, Microsoft, and Citrix virtualization.

Virtualization Platform Requirements 13

VMware Virtualization PlatformProduct VMware vSphere Version 5.0 Supported?

VMware vSphere

4.1 U1

Install one of the following environments for VMware: VMware ESX Server and vCenter Server VMware ESXi and vCenter Server VMware ESXi and vSphere ClientProduct ESX Release 4.1 U1 Supported?

ESXi with vCenter Server

5.0 4.1 U1

ESXi without vCenter Server

5.0

Limitations of Pano Controller without vCenter Server 4.1 U1

Limitations of Pano Controller without vCenter Server vCenter Server (Optional)Note: vCenter Server Linux Virtual Appliance is not supported.

5.0 4.1 U1

Install Microsoft Sysprep tools on your VMware vCenter Server. The Pano Controller automatically provisions DVMs. To use these features, you need Microsoft Sysprep tools. Go to (Windows XP) Install Sysprep Tools on vCenter Server on page 192.


Microsoft Virtualization PlatformProduct Microsoft Hyper-V Version Supported? Windows Server 2008 R2 Standard Windows Server 2008 R2 Enterprise Windows Server 2008 R2 Datacenter Hyper-V Server 2008 R2 Enterprise Edition 2008 R2

Microsoft System Center Virtual Machine Manager1

1. Microsoft System Center Virtual Machine Manager 2008 R2 must have SCVMM Administrator Console installed locally on the SCVMM server

Virtualization Platform Requirements 15

Citrix Virtualization PlatformProduct Version XenDesktop 5 5 XenDesktop 4 4

Citrix XenDesktop

VDI, Enterprise, or Platinum Editions

VDI, Enterprise, or Platinum Editions 4 SP1 (with or without Feature Packs) VDI, Enterprise or Platinum Editions 5.6 FP1, 5.6 Enterprise Editions

Citrix XenServer (Hypervisor)

5.6 Standard and Enterprise Editions 4.1 ESX/ESXi 4.1 and vCenter Server 4.1

VMware vSphere (Hypervisor)

XenCenter Citrix Desktop Delivery Controller (DDC) Citrix XenDesktop Controller Citrix Provisioning Services (PVS)* Machine Creation Services* XenTools Citrix Virtual Desktop Agent x86 (Windows XP and Windows 7) Citrix NetScaler (physical appliance)1 Citrix NetScaler (virtual appliance)

5.6.1 FP1 n/a 5.0 5.6 SP1 integrated version 5.6 5.0

5.6 4.0 SP1 n/a 5.6 SP1 n/a 5.6 4.0

9.2 9.2

9.0 9.2

1. Load Balancer is optional for a single XenDesktop Controller deployment. You can use a virtual appliance or a hardware appliance. For more information, go to XenDesktop FAQs. * Components marked with an '*' in this table do not directly interface with the Pano Logic system. Such components are listed here to indicate which versions Pano Logic tested with and are expected to interoperate with other components. Pano Logic does not assume responsibility for such components because they do not interact directly with the Pano System.


VMware ViewProduct VMware View Version 5.0 Supported?

VMware View VMware View

4.6 4.5

Related Topics Choose Your VMware Virtualization Infrastructure on page 114 (Overview) Integrate Pano Controller into Your VMware Environment on page 120 (Overview) Integrate Pano System with VMware View on page 414 Limitations of VMware View Manager on page 43 (Overview) Integrate Pano Controller into Your VMware Environment on page 120 (Overview) Integrate Pano Controller into Your XenDesktop Environment on page 152

Network Addressing RequirementsThe Pano System relies on IPv4 for network addressing. If both IPv4 and IPv6 are enabled on a DVM, which is the Windows 7 default, the Pano Controller communicates via IPv4 despite IPv6 being active. You do not need to disable IPv6 on the DVM or on the server thats running your virtualization platform as long as IPv4 is enabled; in fact, disabling IPv6 can increase DVM performance. However, if IPv4 is disabled, the Pano Controller cannot communicate with the DVM. In this case:

the Pano Direct Status column indicates Unreachable. the IP Address column shows the IPv6 address.To ensure that your users do not disable IPv4, consider setting up a GPO policy to enable IPv4.

Network Addressing Requirements 17

Hardware Requirements VMware Trial Requirements Microsoft Trial Requirements Citrix XenServer Trial RequirementsFor additional tools, browse the following resources:Resource Pano Logic Solution Brief: Virtual Desktop Infrastructure Sizing Deployment Architecture Overview Redbook Remote Deployment Redbook Pano on Citrix XenDesktop Redbook Pano on VMware View Redbook Pano Logic Total Cost of Ownership Calculator

Hardware and Resource Requirements for VMware vSphereThe hardware and software resources required to support your environment depend on your: Workload requirements Operating system to be used (Windows XP or Windows 7) Network topology Number of virtual desktops that you intend to run in your environment In addition to provisioning for virtual desktops, you need to consider the reso

Documents

AdminGuidev5.0