For those who don’t know what RES Software’s Virtual Desktop Extender (VDX) is, check it out: RES VDX
VDX effectively allows users to view locally running/installed apps on top of their full screen virtual desktop/RDSh session. It’s a little more than that but I’m not doing a sales pitch today (not feeling creepy enough).
VDX as it currently stands, supports Citrix ICA/HDX, Standard RDP (including RemoteFX) and I think PCoIP (not sure). With a little bit of tweaking it will work with the current (7.2 MR1 at the time of writing this) version of vWorkspace.
Actually VDX worked with vWorkspace since before it was called VDX and before vWorkspace was called vWorkspace, http://support.ressoftware.com/Modules/KnowledgeBase/knowledgebaseTreeView.aspx?id=1760
However as solutions evolve compatibility issues arise from time to time… With the help of the splendid chaps from both Quest and RES, I have been able to get VDX working with vWorkspace and this is how…
|Create the following path:
HKLM\Software\Provision Networks\Terminal Services Client\AddIns\VDX
Without the ”…
Note: As the vWorkspace connector for Windows is only 32bit, you still need to set the same dll (as above) on x64 systems however the Provision Networks key is located in, HKLM\Software\Wow6432Node\ – I guess once Quest release a x64 connector then you will need to switch to the x64 VDX DLL.
Also… In the original RES KB, HKLM\Software\Provision Networks\Terminal Server Client was used… This now needs to be, HKLM\Software\Provision Networks\Terminal Services Client. This is where I went wrong!
I have tried this on both X32 (Win XP/7) and X64 clients (Win7) using RDP/EOP and RDP with RemoteFX and EOP connecting to a RDSh session. I assume it will work for RemoteFX/EOP on a VDI box but I’ve not had chance to test.
I guess the next step is to get Quest and RES’s products aware of each other to automate this process!
My Next RES/vWorkspace compatibility post will include RES Workspace Manager working with vWorkspace for VDI and RDSh.