Linux Enterprise Desktops

[Luberti, Carl]

I think, personally, that the best way to migrate is to run VMWare
(http://www.vmware.com) or Win4Lin (http://www.netraverse.com) so that
applications are not just dropped, users can be migrated in a greater
timeframe and more "at their leisure", so to speak.  As far as BDC or NIS, I
am unsure.  I use Samba for most PDC/BDC operations here, but I cannot speak
to other options as I have not tried them.

> Carlo Luberti
> EDS - New York Solution Centre
> NYSC Design Cell - Platform
> 25 Northpointe Pkwy.
> Amherst, NY 14228
> * phone: +01-716-564-6678
> * pager: +01-716-623-9062
> * mailto:carl.luberti at eds.com
> http://www.eds.com


-----Original Message-----
From: Michael R. James [mailto:mrjames at localnet.com]
Sent: Tuesday, July 17, 2001 8:54 AM
To: nflug at nflug.org
Subject: Linux Enterprise Desktops


Having spent over 6 years as a network administrator with approximately 1200

users spread across the US in a multi-site WAN, I was charged with seriously

looking at Linux for the desktop and server environments.  I have experience

with Microsoft NT, and Novell Netware servers.  Based on my experience,
along 
with the research I completed, I believe that Linux can successfully control

the desktops.  There must, however, be some prerequisites completed first.  
Enterprises won't just drop Windows (or Netware) and migrate to Linux on a 
whim.    There has to be some type of blueprint available, allowing them a 
smooth transition from one to the other.  I've scoured the web and found
very 
little documentation in transitioning existing networks to Linux solutions.
I 
propose that the administrators in this forum share their experiences, both
the 
problems encountered and the solutions implemented.  

Windows NT allows for either a workgroup configuration, where every
workstation 
maintains it's own user id's and passwords, or for central authentication,
the 
Primary Domain Controller.  The workgroup environment is easily mimicked
with 
Linux, as every Linux workstation would maintain it's own list of users and 
passwords.  The Primary Domain Controller could also be mimicked, using a
NIS 
server.  The question is how to implement Backup Domain Controllers?  Could
the 
NIS database be securely replicated to other servers?  Common "home" 
directories could be maintained as NFS exports from a central server.
Printing 
is a no brainer, using LPR/LPD.  Star Office could be used as the 
wordprocessor, spreadsheet, etc application.  What services are absolutely 
necessary for the Linux workstations?  Certainly, each and every workstation

wouldn't need MySQL or Apache running as a service.  How would one implement

NTP for standard time synchronization on the network?  How would one plan
and 
implement a heterogeneous network, with Linux, Window, and Mac clients?
What 
obstacles are now forced on the plan?  Certainly an enterprise migrating to 
Linux would not do so in a day.  They would be much more receptive to a
phased 
transition, which would ultimately mean heterogeneous clients on the
network.

Until a "blueprint" or outline for the transition is detailed, I fail to see

Linux being implemented in the Enterprise on a grand scale.  I believe all
the 
pieces are present for this eventuality.  They just need to be orchestrated 
into a reasonable solution.  Perhaps we, as a group, could contribute to
this.

Thoughts, ideas are welcome.


Michael R. James, CNE
mrjames at localnet.com