Local printers won't show up in Remote Desktop Connection Manager 2.7

Hi everybody
I really need help. I connect to a server through RDC Man 2.7 on my Surface Pro 3 to use the installed accounting software. Now I want to print stuf such as journals but when I print, I cannot choose my locally installed wirless Printer. I used to be able
to do it using RDC Man on my iMac in OSX.
I have ticked printers on the local resources tab in settings to no avail. I hope somebody can help me with this issue as I really need to be able to print.
Thanks a million.
Best regards
Ben

Hello Ben,
Do you mean that the Surface Pro 3 can’t find the local wireless printer when you remote desktop to a server? And when you remote from a iMac at the same time, the Surface Pro 3 can find the printer?
Can the surface pro 3 printer when it is not connected with the remote server?
Please take the following steps for troubleshooting:
1. Check if you can normally ping the IP address of the printer when you can’t printer.
About the command ping, please take a look at the following article.
https://technet.microsoft.com/en-us/library/bb490968.aspx?f=255&MSPPError=-2147217396
2. Go to Control Panel\All Control Panel Items\Troubleshooting\All Categories
and run printer troubleshooter
3. Please try to update the driver from the manufacturer website and check if the issue still exists
Best regards,
Fangzhou CHEN
Fangzhou CHEN
TechNet Community Support

Similar Messages

Remote Desktop Connection Manager can only open 6 sessions at a time on Server 2012

I am only able to open, and view thumbnails, for a maximum of 6 RDP sessions on my Server 2012 box at a time in Remote Desktop Connection Manager (RDCM). If I add more sessions I just get a variety of connection errors for the additional sessions. If I activate
a 7th session one of the existing 6 sessions goes off-line with a connection error message. Sometimes the error says 3334, sometimes the error says 0x8345000E, and sometimes it just says there is a connection error.
I have checked Group Policy on the server to ensure I don't have any settings restricting the number of RDP sessions.
In fact, I will often have 30 or 40 RDP simultaneous sessions opened, I am just not able to view them all in RDCM. I have seen reviews of RDCM with screenshots showing dozens of thumbnails so it seems to be something that's possible to do.
Are there any settings I should make on the server to allow RDCM to connect to more than 6 simultaneous RDP sessions?
Just to be clear, all these RDP sessions are running on the same server. Also, I am just using the trial license for Server 2012 and Remote Desktop Services right now. I don't think that should have an impact, but I wanted to be thorough.

Thanks Jakub for "corflags" info.
Unfortunatelly it doesn't work because running mRemoteNG.exe process in 64bit can't load MSTSC ActiveX component (referenced assemblies) because original files were assembled from 32bit dll [mstscax.dll]?
Error message when making RDP connection:
Could not load file or assembly 'Interop.MSTSCLib, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. An attempt was made to load a program with an incorrect format.
I was able to create new AxInterop.MSTSCLib.dll and Interop.MSTSCLib.dll assemblies from 64bit dll version and now it works with "AnyCPU":-)
http://www.filedropper.com/axinteropmstsclib-mremoteng
Using AxImp.exe and TlbImp.exe didn't worked for me because it creates assemblies in wrong namespace "MSTSCLib" instead of "Interop.MSTSCLib" (AxImp.exe) and TlbImp.exe for changing namespace generated many "marshaled errors"
so final .dll wasn't working.
Adding MSTSCAX.dll reference in Visual Studio directly created correct and functional assemblies. Who don't know how to create 64bit compatible assemblies or don't have Visual Studio, feel free to check linked file.
Hope it helps
P.S. Sorry for possible technical misinterpretation, I am not programmer so creating new assemblies was trial-error process...

Remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed

remote desktop connection manager on windows 8.1, can't connect to windows server 2012 R2, Socket closed each time i try to open remote connection to the server,
does remote desktop connection manager V2.2 not compatible with windows 8.1, and if so, is there are any other compatible versions
or what's the problem,
Mahmoud Sabry IT System Engineer

this issue maybe will be fix by latest version, we still waiting for it
maybe your issue can be fix using this methods
https://social.technet.microsoft.com/Forums/windowsserver/en-US/61f218a5-5ef8-49da-a035-90cdd64fc9a0/problem-with-remote-desktop-connection-manager-error-3334?forum=winserverTS
http://shawn.meunier.com/?p=1#comment-43

Remote Desktop Connection Manager alternative

Hi Guys,
Not too sure if anyone has asked this question before, are there any tools that you guys are using other than RDCMan where it will not store password in plain text? Saw some paid app, but doesn't seems to have much review on this portion.
thanks in advance.

Hi Kinshi,
Do you want to encrypt or decrypt the password? If you want to decrypt password then you can able to perform by this way.
Go to Remote Desktop Connection Manager -> Edit -> Properties -> Logon Credentials - Clear the Password. Then click Save
In addition you can refer below thread for encrypt password.
How does Microsoft Remote Desktop Manager encrypt passwords?
Apart from this, there are other 3rd party software but I will suggest that to use in windows system Remote Desktop Connection Manager is the best option as it’s a product of Microsoft itself and it’s free.
Remote Desktop Connection Manager 2.2 Clear Text Gateway Passwords?
Hope it helps!
Thanks.

Remote Desktop Connection Manager hang

I work at a win8.1 client. I use Remote Desktop Managr to access my servers and clients.
It was working fine till it goes in hanging state and the the screen freez when i am tring to remote login to any PC.
The version of RDM is 2.2 build 2.426 by Julian Burger.
I uninstall it and install again, but still the same problem.
can anybody help me to fix this problem?

Hi,
Is this the RDCman you downloaded?
Remote Desktop Connection Manager
The system requirements told that it's supported OS is Windows 7, Windows Server 2003, Windows Server 2008, Windows Server 2008 R2, Windows Vista, so there might be some compatiblity issues when using in Windows 8.1.
Here is another thread talking about the RDCMan version:
Where to download Windows Remote Desktop Manager
V2.5
Best regards
Michael Shao
TechNet Community Support

Remote Desktop Connection Manager can't stop Reconnecting

I use RDCM in different customer sites to connect to their Windows Server 2008/2008 R2 servers. Typically the server on which RDCM is running on is Windows Server 2008 Standard SP2 (64-bit). In some sites, when I disconnect from a server, instead
of completely disconnecting, the session turns gray and a "Reconnecting" window pops up:
Pressing the Cancel button simply grays out the button and I can never actually disconnect until I exit RDCM and restart it. "Disconnect group" doesn't help either. It seems like the problem occurs always in some sites and never in
others.
Is there a fix for this annoying problem?
David Collacott

Hi David,
The RDS feature is also available on Server 2008 but just the name is different, on server 2008 it’s called Terminal Server. So you can able to find the option “Set time limit for disconnected sessions” or the
session is active then you can choose the option “Set time limit for active Terminal Services sessions
“under below mention path.
User Configuration\Policies\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Session Time Limits
Please refer “Session Time Limits” for more guidance. In addition you can refer below article for Remote Desktop disconnection issue with server 2008.
Remote Desktop disconnected or can’t connect to remote computer or Remote Desktop server (Terminal Server) that is running Windows Server 2008
http://support.microsoft.com/kb/2477133
Hope it helps!
Thanks.

Is there a way to fix the Remote Desktop Connection Manager memory usage crashes?

I'm using RDCMan and it has been using a lot of memory and crashing. With 12 connections it uses 1,548,976 K of memory and crashes with an "Unhandled exception" "Not enough storage is available to process this command. (Exception from
HRESULT: 0x80070008)." I love this program and want to know if there's a way to fix this on my end. It seems like other people are not having this issue. I'm running a fresh install of Win7 Ent. I have .NET 3.51 and 4 installed.
Do I need to installed .NET 2.0?
Here is the info from the crash:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.Runtime.InteropServices.COMException (0x80070008): Not enough storage is available to process this command. (Exception from HRESULT: 0x80070008)
at System.Windows.Forms.UnsafeNativeMethods.CoCreateInstance(Guid& clsid, Object punkOuter, Int32 context, Guid& iid)
at System.Windows.Forms.AxHost.CreateWithoutLicense(Guid clsid)
at System.Windows.Forms.AxHost.CreateWithLicense(String license, Guid clsid)
at System.Windows.Forms.AxHost.CreateInstanceCore(Guid clsid)
at System.Windows.Forms.AxHost.CreateInstance()
at System.Windows.Forms.AxHost.GetOcxCreate()
at System.Windows.Forms.AxHost.TransitionUpTo(Int32 state)
at System.Windows.Forms.AxHost.CreateHandle()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.AxHost.EndInit()
at RDCMan.RdpClient7..ctor(RdpClient parent, MainForm form)
at RDCMan.RdpClient..ctor(MainForm form)
at RDCMan.RdpClient.AllocClient(Server server, MainForm form)
at RDCMan.Server.InitClient()
at RDCMan.Server.ConnectAs(ILogonCredentials logonCredentials)
at RDCMan.Server.Connect()
at RDCMan.ServerTree.OnDoubleClick(EventArgs e)
at System.Windows.Forms.TreeView.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
RDCMan
Assembly Version: 2.2.2.426
Win32 Version: 2.2.2.426
CodeBase: file:///C:/Program%20Files%20(x86)/Remote%20Desktop%20Connection%20Manager/RDCMan.exe
System
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Deployment
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Deployment/2.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
AxMSTSCLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/Remote%20Desktop%20Connection%20Manager/AxMSTSCLib.DLL
MSTSCLib
Assembly Version: 1.0.0.0
Win32 Version: 1.0.0.0
CodeBase: file:///C:/Program%20Files%20(x86)/Remote%20Desktop%20Connection%20Manager/MSTSCLib.DLL
afvxqrqi
Assembly Version: 2.0.0.0
Win32 Version:
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

I am experiencing the same sort of problem with RDCman after my laptop installed Windows updates last weekend so it is probably caused by a recent .net framework update, not sure which one it is yet, has to be one of last weeks updates for sure.
See below for the detail log:
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
   at RDCMan.RdcSettingsProvider.SetPropertyValues(SettingsContext context, SettingsPropertyValueCollection values)
   at System.Configuration.SettingsBase.SaveCore()
   at System.Configuration.SettingsBase.Save()
   at System.Configuration.ApplicationSettingsBase.Save()
   at RDCMan.Preferences.Save()
   at RDCMan.MainForm.AutoSaveTimerTickHandler(Object sender, EventArgs e)
   at System.Windows.Forms.Timer.OnTick(EventArgs e)
   at System.Windows.Forms.Timer.TimerNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5466 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
RDCMan
    Assembly Version: 2.2.2.426
    Win32 Version: 2.2.2.426
    CodeBase: file:///C:/Program%20Files/Remote%20Desktop%20Connection%20Manager/RDCMan.exe
System
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Windows.Forms
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5468 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5467 (Win7SP1GDR.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System.Xml
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
System.Configuration
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Deployment
    Assembly Version: 2.0.0.0
    Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
    CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Deployment/2.0.0.0__b03f5f7f11d50a3a/System.Deployment.dll
AxMSTSCLib
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/Remote%20Desktop%20Connection%20Manager/AxMSTSCLib.DLL
MSTSCLib
    Assembly Version: 1.0.0.0
    Win32 Version: 1.0.0.0
    CodeBase: file:///C:/Program%20Files/Remote%20Desktop%20Connection%20Manager/MSTSCLib.DLL
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
    <system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.

Remote Desktop Connection in Windows 8

Hi, I can't seem to figure out how to make my local drives available when using the app Remote Desktop Connection on my Windows 8. All the instructions I found on Microsoft do not apply to Windows 8 http://technet.microsoft.com/en-us/library/cc728050(v=ws.10).aspx
. Or else I can't find this "Options" tab they're talking about.

The program doesn't come up in a window anything like that. It's full screen with only the option to connect to a server. And in settings there are no options that resemble that.
Hi,
Could you please snapshot about RDC with us? Mine is shown as below
Yolanda Zhu
TechNet Community Support

Remote Desktop Connection Mannager

I know this is a long shot, but is possible we will see an updated version of this handy application. I use this more then anything else, well besides RSAT and would love to see this updated. I have yet to install the old version as I havent enabled
.net 3.5 yet but will be doing so tomorrow.
Dusty

Hi,
I also found Windows 8 is not in the supported list of the latest Remote Desktop Connection Manager; please check if it works. Meanwhile, do you mean .Net 3.5 caused issue to Remote Desktop Connection Manager? If so, please also let us know the details.
Remote Desktop Connection Manager
http://www.microsoft.com/en-us/download/details.aspx?id=21101
Thanks.
Nicholas Li
TechNet Community Support

Dymo Labelwriter printers not working via Mac Remote Desktop connection into Windows Server 2008

I'm having a really hard time getting Dymo labelwriters (models 335 turbo and 450 turbo) to work over a remote desktop connection and I'd appreciate any help you can offer.
To briefly describe the situation, I'm working for a Doctor's office, moving their IT from a remotely-hosted environment where employees connect to their Windows Server 2008 virtual machines (hosted off-site) via Windows 7 machines through Microsoft's remote
desktop software.
The new setup will have new servers running in-house instead of remotely and will be based on Apple's Mac Mini machines running Windows 7 for some tasks through Parallels virtualization
software running directly on each employee's Mac Mini.
We have 3 of the Dymo 450 Turbo products and one 330 Turbo, each connected directly to a Mac Mini.
Here's the problem: I have Microsoft's Remote Desktop software running on the Macs natively, connected to each employee's virtual machine on the remote server for now, until the time comes to make the switch to using the new in-house server. The remote desktop
software works fine - employees are able to connect successfully and access their desktops fine. I have the "Forward Printing Devices" option checked in the Microsoft Remote Desktop app so that the hosted virtual desktops can see the local labelwriters.
However, the Dymo Label software running on the remote server will not recognize that a labelwriter is present.
If I go to the Printers and Devices window on the remote server, the labelwriter shows up fine, named "dymo labelwriter 450 turbo (redirected 10)" however running the Dymo Label software gives an error, "Dymo label says no printer connected:
dymo label printer requires a dymo label printer be installed and connected ..."
To try and narrow down the cause of the problem, on the same Mac, I ran Windows 7 via Parallels and set up a new remote desktop connection within that Windows VM. Just to be clear, instead of using the RDC software running in the Mac OS, this new connection
is using a Windows virtual machine running on the same Mac, with the RDC being established from within that Windows VM. Again, I forward printing devices and the labelwriter shows up in Printers and Devices on the remote server as "dymo labelwriter 450
turbo (redirected 10)" This time, the Dymo Label software recognizes the attached labelwriter and runs fine.
I'd appreciate any advice you can give on why, as far as the remote server is concerned, a forwarded labelwriter from Microsoft remote desktop running natively on a Mac isn't recognized
but it is if forwarded from within Windows, bearing in mind that the labelwriter shows up on the remote server in both instances and is called the same name in devices and printers.
Sorry for the long-winded question. I hope you can help me.

Hi,
Thank you for posting in Windows Server Forum.
Firstly please check whether you have driver capable for your printer with MAC MRD. Also I would like you to check with updated MRD version 8.0.9 for MAC OSX.
https://itunes.apple.com/in/app/microsoft-remote-desktop/id715768417?mt=12
Because as you have commented it can work with windows RDP, so please also try to contact Dymo Labelwriter printer and inquire regarding the issue.
Hope it helps!
Thanks.
Dharmesh Solanki
TechNet Community Support

Windows 7 remote desktop connection cannot logoff the local user

Windows 7 remote desktop connection cannot logoff the local user
Remote Desktop connection:
(This experience is from Windows 7 remote to Windows Embedded Standard 7 computer)
I used Remote Desktop to try to log on to a Windows 7 (WES7E) computer and someone is already logged on locally (Console Session), I saw a message like this:
"Another user is currently logged on to this computer. If you continue, this user has to disconnect from this computer. Do you want to continue?"
I click on Yes.
Then I saw "Please wait for [username] to respond". No action from the logged-on local user, I waited for 30 seconds, then I was able to login the computer and at the same time was able to disconnect the logged-on local user.
Question:
1. "Another user is currently logged on to this computer..." message doesn't show me the actual logged-on user name. Is there any way to show the user name in this pop-up message?
2. After waiting for 30 seconds, I was able to login the computer and the logged-on local user is disconnected, however this local user is never been logged-off. I wanted to logoff the local user (with Console Session) when I made the connection remotely
to the computer from remote desktop (Just like Windows XP) Is there any group policy can change the behavior?
The policies I have looked at are:
Local Computer Policy | Computer Config | Admin Templates | Windows Components | Remote Desktop Services|Connections|Deny
logoff of an administrator logged in to the console session => disabled
Regards,
Mei Davis

Hi ,
These behavior is by design. There is no way to change that. Thank you for your understanding.
Best Regards.
Tracy Cai
TechNet Community Support

My external hard drive won't show up on the desktop!!

Alright!
I bought a 250Go external hard disk at the same time as my alumnium iMac around september 2007. Since then I had no problems.
I also created partitions on my hard disk:
1 - Mac = Mac OS extended (Journaled) 202 Go
2 - PC = MS-DOS (Fat) 30 Go
When I turn on on my hard disk, both icons usually appear on my desktop but since yesterday, ONLY my PC icon appear.
I went in the Disk Utility and it seems that the MAC partition is always here but won't show up on the desktop. It's like it's become invisible or something.
Should I be worried? Because I use the MAC partition to back up all my files with Time Machine.
I find it annoying so anybody can help me out? Thanks!!

Patrick, I have same issue with my (Intel) MacBook's internal HD. Tried your Script solution but recv'd Systems Events ERROR "Can't set disk "MacBook HD" to true".
The (missing) HD is Boot Camp Partitioned and running Fusion. BTW, Fusion/WinXP will no longer open - "File not Found" error. Also, I didn't immediately notice the disappearance because my MacBook started booting from one of ext HD's (w/o me changing the startup drive).
Any ideas greatly appreciated. I haven't tried the Terminal solutions posted since I'm not Terminal savey.

Users not showing in Terminal Server Under Remote desktop services manager and Task Manager

Hi All,
I have a problem here in Terminal Server. I can not see the users logged in to Server but i know users are accessing the files and currently working.
1. From the Task Manager-- Show processes from all users displayed all the processes accessing by users.
2. From the Task Manager-- From Users Tab--No users list at all
3. From the Command Prompt- Query users-- No information
4. From the Remote desktop services Manager-- used with IP/Host name-- Still can not see the users list and processes. So i can not kill the session if needed.
Enviroment:
TS CALS 20 currently accessing 15 users
VM-WARE GUEST: 2008 RS Terminal Services/Remote Desktop services installed
Windows up to date-- Just updated last month
Problem is here for long time. Just couldn't find the time to trouble shoot.
UMESH DEUJA MCP,MCTS,MCSA,CCNA

Hi,
Thank you for posting in Windows Server Forum.
As you have tried many steps, I suggest you to try below command line and power shell command if successful in your case. Please try below command with Admin access:
qwinsta /server:<servername>
To kill a session use rwinsta to delete the session specifying the ID number:
rwinsta /server:computer01 3
Here's the list of command line tools for Remote Desktop Or, you can use PowerShell:
Get-RDUserSession and Disconnect-RDUser
Please check the list of Power Shell command from
this link.
Hope it helps!
Thanks,
Dharmesh

Bug report: Under Remote Desktop Connection, local units and resources menu has OK button missing

I've noticed that the "Local units and resources" in Remote Desktop Connection is missing an OK button. It seems to be a localization issue because I changed my Windows profile language to English, logged out and back in again, started RDC and
the Ok and Cancel button became visible. Changed my language back to Norwegian again and the buttons are gone again.
I have also confirmed this by testing the same on a clean new installation.
Temporary Work-around: Select an option, press tab-key once (it will select the OK button which you cannot see), then press Enter.

Hi,
Based on my test,I got the same result.
Thanks for your feedback.
We will submit this issue to Microsoft product team.
Regards,
Kelvin Xu
TechNet Community Support

TS1398 After updating to iOS 7 my iphone 5 won't show any wifi networks or connect to any wifi even after resetting the network connections. HELP!

After updating my iphone 5 to iOS 7 my phone won't show any wifi networks or connect to any. I reset the network connections and still nothing.

I Just found it on the apple site, it arrived on a cd a few days later and worked just fine again.
i would recommend backing everything up just in case. Better safe than sorry, trust me. I've lost so much when i didnt back up once when re-installing the system.
IT shoulldnt erase everything, bt it might, so back up just in case
should you loose everything, then i have some tips on moving stuff fromyour iphone/ipod to the computer

Local printers won't show up in Remote Desktop Connection Manager 2.7

Similar Messages

Maybe you are looking for