Universal or alternativ Remote Desktop Connection client

Hi everyone,
I was wondering whether one of you, know of a better and maybe even in Universal of the Microsoft 'Desktop Remote Connection' client.
It's because I have an Intel iMac, and remotes my company desktop, but the DRC application are a bit slow in screenupdates and key strokes compared to the Windows client. I am guessing that it as to do with the Rostatta layer, which slows the application.
Any surgestion?

Hi,
I wasn’t able to find group policy setting to optimize memory usage for Windows Server 2012/2012 R2, could be due to its added new features need to consume more memory.
Besides, memory usage of remote desktop connection depends on the programs running within the session, you may try to check programs those are open within different sessions to determine which one is causing too much memory.
If memory usage is abnormally high, please keep systems fully patched.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Similar Messages

Remote Desktop Connection Client 9.3.9600 unable to connect to Server 2012 RDS via Gateway

Hi,
I have a Windows Sever 2012 R2 RDS environment with two Gateways servers configured in high availability mode (RD Web Access, RD Gateway, RD Connection Broker roles installed) and four Windows Server 2012 R2 RDS Session Hosts. The servers are all running
the most recent public server updates. With this configuration I when connecting externally using a Windows 7 computer with the older Remote Desktop Connection client (6.1.7601) I am able to connect without any problems however when I try connecting with a
newer client from a computer running Windows 8.1 and the 9.3.9600 client I am unable to connect.
At the moment a NAT rule is configured to pass 80/443 traffic to only one of the RDS gateway servers, I've removed our load balancer from the configuration for the moment to reduce the complexity.
No error is generated by the client when it tries to connect it just stops trying to connect after a while.
On the Gateways servers event logs for
Things I have looked into so far.
- I've double and triple checked the RDS configuration and checked it against one of my other clients configurations that is working and they are identical.
- Connecting from an older client version works fine.
I'm not sure what else can be checked does anyone have any ideas?

Hi,
1. What entries are you seeing in the RD Gateway's log? Event Viewer\ Applications and Services Logs\ Microsoft\ Windows\ TerminalServices-Gateway
2. How come you are not forwarding UDP port 3391 in addition to TCP port 443? It should work without UDP, but you will not have UDP support which is one of the benefits of RDP 8.0/8.1.
3. Are there any non-default group policy settings being applied to the servers and/or client PCs? To be clear, I'm asking if any changes have been made to the default local and domain security policies, group policy objects, new GPOs that may have
been added, etc., that are applicable to the servers and or client PCs.
-TP

Microsoft Remote Desktop Connection Client for Mac Not Working

I recently purchased Office 2011 for Mac. I work at home on my Mac at work on Windows 7. I also have a work laptop, running Windows 7, that comes home with me. My goal is to RDC my Mac to the laptop running Windows 7 to reduce desktop clutter, and easily work between machines.
I CAN NOT FIGURE OUT how to get Microsoft RDC:mac to connect to my pc.
I know that the pc allows remote desktop connections because I often use RDC at work from PC to PC.
SOME PLEASE HELP! I have spent hours and hours trying to figure this out and I think it is the time capsule that is causing the problem.
My research has found that I have to use port 3389 to get this done. I am pretty computer savy but when it comes to networking I guess I have no clue. I have tried just about everything a and can't figure it out.
Thanks to anyone that can dedicate some time to configureing my time capsule to allow for RDC.

I cannot quite put together your whole network..
I work at home on my Mac at work on Windows 7. I also have a work laptop, running Windows 7, that comes home with me. My goal is to RDC my Mac to the laptop running Windows 7 to reduce desktop clutter, and easily work between machines.
So this is in local lan.. the PC laptop running win7 and the Mac loaded with RDC software. If this is local lan then the issue is nothing to do with TC.
That is only if you are trying to connect from work. to home through the router at work and TC at home. On local lan there is no blocking to ports. Are you using the local network IP of the PC Laptop?
Explain a bit further as it needs a bit more clarification.

Slow Microsoft Remote Desktop Connection client

Hi Everyone,
I was wondering whether one of you, know of a better client of the Microsoft 'Desktop Remote Connection' client for Mac OS X.
It's because I have an Intel iMac, and remotes my company laptop, but the DRC application are a bit slow in screenupdates and key strokes compared to the Windows client. I am guessing that it as to do with the Rostatta layer, which slows the application.
Any suggestion?

It is like that on my first gen G5 iMac as well. It is just part of how the program operates and has nothing to do with Rosetta.
It also works slow like that - but less so - when I try to use RDC to control a PC I have set up as a file server from my other PC.

Remote Desktop connection and retina display

I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop. it's really important that that this staff works as good on my new computer. The problem is that when I open the connection on MacBook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, making it bigger or smaller but the display is still not great. Any suggestions or advice would be greatly appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resultion settings, still the same.
Any suggestions/help would be much appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resultion settings, still the same.
Any suggestions/help would be much appreciated.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, still the same.
I've been trying to set up my new MacBook Pro [with Retina display 2015 edition]. I use a lot of university software via Remote Desktop connection, it worked very well on my Acer laptop and it's vital that this staff works as good as on Windows machines.
The problem is that when I open the connection on MacBoook the display is not great - I can see pixels, just like my grandmas' TV from the 1970s. I tried with different resolution settings, still the same.

Should I assume from your reply that the solution lies with my corporate IT?

Remote desktop connection lost due to intel?

Since some time i cannot get my intel-macbook connected to my work's windows network through remote desktop connection (version 1.0.3), while i still can do so with my g5-imac. So the network does not seem to be the problem.
It used to work but now it doesn't anymore. Tried reinstalling the program, reinstalling mac os, used bin and hqx, downloaded with safari, firefox and internetexplorer, but it dos not help. Appel support directed me to this forum an window's support wouldn't talk unless i paid 300 euro's (for support on a free dowloadeable program!!).
On window's mactopia site it says "Stability is also improved (...) when Remote Desktop Connection Client is used on Macintosh computers with PowerPC G5 processors." But is the opposite true: does it not work on intel?
Who can help me out?

First, RDC does work for many folks on Intel Macs. It does have problems with printing but for the most part it's stable.
What exactly doesn't "work"? What do you see when you try to connect?
You should troubleshoot by creating a new Mac OS X user account and trying to use RDC within that account to connect to your Windows machine. If that works then you have some corrupt preferences and those are relatively easy to locate.
If you're still unable to connect then you have something at the system level that's hindering your connection. Turn off your firewall for starters. Try logging in with the Shift key held down so that you don't have any extraneous applications blocking your connection.
Finally, if your G5 works and your Intel Mac doesn't then you might want to move one machine to the other machine's network connection and verify you have the same connectivity. And verify all of this by using the same user name and password from both Macs.
Hope this helps! bill
1 GHz Powerbook G4 Mac OS X (10.4.9)

Apple Remote Desktop - connect to computer after their password changed?

I have a problem with Apple Remote Desktop which is driving me up the walls.
When I observe or control a computer, Apple Remote Desktop saves the username and password so that next time I'm not prompted for a username or password.
Problem is, when the password on the computer changes and I once again try to control it, Apple Remote Desktop simply comes up with an "authentication failed" message. There is no option to put a new username and password in. I cannot find any option to delete previously stored passwords.
Currently I'm resorting to deleting:
/private/var/db/RemoteManagement/ClientCaches
/private/var/db/RemoteManagement/caches
It is extremely frustrating doing the above each time a computer's password changes!
I must be missing something. Does anyone have a better way of going about this?

Hi Zachary!
Have a look at RealVNC at http://www.realvnc.com/download.html. Install this on your Windows computer and be sure to configure a password for VNC connections. You should then be able to see your XP system in Apple Remote Desktop.
Keep in mind that the VNC software is free (unless you choose to purchase a version with more features) but the Apple Remote Desktop client is a commercial product http://www.apple.com/remotedesktop/.
If you need a different (free) client for your Mac, I suggest using the Microsoft Remote Desktop Connection client found here http://www.microsoft.com/mac/otherproducts/otherproducts.aspx?pid=remotedesktopc lient. This only works with Professional version of Windows XP and not the Home version. Or you can downlod a VNC client for Mac such as Chicken of the VNC found here http://sourceforge.net/projects/cotvnc/.
Hope this helps! bill
1 GHz Powerbook G4 Mac OS X (10.4.4)

Remote DeskTop Connection on iMac OS X (10.6.5)

I am using RDC into work. I also have a need to use my system as do others in my home. We have 3 user accounts on the iMac and when I walk away I would like to log out of my account so others can use the system. Is there a way to do this keeping the RDC connected in the background?
Thanks
Steve

If you are referring to Microsoft's Remote Desktop Connection Client for Mac, that's a different product. As such - this forum being specifically for Apple Remote Desktop, Apple's software for managing networked Macs - you might have more luck getting suggestions if you ask in Microsoft's own forums.
Good luck.

UAG SP4 and Windows 8.1 Remote Desktop Connection 8.1

Hello,
I found on the description of SP4 for UAG the following: "Remote Desktop: Forefront UAG SP4 supports the Remote Desktop Connection (RDC) 8.1 client." Does that apply to the publication of servers using "TS Client Tunneling
(Windows Vista/Windows XP)"?
When I use my Windows 8.1 32bit client to connect to the portal, I can see the published application, click on the icon that is on the portal and it start the SSL Application Tunneling and the SSL icon appears at the Taskbar. Then it opens the "Remote
Desktop Connection" client. However when I type the name or IP of the machine to what I want to connect, it fails. Is something wrong? Or this is not working on Windows 8.1? My windows 7 cliesnt have no problem to connect using this application.
Thank you!

Hi Rob,
Let's confirm some situation:
Did you mean connect to Windows 7 from Windows 8.1 computer?
Did you mean the printer connect to another Windows 8 computer at home, and shared to that Windows 8.1 or the printer connect to that Windows 8.1 directly?
Firstly double check your settings:
1. Launch Remote Desktop Connection.
2. Click Options, and then click the Local Resources
tab.
3. Under Local devices and resources, select the Printers check box.
After that make sure that the proper printer driver version is installed on the remote computer.
Meanwhile, refer to this thread to check the port:
http://answers.microsoft.com/en-us/windows/forum/windows_7-networking/win-7-remote-desktop-and-local-printing-not/544acb1b-a259-4170-bc05-2c6dbfd0ca05
Karen Hu
TechNet Community Support

Keyboard layout under Remote Desktop Connections (US-International)

Hi,
I'm using Microsoft's Remote Desktop Connection on Mavericks 10.9.3 to connect to a Windows 7 machine using the US-International Keyboard layout, but some keys don't seem to work (quote, double quote, ~, etc.) The Mavericks machine is set up as Language English / Region UK / Input Source US International - PC. The Windows 7 with Language English (UK) / Keyboard US International.
Any ideas?
Cheers,
Luiz
P.S.: A similar question has been raised for Mountain Lion a couple of years ago, but the solution provided was to use an external software that is not compatible with Mavericks

Even though it works under Lion, I never tried it under ML, Microsoft states
Note Microsoft Remote Desktop Connection Client for Mac (version 2.1.1) is not intended for use with Mac OS X v10.7 (Lion) or later.
So I dropped it and now I am using CoRD.

Remote Desktop Connection Server 2012 Clients only using on DC as Logon Server.

I am using Server 2012 and have an RDC Server running on a VM. Originally I had ordered the licensed version as Essentials was provided to me which does not allow for a full domain environment, which is required for the RDC server. Anyway, I
used Eval versions to get started, not thinking or realizing that the DC would never be able to get Activated since it is an Eval. So after 4 days I have finally, loaded Server 2012 on a new VM, promoted to DC, Transferred FSMO roles...DNS is up and
replicating across both DC's. The Eval keeps shutting off and was going to demote it and remove, but whenever it is shutdown the Clients receive a "No Logon Servers are available " error. I start up the old DC and it works. I doublechecked
all of the roles have been moved, I checked the RDC gateway, everything points to the same Domain information, but when I check an account using 'CMD set' it shows the old DC as the Logon Server. Is there something I am missing in the RD Gateway or somewhere
else. Is there a way to force it to use the new DC? I have tried setting the options in remote desktop connection to use a particular TS Gateway setting and it doesnt seem to work. Can someone please help me think about this and offer a
suggestion or let me know if you need more info. I can figure nothing else out at this point.
Thanks so much in Advance.
-T

it sounds like your clients / rdc servers may still be pointing to the old DC for DNS.
Can you check you have updated DNS on the clients to talk to your new domain controller.
Regards,
Denis Cooper
MCITP EA - MCT
Help keep the forums tidy, if this has helped please mark it as an answer
The new DC is the only DNS server listed on the RDC Server and is the only DNS listed for the clients other than the gateway which have as a secondary. If I change the static on the old DC I cannot login, as soon as I put it back, I can login and it
shows that DC as the logon server.
I did a simple recursive test on both DNS servers....The new Domain Controller passes, the Old One which I am trying to remove, does not.
I will reply with any other updates as I continue to look into this and thanks for the suggestions.
So I also Pinged the domain from the RDC Server as suggested and it replies back with the old DC IP.
Not sure why.

T5325 Thin Clients losing remote desktop connection

My company just bought about 50 of these thin clients and they are setup to run an automatic remote desktop connection. I have the connection setup to auto start when the thin client is powered on and it just brings the user to a windows login screen. After they have logged in and leave their thin client to go on break sometimes it just brings them to a blank screen with an HP logo and the thin client has to be restarted to get back into the remote desktop, or I have to go into admin and restart the RDP connection. Any idea why this is happening? Is there a setting somewhere I need to change?
Any help would be great!

We are having this same issue and it is maddening. I have contacted HP on several occasions and I don't know if it is the language barrier or simple ignorance, but so far the issue is ongoing. I have looked high and low on the net and no one seems to be able to tell me why this is happening despite a number of plausible theories. We have a couple hundred terminals throughout the company which are spread across three servers none of which are close to congested yet.. However, the 10 or so t5325's we have are used specifically for digital signage. They run automated sessions that launch animated JAVA windows. They run great for the most part, but seemingly at random they will freeze in their tracks. The sessions drop from our terminal server and cannot be restarted remotely. After the units are power cycled they come back up directly and begin their sessions again. You can shadow these units (VNC) and the moment the display come on the unit closes the RDP session and reopens the same and start running again, odd behavior. I have tried changing session logout timers, disabling / enabling TCP settings, creating client-side refresh scripts, restarting the sessions at regular intervals via admin script, flashing BIOS and ThinPro OS to the current level, voodoo rituals, and pagan sacrifice. Yet, they still behave in exactly the same manner with no actions on my part having any apparent affect.. Currently, I am of the mind to purchase small all-in-one pc's to do the job. If anyone knows of any way to fix this PLEASE respond to this post.

Missing cbclient.h - Remote Desktop Connection Broker client API

Hi,
I am searching for cbclient.h, which is referenced in the "Remote Desktop Connection Broker client API" documentation:
msdn.microsoft.com/en-us/library/hh769100/
However, I could not find cbclient.h in any Windows SDK (I searched in the Windows 7, Windows 8, Windows 8.1 SDKs).
I found a question on these forums from 2012 asking for the same thing, but there is no public answer:
http://social.msdn.microsoft.com/Forums/windowsdesktop/en-US/9b51f493-2b32-4feb-a62b-bc74aa163460/remote-desktop-connection-broker-client-api-headers?forum=windowssdk
Where is cbclient.h, and why is it missing if it is referenced by the public documentation?
Thank you!

Did you ever get a response?

Easy print not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1

Easy print is not working on a 64 bit Windows 8.1 client with Remote Desktop connection version 8.1 . Printers dont get redirected when you connect to the terminal server. The server we are connecting to has Windows 2008 server. On 32 bit Windows
7 and windows XP clients Easy print is working fine and printers get redirected in terminal server.

I am having the exact same problem. Windows 7 works fine, but 8.1 will not redirect printers. Others said to check local policy terminal services settings and my setting are all set as they should.
I think Windows 8.1 is not telling the terminal server what printers it has.

Server 2012 RDS - Remote Desktop Connection Broker Client failed to redirect the user domain\username. Error: NULL

Seeing the error listed here.
The Remote Desktop Connection Broker server could not enumerate the targets for the provider named NULL from the database.
Pooled virtual desktop collection name: NULL
Error: Error code: 0xFFFFFFFF.
Broker and Hyper-V are on the same physical machine.
Any ideas on where to start troubleshooting this?
Used the happy wizard to create everything, and got no errors.
I have created a small pool collection, and given rights to domain users. Everything "looks" good.

I have the same problem.
(Making this long hand for those who come after)
I have installed SQl Management Studio Express 2012 SP1
http://www.microsoft.com/en-us/download/details.aspx?id=29062
(You only need the one file "SQLManagementStudio_x64_ENU.exe")
Ran this as Administrator
And typed in the Server Name field
\\.\pipe\MICROSOFT##WID\tsql\query
Then hit connect.
Expanded Databases (+sign)
Expanded RDCms
Expanded Tables
Right Clicked on rds.target, select Edit top 200 rows
Right Clicked and copied, then pasted this into a notepad file on the desktop (As a backup)
Right Clicked and selected Delete to delete the row with the data in it (and PoolID was set to Null in this row)
Did the same for rds.pool
Manually added Remote Desktop server into the MEMBER OF tab of
“Windows Authorization Access Group” via Active Directory Users and Computers. As this domain was Windows 2003 Native when the RDS server was first installed.
Rebooted server and same issue>
Checked SQL again and rows had come back.
Is that what you meant by "delete
the rds.target and rds.pool with pool id = NULL"?
Not a SQL guru, so any help appreciated.

Universal or alternativ Remote Desktop Connection client

Similar Messages

Maybe you are looking for