Integration
Table Of Contents
- View Integration
- Contents
- Introduction
- Integrating with the Event Database
- Using View PowerCLI
- Introduction to View PowerCLI
- View PowerCLI Cmdlets
- View Administrator, View PowerCLI Cmdlet, and vdmadmin Operations
- View PowerCLI Cmdlet Parameters
- Examples of Using View PowerCLI Cmdlets
- Displaying Information About a View Connection Server Instance
- Updating the Configuration of a View Connection Server Instance
- Managing the Configuration of vCenter Servers in View
- Managing Desktop Pools
- Creating and Updating Automatically Provisioned Desktop Pools
- Creating and Updating Linked-Clone Desktop Pools
- Creating and Updating Manually Provisioned Desktop Pools
- Creating Manual Unmanaged Desktop Pools
- Creating and Updating Desktops Provisioned by RDS Hosts
- Obtaining Information About Users and Groups from Active Directory
- Managing Desktop Entitlements
- Managing Remote Sessions
- Managing Virtual Machines
- Displaying Information About Physical Computers
- Updating the Ownership of Machines
- Displaying Information About Events
- Managing the Global Configuration of View
- Managing View Licenses
- Examples of Using View PowerCLI for Enhanced Functionality
- Assign Multiple Network Labels to a Desktop Pool
- Customizing LDAP Data
- Integrating with SCOM
- View Management Packs
- Name a View Connection Server Group
- Import the View MPs
- View Discovery Script
- Run the Discovery Script
- Display Discovered Objects
- Display Managed Objects
- Views and Monitors
- Enable a Proxy Agent on a Server
- Display Performance Data
- Display Information About an Alert
- Restart a Service
- Exclude a Domain from Connectivity Monitoring
- Close Alerts
- Class and Relationship Definitions
- Examining PCoIP Session Statistics
- Dynamically Setting Desktop Policies with Start Session Scripts
- Index
VMware, Inc. 81
7
When a user connects or reconnects to a View desktop, you might want to dynamically configure particular
View desktop settings before the desktop session starts, according to information recieved from Horizon
Client and View Connection Server. For example, you might want to set different policies for clipboard
redirect, mapped drives, or other desktop features, depending on the location of the user’s client system.
Using information from Horizon Client, such as the client system’s IP address, and information from View
Connection Server, such as the DNS name of the View Connection Server instance, you can set up scripts that
determine the View desktop experience when a user requests a desktop connection. For example, a script
might allow mapped drives, clipboard redirection, and so on, for a user with an IP address in your
organization’s internal domain , but disallow these features for an IP address that comes from an external
domain.
Using start session scripts lets you dynamically configure desktop policies based on the client device and the
user’s location without having to set up multiple desktop pools. You can enforce your organization’s security
policies without the storage and licensing costs of adding pools to your deployment.
N
OTE Use start session scripts only if you have a particular need to configure desktop policies before a
desktop session begins. As a best practice, use the View Agent CommandsToRunOnConnect and
CommandsToRunOnReconnect group policy settings to run command scripts after a desktop session is
connected or reconnected. Running scripts within a desktop sesion will satisfy most use cases. For details, see
“Running Commands on View Desktops” in the View Administration document.
This chapter discusses the following topics:
“Overview of Configuring Start Session Scripts” on page 81
“Example Start Session Scripts” on page 82
“Enable the VMware View Script Host Service” on page 83
“Add Windows Registry Entries for a Start Session Script” on page 83
Overview of Configuring Start Session Scripts
To enable a start session script, you perform the following tasks on the View desktop:
Enable the VMware View Script Host service
(Optional) Configure the account of the user who has the appropriate privileges to run the script
Add entries in the Windows registry to enable the script
You must configure all View desktops that need to run start session scripts. There is no mechanism to
propagate registry changes, VMware View Script Host service configuration changes, and start session scripts
to multiple View desktop virtual machines.
Dynamically Setting Desktop Policies
with Start Session Scripts
7