Remoteapp на mac os
The following forum(s) have migrated to Microsoft Q&A: All English Windows Server forums!
Visit Microsoft Q&A to post new questions.
Answered by:
Question
I’ve successufully installed TS 2008 with RemoteApp, so users are able to start applications from TS server through RDP tunnel. Problem apprears on MAC laptops: they are able to open file share with .rdp applications, but when they select it it opens Remote Desktop, not RemoteApp.
How to publish any applications for MAC users? Maybe publish it through Web Access? If yes — how I can do this?
Answers
Tthe MAC client supports RemoteApp connections.
However you can post your question here to confirm :https://connect.microsoft.com/macrdc/content/content.aspx?ContentID=5893&wa=wsignin1.0
«The MAC client supports RemoteApp connections.»
How? When I started something.rdp (published application through Terminal Services 2008) MAC opened RDP, not application.
All replies
Tthe MAC client supports RemoteApp connections.
However you can post your question here to confirm :https://connect.microsoft.com/macrdc/content/content.aspx?ContentID=5893&wa=wsignin1.0
«The MAC client supports RemoteApp connections.»
How? When I started something.rdp (published application through Terminal Services 2008) MAC opened RDP, not application.
Hi James
I know this is backtracking slightly but I am currently using TS 2008 and with Web Access for our PCs it works perfectly but I cannot get the Macs to connect at all! You mentioned that anything you try to open for the macs it opens in Remote Desktop. How can you get it to do this?
For myself on a mac I get nothing at all appearing
Any help would be very much appreciated!
Many Thanks
Mike Donaldson
I ran into the same issue as well, the remoteapp worked fine on the Windows side but would load the desktop for the MACs. I found that if you edit the .rdp session with the Mac .rdp client that you can find the Applications portion of the edit and put the path where the packaged program is: ex: c:\program files\ packaged programs.
Now when you launch the .rdp session it will just open the app you want instead of load a desktop session.
Hope this is what you were looking for.
Fravocado,
My organization has been trying to get RemoteApp to work for our Mac clients but have so far been unsuccessful. We have tried editing the .RDP file with numerous paths to the applications we want but it always loads the full desktop session. Would it be possible for you to copy/paste that section of your .RDP file so we can see what exact syntax you are using? Also was there any other special settings you had to use on the server itself? Any help would be greatly appreciated!
I got it to work this way: I created the .rdp from the remote app that I desired. create your .rdp as normal and test with your PC, it should only open that app. Now take the .rdp from C:\program files\packaged programs and copy and paste it to your mac to edit and test. Open RDC 2.0 on the mac and go to File > Edit a Connection. Point it to the .rdp file and it will open a screen showing you what you can edit. Now click the applications portion of the menu and check the box that says «start only the following windows applications» the rest should be fine. You can also specify the domain if you are using domain logins. Save it and test.
Wow that worked perfectly! Thank you so much for your help. =D
Wow that worked perfectly! Thank you so much for your help. =D
Has anyone else had success getting TS RemoteApp to work for Macintoshes?
Travis L. Grundke Ashton Technology Solutions, Inc.
That works for me but, as you said, I’ve also a background; on my Windows PC I don’t have it. Do you have resolved this ?
Thanks a lot and receive from FRANCE a merry Christmas and happy new year 2011.
In a same manner, I want to list a directory and the files inside. I put a program in remoteApp which is c:\windows\explorer.exe. This works with a PC but with my MAC (rdp file) I receive an error «Access denied». I don’t know why. If you have the solution.
I reply to myself: I have found a software (name: FreeCommander); it works, files are listed in a window but the problem is the «copy/paste». I can select a file and click on «copy» on this windows; after I click on the desktop of my MAC but the command «paste» doesn’t appear in the context. If I try this on my PC, the command «paste» appears and I can «paste» the file onto my PC.
I think it’s not possible to do a «copy/paste» on the MAC. Any idea for a «miracle» program ?
Thanks you very much.
I think what your problem is, is that you need to change the preferences of the RDP file on your Mac to map local folder or hard disk. Its been a while since I set this up on a Mac so I’m not sure of the actual option but if you look in the RDP File preferences you’ll see an option to share your local drive or folder.
I suggest selecting folder and then either creating a new folder on the desktop and sharing that or share you Mac Documents folder.
If by «a background» you mean that if a user closes the app, but does not close their Mac RDC Window, they are stuck with an empty blue background, I may developed a workaround that I am currently testing.
The main problem I have been experiencing is that a user can leave a disconnected session on the server that has no valid shell (meaning neither the remoteApp process nor explorer.exe). If you do not have disconnection timers that immediately log off disconnected users, then your users can reconnect to the «blue window», which is essentially a shell-less session.
In my environment, I cannot set my disconnection timers to be low enough to alleviate this problem, so I have developed a work-around (again, still in testing) with Powershell. The workaround requires the installation of the PS modules — RDSRemoteApp and PSTerminalServices — both freely available from MSDN.
Basically, the script looks for disconnected sessions, and then, if the session is running neither explorer.exe, nor an executable associated with a RemoteApp, it logs the user off. This way, legitimate disconnected sessions can remain open on the server, while those Mac users who would otherwise be stuck with an empty blue window, will be correctly logged off.
The PS script should be run from Task Scheduler, and your Task Scheduler trigger should execute on «On remote disconnect from any user session».
Like I said, I’m still testing this, so buyer beware. I’d be interested in any feedback, suggestions, or observations on how this performs in a more heavily-used production environment.
Hope this helps anyone struggling to get the Mac RDC client to behave a little more like RemoteApp on Windows.