If an unlicensed client connects to a Terminal Server for the first time, the Terminal Server issues the client a temporary Terminal Server Client Access License (CAL) token. After the user has logged into the session, the Terminal Server instructs the License Server to mark the issued temporary Terminal Server CAL token as being validated.
Is there any Mac OS software that supports properly Windows Terminal Server RemoteApp? By Properly I mean with an experience comparable to Windows Remote Desktop, that is, the Remote App Window is resizeable, etc, as if it was just another application.
Most tools (RDC for Mac, CoRD) seem to simply open a desktop for the application, but it does not have a truly windowed behavior.
Stu Wilson
7 Answers
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
- Mac Remote Desktop Client As you can see in the above pictures, you specify the port as part of address by using a colon. You should now know how to connect to a Terminal Server or Remote Desktop.
- It was all working on our old Windows 2003 terminal server before we moved everyone over to Windows 2012 R2 RDS server. The RDS server is running as a Hyper-V VM on a Windows 2012 R2 server with the bandwidth management disable for the VM.
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 iTap Mobile RDP. 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. Their free client supports all versions of the RDP protocol up to 7 (RemoteApp requires 6.1 or greater)
CajunLukeAnother RDP client for Mac is Ericom Blaze. Blaze supports application publishing. It also accelerates RDP, which can be especially useful if you are connecting to graphics files like PDFs or Flash movies.
Please note that I work for Ericom
I'm one of the authors of iTap mobile RDP. Our next version (1.2) will support Remote App and also fetching the published applications feeds from remote app manager.
If you are interested in getting a beta version, please drop us a note at support@itap-mobile.com
-Peter
It looks like Microsoft has released an Remote Desktop Protocol (RDP) client with full-support of RDP sessions including RemoteApps.
The newest version does not support RemoteApp that you host yourself. It only supports Azure RemoteApp (preview).
Graham MilnThinomenon Remote Desktop Client is working well for us.
We're looking for long answers that provide some explanation and context. Don't just give a one-line answer; explain why your answer is right, ideally with citations. Answers that don't include explanations may be removed.
check Thinomenon Remote Desktop work fine remoteapps WS2008 in mac Mountain Lion
I can't say when Microsoft Remote Desktop for OSx/Mac OS started working with RemoteApp. But, as of March 2018, it does.
You must log in to answer this question.
Not the answer you're looking for? Browse other questions tagged windowsremote-desktop .
This is my first implementation of Remote Desktop Services/Terminal Services; we are using it as a solution for Mac clients that need to run a piece of new Windows-only software.
My question is about streamlining the user installation process. We don't have a directory service that extends to the Windows Server at present, so I need to temporarily activate these accounts with an admin-defined password, and force the user to change their password at first login.
Unfortunately, the relevant checkbox in user management does not seem to be a workable solution... the Mac client as well as the windows RDP client fail to log in.
(Perhaps I am missing something here? We only have the RD Session Host installed so far; I'm not sure what the purpose of the Gateway Server is in our implementation. Maybe one of these solve the password reset issue? I am using the new 'Microsoft Remote Desktop' client available from the App Store, but see the same behavior with the old RDC app.)
Ideally I would like the user to be able to log in with my provided credentials, and be immediately prompted with a password change dialog. I already have a batch file running at first login, and was hoping for something that could be implemented there... the farthest I've gotten is control /name Microsoft.UserAccounts, but I'm unable to figure out how to drill down into the 'Change your password' screen.
I was also considering net User %USERNAME% * until I realized that has to be run as Admin, which the batch file is not.
It's almost certainly going to be difficult to extricate myself from the client setup process in the first place, so one final alternative I've been considering is to randomly generate secure passwords on my own, and save the user's to his or her OS X Keychain when I install -- effectively making the server login transparent.
Any wisdom from more experienced admins about how I should go about this?
NReilinghNReilinghMac Terminal Program
1 Answer
Mac Terminal Download For Windows
The only thing here preventing the 'automated' password change is the requirement for Network-Level Authentication. As long as the Remote Desktop server allows connections without NLA, the password changing functionality will work fine in either the Mac or Windows clients.
The client can still connect using NLA once the password has been changed, but the password change itself requires that a session begin without having been authenticated--NLA takes place before the session begins, and must use a valid login. Logins marked 'User must change password at next logon' are considered expired, i.e. not valid, so they cannot be used to Network-Level Authenticate a session.
To allow non-NLA sessions, open RD Session Host Configuration and double-click the RDP-Tcp connection. The checkbox for NLA is in the security Section of the General tab.
NReilinghNReilingh