That sounds like a great approach. I'll start with the server, and look to upgrade the clients after. Thanks for the info...
Shane
On 10/2/06, Francesco Duranti <fduranti at q8.it> wrote:
You can use bb clients (unix and windows work). The big difference is that with bb you'll need to have distributed configuration on all client, using the hobbit client you can centralize the configuration on the server for the Unix machine. The hobbit unix client have also some more tests it do on clients and is a bit more user friendly on configuration. You can probably start with the bb client and migrate them to hobbit in some times (the client installation is a compile 1 time for architecture and copy the directory to the same architecture servers operation so it will not require too much time). And one time you've installed 4.2 clients you can them update/upgrade them in the future automatically.
We're currently using the bb windows client on more then 50 servers, we're thinking to change to the bbwin client that have some more functionality but having a xml configuration file (instead of having a centralized configuration like the unix client) and without a GUI it's a bit more complicate than the unix ones. Some of the next versions of the bbwin client should also have the gui and the centralized configuration so it could be a good thing to start testing with it also.
Francesco