Integration
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, View PowerCLI, and vdmadmin 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
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 View 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.
If a timeout occurs and the pool uses floating assignments, View Connection Server tries to connect the user
to another virtual machine. If a timeout occurs and no virtual machine is available, View Connection Server
rejects the user's connection request.
As a best practice, set a hard timeout for the script host operation so that a specific error can be returned if a
script runs too long.
Making Start Session Scripts Accessible
The path where you configure your start session scripts must be accessible only to the SYSTEM account and
to local administrators. Set the ACL for the base key to be accessible to these accounts only.
As a best practice, place start session scripts in the View_Agent_install_path\scripts directory, for example:
%ProgramFiles%\VMware\VMware View\Agent\scripts\sample.vbs
By default, this directory is accessible only by the SYSTEM and administrator accounts.
Preparing a View Desktop to Use a Start Session Script
To prepare a View desktop to use a start session script, you must enable the VMware View Script Host
service and add entries in the Windows registry.
You must configure all View desktops that need to run start session scripts. View does not provide a
mechanism to propagate registry changes, VMware View Script Host service configuration changes, and
start session scripts to multiple View desktop virtual machines.
Enable the VMware View Script Host Service
You must enable the VMware View Script Host service on each View desktop virtual machine where you
want View to run a start session script. The VMware View Script Host service is disabled by default.
When you configure the VMware View Script Host service, you can optionally specify the user account
under which the start session script runs. Start session scripts run in the context of the VMware View Script
Host service. By default, the VMware View Host Script service is configured to run as the SYSTEM user.
IMPORTANT Start session scripts are run outside a desktop user session and not by the desktop user account.
Information is sent directly from the client computer within a script running as the SYSTEM user.
Procedure
1 Log in to the View desktop virtual machine.
2 At the command prompt, type services.msc to start the Windows Services tool.
3 In the details pane, right-click the VMware View Script Host service entry and select Properties.
4 On the General tab, select Automatic from the Startup type drop-down menu.
5 (Optional) If you do not want the local System account to run the start session script, select the Log On
tab, select This account, and type the user name and password of the account to run the start session
script.
6 Click OK and exit the Windows Services tool.
View Integration
82 VMware, Inc.