Mac OS X – Terminal Server The Marriott Library, Computer & Media Services has a Mac OS X Terminal Server running software from Aqua Connect, see web site http://www.aquaconnect.net/. This enables the Mac operating system and its applications to be accessed by diverse hardware from anywhere. Aqua Connect Terminal Server is a server based computing technology that streams the complete Mac OS X desktop experience over the network to end-users. Incorporating Microsoft's Remote Desktop Protocol (RDP) and Remote Frame Buffer (RFB/VNC) protocol, Aqua Connect Terminal Server makes it possible for diverse workstations and RDP or RFB-enabled mobile devices to function as thin clients of a Mac OS X server, but due to lack of support with load balancing our server will only support RDP.

To use our Mac OS X Terminal Server, you need a RDP client for your operating system or mobile device. For list of RDP client software, see toward the end of this document. Off-Campus If you are accessing this service off campus, you first need to connect to the University of Utah’s campus VPN. To do this, you can log into the Web VPN…

https://vpnaccess.utah.edu/+CSCOE+/logon.html …with your uNID and password, click Continue, and then click Start AnyConnect.

This will install an application on your computer that temporarily connects you to the University of Utah’s network. An alternative for iOS (i.e. iPhone, iPad, iPod Touch) and Mac OS X 10.6/10.7 is to use the operating system’s built-in VPN support. To ease setup, you can download VPN profiles for iOS & Mac OS X 10.7, manual instructions also included, from the following web site. http://www.macos.utah.edu/documentation/security/campus_iphone_2_vpn_setup.html Note, you don’t need to connect to the campus VPN, if you are already on the campus using the wireless or wired network.

Connecting & Logging In Next, you just enter the Mac OS Terminal Server’s hostname into your RDP client configuration. Server Hostname: terminal.scl.utah.edu This will take you to the Mac OS X Terminal Server load balancer, where you will see the following screen…

The load balance will take you to the server, which has the least load based on this like open sessions, CPU and RAM usage, and amount of free licenses, etc. Next, you will see the login window, enter your uNID and password at this window

It should take 20-30 seconds for the login to complete and display the following Mac OS X Desktop.

Opening & Saving Files The Mac OS X Terminal Server currently doesn’t support accessing local files, but this will be an added feature in the future. So, you need to use a cloud service like Dropbox, which offer a free 2 GB account http://www.dropbox.com/. Or you can connect to a server to download and upload files you would like edit during your remote session. Note, if you are trying to connect to your home computer using an ISP, your upload & download speed will probably be very slow to be almost be counter productive. Instead, try to use a service like Dropbox or a campus file server, which will have much faster network speeds. For example, College of Fine Arts offers file storage to their students on their servers, which you can access during your remote session. Logging Out When you are finished with your work and have saved your files, click the Logout icon on the desktop to end your session. If you are using a service like Dropbox, make sure your saved files have been backed up to the service before logging out. To check click on the Dropbox icon in the menu bar, and you should see the text “All files up to date”

RDP Client Software Here is a list of RDP client software…

Operating System RDP Client Software

Mac OS X http://www.apple.com/macosx/

CoRD ‒ Open Source http://cord.sourceforge.net/

Microsoft Remote Desktop Connection - Free http://www.microsoft.com/mac/downloads

iOS http://www.apple.com/ios/

iRdesktop ‒ Free http://itunes.apple.com/us/app/irdesktop/id311467740?mt=8

Mocha RDP Lite - Free http://itunes.apple.com/us/app/remote-desktop-lite-rdp/id288362576?mt=8

Windows http://windows.microsoft.com/en-us/windows7/products/home

Microsoft Remote Desktop Connection ‒ Free http://www.microsoft.com/download/en/details.aspx?id=856

Microsoft Remote Desktop Connection Manager - Free http://www.microsoft.com/download/en/details.aspx?id=21101

Linux https://www.linux.com/directory/Distributions

rdesktop‒ Free http://www.rdesktop.org/

Android http://www.android.com/

2X Client for RDP/Remote Desktop - Free http://www.2x.com/rdp-client/

Remote Desktop Client - Commercial http://www.xtralogic.com/rdpclient.shtml

Mac OS X computers and keyboard shortcuts If you are using Mac OS X to connect to our Mac OS X terminal servers then you will notice quickly that most keyboard shortcuts are not sent to the server but are interpreted by the RDP client. The worst keyboard shortcuts are Command-Q and Command-W, which will effectively log you off with no warning. To prevent accidental log offs, you can remap Command-Q and command-w to an effectively meaningless menu like “Bring All to Front” using System Preferences. Open the “Keyboard” Preference Pane, then click the “Keyboard Shortcuts” tab. Click on “Application Shortcuts” in the left hand list. Then click the plus button and in the sheet that appears it will ask for the Application. Click the Application popup and find “CoRD” or “Microsoft Remote Desktop Connection”. Click in the “Menu Title” field and type “Bring All to Front” (since that effectively does nothing). Click on the “Keyboard Shortcut” field and press command-q. Click “Add”. Repeat the process for Command-W except with one modification. If you try to add multiple shortcuts to the same menu title it will not let you. For the “Menu Title” enter “Arrange in Front” or some other benign menu title. If you misspell the menu title then the shortcut will not work. Test to make sure your keyboard shortcut really did work before connecting to the terminal server by launching your RDP application and press Command-Q and Command-W.

Xcode We do not allow step debugging in Xcode on the Terminal servers. If you want to debug, you must use print/NSLog() statements. The following pdf is written for perl, but starting on page 300 there is the section called "Debugging Techniques" that applies to every language. It basically describes why you would want to use non-step debugging techniques even if you could use them. It is a good read and something every programmer should know and be able to do. http://blob.perl.org/books/beginning-perl/3145_Chap09.pdf We have a video demonstration of debugging this way on the website listed below. In essence, when you build and run, it will ask for an administrator password, which you do not have. You need to press cancel for every authentication dialog that appears, then you need to click the “Stop” button in Xcode, then go back to the find the application build (for native applications) or go to the iOS simulator and launch the newly built application. All NSLog() statements can be viewed by opening /Applications/Utilities/Console.app. Support – Problems, Questions & Feedback If you have any problems or have suggestions about this service, please contact us using this web page…

http://support.scl.utah.edu/index.php?departmentid=49&_m=tickets&_a=submit&step=1&subject=Remote Software Feedback

For update information, please go to the web site…

http://www.lib.utah.edu/services/labs/remote-software/

Note, this is a currently a pilot project with specific classes, please do not share this document of information with other classes or student, staff or faculty without contacting us first to verify if we can support the extra users, etc.