For detailed information, please read the Up2Date Blog posting here: Astaro Up2Date Announcements: Astaro Command Center 2.2 Public Beta Begins
This forums will also eventually direct you to other resources including the preliminary release notes, updated hardware requirements, a quick start guide, the KIL and HCL. If this is too much detail and you just want to get to the ISO and start downloading and installing, you can grab your free copy here: ftp://ftp.astaro.de/pub/Astaro_Command_Center/v2/beta/acc-2.150-100531-3.iso
IMPORTANT NOTE: The ACC V2.2 Beta (2.150) currently requires the latest ASG V8 Beta (7.920) for full support of the new features (such as Central Packet-Filter and Web Security configuration). ASG V7.920 is scheduled for release tomorrow, but you can already install ACC V2.150 and prepare all the cool configurations which you can then roll-out to your devices tomorrow. On V7.5, the new features will be supported with the release of ASG 7.506, which is planned for release in Mid-Late June. Of course, ACC V2.2 BETA is backward compatible to previous versions of ASG V7.5 and ASG V8 Beta now.
Now that you are aware of where and how to get your hands on the Beta, we'd like to welcome you to the Astaro Command Center V2.2 BETA challenge. Similar to the previous ACC and ASG BETA challenges, we want to give you some incentive to install, test and use the ACC V2.2 BETA version. It is easy to participate in this little contest, plus you will show up on our internal radar and might win some nifty gift certificates.
Please report bugs in this forum by opening a new thread. Be sure to include the following pieces of information.
[2.150] Small synopsis of the suspected bug/issue
Hardware : CPU, RAM, HDD
Devices : number of devices, bandwidth to/from ACC
Users : number of users, bandwidth to/from ACC
Short problem description.
Attach Logfile snippets if feasible.
Here is a short example post:
[2.150] core daemon should really take more of a beating
Hardware : P4 3 GHz, 1024 MB RAM, 40 GB HDD
Devices : 23 devices, 2 Mbit / 192 Kbit
Users : 03 users, 6 Mbit / 640 Kbit
When I press the "snafu" button exactly three times in a row on sunday afternoons, the core daemon crashes and gets restarted by the selfmon.
Please see this (imaginary) logfile snippet here:
2008-08-03@10:32:12.1323 there are too many failed attempts to gain entry to the subsystemThere will be a point award system and a related high-score list for top UBB bug reporters. The more concise, precise, complete, helpful and useful your bug report, the more points we will award to you. You should at least enumerate your configuration and describe the effect(s) the bug exhibits. By including log file snippets, tcpdumps, screenshots and other helpful items you may earn additional points.
2008-08-03@10:32:18.2383 "snafu" is not an allowed operation on sundays
2008-08-03@10:32:32.9323 unclean shutdown/crash detected, reinitializing data
You can report any bug you find, however it must be a "new" bug (one that is NOT already filed in our internal issue tracker). I'll keep track of the found bugs in this posting. Please check the list below before reporting. Also Henning and the team here is the final arbiter in report evaluation. Please do not start discussions about the fairness of the process. Please note, that reporting dupes will not get you any points. You can view current awards (which doubles as a confirmed issue overview) and a high score list here in the forums shortly.
When the Beta phase ends, the three top UBB bug reporters will receive Amazon Gift cards. For non-EU national winners, we'll try to get gift cards in your local currency. Failing that, you'll get a card for amazon.com, in US dollars.
Have fun and thanks for your participation!