I have 2 servers. The DC/AD server is SBS 2008 and the Terminal Server is Standard 2008 (SBS 2008 cannot run Terminal Server). I have it working so AD users can log in to the Terminal Server (finally) but am having issues getting all clients to connect. Remote Desktop settings on the Terminal Server are set to Allow Any client (less secure). The only two machines that can login with a domain user are the SBS 2008 server and one other Mac with RDC. My Mac which is connected via VPN won't work and neither do any of the other Macs on the network.
Trying to print in MAC while using RDC in a Windows 2008 Server. The Windows Clients get the printer sessions correctly. The MAC, using MAC RDC 2.0.1 do not get those printing sessions. Users can connect to NuoRDS Server using a standard Microsoft RDP Client for Windows, Mac, iOS, Android or any other RDP compliant device or software. List of supported features may vary depending on RDP Client software.
![Services Services](/uploads/1/2/5/3/125381643/465302822.png)
They can connect with the local admin user but not a domain user. I'm so close to completion. Have tried logging in with different domain users and same thing happens, I don't think it's a user thing. Went through the guide for GPO and have it linked to the TS group. Added loopback policy, no change but now my local admin can't even login, says I need to be a member of the Remote Desktop Users group/allowed through Terminal Services. How do I add a local user on the TS server to the remote login group on my AD box?
THe admin is already a member of the admin group on the TS server which should have remote desktop access by default. Although my Domain Admin can still login and do Shutdown/Restart I discovered. Have tried updating RDC on the Macs but no luck. ISSUES: Again, only my AD box and one of the Macs can connect with domain users. All others fail even though they are on the same subnet and using the same version of RDC for Mac. This is what's so baffling to me. Why can 2 connect but none others?
I have a 5 user TS CAL and have tested with no more than 2 at a time so it's not licensing.
Not even the official Microsoft RDP Client for OS X supports this; in fact that product still cannot do Terminal Services Gateway connections that were introduced with Windows Server 2008 But the answer to your question is, yes there is at least one client that promotes full RemoteFX implemetation in their OS X client (and incidentally also TSG), and that's. It is a commercial program however there is a trial version available from that page. Update: it looks like iTap don't fully support RemoteApp The only other client I can find is one by Thinomenon.
Supports all versions of the RDP protocol up to 7 (RemoteApp requires 6.1 or greater) Enjoy latest RDP features, including application publishing (RemoteApp or RAIL), even if your platform is not supported by Microsoft. Product Features: - RDP 4.0, 5.0, 5.1, 5.2, 6.0, 6.1 and 7 -compatible, - Copy and Paste via clipboard, - Encryption for communication security, - Local audio.
I just tried iTap Mobile RDP and I cannot make it work as a resizeable window. If I open the same.rdp file I use on Windows, it lauches full scheen, and if I switch to non-fullsecreen mode, there is not a seemless resizing connection among the Windows application window frame and the Mac window frame. MOreover, if I launch a Windows Explorer from the Windows application, its the Explorer window is not a Mac Window by itself, but instead is confined within the application's window. Is there any iTap Mobile RDP setting that I am missing? – Sep 7 '12 at 9:54.