Both are relatively easy to set up.
The server side runs under either Windows or Linux, the client side (as of now) is Windows only.
As to the server, you unzip the files to the program files area and run the batch files to start the servers. You simply need to alter a few lines in the configuration file for each class-server. These include port configurations. Multiple servers can be run on the same machine. A series of ports are assigned to each server.
A good rule of thumb-server side (without using the video) is 500mghz, 500 meg memory and 500 kbs upload for every 25 concurrent participants. Now, it really doesn't take that much, that would be if you set the system where it was running just wide open under unicast. It runs under either unicast or multicast, so a multicast would save a ton of bandwidth. Access from the client side can be very low. I have a student in Bulgaria who has a connection that MIGHT hit 30k on a good day and while we have some problems, it works well for him.
As to the client side, GMU has a strange install process, which can be very confusing. I created an installer which works very well. My ESL students master the installation process with no problems. It does require the Java Runtime Environment, which I include on my installed version. Total size of the installer, with the JRE, is about 8.5 meg..
While the client side can run on its own, I created a web page that allows the students to pick a "classroom" (server) and the method of entry to that classroom (with or without recorder or streaming playback of a recorded class). When they click on the link, a required client side configuration file (very small in size) is downloaded to their system and the classroom starts using their selected parameters.
This does mean that the person running the server must also create these client side config files, but it isn't as tough as it may seem. Each classroom can have about 6 different combinations of access. A series of sample config files are provided. The server operator just opens each file and changes the room name and port assignments. It takes me about 30 seconds per file to change them. In my installer version I provide all the files needed for 5 different "classrooms", the only thing that needs to be changed in these is the URL in each file telling the system where to go for the server. This change takes just a couple of seconds to accomplish.
A tunnel is created between the client machines and the server. This allows us to reduce any problems we have with NAT or firewalls. The newest version is using a stunnel (secure tunnel), which provides for encryption of the classroom information (voice, graphics, data).
There are some fixes going on now in the version 4, which should be completed in the next couple of weeks. I'll post the links to the sofware when these are done.
Dave