Linux Enterprise Desktops

Wed Jul 18 12:34:12 EDT 2001

Actually, this is the same kind of problem that Windows people have when
they are switching from WinNT to Win2K.  It is such a big issue that M$ has
several $2000 courses that cover many of the issues involved in a migration
from one system to another.

It basically boils down to project planning.  What objectives are you
trying to accomplish, what is your timeframe, what resourses (money/equpt
and personnel) do you have at your command?  Give those answers priorties
of 1-3 (no duplicates) and your on your way.

As far as what is available regarding linux technologies, you seem to be
alluding to one of the 'holy grails' of computing, the single log on.
There are a couple of technologies for that (and i'm about to exhaust my
knowledge) NIS, and Kerberos seem to be the bigger players.  There are some
'by hand' solutions you can try, such as NFS and cron scripts to copy
/etc/passwd and or /etc/shadow files back to a server periodically, and an
awk script or two to parse out the users line to update the server's copy.
(i've done this, not recommended if you know as little as i do!, it isn't
pretty)

There is also Samba, which replicates the functionality of an NT PDC.
There is no such thing as a BDC for Samba, because if you are aware of what
a BDC actually does in NT, you could probably replicate the functionality
with a couple of shell scripts.  This BDC won't be able to deal with M$
PDC's.  Samba client software could then be used for mounting the Samba
shares.

Samba and Kerberos are appealing because these can be phased in with little
or no immediate impact (except your server up time goes up).

BTW, your point on companies adopting linux is well taken.  Many Fortune
500 Windows NT shops have still not replaced their NT PDC's with Windows
2000 because the planning/migration can be a real pain.

Richard A. Hubbard III
MCSE, MCDBA, MCSD, MCT, CLI, CLP,LCI,LCP,
 A+, Net+,I-net+
Training Manager, New Horizons Buffalo
richard.hubbard at nhwny.com
phone (716) 681-8500 x2241
           (716) 206-2241 Direct
fax      (716) 206-2222

                    "Michael R.                                                                                    
                    James"               To:     nflug at nflug.org                                                   
                    <mrjames at loca        cc:                                                                       
                    lnet.com>            Subject:     Linux Enterprise Desktops                                    
                    Sent by:                                                                                       
                    owner-nflug at n                                                                                  
                    flug.org                                                                                       

                    07/17/01                                                                                       
                    08:53 AM                                                                                       
                    Please                                                                                         
                    respond to                                                                                     
                    nflug                                                                                          

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