Having a need for a small-business groupware solution (specifically for project management, task management and possibly timesheeting, issue tracking) I started to poke around to see what's around.
My preference is ASP, SQL based.
 
Here's a shortlist:
 
*Stylite Egroupware
http://www.egroupware.org/Home
-New release Oct 2008
-PHP under IIS (XAMP recommended) http://www.egroupware.org/index.php?page_name=dependencies&lang=&wikipage=php
-MySQL5 (MSSQL "sort of works"
-Free - vendor sells managed, hosted services
-Windows Mobile vis Synthesis client via SyncML
-Features: http://www.stylite.de/EGroupware_functions
Good task management and tracking, calendaring, contacts (not sure about how well Outlook/Windows Mobile sync works), web-based file manager (not quite Document Management but is WebDAV enabled) 
Knowledge management (articles etc), resource bookings (cars etc), timesheets linkable to anything on the server, 

*Redmine
http://www.redmine.org/
-Under regular development
-Deployment tips here - http://fluxqubit.wordpress.com/2008/08/22/the-absolute-all-in-one-project-managment-tool-redmine-extensive-howto/
-Ruby 2.12, MySQL >4.1 (eg http://rubyinstaller.rubyforge.org/wiki/wiki.pl) http://mirrors.ntua.gr/MySQL/Downloads/MySQL-5.0/
-Not particularly Windows/IIS friendly
Gantt charts, Doc and file management, feeds and email notifications, Per-project wiki and forums, time tracking, custom fields for timetracking/issues/projects
Subprojects, Flexible issue tracking. HTML or text view.

*Sharpforge
https://sharpforge.org/p/SharpForge.aspx
-Targeted at software development but is applicable to other uses
-Still in beta, kind of active development but slow
-FOSS, C#, .Net 2.0, SQL2005Ex+, IIS, 
-Aims to be a sourceforge replacement
-Not a particularly intuitive product for project management

*OpenGoo
http://www.opengoo.org/
-Seems to be more of a web based office package
Reasonable task management with time tracking

*Project.Net
http://www.project.net/
-LAMP/WiMP (PHP/MySQL)
-Moderate ongoing development - new release July 2008
-Used by deBortoli Wines
-Focused on Project Management
Email ticketing, Client/Company management, project listings, hierachical task lists, File repository, Calendar, Forums, ACLs

*ProjectCompanion
http://www.projectcompanion.com/products.asp
-IIS4+, .Net1.1+, SQL2000 or SQL2005Ex
-Free version, not fully featured but still very useful ($80 per user standard)
-Project management, Action management, Project diary, document management
-Licensed versions add project portfolio, time/expenses, workflow . Enterprise == nvoicing, sales/profitability reports, business trend analysis, other features
Very good, focused project management - great UI.
Enterprise Features are strong, could replace an accounting system? But price unknown. http://www.projectcompanion.com/enterprise/

I'm trying to disable the warning message when connecting to a client - "The identity of the remote computer cannot be verified".
This is still WiP, I'm over it for today :)

Thought I'd record for reference the registry values the TS client (MSTSC v6.1 as with Vista) queries.
Lots of these aren't present by default. Many of these queries are also duplicated in HKLM but I've omitted these - we all know HKLM regedits are naughty :)

HKCU\Software\Microsoft\Terminal Server Client\DisablePrinterRedirection NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DisableClipboardRedirection NAME NOT FOUND
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\AuthenticationLevel NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\AuthenticationLevelOverride NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\BitmapPersistCacheSize NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\BitmapPersistCache16Size NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\BitmapPersistCache24Size NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\BitmapPersistCache32Size NAME NOT FOUND
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\AllowUnsignedFiles NAME NOT FOUND
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\AllowSignedFiles NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\PinConnectionBar NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\Default\RemoteDesktopFolder NAME NOT FOUND
HKCU\Software\Policies\Microsoft\Windows\CurrentVersion\Internet Settings\MBCSServername NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\EnableSslWithUserAuth NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\Shadow Bitmap Enabled NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\UseShadowBitmapInFullScreen NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\MaxRdpCompressionLevel NAME NOT FOUND
RegOpenKey HKLM\SOFTWARE\Microsoft\Terminal Server Client\RedirectDevices NAME NOT FOUND
RegOpenKey HKLM\Software\Microsoft\Terminal Server Client\TransportExtensions SUCCESS
HKLM\SOFTWARE\Microsoft\Terminal Server Client\TransportExtensions\Gateway SUCCESS Type: REG_SZ, Length: 26, Data: aaclient.dll
HKCU\Software\Microsoft\Terminal Server Client\DisablePrinterRedirection NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DisableClipboardRedirection NAME NOT FOUND
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\AuthenticationLevel NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\AuthenticationLevelOverride NAME NOT FOUND
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\PromptForCredsOnClient NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\AuthenticationLevelOverride NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\RemoteDesktop_SuppressWhenMinimized NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\Min Send Interval NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\Allow Background Input NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\OffscreenSupportLevel NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\OffscreenCacheSize NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\OffscreenCacheEntries NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\BitmapPersistCacheLocation NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\MultiFragmentUpdateMaxSize NAME NOT FOUND
RegOpenKey HKCU\SOFTWARE\Microsoft\Terminal Server Client\Servers\<<hostname>>NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR\ThreadTimeOut NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR\DisableDeviceRedirection NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\LicensingTimeout NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusEnabled NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusSupportLevel NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusCacheLevel NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusGraphicsCacheEntries NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusBrushCacheEntries NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusPenCacheEntries NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusImageCacheEntries NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusGraphicsCacheChunkSize NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusBrushCacheChunkSize NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusPenCacheChunkSize NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusImageAttributesCacheChunkSize NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusImageCacheChunkSize NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusImageCacheTotalSize NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusImageCacheMaxSize NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawGdiplusImageattributesCacheEntries NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawNineGridSupportLevel NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawNineGridEmulate NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawNineGridCacheSize NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\DrawNineGridCacheEntries NAME NOT FOUND
HKLM\SOFTWARE\Policies\Microsoft\Windows NT\Terminal Services\AuthenticationLevel NAME NOT FOUND
HKCU\Software\Microsoft\Terminal Server Client\AuthenticationLevelOverride NAME NOT FOUND

Let me know if you find any of this useful and have further info on any entries.

This entry was prompted by a question posed on slashdot. It is meant to shed light on the true issues surrounding QoS in most commercial home-grade links.

There's a huge number of people who don't know what the issues with QoS actually are - an unfortunately very common misconception is that configuring CPE QoS features == successful QoS. Also common among the 'enthusiast' group is the belief that sticking in a linux-based QoS-enabled distro is a panacea for QoS (eg "Put in IPCop == solved'").

In a situation where a link is a simple, as-designed ptp situation with no re-encapsulation (eg E1/SHDSL) QoS can be effectively implemented using in-box configuration. Home-class routers and OS-based control will work provided QoS is configured at each endpoint.

Unfortunately few people have the kind of service which out-of-box QoS can be used effectively.

The root issue of QoS today is the lack of outbound interface queuing. Unless one can 'see' the hardware/egress packet queue at its final point, QoS will not work successfully (without creating a 'dummy' artificial queue.. see below). When a link is congested, or when smaller frames/packets need to be sent before larger ones, QoS comes into play.

First component of QoS is the "queue". This is the 'waiting list' for packet egress (and ingress to a small degree, especially where link-congestion indication is supported). Here is where packets line up to be sent. QoS works by managing the priority of each packet (either by classification or by respecting the IP CoS/DSCP bit in the header). In a simple ptp link, this works well and as intended. Policy is applied to each end, and each router applied a queuing strategy and policy to the packets going out. Bandwidth is known, and the load on the link is directly observable by queue depth. Even applying 'fancy queuing' eg weighted round-robin, Random Early Detection is often enough to ensure equitable access.

Unfortunately in this day and age, most link implementations remove the ability to observe queue depth - by either shaping in the middle, by virtualising the terminating interface, or by multi-hopping the termination.. all three at once is common.

I am discussing DSL specifically as it's the most common access technology, but the same thing applies to cable as rarely can one apply QoS inside the cable CPE.

Originally DSL-based WAN's were intended to be implemented over an ATM-native network, where the CPE configures one or more PVC's and this PVC(s) terminates on the decapsulating aggregation router. The PVC (at each end) has known properties (bitrate, class of service). It was also intended to have multiple PVC's (eg VPI/VCI virtual circuits) with different Class of Service parameters for each to manage QoS.

Sadly this model has been discarded, and almost all DSL services 'ignore' the ATM component and just treat it as a 'throwback'. One CPE has one PVC, and this is terminated on an AVGC far outside the reach of the actual ISP with the ATM component having no real impact other than simply being an access transport. To complicate matters, usually shaping is applied at the AVGC end, and the whole path is a series of virtualised interfaces double and triple encapsulating the link. So we have lost the ability to 'see' the actual queues - you can only throw packets at the link and hope they come out the other end.

So now the native ATM opportunity for traffic management is gone, what now? As mentioned, most commercial DSL operates using L2TP multihop and virtual interfaces. A virtual interface has no real queue and in the Cisco world at least, there's no practical method to do anything with the provider end of the link. The QoS mechanism cannot 'see' what the link is doing load-wise and as such can't effectively manage service.

So, what's left?

The only avenue open is to create a 'false queue'. This is effectively an artificial bottleneck.

Here, you implement traffic shaping by taking the maximum amount of bandwidth in one direction (and with the bandwidth tax of multiple encapsulations eg PPP, L2TP, ATM which can often be difficult to determine) and subtracting say 10%. This creates a situation where packets can actually queue up and be seen by the QoS process.

It can be done inside some routers, although many home-grade CPE implementations are unacceptable in that they force you to allocate a fixed percentage of bandwidth to a certain service (and often this is TCP/UDP port based which is very limiting in itself).

This is the only way to make QoS work in the current environment. The limitations are obvious: it must be also be done at the provider end, 10% or more loss of bandwidth is incurred, and if there is any congestion between the two endpoints QoS will not be effective.

There is also the option of the CPE router using coarse techniques to 'poison' or control non-sensitive traffic in the presence of time-sensitive traffic. This can be done by using/managing TCP resets, ACK's and window sizes. This approach has many limitations and I cannot recommend it as a practical alternative.

So, if you're after QoS, the CPE router must support traffic-shaping and QoS for upstream control. Your provider must also be willing to provide the same service at the head end. You lose bandwidth, and any congestion between ends can't be accounted for.

Pretty horrible isn't it? Until the IT industry gets off its' backside and addresses these issues, the most practical solution for low-latency, low-jitter, low-loss internet is the same as it's always been: get a bigger pipe.