OS X Server Configuration File

[mleacy]

I primarily manage Mac servers these days and would like to use InstaDMG to create my base installs. I also use the Casper suite, which I use for deploying patches and applications.

What I’m having a bit of difficulty wrapping my head around is how to handle the server configuration file in an automated way. I figure I’ll pre-generate the file once I have the serial & MAC addresses for the new hardware, but then how to get it onto the machine? I have considered a few options, and would like to get opinions of those who know more about InstaDMG than I.

Option 1: Build it into the InstaDMG workflow. This will result in a seperate base image for each server, which doesn’t seem very practical, storage-wise.

Option 2: Build and continually update a package that contains configuration files for all of my active servers. Include this package in the InstaDMG workflow.

Option 3: Build the InstaDMG server image without a configuration file. Deploy it as a separate package to be included in a Casper configuration.

Options 2 and 3 seem best to me, but I’d like to get some opinions before I start pursuing these, or perhaps another option I haven’t thought of.

Thanks in advance.

[brent.bb]

There’s some more options for doing this.
4: How are you deploying your image to your servers? If you are using NetRestore, then it may be possible to insert the appropriate configuration files via the Post-Actions.
5: Insert a basic configuration file that tells the server to get its configuration from Open Directory. You should be able to generate and insert the configurations using the Server Assistant app. Of course, this requires your OD infrastructure to be up before the server you are imaging.
6: Make a post-boot first-run package with all of the configuration files as the payload to some hidden directory, with a postflight script that will determine the correct set and place it accordingly. You may even be able to use this package with the NetRestore Post-Actions.

[mleacy]

[quote][color=Violet]How are you deploying your image to your servers?[/color][/quote]

Currently by manual install. The goal is to use Netinstall or Casper Imaging. I’d like to build the image, using the InstaDMG workflow, to include just the OS and Apple patches & updates. I’ll handle additional software and service configuration via Casper policies once the image is laid down.

[QUOTE][color= Violet]5: Insert a basic configuration file that tells the server to get its configuration from Open Directory. You should be able to generate and insert the configurations using the Server Assistant app. Of course, this requires your OD infrastructure to be up before the server you are imaging.[/color][/QUOTE]

Excellent one I hadn’t thought of.

[QUOTE][color= Violet]6: Make a post-boot first-run package with all of the configuration files as the payload to some hidden directory, with a postflight script that will determine the correct set and place it accordingly. You may even be able to use this package with the NetRestore Post-Actions.[/color][/QUOTE]

I don’t think this is necessary, since configuration files are named by MAC addresses, which are reasonably unique. The server just uses the one that matches the hardware and ignores any others. These are also relatively small files. You should be able to get more than 10 configuration files to the megabyte. This is why I was leaning toward a package of all config files until you reminded me of the OD option.

[Author]

Posts