Hi Kim, When I work remotely I tend to establish a VPN connection and run SAS Management Console locally on my workstation and then connect to the remote server. It's by no means fast, but is quite usable. I tend to do this more from habit than anything else, and the fact I have all the profiles and settings already configured on my workstation anyway. An RDP / terminal server session should perform ok too - I just don't tend to run it that way when I'm connecting to Linux servers. I have also found that SAS Management Console when run remotely and displayed locally via ssh with X forwarding over a slowish connection is very slow. Because the term "slow" can be very subjective I've captured some rough timings for comparison. I used a workstation with a 3G mobile broadband connection to a remote network (containing a SAS 9.3 server) which itself was connected via an ADSL modem. To give you an idea of the network performance an SCP of a 10MB file from the client to the server took about 1.5m (~120KB/s) and back from the server to the client about 2m (~90KB/s). i.e. not a very fast connection. These are some timings from running SAS Management Console on the remote Linux server via ssh with X fowarding to the local workstation over this 3G mobile broadband connection: sasmc command line to login dialog: 1m38s login dialog connection to usable SAS MC session: 2m31s switch from plugins to folders tab: 40s select a different folder in folders tab: 37s This was quite painful and I'm guessing you were getting similar results. I did some Googling and saw that Java apps have historically had user interface performance problems when run remotely over SSH with X forwarding. There are some settings that can be tweaked but I think a VPN connection is simpler (if you can get one). For comparison here are some timings for running SAS MC on a local workstation connecting to the remote SAS server over a VPN over the same 3G mobile broadband connection: Running SAS MC on a local Linux workstation with a VPN connection to the server network: sasmc command line to login dialog: 8s login dialog connection to usable SAS MC session: 1m58s switch from plugins to folders tab: 5s select a different folder in folders tab: 6s Running SAS MC on a local Windows workstation with a VPN connection to the server network: from clicking shortcut to login dialog: 5s login dialog connection to usable SAS MC session: 1m55s switch from plugins to folders tab: 5s select a different folder in folders tab: 5s In this case, when using SAS MC locally and connecting remotely over a VPN, whilst the initial connection is similar (a little bit faster), moving around in the local SAS MC is much faster (than the remote SAS MC via ssh with X forwarding). I would suggest you try that method to see if you get similar results. Alternatively, as Quentin and Jaap have suggested, RDP into a Windows server in the remote network and run SAS MC on that remote Windows server (after installing the SAS clients on it). I hope this info helps you with your choices. Cheers Paul
... View more