Link to home
Create AccountLog in
Avatar of medium_grade
medium_gradeFlag for United States of America

asked on

Weird Windows 7 RDP Issues

I recently setup a 2008 R2 server running remote desktop services. I setup the Session Manager to use per-user CALs, I installed 10 user CALs in the Licensing Manager and the Session Manager says that my licensing is setup correctly. When I try to log into the remote desktop server on some of my Windows 7 workstations, it gets to the point in which is says "Configuring remote session" then it eventually says "This computer can't connect to the remote computer." I was able to get around this on a few of the machines by logging in via a different user. On one machine, I deleted the MSLicensing registry key which seemed to fix it. However, I can't help but feel that shuffling local user accounts isn't the real answer to my problem. I looked at the server logs but I can't seem to find any event that directly correlates with the failed sessions. I did notice that when I go to the Licensing Manager, the number of user CALs issued does not seem to change. Is that supposed to show right away? The fact that I can get it to work when I log into the same PC as a different user is really puzzling. I am really at a loss here. Any ideas?
Avatar of Ben Hart
Ben Hart
Flag of United States of America image

Did you add either the users or the security group the users are members of into the local RDP users group?
if that doesn't work I would suggest moving to per device as appossed to per user CALs
Avatar of medium_grade

ASKER

The licenses were installed as per user. I can change the licensing mode in the Session Manager, but it then shows that I have no licenses available. How can I change my existing licenses?
Apparently, I can't move to Per Device CALs at this point. Any other ideas?
ASKER CERTIFIED SOLUTION
Avatar of medium_grade
medium_grade
Flag of United States of America image

Link to home
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
See answer
Problem had nothing to do with RDP protocol or licensing. Was a network issue. Fixed on my own.