From owner-freebsd-questions@FreeBSD.ORG Mon Oct 18 16:52:51 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3AC2416A4FF for ; Mon, 18 Oct 2004 16:52:51 +0000 (GMT) Received: from mail.chrononomicon.com (chrononomicon.com [216.37.143.27]) by mx1.FreeBSD.org (Postfix) with ESMTP id 09B0C43D41 for ; Mon, 18 Oct 2004 16:52:51 +0000 (GMT) (envelope-from bsilver@chrononomicon.com) Received: from [127.0.0.1] (unknown [192.168.0.42]) by mail.chrononomicon.com (Postfix) with ESMTP id C11B61278CB; Mon, 18 Oct 2004 12:52:48 -0400 (EDT) In-Reply-To: <20041018163755.33132.qmail@web53906.mail.yahoo.com> References: <20041018163755.33132.qmail@web53906.mail.yahoo.com> Mime-Version: 1.0 (Apple Message framework v619) Content-Type: text/plain; charset=US-ASCII; format=flowed Message-Id: <239BA16E-2126-11D9-BCBA-000D9338770A@chrononomicon.com> Content-Transfer-Encoding: 7bit From: Bart Silverstrim Date: Mon, 18 Oct 2004 12:52:47 -0400 To: stheg olloydson X-Mailer: Apple Mail (2.619) cc: freebsd-questions@freebsd.org Subject: Re: feasible w/ samba? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 18 Oct 2004 16:52:51 -0000 On Oct 18, 2004, at 12:37 PM, stheg olloydson wrote: > > What you have here is a hardware, not software, problem. The root cause > is the unreliable connectivity between buildings. To ensure all network > resources are always available, use redundant fiber-optic connections > and set your routing such that you can reach buildingX from buildingY > via buildingZ, as well as directly. Actually, it would be connectivity + bandwidth + geography. Some of the buildings are close together...close enough that you can lean on the wall of one and throw a softball to hit the other. Others are over 20 miles apart, and it's not really 3 buildings...I was using that just to simplify the scenario. there would be 7. Unfortunately, there's no way we currently know of to lay out enough fiber for every building and still have reliable (and *fast*) transfers compared to a "proxy" approach as I was envisioning in my head. > Then you can (although it may be heresy on this list) avoid using FBSD. > Your simplest solution is to use Windows built-in Roaming Profiles. The > feature exists to accomplish the exact task of making the user's > resources (including desktop config) available on the login > workstation. the problem here is that we're currently using Windows profiles and home directories; it has problems, too. I.e., it's not that every day people are moving buildings...they only occasionally do it. We noticed problems with profiles in that some of the users like doing things like shutting down machines before a profile is fully saved, and saving data in locations that are not routinely backed up. Profile corruption. We're also currently using Terminal Servers, so profile corruption can be a worse problem, as is people logging into the wrong servers from the wrong locations. We'll actually be locking out some "profile" features...too many complaints about students using illegible personalized themes when teachers try to help them. Thanks for the input, though. I didn't know if this was a feasible idea or not. Didn't know what others on the list had run into.