Unsolved
This post is more than 5 years old
19 Posts
0
2893
April 13th, 2011 16:00
Questions about App-V-Integration
Hi,
regarding the App-V-Integration, i've some questions:
- why can i assign an application to one desktop group only?
- why can i assign just a server-based app-v-app to a location other than "My Application"?
- do my users that i assign an app-v-application to need to be in the user-group which i defined on the app-v-server?
what i would like to achieve is, that my users have access to the same applications regardless of the desktop or terminal server group they're working on!
OT: there seems to be an annoying bug with quest support portal and community and firefox 4- if you try to change your password from a temporary password, the wizard gives no error message, but the newly inserted password doesn't get saved and you find yourself in an endless loop...!
kind regards,
tim
DELL-Terry L
29 Posts
0
April 21st, 2011 17:00
Our database schema dictates that published application are linked/related to desktop group or terminal server objects. Thus, our application definition has two name fields -- application name AND display name. In the application name of app-v imported apps, copy the application name to the display name and then modify the application name to reflect where it's published. For example, "Abode Reader X" might become "Adobe Reader X - RDS". Next, simply duplicate this publication by right clicking and selecting duplicate. Change the application name from "Copy of Adobe Reader X - RDS" to "Adobe Reader X - HQ Group". Then within the properties, change the publication destination to the corresponding HQ Desktop Group... The user sees the display name so both VDI users and RDS users simply see "Adobe Reader X". You see two published apps in the console.
The folder assignment dialog provides two functionalities. The lower portion of the dialog provides you with the ability to publish apps -- both installed and app-v apps, into the vWorkspace client (App Portal and Web clients). You can create your own client folders it you need application seperation within the client.
The upper section of the folder assignment dialog is less intuitive. The upper section allows you to manage the RDS session or VDI session desktop and start menu. We uniquely provide you with the ability to control the RDS or VDI users desktop and start menu as a desktop management feature. As such, the application MUST be installed within RDS or VDI, OR the app-v client must be installed on RDS or VDI so that we could stream the app into the app-v client. When the app-v app is imported it asks if it will be published to the client or server. This actually means "where is the app-v client installed" where server is the RDS or VDI session and client is the user end-point. Server is the default but both would need the app-v client installed for them to receive the app.
vWorkspace can assign resources/apps to users, groups, ous, ip addresses and device names. BUT for app-v these must be subsets of the app-v application group(s) that are authorized to run the app-v app.