I've seen this with RDS and VDI VM's.

Even tried using the registry feature to inject the association but it requires a "Default" value which isn't supported with vWorkspace.

You could create a package that adds the values to the registry and associate it to the VM's/RDS server - not ideal. Or maybe use the Scripts feature to run a script that adds the values at login or something?

Dan.

Do you have a App-V Management server with your environment that you have integrated into the vWorkspace Broker?  If so, how are you deploying the application to the endpoint (App-V Client or through vWorkspace App-V Packaged Applications)?  I currently have App-V running using both scenarios, so I might be able to help if you provide more details.

Thanks,

Patrick

You need the App-V client to do FTA. if you do it for a user once and save the appropiate keys using User Profile Management this should do it, I would think. Are you saying this is not the case?

Paul, this appears to be normal AppV behaviour,

To save the pain of every User having to make the file association, I'd send the reg key to all Users.

HKEY_CURRENT_USER\Software\Classes\osd_auto_file\shell\open\command

And set the (Default) to "C:\Program Files (x86)\Microsoft Application Virtualization Client\sfttray.exe" "%1" %*

Normally we'd recommend using the Management Console | Registry Tasks option to set this. Sadly, you cannot currently use our "Registry Tasks" option in the Management Console to do this as we don't allow you to edit (Default) values.

You could use a login script to set this reg value for every user who logs into your RDS.

Thanks, Andrew.

You could also make a custom ADM that inserts these keys for this and associate to the user/users. It "feels" a little cleaner than using scripts.

In addition to the "shell\open\command" Default value you have to specify another class for the .OSD file extension too (HKCU\Software\Classes\.osd).

so:

HKCU\Software\Classes\.osd

HKCU\Software\Classes\osd_auto_file\shell\open\command < Default Value = "C:\Program Files (x86)\Microsoft Application Virtualization Client\sfttray.exe" "%1" %*

Dan

a work around exists where you publish sfttray.exe and pass the /launch switch and path to the OSD in the arguments field of the published application.

Kelly, Thanks

For more information

Andrew, the ability to set/remove the (default) values with a registry task will be available in 7.2 BETA 2.

-Adam

Here's the actual article link should you need it: https://support.quest.com/Search/SolutionDetail.aspx?id=SOL64291&category=Solutions&SKB=1