I once had the opportunity to test all control panel systems on my test VPS. So here is a brief overview of my experience just in case anyone should need a concise overview. It was based on a fresh Debian Lenny 64-bit system.
SysCP: Probably the slimmest of all control panels. I liked it very well because it is actually perfect for a VPS with a handful of domains and hardly more email addresses. But also for commercial hosting SysCP is to use; thanks to the ticket system and various user levels.
The installation was pretty easy, even when the manual to change the config files is a bit time-consuming. However, I wanted to send the mail postfix part out not (but probably was more like gadgets than on my previous SysCP ).
Conclusion:
* Very slim and resource-efficient panel
* Relatively easy to install
* Updated user interface
* Own Apache directives conveniently controlled via the panel
* Supports many distributions
* Does not so deep into the system
* Time-consuming to change the configurations of the respective components
* Partially annoying dependencies when installing the deb package
* Configuration of nameserver manually only
* Unwieldy Prefixsystem
The control panel I liked well, but I have for my taste nearly contain enough features. I would have shut me here and there but want some more configuration options for each service. Above all, the ability to manage the DNS zones on the control panel. I would have liked it. Thus the control panel offers few advantages in this respect to the work in the shell.
ispCP Omega installation was even simpler than that of SysCP since one is the change of the individual config files could save. It is therefore commendable in my opinion could determine application trust the admin name itself, which provides a little more security. In addition, the CP brings many features such as webmail in their own design, with much more detailed statistics, that makes the resource consumption seen, which is higher than that of SysCP.
what annoyed me uttered, however, is that only php cgi / fastcgi can integrate. That may be safer but it is much slower and thus a failure of the CP. Ensures that it is on vServer seemingly unusable. Quite often the cgi processes are not started properly terminated. So that they fall into an infinite loop, which may affect VDS (so is reported in various forums) and even the entire node crashes can bring.
However, this should occur only on VPS with 64-bit OS. For me, the problem then, whereupon the VDS was about the only VPS Control Panel addressed the host. Although there are many instructions all operate with mod_php but this would require after each update of the CP re-adjustment.
Summary:
* Elegant surface
* No manual adjustment of the config files needed
* Many features
* Name of the admin accounts on their own identifiable
* PHP will only fastcgi / cgi-usable
* Resource consumption partly tangible
* Bug on 64-bit systems vServer
The CP seems more likely to be somewhat larger for hosting and the corresponding server. Many features and configuration options are nice for the lazy admin shell, however, impede the creation of deeper configurations, since they are overwritten by the CP again.
The resource consumption was by the (almost) acceptable use and partly outside the cgi. But it should be mainly responsible for the above bug. Therefore I could not completely take the test over and “explore” all functions. Therefore it should be missing some points on the list above conclusion.
ISPConfig 3: First a little note; one must distinguish between ISPConfig 2 to 3, because both versions are not only very different from each other but with some rooms even have their own developers hanging. I opted for version 3. For the full installation, I led a HOWTO, which set up the same time a Debian system with a general explanation.
The installation should perform well for a beginner can be, but it is advantageous that is not immaculate fully in dealing with Linux to be. After installing the CP did his service at once (only with the mail server I am still having problems, again) and its many possibilities spread out before you figured it out.
In addition to a comprehensive monitoring site with which you deal with many logs, RAM, and CPU load, view general information directly into the CP, and the CP also contains the usual admin, customer, and reseller system.
Additionally, the CP waits with many more features to help the one in the management of many domains, such as the possibility of CSRs (certificate signing requests) directly generate from the CP. Your own Apache directives can include on the CP.
Conclusion:
* Functional and thanks to Ajax by far the fastest surface
* Many (in my opinion) useful features
* Own Apache directives simply include
* Allows quick access to page monitoring for various logs, etc …
* Many additional components for the monitoring of emails (ClamAV, SpamAssassin, etc…)
* Own DNS zones
* No problem for managing multiple IPs
* Very helpful community (even if it comes along as a complete beginner)
* The CP is easily extensible via plug-ins
* But there is not many for version 3
* Interface only works with JavaScript
* Installation may not be suitable for beginners
So I will probably put ISPConfig 3 on my new VPS since it is the best as compared to functionality and resource conservation. Everything depends on the sending and receiving of emails gives me a headache, but this probably is not the CP, since I use Postfix on GeneRally somewhat at odds. But I should solve the problem, this is my dream CP.
Plesk: At the end of another narrow field report with Plesk, which is to version 9.2, a Debian-based 32-bit system where I used Plesk for almost 2 years in use, but this was not necessarily to the conviction but rather to the fact that the VPS with other CPs behaved quite bitchy.
The installation of Plesk for Windows is moderately easy. You start the install script and the rest of the task makes almost by itself. Plesk was moderate at the best resource on average time consumption, the side structure of the surface was always horribly slow.
Plesk provides by far probably the most features with the average Admin access, however, it is very low gearing. This does have a positive impact for beginners with chronic Shell-phobia, but who want to set up a service time on the Plesk custom configuration so looks often in the tube, as Plesk’s own changes are quite cheeky about writing again, and other settings not offered.
Conclusion:
* Offers many features
* Easy installation
* Very easy to use (for beginners)
* Well-functioning auto-update
* Requires many resources
* Own Apache directives can be placed manually only by Shell
* Dovetails very much with the system
* Completely overloaded interface, Which loads very slowly
* Sometimes useless features (Application Vault, etc.)
* License for the small private users priceless
So I must keep Plesk credit, as it has always worked very reliably and the auto-update feature was very convenient. However, I still cry no tears for the CP. If you wanted to just quickly change one thing this has been hampered by sometimes extremely slow-loading pages, so some options to hide in the seemingly endless icons soups such skill that one might despair.
Thus, virtually the entire Plesk server digs under the nail, preventing almost any self-employment. All in all, the value of a joke, if you are not on the mass license can call your provider. Mostly Plesk is recommended for beginners. Thus, particularly those who want to control everything rather than a graphical interface.
So that is my rundown of the most common CPs, maybe someone can take advantage of it. Please understand it is not a professional report or test but rather a rough overview.