Can I forward your response to the UMBC lug list? David ----- Original Message ----- From: "John Madden" <weez@xxxxxxxxxxxxx> To: <linux-discussion@xxxxxxxxxxxxx> Sent: Sunday, January 06, 2002 4:53 PM Subject: [Linux-Discussion] Re: chance for linux in local govt- county gov asks question > > > My cousin's husband heads information systems for a county > > govenment outside Philly. Although a long-time Windows > > proponent he was ranting when I saw him over Christmas at the > > unconscionably arrogant and avaricious treatment he'd > > received recently at the hands of Microsoft: usurious pricing, > > retroactive charges, over-licensing requirements, threats of > > having to re-license already purchased products for failing to > > meet unreasonbale decision deadlines, arbitrary > > discontinuation of products ... and is anybody surprised? > > No, I don't think anyone here is surprised. :) This is the same story > that a lot of companies are telling, and I suppose it's about damn time, > eh? > > > Anyway, he wants to migrate to Linux eventually. But it is > > daunting to move 2000+ PCs and users and customized Access > > databases and scripts from Windows to Linux. What companies > > are in the business of doing this? Has anybody attempted this > > or does anyone know of any success stories? > > Just about any consulting company ought to be able to provide such > services (moving crapccess databases to postgresql or mysql). > > They should, instead, hire a programmer to work permanently on > implementing replacement solutions. I don't think this is something that > should be done as a "migration" with a set time schedule, where a company > comes in, does the work, and leaves. I see it as a continuous process, > and for that you need in-house savvy. > > Split the job up into phases based on user groups. An HR department, for > example, is a fairly distinct piece of the whole with their own distinct > application and desktop needs. Find out what applications they need and > re-write them. Roll the new applications into production one at a time > (next paragraph is key for this to be applicable). When all applications > have been moved and users have been trained on their new desktop > interfaces, move them to their new workstations. Then move onto the next > group. > > My recommendation is to make all of these applications web-based. The > benefits of web-based as opposed to client, gui-based applications are > staggering, but here's one that should mean something to them: if they > ever have to switch OS's again, they won't have to rewrite any > applications. :) > > As for the desktop migration: Any experienced (and perhaps creative) > sysadmin could handle the 2000-user desktop migration, provided they make > the switch to diskless workstations. (A couple of central servers, 2000 > diskless x window boxes - Largo, FL just made a switch to this sort of > setup, and it's been a huge success story.). The typical desktop PC > setup, on the other hand, would require a lot of manpower to do things > like OS installations, user support, etc. Again, these people should be > in-house, not a consulting agency. > > You may or may not be able to re-train your existing staff, and you > probably don't want to try. You certainly won't need your windows > administrators anymore, so you can let them go after this migration is > complete. The long-term cost savings benefits of a Linux solution will > easily pay off the difference of having to employ both unix and windows > people in the interim. > > This sounds like an exciting project. Make sure they hire the right > people though, no matter how much they cost. > > John > > > > > -- > # John Madden weez@xxxxxxxxxxxxx ICQ: 2EB9EA > # FreeLists, Free mailing lists for all: //www.freelists.org > # UNIX Systems Engineer, Ivy Tech State College: http://www.ivy.tec.in.us > # Linux, Apache, Perl and C: All the best things in life are free! > >