Using RDCMan v2.2 build 2.426 downloaded from http://www.microsoft.com/download/en/details.aspx?id=21101

Client is Windows 7 x64 SP1

Servers vary from Windows Server 2003 R2 to Windows Server 2008 R2 with same result

Error message when attempting to logoff a session either individually or as a group: 

"Unable to log off from [servername] Reason: Unable to enumerate remote sessions."

Hello,

You must run the application as a user with local administrator or doamin admin rights on the remote machine.

• Marked as answer by tektotket Monday, January 16, 2012 3:47 PM

That did it.  I just launched RDCMan with domain admin credentials and now the logoffs are working.

Thanks

Hi Guys, 

I am using the same version of Remote Desktop Connection Manager V2.2 Build 246 and my account is part of Domain admin, but I still get the same message, can anyone advise the back-end mechanism of the error message? 

Many thanks,

James Yang

I hit this issue as well when going cross domain (e.g. into our test or alternate domains) since the account I use is only a domain admin in one account. If that's what is going on for you, a possible way to work around it would be to have a universal group that contains your domain admins from your primary account in the target domain, and have that group added to the local administrators group.

Even if that works, it's annoying that you would have to approach it in that manner. If I can log into a remote system, then the tool should be able to send a logoff request to that system using the credentials with which it's already connected to the resource.

Thanks for the reply.

The root cause for me was that I logged on to my PC with my basic domain user account. When I connected to a server RDP session, I logged into it with my domain admin account.

But it is still my basic domain user account initiate the log off function, hence the error: unable to enumerate the session.

from my investigation this has something to do with the console switch.  MSTSC works for loging in to my server where i see this error so I configured my RDCMan not to Connect to console and presto-change-o i logged in to my server.  Now troubleshooting console connection will be left for another time. 

• Proposed as answer by BrianMalerby Friday, October 12, 2012 2:08 PM

Hi guys,

I have the same problem.

RDCMan get user account (my local machine) to do "logoff" on everyserver, I need RDCMan takes domain user setup about everyconnection because I have diferents user domain.

If you look in event viewer about target server, you will see audit failure because RDCMan takes your local machine user...

Do you know fix about that?

Regards.

Hi

Run as administrator or domain admin

this solution is not working.

I am administrator on my laptop (DOMAIN: HOME\josuamix) and I am execute RDCMan with administrator privilegies.

Later that, I have several folder with differents DOMAINS and severals servers each folder as following:

FOLDER_EUROPE (DOMAIN:  EUROPE\admx0001) --> This domain is the same for every server in this folder.

SERVER1

SERVER2

FOLDER_ASIA (DOMAIN:  ASIA\admx0001) --> This domain is the same for every server in this folder.

SERVER1

SERVER2

When I am trying to logoff I can see in the event viewer tool about every server (SERVER1, SERVER2...etc) errors trying to connect with my credentials about my laptop (HOME\josuamix), I think so for this reason is not working, RDCMan must take credentials about each server is logged in this moment.

Do you understand?

Thanks a lot!!

Regards,

I have this same problem and it's with the design of the MS API.

You can connect to the machines with an account from that domain. What is happening though is you launched this application as the user who is on your laptop. When the program is sending the logoff, it's using the account on your local computer, which has no permissions to the domains you are connected to.

To workaround this issue you would need to create a connection for each domain, then launch the manager with those credentials. Then your logoff group will work.

The problem is the API was not written to use the proper credentials. Pretty much any 3rd party app would use this method as well, so you'll likely see this issue in most other apps. Unless they have written their own way to get around this.

No one other than MS can fix this problem, so you'll probably just have to live with it... until MS fixes the API or you find a better tool.

• Proposed as answer by testetsetsetestsetsetset Thursday, September 18, 2014 9:46 PM

I added my own (domain) account to the local administrator group on the server and now I can log off from within RDC without error.

Tried it on 2008 R2. Drawback is off course me having all rights to this server, I don't want that. I prefer keeping my own account and domain administrative account separate.

So I removed my account from local administrators on the server and added it to remote users. After a reboot I was able to log off without error, so that's probably all you need to do; add you own domain account to the remote users group and use this feature after a reboot of the server.

Tried it on 2003 R2 as well, didn't work. Only when adding your account to the local admins.

• Edited by Veldje 21 Thursday, March 12, 2015 10:17 AM 2003 R2 remark
• Proposed as answer by Lee Crawford Thursday, March 26, 2015 1:57 PM

I have the same error message, and I'm fairly certain it's not related to the access rights of any particular remote user, but initially I thought: kudos to the comment about this involving the Console session, because that's what I'm doing.

I have a half dozen Windows Server 2012 R2 VMs I am connecting to, all on a workgroup (no domain, so no domain admin accounts).  I am logging onto each VM as the Administrator user (this is a testing / development environment so I'm happy with this approach).  Windows Firewall is disabled for Domain/Private/Public, and no third party firewall or AV program has been installed.  I am logged onto my local PC as a workgroup user who is a member of the Administrators group on my local PC, but which does not exist on the VMs.  UAC is disabled in all locations.  I am connecting to the console session on all of the servers.  I am connecting to the console session on all servers.  I am also connecting to these servers behind a NAT-enabled router, so I connect to 6 VMs using one IP address, but with a different port for each.

1. Running RDCM as an administrator changed nothing (as expected, since I'm already a local administrator).

2. Connecting to a server non-console ("Connection Settings" tab, "Connect to Console" unchecked) did not fix the issue.

3. I read that the following registry key may not exist (but it did, so not my fix):

"HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\AllowRemoteRPC DWORD value should be 1.

Hopefully this info helps someone in their quest to find a solution.  I am able to log onto a group of servers and disconnect from the same group of servers, but it would be nice if logging off of those servers also worked.  It seems the issue is simply that the user I launch RDCM with on my local PC is not a user on the remote PC (no domain), and the request to log off is being sent as the local user of RDCM instead of the user which is logged onto the remote PC.  So for those of us without domains, maybe there is no workaround?

• Proposed as answer by laurin1 13 hours 46 minutes ago

I'm having the same problem. Yes, I am using the same account to connect as I'm logged in with to use the client. Yes, I am a Domain Admin.

The thing is, this issue only occurs for Desktop OS's, i.e., Windows 7 or Windows XP. I don't have this problem with Server 2003, Server 2008, or Server 2012.

I have the same error message, and I'm fairly certain it's not related to the access rights of any particular remote user, but initially I thought: kudos to the comment about this involving the Console session, because that's what I'm doing.

I have a half dozen Windows Server 2012 R2 VMs I am connecting to, all on a workgroup (no domain, so no domain admin accounts).  I am logging onto each VM as the Administrator user (this is a testing / development environment so I'm happy with this approach).  Windows Firewall is disabled for Domain/Private/Public, and no third party firewall or AV program has been installed.  I am logged onto my local PC as a workgroup user who is a member of the Administrators group on my local PC, but which does not exist on the VMs.  UAC is disabled in all locations.  I am connecting to the console session on all of the servers.  I am connecting to the console session on all servers.  I am also connecting to these servers behind a NAT-enabled router, so I connect to 6 VMs using one IP address, but with a different port for each.

1. Running RDCM as an administrator changed nothing (as expected, since I'm already a local administrator).

2. Connecting to a server non-console ("Connection Settings" tab, "Connect to Console" unchecked) did not fix the issue.

3. I read that the following registry key may not exist (but it did, so not my fix):

"HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\AllowRemoteRPC DWORD value should be 1.

Hopefully this info helps someone in their quest to find a solution.  I am able to log onto a group of servers and disconnect from the same group of servers, but it would be nice if logging off of those servers also worked.  It seems the issue is simply that the user I launch RDCM with on my local PC is not a user on the remote PC (no domain), and the request to log off is being sent as the local user of RDCM instead of the user which is logged onto the remote PC.  So for those of us without domains, maybe there is no workaround?

Ha! I didn't try the last solution! This worked for me:

"HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server\AllowRemoteRPC DWORD value should be 1.