View Integration VMware Horizon 7 Version 7.0 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
View Integration You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2016 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc.
Contents View Integration 5 1 Introduction to View Integration 7 View Components 7 Integration Interfaces to View 8 2 Integrating View with the Event Database 9 Event Database Tables and Schemas 9 Connection Broker Events 11 Horizon Agent Events 16 View Administrator Events 17 Event Message Attributes 24 Sample Database Queries and Views 25 3 Using View PowerCLI 27 Getting Started with View PowerCLI 27 View Administrator, PowerCLI Cmdlets, and View Command-Line Interfaces Compared 30 View PowerCLI cm
View Integration 7 Setting Desktop Policies with Start Session Scripts 83 Obtaining Input Data for a Start Session Script 83 Best Practices for Using Start Session Scripts 83 Preparing a View Desktop to Use a Start Session Script 84 Sample Start Session Scripts 86 Index 4 89 VMware, Inc.
View Integration The View Integration document describes how to integrate View™ software with third-party software such as Windows PowerShell, business intelligence reporting engines, and Microsoft System Center Operations Manager (SCOM). Intended Audience This document is intended for anyone who wants to customize or integrate software to work with View.
View Integration 6 VMware, Inc.
Introduction to View Integration 1 With View, system administrators can provision desktops and control user access to these desktops. Client software connects users to virtual machines running in VMware vSphere™, or to physical systems running within your network environment. In addition, View administrators can configure Remote Desktop Services (RDS) hosts to provide View desktop and application sessions to client devices.
View Integration vCenter Server A server that acts as a central administrator for ESX/ESXi hosts that are connected on a network. A vCenter Server instance provides the central point for configuring, provisioning, and managing virtual machines in the datacenter. View Composer A software service that is installed on a vCenter Server instance to enable View to rapidly deploy multiple linked-clone desktops from a single centralized base image.
Integrating View with the Event Database 2 You can configure View to record events to a Microsoft SQL Server or Oracle database. View records events such as end-user actions, administrator actions, alerts that report system failures and errors, and statistical sampling. End-user actions include logging and starting desktop and application sessions. Administrator actions include adding entitlements and creating desktop and application pools.
View Integration View records details about events to all the database tables. After a certain period of time has elapsed since writing an event record, View deletes the record from the event and event_data tables. You can use View Administrator to configure the time period for which the database keeps a record in the event and event_data tables. IMPORTANT View does not restrict the growth of the event_historical and event_data_historical tables.
Chapter 2 Integrating View with the Event Database Table 2‑2. Schema for the event and event_historical Tables (Continued) Column Name Oracle Data Type SQL Server Data Type Description ThinAppId NVARCHAR2(512) nvarchar(512) ID of the associated ThinApp™ object. Time TIMESTAMP datetime Time at which the event occurred, measured from the epoch (January 1, 1970). UserDiskPathId NVARCHAR2(512) nvarchar(512) ID of the user disk.
View Integration Table 2‑4.
Chapter 2 Integrating View with the Event Database Table 2‑4.
View Integration Table 2‑4.
Chapter 2 Integrating View with the Event Database Table 2‑4.
View Integration Table 2‑4.
Chapter 2 Integrating View with the Event Database View Administrator Events View Administrator events report information about actions that users initiate in View Administrator. Table 2‑6.
View Integration Table 2‑6.
Chapter 2 Integrating View with the Event Database Table 2‑6.
View Integration Table 2‑6.
Chapter 2 Integrating View with the Event Database Table 2‑6.
View Integration Table 2‑6.
Chapter 2 Integrating View with the Event Database Table 2‑6.
View Integration Event Message Attributes ModuleAndEventText messages use certain attributes. To determine the data type for an attribute, you can examine its value in the type column in the event_data or event_data_historical table. Table 2‑7. Attributes that ModuleAndEventText Messages Use 24 Attribute Name Description AdminFolderName Name of a folder that requries privileged access. AdminPermissionEntity Name of an object that requires privileged access.
Chapter 2 Integrating View with the Event Database Table 2‑7. Attributes that ModuleAndEventText Messages Use (Continued) Attribute Name Description ThinAppRepositoryName Name of a ThinApp repository ThinAppRepositoryPath Path of a ThinApp repository. Time Date and time value. UserCount Maximum number of desktop users over a 24-hour period. UserDiskName Name of a user data disk. UserDisplayName User name in the form DOMAIN\username. UserName Name of a user in Active Directory.
View Integration The following query lists all recent events where the agent on a machine shut down. CREATE VIEW agent_shutdown_events AS ( SELECT ev.EventID, ev.Time, ed.StrValue FROM dbo.VE_event_historical AS ev, dbo.VE_event_data_historical AS ed WHERE ev.EventID = ed.EventID AND ev.EventType = ‘AGENT_SHUTDOWN’ AND ed.Name = ‘MachineName’ ); The following query lists all recent events where a desktop failed to launch because the desktop pool was empty.
Using View PowerCLI 3 View PowerCLI provides an easy-to-use PowerShell interface to View. You can use View PowerCLI cmdlets to perform various administration tasks on View components.
View Integration Start the PowerShell Console with View PowerCLI Loaded You can run the View PowerCLI cmdlets directly on a View Connection Server host. Prerequisites Verify that the View Connection Server host has the following software installed. n View 4.5 or later n Microsoft .NET framework n Windows PowerShell 1.0 Procedure 1 Log in to the View Connection Server instance as a user in a role that has sufficient privileges to modify configuration data.
Chapter 3 Using View PowerCLI 2 Display the View PowerCLI help. Option Action List all View PowerCLI cmdlets Run the Get-Command cmdlet. For example: Get-Command -PSSnapin VMware.View.Broker | more Display help for a specific cmdlet Type Get-Help followed by the name of the cmdlet. For example: Get-Help Add-ViewVC | more Display detailed help for a specific cmdlet Type Get-Help followed by the name of the cmdlet and the -full parameter.
View Integration Table 3‑2.
Chapter 3 Using View PowerCLI Table 3‑3.
View Integration Table 3‑3.
Chapter 3 Using View PowerCLI Table 3‑3.
View Integration Table 3‑3.
Chapter 3 Using View PowerCLI Table 3‑4. View PowerCLI cmdlets (Continued) Object cmdlet Description Send-LinkedCloneRefresh Refreshes the operating system disks of linked-clone desktops to their original state and size. ExportNetworkLabelSpecForLinkedClone Lists the shared network labels on all the hosts in a specified cluster on which a linkedclone desktop pool is to be deployed. The output is exported to a configuration file.
View Integration Table 3‑4. View PowerCLI cmdlets (Continued) Object cmdlet Description Remote session Get-RemoteSession Returns information about active remote sessions. Send-SessionDisconnect Disconnects an active remote session. Send-SessionLogoff Logs out an active remote session. Get-User Returns information about users. Remove-UserOwnership Removes the ownership of a virtual machine. Update-UserOwnership Assigns a user (specified as a SID) to a virtual machine.
Chapter 3 Using View PowerCLI Flash Quality Parameter The -flashQuality parameter specifies the maximum allowable quality for Adobe Flash content. This value overrides the setting on a Web page. If the Adobe Flash quality for a Web page is higher than the maximum value allowed, the client reduces the quality to the specified maximum. Lowering the quality of Adobe Flash content causes the content to use less bandwidth. Table 3‑7.
View Integration Pool Type Parameter The -poolType parameter specifies the desktop pool type. Table 3‑10. -poolType Parameter Settings Setting Description IndividualUnmanaged The pool contains an individual unmanaged machine. IndividualVC The pool contains an individual machine that is managed and configured by a vCenter Server instance. Manual The pool contains manually configured floating (nonpersistent) machines that are managed and configured by a vCenter Server instance.
Chapter 3 Using View PowerCLI Table 3‑11. -powerPolicy Settings Setting Description AlwaysOn Configure the machine to remain powered on, even when no one is using it. If you shut down the machine, the machine restarts immediately. RemainOn Start the machine when required if the machine is powered down. The machine remains powered on until you shut it down. PowerOff Shut down the machine when no one is using it. Suspend Suspend the machine when no one is using it.
View Integration Table 3‑14. -composerTask Parameter Settings (Continued) Setting Description mkChkPoint Create a checkpoint snapshot. rebalance Rebalance a linked clone machine. replaceUdd Replace a persistent disk. resync Recompose a linked clone machine. Examples of Using View PowerCLI cmdlets With View PowerCLI cmdlets, you can perform View management tasks from the command line or from scripts instead of using View Administrator.
Chapter 3 Using View PowerCLI Table 3‑16. Examples of Common vCenter Server Management Tasks in View (Continued) Task Example View PowerCLI cmdlet Syntax Change the create ramp factor value for all vCenter Server instances in a specific DNS domain Get-ViewVC -serverName *.mycorp.com | Update-ViewVC createRampFactor 5 Remove a vCenter Server instance from the View configuration Get-ViewVC -serverName vc02.mydom.
View Integration Because the datastores specified in the -datastorePaths parameter override the previous setting, you must specify any existing datastores in the parameter for the desktop pool to continue to use those datastores. Creating and Updating Linked-Clone Desktop Pools You can use the Get-ViewVC and Get-DesktopVM cmdlets to create and update linked-clone desktop pools. In the following example, the Get-ViewVC cmdlet adds a linked-cloned desktop pool named lcdpool_1.
Chapter 3 Using View PowerCLI Creating and Updating Manually Provisioned Desktop Pools You can use the Add-ManualPool, Get-ViewVC, and Update-ManualPool cmdlets to create and update manually provisioned desktop pools. In the following example, the Add-ManualPool cmdlet creates a manually provisioned desktop pool named manPool that contains a virtual machine named myVM. Add-ManualPool -pool_id manPool -id (Get-VM -name "myVM").
View Integration Managing Desktop Entitlements You can use View PowerCLI cmdlets to manage desktop entitlements. Table 3‑19. Examples of Common Desktop Entitlement Management Tasks Task Example View PowerCLI cmdlet Syntax Entitle a user in a specific domain to a specific desktop pool Get-User -name "mydom\fred" | Add-PoolEntitlement -pool_id dtop-12 Entitle a user to all desktop pools Get-Pool | Add-PoolEntitlement -sid (Get-User -name "usr1").
Chapter 3 Using View PowerCLI Table 3‑21. Examples of Common Virtual Machine Management Tasks (Continued) Task Example View PowerCLI cmdlet Syntax Get information about the virtual machines managed by the same vCenter Server instance that provisions a specific desktop pool Get-ViewVC -pool_id dtpool-1 | Get-DesktopVM Get information about all the virtual machines managed by a specific vCenter Server instance Get-ViewVC -serverName vc01.mydom.
View Integration Table 3‑22. Examples of Common Event Reporting Tasks (Continued) Task Example View PowerCLI cmdlet Syntax Display all the user events that occurred during for the last 24 hours Get-EventReport -viewName user_events -startDate ((GetDate).
Chapter 3 Using View PowerCLI Write-Warning "Connection Broker service is stopped, attempting to start." $errCountBefore = $error.Count Start-Service wsbroker $errCountAfter = $error.Count if($errorCountAfter -gt $errorCountBefore){ break } } else { Write-Error "Connection Broker service is stopped." break } } while(!$started){ # Loop until service has completed starting up. Write-Warning "Waiting for View Connection Server to start." $errCountBefore = $error.
View Integration # Retrieve all pool objects and check each one individually $pools = Get-Pool foreach ($pool in $pools){ PollPoolUsage $pool $increment } } # # # # PollPoolUsage Parameters $Pool Pool object that represents the pool to be checked. $increment Amount by which to increase pool that is at maximum capacity. function PollPoolUsage { param ($Pool, $increment) # Get a list of remote sessions for the pool (errors are suppressed) $remotes = Get-RemoteSession -pool_id $Pool.
Chapter 3 Using View PowerCLI Determining Paths to vSphere Inventory Objects The following PowerShell function uses vSphere PowerCLI to return the full path to a vSphere inventory object. # # # # # # # VVGetInventoryPath Parameters $InvObject Inventory object in vSphere PowerCLI. Examples VVGetInventoryPath (Get-VM -name myVM) VVGetInventoryPath (Get-ResourcePool | Select -first 1) function VVGetPath($InvObject){ if($InvObject){ $objectType = $InvObject.GetType().Name $objectBaseType = $InvObject.
View Integration Determining Paths to vSphere Datastore Objects The following PowerShell function uses vSphere PowerCLI to return the full path to a datastore in a cluster as specified by a resource pool. # VVGetDatastorePath # Parameters # $Datastore Datastore object in vSphere PowerCLI. # $ResourcePool Resource pool in cluster.
Chapter 3 Using View PowerCLI function RemoveDatastoreFromAutomaticPool { param ($Pool, $Datastore) $PoolSettings = (Get-Pool -pool_id $Pool) $currentdatastores = $PoolSettings.datastorePaths $datastores = "" foreach ($path in $currentdatastores.split(";")){ if(-not ($path -eq $Datastore)){ $datastores = $datastores + "$path;" } } Update-AutomaticPool -pool_id $Pool -datastorePaths $datastores } The PowerShell functions in the following example add and remove a datastore for a linked-clone pool.
View Integration Assigning Multiple Network Labels to a Desktop Pool In View 5.2 and later releases, you can configure automated full-clone and linked-clone desktop pools to use multiple network labels. This feature expands the number of IP addresses you can assign to the virtual machines in a pool, making it easier to create pools that have a large number of desktops.
Chapter 3 Using View PowerCLI As a best practice, do not assign a network label to more than one desktop pool. The maximum network label counts are honored only on a per-NIC, per-pool basis.
View Integration ####nic1.network03.maxvm=244 ####nic1.network04.maxvm=244 ####nic1.network05.maxvm=244 ####nic1.network06.maxvm=244 ####nic1.network07.maxvm=244 ####nic1.network08.maxvm=244 ####nic1.network09.maxvm=244 ####nic1.network10.maxvm=244 ####nic2.network01.maxvm=244 ####nic2.network02.maxvm=244 ####nic2.network03.maxvm=244 ####nic2.network04.maxvm=244 ####nic2.network05.maxvm=244 ####nic2.network06.maxvm=244 ####nic2.network07.maxvm=244 ####nic2.network08.maxvm=244 ####nic2.network09.
Chapter 3 Using View PowerCLI The network label cmdlet obtains the network labels configured in vCenter Server for all the ESXi hosts in the specified cluster, sets the maximum number of virtual machines that can be provisioned with IP addresses from each network label, and exports the list of NICs and network labels to the network label configuration file.
View Integration ... ####nic1.network01.maxvm=244 ####nic1.network02.maxvm=244 ####nic1.network03.maxvm=244 ####nic1.network04.maxvm=244 ####nic1.network05.maxvm=244 nic1.network06.maxvm=244 nic1.network07.maxvm=244 ####nic1.network08.maxvm=244 ####nic1.network09.maxvm=244 ####nic1.network10.maxvm=244 ####nic2.network01.maxvm=244 ####nic2.network02.maxvm=244 ####nic2.network03.maxvm=244 ####nic2.network04.maxvm=244 ####nic2.network05.maxvm=244 ####nic2.network06.maxvm=244 ####nic2.network07.maxvm=244 nic2.
Chapter 3 Using View PowerCLI Example: Linked-Clone Desktop Pool Deployment In this example, the Add-AutomaticLinkedClonePool cmdlet creates a linked-clone pool named POOL_NAME and assigns the network labels in the network label configuration file named label.txt file.
View Integration Displaying Network Label Assignments for a Pool You can use the Get-Pool cmdlet to display the network label assignments for a pool. The networkLabelSpecs output parameter shows the network labels that are assigned to the pool. You do not need to add a parameter in the command line to display this information. The following table describes the networkLabelSpecs output format. Table 3‑24. networkLabelSpecs Output Format Value Description nl Network label name. nic NIC name.
Chapter 3 Using View PowerCLI The following Get-DesktopVM cmdlet example displays network label assignments for the virtual machine 918 in the pool pool2. > get-desktopvm -pool_id pool2 ... vm : 918 ps_object_type : vc_vm id : VirtualMachine-vm-47878 vc_id : 2162aa44-e99c-4f1a-875d-dd295681d2ca Name : pool2-1811 UnescapedName : pool2-1811 Path : /resource/vm/Discovered virtual machine/pool2/pool2-1811 GuestFullName : Microsoft Windows 7 (32-bit) GuestID : windows7Guest HostName : POOL2-1811.vdi3.
View Integration pool_id : pool2 isLinkedClone : true composerTask : netLabelAutoAssigns : {Network adapter 1=desktop-auto01-230} ... NOTE Because the -getNetworkLabel parameter is a long-running parameter, run the Get-DesktopVM cmdlet with the -getNetworkLabel parameter during off-peak periods of vSphere utilization. Disable Automatic Network Label Assignments You can disable network label assignments on an existing pool that uses automatic assignments.
Customizing LDAP Data 4 You can use VMware and Microsoft command-line tools to import and export LDAP configuration data to and from View. These command-line tools import and export LDAP configuration data in LDAP Data Interchange Format (LDIF) configuration files. This feature is intended for use by advanced administrators who want to perform automatic bulk configuration operations. To create scripts to update the View configuration, use View PowerCLI.
View Integration Modifying LDAP Configuration Data You can export LDAP configuration data on a View Connection Server instance to an LDIF configuration file, modify the LDIF configuration file, and import the modified LDIF configuration file into other View Connection Server instances to perform automatic bulk configuration operations. You can obtain examples of LDIF syntax for any item of LDAP configuration data in View by examining the contents of an exported LDIF configuration file.
Chapter 4 Customizing LDAP Data You associate each VM Pool entry with one Desktop Application entry in a one-to-one relationship. A Desktop Application entry cannot be shared between VM Pool entries, and a VM Pool entry can only be associated with one Desktop Application entry. The following table describes the attributes you must specify when you modify a desktop pool definition in an LDIF configuration file. Table 4‑1.
View Integration pae-VmPath: /New Datacenter/vm/vm-1 pae-OptSuspendTimeout: 0 pae-OptDisconnectLimitTimeout: 0 pae-OptMaximumSessions: 0 pae-Disabled: 0 # # Virtual Desktop VM entry VM2 # DN: CN=vm2,OU=Servers,DC=vdi,DC=vmware,DC=int changetype: add objectClass: top objectClass: pae-Server objectClass: pae-WinServer objectClass: pae-ThinWinServer objectClass: pae-VM cn: vm2 description: sample virtual desktop entry pae-VmSuspended:: IA== pae-OptIgnoreProcessList: 0 pae-MOID: vm-2 pae-VmState: READY pae-Ser
Chapter 4 Customizing LDAP Data pae-VmStartClone: 1 pae-VmPoolCalculatedValues: 1 pae-ServerPoolType: 0 pae-VmMinimumCount: 0 pae-VmHeadroomCount: 0 pae-VmMaximumCount: 0 pae-Disabled: 0 # # Desktop Application entry Pool1 -- one entry is required for each VM Pool # DN: CN=Pool1,OU=Applications,DC=vdi,DC=vmware,DC=int changetype: add objectClass: top objectClass: pae-Entity objectClass: pae-App objectClass: pae-WinApp objectClass: pae-ThinWinApp objectClass: pae-DesktopApplication cn: Pool1 member:: PFNJRD
View Integration 2 At the command prompt, type the vdmimport command and use the -f option to specify the LDIF configuration file to import. For example: vdmimport -f myexport.LDF After the vdmimport command runs, the configuration of your View Connection Server instance is updated with the data from the file, and the number of records that have been successfully updated is displayed. Errors are displayed if some records could not be updated because your role has insufficient privileges.
Integrating View with Microsoft SCOM 5 You can use Microsoft System Center Operations Manager (SCOM) to monitor the state of View components, including View Connection Server instances, security servers, and the View services that run on View Connection Server and security server hosts.
View Integration What to do next Complete the procedure described in “Import the View Management Packs on the SCOM Server,” on page 68. View Management Packs View management packs enable you to use SCOM to monitor and manage the state of View components. Table 5‑1. View Management Packs View Management Pack Description VMware.View.Discovery.mp Contains the agent that discovers instances of View Server installations. VMware.View.Monitoring.
Chapter 5 Integrating View with Microsoft SCOM Enable a Proxy Agent on a View Connection Server Host or Security Server You must use the Operations Manager console to enable a proxy agent on each View Connection Server host or security server that you want to monitor with SCOM. The discovery script can discover a Windows server only if you enable the proxy agent for the server. Prerequisites Complete the procedure described in “Import the View Management Packs on the SCOM Server,” on page 68.
View Integration View Connection Server and Security Server Managed Objects The discovery script discovers managed objects for View Connection Server instances and security servers. Table 5‑2. Managed Objects for View Connection Server Instances and Security Servers Object View Connection Server Instance Security Server VMware.View.Cluster X X VMware.View.Cluster.Node.Item X X VMware.View.ConnectionServerRole.Item X X VMware.View.Component.ConnectionServer.Item X X VMware.View.Component.
Chapter 5 Integrating View with Microsoft SCOM Table 5‑4. View Library Base Classes Class Name Description VMware.View.Cluster.Node Represents a member of a View Connection Server group. This class has the properties ClusterID, ClusterName, ProductVersion, and InstallPath. VMware.View.Component Represents a View component that has been installed on a member of a View Connection Server group. This class has the property Name. VMware.View.Component.
View Integration Table 5‑5. View Library Concrete Classes (Continued) Class Name Description VMware.View.Component.Directory.Item Represents version 5.1.x or a later release of the Directory component that has been installed on a member of a View Connection Server group. This class inherits its properties from VMware.View.Component.Directory. VMware.View.Component.Framework.Item Represents version 5.1.
Chapter 5 Integrating View with Microsoft SCOM Table 5‑6. Available Views for View Objects (Continued) View Description Groups Displays a diagram of all discovered View Connection Server groups, members, roles, and components. You can obtain details about objects and their relationships by clicking the icons and the connectors. Connection Server Role Performance Data Displays the following data sets.
View Integration Table 5‑7. View Service Component Monitors for a View Connection Server Instance (Continued) Monitor Display Name Monitored Service SecureGatewayCheck Security Gateway Service Health VMware View Security Gateway Component WebServiceCheck Web Service Health VMware View Web Component DirectoryServiceCheck Directory Service Health VMwareVDMDS Service Component Monitors for Security Servers The following table describes the service component monitors that the VMware.View.
Chapter 5 Integrating View with Microsoft SCOM Display Alerts for a View Connection Server Group You can use the Health Explorer in the Operations Manager console to display information about alerts that the health monitors raise for a View Connection Server group. Prerequisites Integrate View with SCOM. See “Setting Up a SCOM Integration,” on page 67. Procedure 1 In the Operations Manager console, go to Monitoring\VMware View and select the Active Alerts view.
View Integration Procedure 1 In the Operations Manager console, go to Monitoring\VMware View and select the Group State view or the Group Node State view. 2 Right-click the View Connection Server instance and select Open > Health Explorer. 3 Right-click the Domain Connectivity Health entry for the View Connection Server instance in the Health Explorer and select Monitor Properties. 4 On the Overrides tab, click Override and select the option for all objects of the same class.
Examining PCoIP Session Statistics with WMI 6 You can use Windows Management Instrumentation (WMI) to examine performance statistics for a PCoIP session by using any of the supported programming interfaces, including C#, C++, PowerShell, VBScript, VB .NET, and Windows Management Instrumentation Command-line (WMIC). You can also use the Microsoft WMI Code Creator tool to generate VBScript, C#, and VB .NET code that accesses the PCoIP performance counters.
View Integration General PCoIP Session Statistics The WMI class name for PCoIP general session statistics is Win32_PerfRawData_TeradiciPerf_PCoIPSessionGeneralStatistics. Table 6‑1. General Session Statistics WMI Property Name Description BytesReceived Total number of bytes of PCoIP data that have been received since the PCoIP session started. BytesSent Total number of bytes of PCoIP data that have been transmitted since the PCoIP session started.
Chapter 6 Examining PCoIP Session Statistics with WMI Table 6‑2. PCoIP Audio Statistics WMI Property Name Description AudioBytesReceived Total number of bytes of audio data that have been received since the PCoIP session started. AudioBytesSent Total number of bytes of audio data that have been sent since the PCoIP session started. AudioRXBWkbitPersec Bandwidth for ingoing audio packets averaged over the sampling period, in seconds.
View Integration Calculating Bandwidth for Received Imaging Data To calculate the bandwidth in kilobits per second for received imaging data over the time interval from time t1 to time t2, use the following formula. (ImagingBytesReceived[t2]-ImagingBytesReceived[t1]) * 8 / (1024 * (t2-t1)) Do not use ImagingRXBWkbitPersec for the calculation.
Chapter 6 Examining PCoIP Session Statistics with WMI Calculating Bandwidth for Transmitted Network Data To calculate the bandwidth in kilobits per second for transmitted data over the time interval from time t1 to time t2, use the following formula. (BytesSent[t2]-BytesSent[t1]) * 8 / (1024 * (t2-t1)) Do not use TXBWkbitPersec for the calculation.
View Integration Calculating Bandwidth for Received USB Data To calculate the bandwidth in kilobits per second for received USB data over the time interval from time t1 to time t2, use the following formula. (USBBytesReceived[t2]-USBBytesReceived[t1]) * 8 / (1024 * (t2-t1)) Do not use USBRXBWkbitPersec for the calculation.
Setting Desktop Policies with Start Session Scripts 7 With start session scripts, you can configure specific View desktop settings before a desktop session starts based on information received from Horizon Client and View Connection Server. For example, you can use a start session script to configure desktop policies based on client device and user location instead of setting up multiple desktop pools that have different desktop policies.
View Integration Managing Start Session Timeouts Make sure your start session scripts run quickly. If you set the WaitScriptsOnStartSession value in the Windows registry, your start session script must finish running before Horizon Agent can respond to the StartSession message that View Connection Server sends. A long-running script is likely to cause the StartSession request to time out.
Chapter 7 Setting Desktop Policies with Start Session Scripts Add Windows Registry Entries for a Start Session Script You must add Windows registry entries on each View desktop virtual machine where you want View to run a start session script. Prerequisites n Verify that the path where you configured your start session scripts is accessible only to the SYSTEM account and local administrators. For more information, see “Making Start Session Scripts Accessible,” on page 84.
View Integration e In the Value data text box, type 1 to enable start session scripting and click OK. You can type 0 to disable this feature. The default value is 0. f (Optional) To delay the StartSession response by Horizon Agent, add a second DWORD value to the Configuration key called WaitScriptsOnStartSession. A WaitScriptsOnStartSession data value of 1 causes Horizon Agent to delay sending a StartSession response and fail if the scripts do not complete.
Chapter 7 Setting Desktop Policies with Start Session Scripts outFile.WriteLine(strEnv) Next outFile.Close The following sample script tests the timeout functionality. Option Explicit WScript.Sleep 60000 The following sample script tests a non-zero exit code. Option Explicit WScript.Quit 2 VMware, Inc.
View Integration 88 VMware, Inc.
Index A Active Directory users and groups 43 advanced PowerShell commands 46 alerts 75 assigning a name 67 automatically provisioned desktop pools 41 C components 7 connection broker events 11 connectivity monitoring 75 D database queries and views 25 database tables and schemas 9 datastore management 50 desktop entitlements 44 desktop policies 83 desktop pool management tasks 41 disabling network label assignments 60 discovery script 69 displaying discovered objects 74 E error handling 29 escaping char
View Integration remote systems 28 resizing pools 47 S SCOM integration 67 start session scripts 83, 84, 86 starting PowerShell 28 V vCenter Server management tasks 40 vCenter Server network label assignments 59 View Administrator events 17 View component services 75 View Connection Server management 40 View Connection Server service 46 View PowerCLI cmdlets 27, 34, 36 View PowerCLI comparison 30 View PowerCLI cmdlet examples 40 View PowerCLI help 28 views and monitors for View 72 virtual machine managem
