Network Settings on Standard Images

[Nicometo]

Hello all, I am wondering if someone has a proven, rock star, strategy for
creating base Leopard OS images for laptops vs. desktops in regards to
networking settings, Airport, modems, etc.

All of our desktop machines are connected via Ethernet and none use Airport,
nor any modems. However, almost all of our laptops connect to the network
via Airport, and in some rare cases via modem.

Is it a safe bet to include all the Airport and modems settings on a base OS
image deployable to all platforms, even though the desktops will never use
these settings? Or do we need to created separate images for laptops and
desktops.

Note, I thought about creating a Composer package just for laptop network
settings, however there were quite a few byhost files that were created in
the process, and to be honest, I am not sure how to handle those.

Thanks in advance for any help/information/strategies...
-- Tim Nicometo
Mayo Clinic
timn at mayo.edu
(507) 255-3034

[milesleacy]

Casper or not, I've always built images on the newest portable hardware available, then run the latest OS combo updater. This always gives me an image that will be backward compatible with all supported hardware

If there is a newer desktop hardware release than the latest portable, after testing the image generated on the latest portable, you may need to create a seperate desktop image using the newer hardware, though when the next OS combo updater is released, you should be able to go back to using an image created from the latest portable.

Since the MacBook Air has some unique hardware, it may require its own base image.

[ernstcs]

Hi Tim,

I use a single Leopard image for everything including AirPort settings.

I include all the required settings for our private network in the AirPort, but I turn Off the AirPort interface when I'm done configuring it before creating the image.

The assumptions are:

Desktop users will be wired so they won't ever need AirPort on and take up addresses
Laptop users would be wired the first time they logon and then turn on AirPort after that, or we make sure it's enabled before we hand it to them

This seems to work fine for us so far since our network is consistent everywhere. If you have multiple network configurations (because of geographical locations, etc.) then that gets a little difficult to do that in the single image.

Craig

[Nicometo]

Thanks Craig (again). I like this part of your post...

I think I will try this, test and see how it goes.

tim

[#5]

I'll have to dig around for the information, but you could manage your network interfaces using shell scripts that run after imaging the system. Again, I use InstaDMG for my base image, that way the image is never booted until it is laid onto the system. Once you have the image on the machine, then push your preference changes to the system. You may even be able to capture the settings using Composer and push those plist files to the system.

Just makes it cleaner, in my opinion.

Just my 2 pennies.

Steve Wood
Director, Information Technology
swood at integerdallas.com

The Integer Group | 1999 Bryan St. | Ste. 1700 | Dallas, TX 75201
T 214.758.6813 | F 214.758.6907 | C 940.312.2475

[tlarkin]

If you are using Leopard then you can configure everything via post
scripts with the following command

/usr/sbin/networksetup

Thomas Larkin
TIS Department
KCKPS USD500
tlarki at kckps.org
cell: 913-449-7589
office: 913-627-0351