This guide is intended for Apple Device Management (ADM) administrators or site administrators of the ADM service using the Casper Suite from JAMF Software. It provides guidelines for the intended use of the Casper Suite used for the ADM service, and it does not serve as a complete reference guide to the Casper Suite. 

View the complete Casper Suite Administrator's Guide by JAMF Software for more information.

JAMF Software Server (JSS)

The JAMF Software Server (JSS) address for the university's ADM service is https://jss.umd.edu:8443. Users must use their university Directory ID and password to log into the JSS for the ADM service.

Top

ADM site administrator's access to Casper admin

Site administrators should email Top to be granted access to the Casper Admin application. Once given access to Casper Admin, Site administrators will be able to download the most current version of the Casper Suite through Box.

Top

Guidelines for using Casper admin

• Log in to JSS and switch the Site to Full JSS and then log into Casper Admin.
• Close Casper Admin as soon as possible after completing tasks. If more than two users are trying to make changes using Casper Admin, database integrity could be compromised.
• Do not delete any packages before confirming the deletion with an ADM Administrator through the ADM Mailing List at device-management@umd.edu. Failure to do so can result in loss of access to the service.
• Save early and often while making changes to packages and configurations.
• Only use Casper Admin to upload and index packages. All other administrative tasks can be performed by using the JSS.

NOTE: There is no limit to the number of users that can be logged in to the JSS simultaneously. Multiple simultaneous logins to the JSS will not compromise the integrity of the JSS database.

Top

Guidelines for naming and uploading packages in Casper admin

• All site administrators must adhere to follow naming conventions for uploaded packages and configurations. The Package naming conventions ensure the easy and effective package deployment from the production server.
  
  • Do not upload a package that has already been added to the server.
• ADM administrators will be creating and uploading packages of the most common software products. If changes to an uploaded package are necessary, contact the ADM administrators through the ADM Mailing List at device-management@umd.edu.
  
  • Package names must include the full product name (or function) and version number.
• Package names do not need to be dated unless the package contains an OS image.
  
  • Information about a package should be added to the Info and Notes fields of the Package Description.
• Double-click on the package in Casper Admin. The Infoand Notes fields are found under the General tab of the Package Description window.
• General information about the package should be entered into the Info field (e.g., type of license, settings).
• The Notes field should contain information about the creator of the package and the hardware and OS version used to create the package.
• All packages must be assigned a Category.
  
  • Suggestions for improving the naming conventions should be forwarded to the ADM mailing list at device-management@umd.edu.

Top

Guidelines for creating and naming configurations in Casper admin

• Parent configurations should only be created by ADM administrators.
• Site administrators are encouraged to create Smart configurations.  If a different Parent Configuration is needed, contact the ADM administrators through the ADM Mailing List at device-management@umd.edu.
• Smart Configurations should be named according to the name of their parent configuration and the building and room number where the configuration will be deployed. For example, a Mavericks configuration for room 1137 in McKeldin Library would be named Mavericks Libraries MCK 1137. In this configuration, the parent and child configurations are arranged as follows:
  
  • Parent configuration: Mavericks. 
  • First Mavericks child configuration: Mavericks + Casper.
  • Second Mavericks child configuration: Mavericks Common Software
  • First Mavericks Common Software child configuration: Mavericks IT-IDS.
  • Second Mavericks Common Software child configuration: Mavericks Libraries.
  • First Mavericks Libraries child configuration: Mavericks Libraries MCK 1137.

NOTE: In the example above, there is one standard parent configuration, named "Mavericks" and a smart child configuration called "Mavericks Common Software".  Site administrators with Casper Admin access should create a smart configuration for their site under the Mavericks Common Software configuration.  That smart configuration will act as a container for all of their configurations.

• Site administrators must follow the above naming convention because Casper Imaging does not display configurations in a hierarchy. Instead, Casper Imaging displays configurations as an alphabetized list.

Top

Guidelines for adjusting JSS features and/or settings 

A number of JSS settings are uniform for all users.  While this may compromise the needs of some users, the goal of the uniform settings is to maintain a consistency that ensures optimal operations.  If there are any questions, concerns, or suggestions regarding JSS settings, contact the ADM administrators through the ADM mailing list at device-management@umd.edu.

Top

Support for Casper Suite technical issues

For support with ADM service issues, contact the ADM administrators through the ADM mailing list at device-management@umd.edu. This mailing list is designed to not only connect site administrators to support but to serve as a resource for all site administrators the University. 

Additionally, questions about the Casper Suite and the JSS can be posted on JAMF Software's global social community of Casper Suite users, JAMF Nation Community.

Top