Casper is the component that is used to image, update, and maintain existing Macintosh computers or set-up new ones. Casper's functionality means consistency between computers, whenever and wherever they're deployed. Local or remote imaging is easy and packages can be pulled from local OS X, Linux, Solaris, and/or Windows servers. You can schedule this activity across your network in the middle of the night, over the weekend, at login, or whatever works for your organization. Using Casper, you can reload a computer from scratch, remove unauthorized applications, perform preventative maintenance, and more.
Even though Network Startup devices can be used to individually image machines, Casper can cost-effectively deliver consistent first-images to all machines using a locally attached FireWire drive.
Casper also gives you the flexibility to do more with your installs. Casper comes with options for installing images, such as: erasing the disk, installing software, naming the computer, creating local user accounts, binding to Active Directory, specifying network settings, and rebooting. Since all of these unique settings are established prior to imaging, there is very little post-fix work to be done.
The most efficient way to update a deployed machine is to use Casper. Casper initiates an end user forced pull from a File Share that has the computer's required packages. The forced pull has dramatically lower network usage than the standard push to end users' machines.
The File Shares that Casper uses as a package source can be housed on either OS X, Linux, Solaris, and/or Windows computers. Since the only requirement for a package source is the support of AFP or SMB, an organization can have as many shares as needed to support multiple floors or locations.
Beyond standard package pushing and uninstalling, Casper has the ability to manage virtually every aspect of the client computers. You can manage the mapped printers, local accounts, Active Directory bindings, add or remove items from user's Docks, and run Software Updates from locally hosted SWU servers.
Supporting machines that are frequently imaged and updated becomes easier because troubleshooting utilities can be run remotely. These actions can be run manually or on an automated schedule: