Tag Archives: EOP

KU vWorkspace Multi Session Initiator – Beta

I’m pleased to be able to announce the public beta of my new vWorkspace session initialization tool for the purpose of load/stress testing vWorkspace deployments.

I say “my new” but Adam Wilden (works with me) brought a lot to the table too.

I’ve dedicate a page (with details and screenshots) HERE




How to Integrate RES VDX and Quest vWorkspace

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



String (REG_SZ)
Value Name – ‘Name’

String (REG_SZ)
Value Data – ‘C:\Program Files\RES Software\VDX Plugin\VDXRDPPlugin_x86.dll’

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.


Top RDP Enhancement Tweak – MinSendInterval

[Skip the nonsense/story – Take me to the good stuff]

Before I start, click the link above to go straight to the enhancement.

One of the things that I hate about “VDI” marketing is when vendors use the term “native experience” or “as good as local”. This can be taken in many ways but I find most if not all to be complete b***ox!

Despite not using XenDesktop for many reasons I’m happy to admit that the out of the box ICA protocol wooops out of the box RDP. This was my largest pain when we moved away from our XenDesktop pilot (first version of XenDesktop) and moved to what was a recent purchase at the time, Quest’s vWorkspace. Don’t get me wrong vWorkspace is my preferred solution and out performs XenDesktop on many levels but it fundamentally uses RDP as it’s it display protocol.

When you move the mouse cursor up and down the start menu, the item on the menu is highlighted in pretty much real time. Do this over RDP and you will notice a slight delay. Do a freehand circle in MS paint with the brush tool over RDP and the movement is jerky. Insert the smiley face shape in Word, re-size and move it around the screen, again in RDP this is jerky.

ICA doesn’t suffer with this so why should RDP??. At the end of the day those tasks I described aren’t the tasks of power users or gamers. This is basic Windows functionality. Actually scrolling up and down a web page or document with standard RDP is NOT good.

The enhancement for this is actually an old fix by MS for a mouse lag issue with early versions of Terminal Services. This is MS’s blurb,

On a client computer, if you use Microsoft Terminal Services Advanced Client 5.1 or later to connect to a terminal server (that is, a server that has Terminal Server enabled), you may notice that the mouse pointer movement is not smooth; it may move in small jerks. This is most noticeable when you use a painting program, such as Microsoft Paint, or the drawing tools in a Microsoft Office program.

You know the phrase, “you can’t polish a turd”? Well that applies to RDP but with this enhancement you can roll it in glitter 🙂

Close down any open RDP sessions on the client computer and start Regedit. Navigate to the following registry subkey:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Terminal Server Client

Create a new DWORD called, Min Send Interval (with spaces). Set the value to 10 and exit Regedit.Normally this is good enough but if it makes you feel better restart the computer.

I’ve tested this process for HKLM as an alternative to HKCU on Vista and Win7. I assume it works for XP clients too.

Open up an RDP session and you “should” notice a big difference in the visual performance.

At some point I’ll do a Hollywood Spielberg style video of a before and after registry change to prove it really works!

Happy glittering!