Product Documentation

The Process.xml File

Feb 08, 2011
Note: The process.xml file is created on each workstation or device where Hot Desktop is installed in the C:\Program Files\Citrix\MetaFrame Password Manager\HotDesktop folder. A sample process.xml file is also located in the \Support folder of the installation media. Therefore, any changes you want to make to this file must be performed on a device-by-device basis. However, refer to the Citrix Support article http://support.citrix.com/article/CTX110394 to learn how to replace each user process.xml file through a Machine Group Policy in Active Directory.

Use the process.xml file to specify which applications continue to run after a Hot Desktop User logs off. These applications are known as persistent applications or persistent processes.

You can also use the process.xml file to specify applications that terminate after a Hot Desktop User logs off. These applications are known as transient applications or transient processes.

Note that you must include your desired tags within the <configuration> and </configuration> tags in the file.

Important: Save the process.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 process.xml file contains special or foreign characters such as Asian language characters, you must save it in UTF-8 format.

shellexecute_processes

Use this section of the file to specify any applications or file types to be run as the Hot Desktop User. This setting helps ensure the security of those applications to be run using the credentials of the currently logged on users.

Note: After installation, the plug-in software automatically specifies a shell executable application named ssoshell.exe (the Single Sign-on Plug-in software) in the process.xml file. By default, it is specified as a process to be run as the Hot Desktop User.

While the start script in the session.xml file specifies the applications that launch when a Hot Desktop session first starts up, <shellexecute_processes> lists those applications that users can launch in the context of their Hot Desktop session.

 
<shellexecute_processes> 
	<process> 
		<name>appname</name> 
	</process> 
</shellexecute_processes> 

where:

appname Indicates the application name only of the process or application to be run. The full path is not required. For example:

pnagent.exe.

Note: process.xml allows the use of a wildcard (*) in addition to static file names such as Notepad.exe. Wildcards can be used alone or in combination with file names. For example, *.txt, pnagent.exe, and *.doc are all valid appnames.

persistent_processes

Use this section of the file to specify any applications that continue to run after the Hot Desktop User logs off. Specified applications are not terminated on shutdown (logoff) of Hot Desktop sessions, even if they were started during a session. Specify the full path of the persistent process to ensure that only the correct processes remain running after each session.

 
<persistent_processes> 
	<process> 
		<name>path_options</name> 
	</process> 
</persistent_processes> 

where:

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

Note: After installation, the plug-in software automatically creates an entry for a persistent application named activator.exe in the process.xml file. The activator.exe application provides users with their Hot Desktop session indicator. The session indicator is a transparent moveable window users see when they are logged on; it contains information about users and their sessions as defined by the administrator. By default, activator.exe is specified as a persistent process so that it is not restarted when each Hot Desktop User logs on or off.

transient_processes

Use this section of the file to specify any applications that will terminate after the Hot Desktop User logs off.

Note: After installation, the plug-in software automatically specifies a transient application named shellexecute.exe in the process.xml file. By default, it is specified as a transient process so that it is terminated when each Hot Desktop User logs off.
 
<transient_processes> 
	<process> 
		<name>appname</name> 
	</process> 
</transient_processes> 

where:

appname Indicates the application name only of the process or application to be terminated. The full path is not required. For example:

pnagent.exe.