[Casper] 10.5.6 Laptop Airport Issues

[John Wetter]

Apple and JAMF both say you must always use the most recent hardware to build your image.  Not all 10.5.6's are created equal.  It's important to look at the build number.  The build is what is important.  On the new macbooks and MBP's you'll notice that the build of the OS is 9S2110 or larger.  The actual release of 10.5.6 available is 9S55.  9S55 will not have the drivers for the latest white macbook or the latest iMac and also the latest MBP.  So... you'll need to make a new base from that new hardware.  If it isn't really time sensitive I'd do yourself a favor and wait until 10.5.7, but if like me you didn't have that option, you'll need to make a new base image.  I names mine 10.5.6_base_build9S2110.dmg instead of the normal 10.5.x_base.dmg name scheme so that I know it's a special build.

Apple usually updates all the drivers at the next dot update.  10.4.11 did not include these drivers, which means the aluminum iMacs that shipped with Tiger will forever need a special build unless you purchase the Leopard update.

John

--
John Wetter
Technology Support Administrator
Educationsl Technology, Media  & Information Services
Hopkins Public Schools
952-988-5373
________________________________
From: casper-bounces at list.jamfsoftware.com [casper-bounces at list.jamfsoftware.com] On Behalf Of Wade, Evan C. [ecwade at capousd.org]
Sent: Wednesday, April 08, 2009 11:05 AM
To: casper at list.jamfsoftware.com
Subject: [Casper] 10.5.6 Laptop Airport Issues

We are having a problem with imaging machines using a 10.5.6 base image.  Specifically, when the image is deployed onto newer Macbooks (both plastic and aluminum) and MacBook Pros, the airport configuration does not work.  The WEP keys are still registered in the system keychain, and the airport PLIST is correct, but the laptop will not join either wireless network.  I have tried using an external keychain install package at imaging time paired with an On-First-Run configuration AppleScript (using Keychain Scripting), but it does not work in production, presumably due to limitations of keychain scripting (the technique worked perfectly when run locally on affected machines).

This base image includes all of the latest software updates as of yesterday (including the AirPort client update).  Is anyone else experiencing this issue, and (more importantly) have you found a fix that works consistently?

Evan Wade
TIS Support Technician - 949-234-5500
Capistrano Unified School District

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://list.jamfsoftware.com/pipermail/casper/attachments/20090408/ea30dbf3/attachment.html