We looked at solutions from coderebel and aqua connect. Aqua Connect has been around much longer, but they are not cheap. We put the project on hold due to limitations in the software. One of those being using it with developers would allow them to reboot the main host.

had horrible experiences from Aqua Connect. I gave them three chances

1. Didn't work in my environment


2. The Developer didn't call me back after they promised they would


3. The newer version still didnt work in my environment months later

Thanks so much for sharing.

I'm probably going to do a trial for both and see how it goes here.

G. Remote Desktop Connections. Subject to the terms and conditions of this License, when remotely connecting from another computer or electronic device (each a “Device”) to an Apple- branded computer that is running the Apple Software (for purposes of this Section, such Apple- branded computer is referred to as the “Home Mac”), whether through the Screen Sharing feature or through any other means:
(i) only one (1) Device may remotely connect at any one time, whether directly or indirectly, to control the graphical desktop session of the Apple Software that is running and being displayed on the Home Mac; and
(ii) a reasonable number of Devices may remotely connect at the same time for the sole purpose of simultaneously observing the same graphical desktop session of the Apple Software that is running and being displayed on the Home Mac, as long as they do not control the Apple Software in any way; but
(iii) only one (1) Apple-branded Device may remotely connect at any one time, whether directly or indirectly, to control a separate graphical desktop session of the Apple Software that is different from the one running and being displayed on the Home Mac, and such connection may only be made through the Screen Sharing feature of the Apple Software.

That's part of the EULA for OS X 10.8.2, and as far as I know, the most current EULA. As you can see, using any sort of OS X terminal services for controlling more than one session at a time violates the terms. Something to consider in addition to hardware and software.

On a side note - most "legal" OS X Terminal Service installations are using Snow Leopard, sine the above clause is not present in the EULA. The restrictions began when Lion was released.

We're using iRapp and it's woking good so far...
At the point of our initial POC with both vendor, they were some some legal battles and AquaConnect couldn't sell their product.
I had a bad experience with AquaConnect.
iRapp is pretty good with their support.

This was demoed at PSU MacAdmins recently.

http://www.youtube.com/watch?v=9uX-PyDNSDI

http://macadmins.psu.edu/files/2013/06/psumacconf2013-OS-X-Terminal-Services.pdf

Actually, the presentation slides are here:

http://www.mac-mgrs.utah.edu/downloads/2013_PSU_MacAdmins_-_OS_X_Terminal_Services.pdf

I am the person who did the PSU MacAdmin's presentation, if you have any additional questions.