12.03.2014 Views

Casper Suite Administrator's Guide v8.7 - JAMF Software

Casper Suite Administrator's Guide v8.7 - JAMF Software

Casper Suite Administrator's Guide v8.7 - JAMF Software

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Fill Existing User Home Directories<br />

Selecting this option copies the files and folders in the first home directory located in /Users/ to every<br />

existing home directory on the client computer.<br />

Note: This option is only available for DMG packages.<br />

This package must be installed to the boot volume at imaging time<br />

If this option is selected, <strong>Casper</strong> Imaging installs the package with the first run script.<br />

Stage<br />

You can limit how a package is used and deployed by choosing one of the following options from the<br />

Stage pop-up menu:<br />

• Testing—The package can only be deployed using <strong>Casper</strong> Remote (not a policy), and can only be<br />

pushed to five computers at a time.<br />

• Non-Deployable—The package cannot be deployed. This setting is useful if the package needs to be<br />

taken out of production temporarily for licensing or other reasons.<br />

Deleted—The package has been deleted from <strong>Casper</strong> Admin.<br />

• <br />

Allow Uninstall<br />

Selecting this option allows administrators to uninstall a package using a policy or <strong>Casper</strong> Remote.<br />

Administrators will not be able to uninstall a package using a policy or <strong>Casper</strong> Remote unless this option is<br />

selected.<br />

Some packages—for example, operating system updates and security updates—should not be<br />

uninstalled, since they contain files required to boot the client computer.<br />

Note: A package must be indexed before this option can be selected. (For more information on indexing<br />

packages, see the “Indexing Packages” section.)<br />

OS Requirements<br />

If certain operating system requirements are needed to install a package, enter the requirements in this<br />

field using the following guidelines:<br />

If a package can be installed on any version of OS X v10.6 (but not v10.5), type “10.6.x”.<br />

If a package can only be installed on OS X v10.5.6, type “10.5.6”.<br />

• If the entry has more than one requirement, separate each requirement with a comma.<br />

If a package does not have any operating system requirements, leave this field blank.<br />

• <br />

Install Only if Processor Is [PowerPC/x86]<br />

Some packages are built only for a single architecture. You can specify this information by selecting this<br />

option and choosing PowerPC or X86 from the pop-up menu.<br />

To install an alternate package when a non-compliant architecture is encountered, choose an alternate<br />

package from the If the target computer’s processor is not there pop-up menu.<br />

119

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!