During the last month or so, there has been a lot of maturation occuring with the ECC2 client. We are on the 5th version (CF/WD) of the Win 32 client, unofficial Linux/*nix clients are crunching away, and there are GUI wrappers available for Windows and Linux
What have we learned? What is the best way to use the clients, what works to go through firewalls, sneakernetting, client bugs, etc.
Here are my observations...
Win 2000.
I'm using the CD,CE and CF clients installed as a service on my 3 Win 2K boxes here at home.
Advantages-
No need to worry about logging in! It runs when the machine has booted!

It shuts down cleanly, no need to use ctrl+C to stop the client.
Minor disadvantage-
The client does not save it's incremental work between DP finds in the plist, so some work has to be redone when the machine shuts down.
Win 98SE
Again using the CE or CF client along with gilcrest's wonderful ecc2GUI v0.4

It's truly a wonderful thing.
In the GUI, select
AutoStart ecc2 Client
AutoStop on Close
Start ecc2GUI in tray
and
ECC2 Client hidden
I add a shortcut to the ecc2GUI.exe in my \Windows\All Users\Start Menu\Programs\StartUp\ folder, and remove any startup shortcut to the CLIclient.exe file.
Advantages-
The client starts whenever anyone logs in.
No need for the ctrl+C command to gracefully shut down the client when you shut down the computer! [edit] Only seems to work on some 9X boxes.

[/edit]
The kids aren't as liable to shut down the client window.
Disadvantages-
Don't know of any.
How about you?
From eweruk- While running the client as a service on Win 2K (should be able to do the same on XP)
If you want to use the GUI under W2K, at least you can setup the shortcut in your profile so it does not run when others log in. Good one!
viz