Hi,
Since we migrated to Win10 we had an error when we try to connect to a terminal server. No problem to connect to a standard server with RDP, no problem with Win7. Only terminal servers (win2008r2 or Win2012r2) from Win10.
We use ASG RD 2016. Extra info: no problem if we use mstsc.exe.
Complete error (see attachment):Return code 2056 "The remote computer disconnected the session because of an error in the licensing protocol"
1. Delete Registry items in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing
2. Close ASG-RD and start again as Administrator
3. Connect your server...
Is this verified to work? I have the same issue but ASG Remote Desktop is published on a terminal server so I can not delete this value.
Hi,
Yes the solution is working. We had the same problem, ASGRD is published with MS AppV v5. But we must manually remove the registry key. AppV doesn't remove the key.
Remarks: With a manual install, the key is automatically removed.
Is this verified to work? I have the same issue but ASG Remote Desktop is published on a terminal server so I can not delete this value.
Hi,
Yes the solution is working. We had the same problem, ASGRD is published with MS AppV v5. But we must manually remove the registry key. AppV doesn't remove the key.
Remarks: With a manual install, the key is automatically removed.
Rgds
Jonathan
Hi,
but I don't get this. The application is installed on a terminal server and the users launch ASG as a published application. Don't I need this key on my terminal server where the ASG-application is installed? This isn't a ASG-registry key.
Is this verified to work? I have the same issue but ASG Remote Desktop is published on a terminal server so I can not delete this value.
Hi,
Yes the solution is working. We had the same problem, ASGRD is published with MS AppV v5. But we must manually remove the registry key. AppV doesn't remove the key.
Remarks: With a manual install, the key is automatically removed.
Rgds
Jonathan
Hi,
but I don't get this. The application is installed on a terminal server and the users launch ASG as a published application. Don't I need this key on my terminal server where the ASG-application is installed? This isn't a ASG-registry key.
Hi,
It's on our terminalserver that we delete this key. After that working for any users logged on this terminal.
It's indeed a key from Microsoft.
BR
Jonathan
Sorry, this must be a language barrier or something. I don't get it.
First, why must I delete the registry value HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing ?
Secondly, Where would you like me to delete the registry value above? Here is my setup.
One windows server 2012 R2 with terminal server installed, TerminalServer-1. This server is launching an App-V packaged ASG-Remote Desktop when users logs in to this server.
The users then try and launch an RDP session inside ASG-RD to TerminalServer-2.
13-03-2017, 08:21 AM (This post was last modified: 14-03-2017, 06:48 AM by dst.)
(09-03-2017, 11:09 AM)DevOma Wrote: I can't tell you why - we found that solution in MS forums...
Delete the regkey on the server where ASG-RD is installed
This solved the issue.
And for those who dont know this registry value is used to license RDS on a device license basis. If you don't use this I suppose it shouldn't be a problem deleting it.
EDIT:
Thought I mention this just if someone has the same problem as me. You also have to delete any roaming profile you have on the specific user, I assume it's somewhat stuck a setting in there also.
Did you start ASG-RD "as Administrator" after deleting the regkey? And did you also try to delete the roaming profile of the user like in last post described? I'm not an App-V specialist - but the solution worked for all "published" apps...
(05-04-2018, 03:31 PM)DevOma Wrote: Did you start ASG-RD "as Administrator" after deleting the regkey? And did you also try to delete the roaming profile of the user like in last post described? I'm not an App-V specialist - but the solution worked for all "published" apps...
Yes, we have checked as per your suggestions but issue still remains same.
The same users can access other servers with out any issues and this issue occurring for few servers only.
(05-04-2018, 03:31 PM)DevOma Wrote: Did you start ASG-RD "as Administrator" after deleting the regkey? And did you also try to delete the roaming profile of the user like in last post described? I'm not an App-V specialist - but the solution worked for all "published" apps...
Do we have any alternative way to resolve this issue instead of removing registry on server
