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
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 View Agent, add a second DWORD value to the
Configuration key called WaitScriptsOnStartSession.
A WaitScriptsOnStartSession data value of 1 causes View Agent to delay sending a StartSession
response and fail if the scripts do not complete. A value of 0 means that View Agent does not wait
for the scripts to complete or check script exit codes before sending the StartSession response. The
default value is 0.
6 Set a registry value to specify timeout values in seconds rather than minutes to prevent scripts from
timing out.
Setting this timeout value in seconds enables you to configure the VMware View Script Host service
timeout value in seconds. For example, if you set the VMware View Script Host service timeout to 30
seconds, you can ensure that a start session script either finishes running or times out before a View
Connection Server timeout occurs.
a Navigate to HKLM\SOFTWARE\VMware, Inc.\VMware VDM\ScriptEvents.
b Add a DWORD value called TimeoutsInMinutes.
c Set a data value of 0.
7 (Optional) To enable the VMware View Script Host service to time out the start session script, set a
timeout value.
a Navigate to HKLM\SOFTWARE\VMware, Inc.\VMware VDM\ScriptEvents\StartSession.
b In the topic area, right-click the Default (@) key and select Modify.
c In the Value data text box, type the timeout value and click OK.
A value of 0 means that no timeout is set.
8 Exit the Registry Editor and restart the system.
Sample Start Session Scripts
These sample start session scripts illustrate how to write environment variables to a file, test the timeout
functionality, and test a non-zero exit code.
The following sample Visual Basic script writes all the environment variables provided to the script into a
file. You can use this sample script to see example data in your own environment. You might save this script
as C:\sample.vbs.
Option Explicit
Dim WshShell, FSO, outFile, strOutputFile, objUserEnv, strEnv
strOutputFile = "c:\setvars.txt"
Set FSO = CreateObject("Scripting.fileSystemObject")
Set outFile = FSO.CreateTextFile(strOutputFile, TRUE)
outFile.WriteLine("Script was called at (" & Now & ")")
Set WshShell = CreateObject( "WScript.Shell" )
Set objUserEnv = WshShell.Environment("PROCESS")
For Each strEnv In objUserEnv
View Integration
84 VMware, Inc.