Resources may be added, changed, or removed based on changes made by your admin. You can also manually look for updates to the resources when needed by selecting Refresh from the Details panel. You can manually refresh a Workspace by selecting Refresh from the overflow menu This section will teach you how to unsubscribe from a Workspace.
You can unsubscribe to either subscribe again with a different account or remove your resources from the system. Workspaces can contain multiple managed resources, including desktops.
When accessing a managed desktop, you have access to all the apps installed by your admin. You can configure some of the settings for desktop resources to ensure the experience meets your needs. To access the list of available settings right-click on the desktop resource and select Settings. The client will use the settings configured by your admin unless you turn off the Use default settings option.
Doing so allows you to configure the following options:. Have a feature suggestion or want to report a problem? Tell us with the Feedback Hub.
You can also give us feedback by selecting the button that looks like a smiley face emoticon in the client app, as shown in the following image:. To best help you, we need you to give us as detailed information about the issue as possible. Browse to or, in the Folder Name field, enter the destination folder, click OK , and then click Next.
On the Application Virtualization Data Location screen, click Next to accept the default data locations or complete the following actions to change where the data is stored:. Click Change , and then browse to or, in the Global Data Location field, enter the destination folder for the global data location, and click OK. If you want to change the drive letter to be used, select the preferred drive letter from the drop-down list.
Enter a new path to store the user-specific data in the User-specific Data Location field if you want to change the data location. The User Data Directory is where the Application Virtualization Desktop Client stores user-specific information, like personal settings for virtualized applications. Note This path must be different for every user, so it should include a user-specific environment variable or a mapped drive or something else that will resolve to a unique path for each user.
On the Cache Size Settings screen, you can accept or change the default cache size. Click one of the following radio buttons to choose how to manage the cache space:.
Use maximum cache size. Enter a numeric value from —1,, 1 TB in the Maximum size MB field to specify the maximum size of the cache. Use free disk space threshold. Enter a numeric value to specify the amount of free disk space, in MB, that the Application Virtualization Client must leave available on the disk. This allows the cache to grow until the amount of free disk space reaches this limit.
The value shown in Free disk space remaining indicates how much disk space is currently unused. Important To ensure that the cache has sufficient space allocated for all packages that might be deployed, use the Use free disk space threshold setting when you configure the client so that the cache can grow as needed. Alternatively, determine in advance how much disk space will be needed for the App-V cache, and at installation time, set the cache size accordingly.
In the following sections of the Runtime Package Policy Configuration screen, you can change the parameters that affect how the Application Virtualization client behaves during runtime:. Application Source Root. Specifies the location of SFT files. Application Authorization.
When Require User authorization even when cached is checked, users are required to connect to a server and validate their credentials at least once before they are allowed to start each virtual application. Allow streaming from file. Indicates whether streaming from file will be enabled, regardless of how the Application Source Root field is used.
Application Virtualization Server Sizing. App-V for RDS 4. The following software prerequisites are installed automatically if you are using the Setup.
Important For version 4. In Remote Desktop Services deployments, application conflicts can lead to silos of remote desktop session host servers. To avoid application conflicts, applications typically must undergo significant testing to determine which applications will collide and, therefore, must be separated and run on different session host silos—a time-consuming and costly process.
0コメント