[K12OSN] Generic Accounts?

[Doug Simpson]

We use the inventory sticker number for each computer K-5 and the
password is the same on all of those. We don't put them on the monitor
because those may move around without the computer and since some of our
drive mappings are mapped by computer's building location rather than
user or context, it makes it easier to keep track of the accounts. 

This may not apply to linux networks, but works well for us.

6-12 every user has their own login name.

Doug

Doug Simpson
Technology Specialist
De Queen Public Schools
De Queen, AR
simpsond at leopards.k12.ar.us
"A Dollar Saved is a Dollar Earned"


>>> "Terrell Prudé Jr." <microman at cmosnetworks.com> 10/24/2008 7:52 AM
>>>
That's how our district does it w/ our boxes.  Works out pretty well.

--TP
_______________________________
Do you GNU <http://www.gnu.org>?
Microsoft Free since 2003 <http://www.cmosnetworks.com>--the ultimate 
antivirus protection!


Todd O'Bryan wrote:
> Another option is to put a sticker on the monitor connected to the
> terminal that says
>
> Username: guest27
> Password: guest27-pass
>
> or something. Then students are pretty likely to log in using the
> password and username you've provided.
>
> 2008/10/12 Millard Hill <millard.hill at gmail.com>:
>   
>> I am setting up Linux thin clients for Atlanta Public School System
(RHEL 5
>> network attached storage servers for home directories when we
implement that
>> and CentOS 5 application servers) and we are also using autologin
(kiosk
>> mode).  We have also setup print and USB access for them to save
there data
>> to a thumb drive or print it out.  We presently aren't saving data
on the
>> server, but our next upgrade of the system will allow for individual
login
>> accounts.
>>
>> To setup up autologin you can make changes to your gdm config file
(in our
>> instance, /etc/gdm/custom.conf), to set it up to log in
automatically.  We
>> have given the thin client name the same name as the hostname which
is all
>> determined by DHCP, so the studfents don't even have to know the
hostname
>> they are logged in as, nor do they know the server that they are
logged into
>> (we have anywhere from 2-5 application servers at each school).
>>
>> If you want more details let me know as this is a district wide
initiative,
>> which is centrally managed, so I may be able to you steer clear of
other
>> issues that you may run into.
>>
>> Millard Hill III
>> Linux Engineer
>> Atlanta Public Schools
>> millard.hill at gmail.com 
>>
>> On Fri, Oct 10, 2008 at 2:57 PM, Jamie Lists <jamielist at gmail.com>
wrote:
>>     
>>> We're sprinkling LTSP clients all over a school in my district. I
need
>>> to have a generic account for kids to use.
>>> The problem is if i make one account called student for instance.
They
>>> all have the same home directory, which is bad.
>>> The only other way i can think of is to make 50 generic accounts
and
>>> then tell the kids.. ok on this client you need to login as
student38.
>>> Doesn't seem like such a great solution.
>>>
>>> Ideas?
>>>
>>> Thanks,
>>>  Jamie
>>>
>>> _______________________________________________
>>> K12OSN mailing list
>>> K12OSN at redhat.com 
>>> https://www.redhat.com/mailman/listinfo/k12osn 
>>> For more info see <http://www.k12os.org>
>>>       
>> _______________________________________________
>> K12OSN mailing list
>> K12OSN at redhat.com 
>> https://www.redhat.com/mailman/listinfo/k12osn 
>> For more info see <http://www.k12os.org>
>>
>>     
>
> _______________________________________________
> K12OSN mailing list
> K12OSN at redhat.com 
> https://www.redhat.com/mailman/listinfo/k12osn 
> For more info see <http://www.k12os.org>
>