2 Replies Latest reply: Mar 5, 2011 1:17 PM by foilpan
macno Level 1 Level 1 (0 points)
I'm helping a K-8 school get a handle on their IT issues and one of the tasks I am doing this Spring is taking teacher laptops (10 of), installing more RAM, upgrading from 10.5 to 10.6.6 and setting them up to use share points on the network.

Currently the laptops are just laptops that were given to the teachers and were set up with very little controls in place. They are all admins, have no network login, login straight on boot, etc.

What I have done is set up generic users in Workgroup Manager by grade (teacher1, teacher2...) and created share-points in the "Teacher" directory on the server (data hard drive).

We have groups to Students, Teacher, Admin.

I've configured a NetInstall 10.6.6 image on the server and I'd like to do upgrade a bunch of them at the same time. I'll be hand configuring them after install because it's such a small amount of computers to handle.

After I've done the install and established an ADMIN account on each laptop (we use a generic admin/pwd on all computers so we can monitor activity from time to time via ARD) what do I do?

Do I need to make sure Directory Utility is pointing to LDAP server and then set Login Settings for Name/Password field and that's that?


24" iMac - 2.16Ghz, Mac OS X (10.4.10)
  • 1. Re: Establish New Client Accounts with New Laptop Installs
    macno Level 1 Level 1 (0 points)
    The teachers shouldn't be allowed to install applications EXCEPT Apple Software Updates -- currently we have Software Update Server running but I have no idea if it's working.

    How can I test that?

    How can I ensure they are able to download and install Apple Software Updates regardless of where they are? These are take home laptops too.
  • 2. Re: Establish New Client Accounts with New Laptop Installs
    foilpan Level 4 Level 4 (1,385 points)
    even if you're talking about just 10 machines, i'd use deploystudio and other tools to do most of your work here.

    you can use a workflow to upgrade or image the machines, bind them to OD, set hostnames, install apps, etc.

    manage as much user environment stuff via mcx.

    if you use munki to manage software updates, you can leave the local (or mcx) prefs alone, specifying your internal swupd server only in the munki client prefs. when the laptops are on the school network, they'll look to the local server for updates. when home, they'll use apple's. this has the added advantage of not requiring local admin access to install updates (at least when they're on the school lan).