7.0
Table Of Contents
- View Integration
- Contents
- View Integration
- Introduction to View Integration
- Integrating View with the Event Database
- Using View PowerCLI
- Getting Started with View PowerCLI
- View Administrator, PowerCLI Cmdlets, and View Command-Line Interfaces Compared
- View PowerCLI cmdlet Reference
- View PowerCLI cmdlet Parameters
- Examples of Using View PowerCLI cmdlets
- Managing View Connection Server Instances
- Managing vCenter Server Instances 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 and Updating Manual Unmanaged Desktop Pools
- Displaying Information About Users and Groups
- Managing Desktop Entitlements
- Managing Remote Sessions
- Managing Virtual Machines
- Displaying Information About Physical Machines
- Updating Virtual Machine Ownership
- Displaying Event Reports
- Displaying and Updating Global Settings
- Displaying and Adding License Keys
- Examples of Using View PowerCLI to Perform Advanced Tasks
- Assigning Multiple Network Labels to a Desktop Pool
- Network Label Configuration File Format
- Example Network Label Configuration File
- Obtain and Export NIC and Network Label Information
- Verify and Edit a Network Label Configuration File
- Deploy a Desktop Pool That Uses Multiple Network Labels
- Displaying Network Label Assignments for a Pool
- Displaying Network Label Assignments for a Virtual Machine
- Displaying vCenter Server Network Label Assignments for a Virtual Machine
- Disable Automatic Network Label Assignments
- Customizing LDAP Data
- Integrating View with Microsoft SCOM
- Setting Up a SCOM Integration
- Assign a Name to the View Connection Server Group
- View Management Packs
- Import the View Management Packs on the SCOM Server
- Enable a Proxy Agent on a View Connection Server Host or Security Server
- Run the Discovery Script in the Operations Manager Console
- View Connection Server and Security Server Managed Objects
- View Object Classes and Relationships
- Monitoring View in the Operations Manager Console
- Setting Up a SCOM Integration
- Examining PCoIP Session Statistics with WMI
- Setting Desktop Policies with Start Session Scripts
- Index
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. A start session
script can enable mapped drives, clipboard redirection, and other desktop features for a user who has an IP
address in your organization’s internal domain, but disallow these features for a user who has an IP address
in an external domain.
This chapter includes the following topics:
n
“Obtaining Input Data for a Start Session Script,” on page 83
n
“Best Practices for Using Start Session Scripts,” on page 83
n
“Preparing a View Desktop to Use a Start Session Script,” on page 84
n
“Sample Start Session Scripts,” on page 86
Obtaining Input Data for a Start Session Script
Start session scripts cannot run interactively. A start session script runs in an environment created by View
and must obtain its input data from that environment.
Start session scripts gather input data from environment variables on the client computer. Start session
environment variables have the prefix VDM_StartSession_. For example, the start session environment
variable that contains the client system’s IP address is VDM_StartSession_IP_Address. You must ensure that
a start session script validates the existence of any environment variable that it uses.
For a list of variables similar to start session environment variables, see “Client System Information Sent to
View Desktops” in the Setting Up Desktop and Application Pools in View document.
Best Practices for Using Start Session Scripts
Follow these best practices when using start session scripts.
When to Use Start Session Scripts
Use start session scripts only if you need to configure desktop policies before a session starts.
As a best practice, use the Horizon Agent CommandsToRunOnConnect and CommandsToRunOnReconnect group
policy settings to run command scripts after a desktop session is connected or reconnected. Running scripts
within a desktop session, rather than using start session scripts, satisfies most use cases.
For more information, see “Running Commands on View Desktops” in the Setting Up Desktop and
Application Pools in View document.
VMware, Inc.
83