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.
Note 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: