Publishing Terminal Services for MAC OS X clients through IAG
Mac clients accessing the terminal services through IAG is possible and IAG does have in built support for publishing MAC OSX apps. I think the best approach here is to publish using a Generic Mac OS X Carbon App. Alternatively, you can simply tunnel port 3389 using a Generic Client App and instruct the end user to launch the local RDP app after the tunnel is up.
PS: Please note only MAC OS 10.3 and later, JRE version 1.5 onwards and Safari version 3 and later is supported through IAG 3.7 Sp2 Update 2.
First try with Generic Mac OS X Carbon App:
On your trunk à select the Generic Mac OS X Carbon App wizard.
Generic Mac OS X Carbon App
Server Settings:
Generic Mac OS X Carbon App (hosts required)
Note
This application is supported on Mac OS X operating systems.
So on the wizard when you click next à
Use this screen to configure the application server.
Server Hostname
Hostname of the application server. Use the effective hostname as defined in the DNS.
Port
Port number of the application server.
Executable
Executable that runs the application.
Note
If the installation path of the application is not a default path, you have to add the path in this field. For example: /Applications/MSRDP/Remote Desktop Connection.
Arguments
Address of the remote server, for applications that receive the address as an argument in the command line.
Tip
Use variables in this field.
Launch Automatically on Start
When this check box is selected, if a user is authorized to access the application, the application is automatically launched when the user accesses the portal.
This should launch the terminal services for MAC OS X clients.
If the above doesn’t help then you can take a different approach and use Generic Client type Application wizard and just publish the port 3389.
Generic Client type Application
Server Settings:
Generic Client App
Note
This application is supported on Microsoft Windows, Mac OS X, and Linux operating systems.
When you click next in the wizard à
Use this screen to configure the application server.
Server
Define the server, using a hostname or an IP address. If you use a hostname, use the effective hostname as defined in the DNS.
Note
To enable multi-platform support and support on endpoint computers where the Socket Forwarding component is not installed, enter a hostname in this field, and not an IP address.
Port
Port number of the application server.
Launch Automatically on Start
When this check box is selected, if a user is authorized to access the application, the application is automatically launched when the user accesses the portal.
PS: the idea is to launch the tunnel first before user launches the TS.
Comments
Anonymous
March 25, 2011
Hi, The Generic Mac OS X Carbon App is missing on the UAG, do you know if there a way to get the same functionality in the UAG?Anonymous
November 01, 2014
Can more than one Microsoft Linux operating system download at one time?Anonymous
November 01, 2014
I am just starting to learn about Microsoft Linux osx/I don't know much better.