Terminal Server RDP 64-bit Client on 32-bit Server ?

[rwsjbs]

Thanks for looking.

We have a custom app that uses 2003 R2 Server Std Terminal Server (RDP). When the client logs in, we use the Virtual
Channel to send a license key (for our software) from the client to the server.

If the client is using 32-bit (Windows 2000, XP, or Win7), the server reads the license key with no issues.

If the client is using a 64-bit operating system, the server doesn't read the license key and our custom app will not start.

We store the license key information in two places in the registry of the client.

The first location is:

Hkey_Local_machine \ Software\ OurSoftware \ LicenseKey (in a String Value)

The second location is:

HKEY_CURRENT_USER \ Software \ Microsoft \ Terminal Server Client \ Default \
AddIns \ RDPDR \ ICLcns \ Then there is a String Value Name that points to
c:\Program Files\ico\ICLicenseClient.dll

And we also have the ICLicenseClient.dll in the c:\Program files\ico directory.

So, my questions are:

1. Can you use Virtual Channels with a 64-bit client on a 32-bit server?
2. Does the 64-bit Virtual Channel send the files from a different location? If so, should we put our registery entries in a different location so the 32-bit server can read them?

Thanks for any help you can send.

Richard Scott

 

[baddos]

The registry and program files paths will be different for your application if you have hard coded them as HLM\Software or C:\Program Files\. You should use the environment variables to access the program files path as it will point to the correct location.

i.e.

%programfiles%

32bit applications using the registry will have to use:

HKEY_LOCAL_MACHINE\Software\WOW6432node

instead of

HKEY_LOCAL_MACHINE\Software

For more info, check out this KB:

http://support.microsoft.com/kb/896459

 

[rwsjbs]

baddos,

I appreciate you pointing me in that direction. Looks like I have a project for this weekend!

Thanks,
Richard Scott