Follow best practices when you assign ThinApp applications to desktops and pools.

To install a ThinApp application on a particular desktop, assign the application to the desktop. If you use a common naming convention for your desktops, you can use desktop assignments to quickly distribute applications to all of the desktops that use that naming convention.

To install a ThinApp application on all of the desktops in a pool, assign the application to the pool. If you organize your pools by department or user type, you can use pool assignments to quickly distribute applications to specific departments or users. For example, if you have a pool for your accounting department users, you can distribute the same application to all of the users in your accounting department by assigning the application to the accounting pool.

To streamline the distribution of multiple ThinApp applications, include the applications in a ThinApp template. When you assign a ThinApp template to a desktop or pool, View Administrator installs all of the applications currently in the template.

Do not assign a ThinApp template to a desktop or pool if the template contains a ThinApp application that is already assigned to that desktop or pool. Also, do not assign a ThinApp template to the same desktop or pool more than once with a different installation type. View Administrator will return ThinApp assignment errors in both of these situations.

Although assigning ThinApp applications to local desktops is not supported, View Administrator does not prevent you from doing so. If you want to experiment with assigning ThinApp applications to local desktops, you must meet certain requirements. If you plan to stream a ThinApp application, verify that View Agent in the local mode desktop can access the network share that hosts the ThinApp repository. Streamed ThinApp applications work only when the client system is connected to the network.

Assigning ThinApp applications and removing them from a desktop work only if both View Connection Server and View Agent in the local mode desktop can access the network share that hosts the ThinApp repository.

Caution

Rolling back a desktop might cause View Connection Server to have incorrect information about the ThinApps on the rolled-back desktop.