A target is a collection of disk files, registry data, and other information used to represent an application isolation environment. In addition, each target denotes a combination of operating system, service pack level, system drive letter, and language. Applications can be profiled for each combination of these values to support separate targets; for example: Microsoft Vista for all service packs, drive letter C, and English.
There can be multiple executables inside a target including multiple applications that normally receive an entry on the Start menu. As an example, “Microsoft Office” is a profile and “Microsoft Word” is an application inside that profile. A profile can support multiple targets where the target is a separate installation of the profile-level software targeted for execution on a specific version of the operating system or language. For example, create one target for Windows Vista and another target for Windows Server 2008.
User devices select targets for execution based on the computer configuration you specify while creating the target. By default, a target matches the operating system and configuration of the profiling workstation, but you can select different operating systems as well.
In addition, refer to information about the following selection criteria for creating targets:
You use the profiler to set criteria for each target in a profile. One or more administrators can run the profiler multiple times and from different packaging environments to achieve a complete set of differentiating targets. For many common scenarios, a single installation image supports a variety of computer configurations, which simplifies profile creation.
The criteria associated with each target is stored in a profile manifest, a .profile file, stored with the profile files.
Overlapping definitions are not permitted: only one target in a profile can be a correct match for any computer configuration at application launch.
An administrator can update a profile and target at any time without affecting already active executions on user devices. The cost for this support is that file-server disk space is consumed to maintain old versions. The profiler provides no facility to delete old versions of targets. Instead, manually delete old versions of targets to reclaim server-side disk space. When deleting targets, it is the responsibility of the administrator to ensure that the deleted versions are sufficiently old that no users are employing the target.
For the list of supported operating systems for application streaming, see the system requirements. By design, future operating systems are not supported, and the execution environment refuses to execute an application if the user device has an unsupported operating system.
The service pack field is an optional component that augments the operating system version.
Because service pack level augments the operating system version, the profiler stores service pack selection criteria on a per-operating system basis. For each operating system, set the following rules for service pack selections:
When choosing supported service packs, ensure that you do not choose service packs that are not supported by the Offline Plug-in. Refer to the system requirements for supported platforms.
For best practices, Citrix recommends that you install all applications on the primary system drive. By packaging and executing using the primary system drive, you define a set of criteria that best associates a given target with a given user device.
The system drive letter must be a match between the target and the user device drive for a target to be the correct match for executing an application. There is no provision for the system drive to be variable. The system drive used on the profiler workstation must match the system drive on the user device.
To support user devices with different system drive letters, create a target for each drive letter.
The following languages are supported by the profiler:
Using the English version of the profiler, create targets for the following operating system languages:
The profiler can create targets for all languages, including languages other than those listed here, but doing so is not fully supported. To create targets for other languages, Citrix recommends that you use the English language version of the profiler.
Inter-isolation communication is a feature that links individual profiles so that applications in separate profiles can communicate with each other when launched on the user device. You can also use this feature if a streamed application fails because it needs data from another streamed application, but cannot detect it because both are running in isolation environments.
You can create two types of profiles that provide inter-isolation communication:
When you create a profile enabled for inter-isolation communication, applications launch on the user device and remain isolated from the system and from other isolated applications, but they can interact with each other.
The advantage of inter-isolation communication is that applications can be maintained separately and updates are included automatically in all the linked profiles in which the profile is included. This feature saves time for the administration of the profile set.
When you create a dependent profile, the additional properties added to any of the individual profiles in the linked profile are enabled for all the individual profiles. These properties include custom rules, pre-launch or post-exit scripts, and pre-launch analysis. When users stream applications from the inter-isolation communication profile, the combined properties of all the linked profiles execute in hierarchical order, from the lowest profile to the highest profile as listed in the profiling wizard and Linked Profiles property page.
However, if you create an associated profile, without installing a new application, additional properties are not available. You can add properties only to profiles that have installed applications.