Over the last couple of days, Grant Tiller, our Channel Mananger in the UK. Had some good success with getting RES Subscriber and RES PowerFuse Workspace Extender working under Provision Networks VAS 5.10

When you make a couple of small customisations to the registry everything works properly.

Here follows an example of what needs to be done to get RES Subscriber working properly:

HKCU\Software\Microsoft\Terminal Server Client\Default\AddIns\Subscriber
————————–
String (REG_SZ)

Value Name Name
Value Data C:\Program Files\RES Subscriber\vcsubrdp.dll

 

 


————————–


HKLM\Software\Provision Networks\Terminal Server Client\Default\AddIns\Subscriber
————————–
String (REG_SZ)
Value Name Name
Value Data C:\Program Files\RES Subscriber\vcsubrdp.dll
————————–


It is important to note the differences between Microsoft and Provision:
· Microsoft entry can be found under HKCU whereas Provision entry can be found under HKLM
· Microsoft hive is under Terminal Server Client whereas Provision hive is under Terminal Services Client 

Regarding RES PowerFuse Workspace Extender, the settings are almost identical:

The first setting is already created as part of the RES PowerFuse Workspace Extender installation process.

HKCU\Software\Microsoft\Terminal Server Client\Default\AddIns\Subscriber
————————–
String (REG_SZ)
Value Name Name
Value Data C:\Program Files\RES PowerFuse Workspace Extender\vcsubrdp.dll
————————–


HKLM\Software\Provision Networks\Terminal Services Client\AddIns\Subscriber
————————–
String (REG_SZ)
Value Name Name
Value Data C:\Program Files\RES PowerFuse Workspace Extender\vcsubrdp.dll
————————–


It is important to note the differences between Microsoft and Provision:
· Microsoft entry can be found under HKCU whereas Provision entry can be found under HKLM
· Microsoft hive is under Terminal Server Client whereas Provision hive is under Terminal Services Client

Grant, thanks…