sunhux
asked on
RDP licensing protocol error
http://social.technet.microsoft.com/Forums/windowsserver/en-US/87fc497a-27fd-4a76-ab59-ea5fe01c9091/bug-remote-desktop-session-is-disconnected-with-protocol-error-if-remote-control-is-used-on-a?forum=winserverTS
We encountered the above error between our NetIQ PUM
(Privilege User Manager) & our Win 2008 R2 Terminal server
licensing server (a VM).
We are in a situation where Novell says to look into MS direction
& MS felt it's a Novell PUM related matter.
We tried the suggestions given above but did not help.
Attached is a zip of the screen shot showing the error plus
unifid agents logs
pumlog.zip
We encountered the above error between our NetIQ PUM
(Privilege User Manager) & our Win 2008 R2 Terminal server
licensing server (a VM).
We are in a situation where Novell says to look into MS direction
& MS felt it's a Novell PUM related matter.
We tried the suggestions given above but did not help.
Attached is a zip of the screen shot showing the error plus
unifid agents logs
pumlog.zip
ASKER
The above link suggests to copy mstsc from XP (in 32bit) to the 64-bit & run in
compatibility mode;
I've got this working finally!!! For anyone who's interested, this is what I did.
Find a windows XP machine. Copy onto a USB pen drive (or something like that:
mstsc.exe
mstscax.dll
then create a subfolder called en-US and copy into it
mstsc.exe.mui
mstscax.dll.mui
Now copy these files onto your windows 7 machine. It doesn't matter where, so long as the en-US folder you've created follows it.
go into the properties of mstsc.exe and set the compatability options to windows xpsp3 and run as administrator
Now double click on mstsc. I've just tried remote controlling a user and it worked.
I'm now off to change my file associations to point at this older version of mstsc.exe
compatibility mode;
I've got this working finally!!! For anyone who's interested, this is what I did.
Find a windows XP machine. Copy onto a USB pen drive (or something like that:
mstsc.exe
mstscax.dll
then create a subfolder called en-US and copy into it
mstsc.exe.mui
mstscax.dll.mui
Now copy these files onto your windows 7 machine. It doesn't matter where, so long as the en-US folder you've created follows it.
go into the properties of mstsc.exe and set the compatability options to windows xpsp3 and run as administrator
Now double click on mstsc. I've just tried remote controlling a user and it worked.
I'm now off to change my file associations to point at this older version of mstsc.exe
ASKER
I noticed that the 2 files mstsc.exe & mstscax.dll are of different
sizes in the Terminal server's c:\windows\system32 from the
other Win2008 R2 servers that I have.
Suspect these 2 files could have been bundled with PUM software.
I tried to rename the 2 files mstsc & mstscax.dll with domain admin
& local administrator but it kept giving "Access is denied" despite
that I've shut down the various Remote Desktop services (in case
they lock those files). What did I miss?
sizes in the Terminal server's c:\windows\system32 from the
other Win2008 R2 servers that I have.
Suspect these 2 files could have been bundled with PUM software.
I tried to rename the 2 files mstsc & mstscax.dll with domain admin
& local administrator but it kept giving "Access is denied" despite
that I've shut down the various Remote Desktop services (in case
they lock those files). What did I miss?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
work with MS Terminal Server licensing: saw a Novell
article that describe similar issue between MacOS' Rdp
client & MS Terminal Server's licensing.
Is there any way to replace Novell PUM's Rdp client with
MS Win2008 R2's Rdp client? Heard I can't just copy the
mstsc.exe binary over: some sort of rebuild is needed