User Guide
Table Of Contents
- System Imaging and Software Update Administration
- Contents
- About This Guide
- PartI: System Imaging Administration
- Understanding System Imaging
- Creating NetBoot and NetInstall Images
- Using System Image Utility
- Creating Images
- Understanding Workflows
- Workflow Components
- Configuring the Customize Package Selection Action
- Configuring the Define Image Source Action
- Configuring the Add Packages and Post-Install Scripts Action
- Configuring the Add User Account Action
- Configuring the Apply System Configuration Settings Action
- Configuring the Create Image Action
- Configuring the Enable Automated Installation Action
- Configuring the Filter Clients by MAC Address Action
- Configuring the Filter Computer Models Action
- Configuring the Partition Disk Action
- Assembling Workflows
- Adding Software to NetBoot and NetInstall Images
- Setting Up NetBoot Service
- Setting Up Clients to Use NetBoot and NetInstall Images
- Managing NetBoot Service
- Solving System Imaging Problems
- PartII: Software Update Administration
- Understanding Software Update Administration
- Setting Up the Software Update Service
- Managing the Software Update Service
- Manually Refreshing the Updates Catalog from the Apple Server
- Checking the Status of the Software Update Service
- Stopping the Software Update Service
- Limiting User Bandwidth for the Software Update Service
- Automatically Copying and Enabling Updates from Apple
- Copying and Enabling Selected Updates from Apple
- Removing Obsolete Software Updates
- Removing Updates from a Software Update Server
- Identifying Individual Software Update Files
- Solving Software Update Service Problems
- Glossary
- Index

Chapter 3 Setting Up NetBoot Service 53
6 Click Save.
From the Command Line
You can also specify a volume to store shadow files on by using the serveradmin
command in Terminal. For more information, see the system image chapter of
Command-Line Administration.
Using Images Stored on Remote Servers
You can store NetBoot or NetInstall images on separate remote servers other than the
NetBoot server. You must copy the images from the NetBoot server to the remote
server and then configure the remote server to use the images.
To store an image on a separate remote server:
1 Copy the image.nbi folder from the NetBoot server to the remote server on a NetBoot
sharepoint (/Library/NetBoot/NetBootSPn).
If the image is on the remote server, you can create the .nbi folder on the NetBoot
server by duplicating an existing .nbi folder and adjusting the values in its
NBImageInfo.plist file.
2 Open Server Admin and connect to the remote server.
3 Click the triangle to the left of the server.
The list of services appears.
4 From the expanded Servers list, select NetBoot.
5 Click Settings, then click Images.
6 For each image you want your clients to see from the remote server, click the checkbox
in the Enable column.
7 Select the protocol you want NetBoot to use when serving your image (NFS or HTTP).
8 Click Save.
Specifying the Default Image
The default image is the image used when you start a client computer while holding
down the N key, providing that the client hasn’t selected a NetBoot or NetInstall
volume via Startup Disk. See “Starting Up Using the N Key” on page 58.
If you’ve created more than one startup disk image, you can use the NetBoot service
settings in Server Admin to select the default startup image.
Important: If you have diskless clients, set their boot image as the default image.
If you have more than one NetBoot server on the network, a client uses the default
image from the first server that responds. There is no way to control which default
image is used when more than one is available.










