Please don't apologise for running 10.6.8, I am a strong believer in 'don't fix what aint broken' :-) Thank you for the swift reply!I also believe in ' Don't fix what aint broken! Unfortunately in this case, we were under the impression that these new imacs were being shipped with 10.6 and not Lion, but that's what I get for letting a colleague order them for me - lesson learned!
This script will look for and # files in pkg_dir and at the root level of any sub-directories of pkg_dir pkg_dir="$dir/my_server_software"# Thus, your stage directory should look like this: # $dir # a_sync.command # $pkg_dir # $nb_stg # $dmg_stg # # This should cover all of the files required for your system deployment, # thus you should back this up (preferably off site) whenever you make changes### Script action ### # STEP 1: Copy customizations to the staging Resources directory echo "Copying current packages to local resource directory" pkgs=`ls $pkg_dir` for pkg in $pkgs; do if [ ! `basename -s $pkg_dir/$pkg` == "$pkg" ]; then echo " $pkg" ditto $pkg_dir/$pkg $res_stg/Post-actions/$pkg elif [ -d $pkg_dir/$pkg ]; then echo " $pkg.pkg" ditto $pkg_dir/$pkg/$$res_stg/Post-actions/$fi done# STEP 2: # Sync the staging directories with each of the replicas for host in $replicas; do echo "Syncing staging Net Boot directory to $host" rsync -togrl --delete -e /usr/bin/ssh $nb_stg/ [email protected]$host:$nb_shpt/ echo "Syncing staging disk images directory to $host" rsync -togrl --delete -e /usr/bin/ssh $dmg_stg/ [email protected]$host:$dmg_shpt/ done I've noticed that the Network Image Utility allows images to be updated from the original, but you cannot export the image to another server if an image with the same name is already there.
Can you synchronize the original image with each server (if the original system is on a Fire Wire HD that you could plug into each server for instance)?
To use PXE to initiate operating system deployments you must have a PXE service point site role installed and configured properly.
For more information about setting up the PXE service point site role, click the following link: How to Configure the PXE Service Point Use the following procedure to deploy an operating system using PXE: If you are using the English version of Windows PE and communicating with a Configuration Manager 2007 site server running a double byte character set you should assign a password containing only simple characters or not require a password for PXE initiated deployments.
Many thanks in advance, Sam The procedure to make the on the new (Lion) mac's and copy to Net Boot SP0 is good.don't forget to enable this netboot image as default.
It should work with older Mac's too (except the pre-core2duo mac's)Use the same version of Deploy Studio (the Runtime and the Server should be same version)so either re-make the using the same version of Deploy Studio, or update the server to the same version as you use to create the (probably rc130)You should be able to restore all existing images (10.6..x too) on existing mac's and 10.7.x images to new Mac's.You must also add the boot images to the PXE service point before you add them to a standard distribution point so the logged in administrator will have access to the associated files.You will need at least one boot image for each type of processor architecture present in your Configuration Manager 2007 environment on the distribution point.For example, if you have computers with x64 processors in your environment you will need at least one x64 boot image assigned to the PXE distribution point even if you only plan to deploy x86 operating systems.This is because PXE stub needs some of the native files contained in the boot image to identify the computer before the task sequence can be started.Or does anyone use rsync to update the contents of /Library/Net Boot/Net Boot SP0/ on each server with a "master" server?