Hi all, It seems the greatest advantage that a solution such as RM Community Connect 3 has over installing SuSE Linux with Samba in a large school network to act as a PDC for Window XP clients is: Rolling out software. How do people manage their large installs? Silent install scripts? I'm new to this but I think this issue is possibly the show stopper in terms of convincing management they don't need to be locked in to proprietory companies. For those that don't know, RM Connect has a tool that allows admins to easily monitor changes that an install makes, and then pushes it out to selected machines at tthe click of a mouse. It's worked well here on Connect 2.4 (a purchasing decision made 6 months before I got this job). It's now time to move away from 98 on the desktop as it's being unreliable, and I don't want to be tied in any more. The progression that's assumed is RM CC3, but now's the time to move this school into a more open source solution. I could do with a hand on this specific issue. Any ideas...? (The other two schools I've installed and managed Linux in are small enough to manually install all software - that's less possible here and I'd like a more scalable solution). (I know the advantages of using Linux thin-clients or even fat clients. But XP has been settled on already for the curriculum desktops.) Thanks loads for any suggestions. -- Matt Johnson ________________________________________________________________________ Yahoo! Messenger - Communicate instantly..."Ping" your friends today! Download Messenger Now http://uk.messenger.yahoo.com/download/index.html