Product Documentation

The Session.xml File

Feb 08, 2011

Use the session.xml file to specify the applications that launch when a Hot Desktop session starts (start script) and remove files or other information left behind by a user session (shutdown script). After you edit this file as needed, put it on a network share or other central location for your Hot Desktop workstations to access. You specify this location of the session.xml file in the user configuration.

You must include your desired tags within the <session_settings> and </session_settings> tags in the file.

Note: A sample session.xml file is located in the \Support folder of the installation media.

Example: Cleaning Up a Session with a Script

Use a shutdown Visual Basic script to clean up any user data left behind at the end of a session. The session_cleanup.vbs script launches as the shared account (named HDSA) and is located in C:\.

 
<shutdown_scripts> 
	<script> 
		<account>HDSA</account> 
		<working_directory>c:\</working_directory> 
		<path>c:\session_cleanup.vbs</path> 
	</script> 
</shutdown_scripts> 

Example: Launching Internet Explorer

Launch Internet Explorer with the URL of your mycompany.com intranet. In this case, Internet Explorer runs as a process associated with the Hot Desktop User.

Note that you would enclose your desired tags within the <session_settings> and </session_settings> tags in the file.

 
<startup_scripts> 
	<script> 
		<account>HDU</account> 
		<working_directory>c:\program files\Internet Explorer</working_directory> 
		<path>c:\program files\Internet Explorer\iexplore.exe http://www.mycompany.com</path> 
	</script> 
</startup_scripts> 

startup_scripts

This section of the file is used to specify any applications to launch under the Hot Desktop shared account and the Windows account associated with the Hot Desktop User.

 
<startup_scripts> 
	<script> 
		<account>account</account> 
		<working_directory>wd</working_directory> 
		<path>path_options</path> 
	</script> 
</startup_scripts> 

where:

account Indicates the account under which to run the application. Choices are HDU or the Hot Desktop shared account user name.
wd Indicates the working directory of the application.
path_options Indicates the fully qualified folder path to the application executable file or script on the local computer and any options to run with the application. For example:

c:\program files\Internet Explorer\iexplore.exe http://www.yahoo.com

shutdown_scripts

Edit the session.xml shutdown applications to remove all unused data from the previous user session. Typically, these applications should remove configuration files that might prevent the next user from working, sensitive files such as logs, and documents stored on the system. These applications should ensure that the Hot Desktop environment is clean for the next user session. This part of the file is especially useful for data security.

Note: If necessary, you can initiate administrator programs or scripts to clean up the user environment at logoff. For example, you can write a Visual Basic script using a third-party application to delete user-specific .ini files.
 
<shutdown_scripts> 
	<script> 
		<account>account</account> 
		<working_directory>wd</working_directory> 
		<path>path_options</path> 
	</script> 
</shutdown_scripts> 

where:

account Indicates the account under which to run the shutdown application. Choices are HDU and the Hot Desktop shared account user name.
wd Indicates the working directory of the application.
path_options Indicates the fully qualified folder path to the application executable file or script on the local computer and any options to run with the application. For example:

c:\cleanup.vbs

Launching Applications Using Session.xml

Consider the following:
  • The applications you specify in the session.xml file must already be installed on the workstation.
  • Because Hot Desktop is part of the Single Sign-on Plug-in software, the plug-in software starts automatically and does not need to be specified in this file.

Other applications specified in session.xml can launch under the Hot Desktop shared account shell, which can prompt users for credentials. The plug-in software then performs according to settings in the user configurations.

Important: Save the session.xml file in UTF-8 format. ANSI encoding is acceptable if all characters are in the 0 to 127 (standard English character set) range. If your session.xml file contains special or foreign characters such as Asian language characters, you must save it in UTF-8 format.