Product Documentation

Isolating Services

Dec 17, 2015

Certain applications, such as Microsoft Office 2010, require related services to run on the user device. Beginning with version 6.0 of the profiler, services that are required by applications are automatically installed with the application as you create application profiles.

Important: This feature requires that you create a whitelist of approved locations of profiles in the registry of user devices. After you create the whitelist and edit the registry for the user devices, only services from the approved locations can be loaded and run on the user device. For these steps, see Specifying Trusted Servers for Profiles and Services.
Based on its startup type, a service runs in an isolation environment on the user device with the application that requires it and continues until the session ends:
  • Automatic start: These services start automatically at logon and continue running until the user shuts down or restarts the device.
  • Manual start: These services start when called by an application in the profile and continue running until the application ends the service or the user shuts down or restarts the device.

To view or modify the services available for a target, from the profiler, from the Edit menu, select Target Properties. The Services tab lists the services, their paths, logon names, and start type.

Considerations

  • Isolated services might extend launch time for the first launch of the application each time the device is restarted.
  • When a service runs in isolation, it might not communicate all the needed information with services running outside isolation, such as locally installed services. If communication is required, consider removing the service from isolation and installing it locally on the user device.
  • If the profile uses inter-isolation communication to link one or more subprofiles, all services within the linked profile are started.
  • To update a service, open the existing profile in the Update Profile wizard. Citrix recommends updating services during off-peak hours because the procedure stops the service and closes that application for end users. After completing the update, the service restarts and users can relaunch the application.
  • In any environment, only a single instance of the service launches in isolation. For example, in a multiuser environment, the service starts when the first user launches the application and then is shared by all subsequent users running the application.