This repository contains specific scripts and standalone applications that utilize the Casper Suite API.
Convert-SG-Search-Search-SG.sh
Create-JSS-Computer-Group-Report.sh
Create-JSS-Policy-Scope-Report.sh
Get-Network-Segments-as-csv.sh
Install-Configuration-Profiles.sh
JSS-Package-Report.sh
Make-StaticGroup-From-SmartGroup.sh
Description:
This script was designed to be run interactively in Terminal. It allows you to use the API (along with valid API credentials) to convert an existing Smart Computer Group into a new saved Advanced Computer Search, or convert an Advanced Computer Search into a new Smart Computer Group
Requirements:
To utilize this script, the JSS API account must have the following privileges:
- READ Smart Computer Groups
- READ Advanced Computer Searches
- CREATE Smart Computer Groups
- CREATE Advanced Computer Searches
Special Notes:
- Because of the need to use APi credentials with Create privilges, the script allows you to interactively enter the credentials so they don't need to be stored within the script.
- The script does only minor error checking. Please be sure you use proper API credentials or you will encounter errors.
- The script will let you choose the Smart Group or Advanced Search to convert into the other type from a list with index values next to their names.
- By default, when creating new Advanced Computer Searches, the only data column that will be displayed is "Computer Name" Currently it doesn't seem possible to extract the default column view set via the API to inject into the final xml. Feel free to modify the section when creating Advanced Computer Searches with additional view columns if you wish.
Warning Because of how the JSS API operates, when converting from a saved search into a Smart Group, there will be a delay as the API runs the full search for the item you select. There isn't a way to only pull the search criteria using the API WITHOUT also running the full search. This means it may take some time for that conversion direction to complete.
Usage:
Because this script uses some BASH specific items, please run the following against the script to make it executable before using it:
chmod +x /path/to/Convert-SG-Search-Search-SG.sh
To use the script, then do:
/path/to/Convert-SG-Search-Search-SG.sh
Description:
This script was designed to run against a Casper Suite 9.x server to generate a report on all Computer Groups in the JSS.
The resulting report will indicate the group's JSS ID, the group's name, if its a Smart Group and two columns that will show what policies the group is scoped to, which are: 'Policy Scopes' and 'Policy Exclusions'
Requirements:
To utilize this script, the JSS API account must have READ access to the following objects:
- Computer Groups
- Policies
Usage:
Make sure to edit the section that contains the API Username, Password and JSS URL before trying to run it.
/path/to/Create-JSS-Computer-Group-Report.sh
The script will display output of the steps and what its working on as it runs.
Notes:
Due to the large amount of cross referencing the script needs to do between groups and policies to generate an accurate report, on large JSS installations, it can take some time to complete a report. Some reference times I have seen - on a small JSS installation with only around 30 groups and about 40 policies, it completed a report in approximately 5 minutes. On a large JSS with 330+ groups and close to 300 policies, it took around 2 hours to finish a report. So completion time will vary depending on the size and complexity of your JSS.
While I've made every effort to ensure the resulting report is as accurate as possible, I can't gurantee 100% accuracy on all JSS installations since there may be unknown variations I didn't account for. If you see any inconsistencies in the final report, feel free to send me some information and I can see about making the script more accurate.
Because its impossible to ensure absolute accuracy, please do not use this script as your sole guidance on which groups can be safely removed. Always do some of your own investigation to ensure you are not removing anything in use. However, this should at least help in pinpointing the groups to examine more closely.
Description:
This script was designed to run against a Casper Suite 9.x server to generate a basic scoped related report on all Policies in the JSS.
The resulting report will indicate the policy's JSS ID, the policy's name, and five additional columns that will show the following information:
ALL COMPUTERS (SCOPE) - Yes or No
COMPUTERS (SCOPE) - individual computers added to scope
COMPUTER GROUPS (SCOPE) - Computer Groups in scope
LIMITATIONS (SCOPE) - Anything added to Limitations, like Network Segments, etc
EXCLUSIONS (SCOPE) - Anything added to Exclusions, like Computer Groups, Network Segments, etc.
Requirements:
To utilize this script, the JSS API account must have READ access to the following objects:
- Policies
Usage:
Make sure to edit the section that contains the API Username, Password and JSS URL before trying to run it.
/path/to/Create-JSS-Policy-Scope-Report.sh
The script will display output of the steps and what its working on as it runs.
Notes:
While I've made every effort to ensure the resulting report is as accurate as possible, I can't gurantee 100% accuracy on all JSS installations since there may be unknown variations I didn't account for. If you see any inconsistencies in the final report, feel free to send me some information and I can see about making the script more accurate.
Because its impossible to ensure absolute accuracy, please do not use this script as your sole guidance on which items can be safely removed. Always do some of your own investigation to ensure you are not removing anything in use. In addition, its possible for some policies to not have available scope other than set to "All Computers" or even no scope and be disabled, but may not be items you will want to remove. Use your own judgement on what to delete from your JSS!
Description:
This script was designed to run against a Casper Suite 9.x server to pull down the current Network Segments as a csv file.
To use it, you will need to supply the API credentials within the script. The API account must have at least Read access to the "Network Segments" object in the JSS Objects privileges category.
Usage:
/path/to/Get-Network-Segments-as-csv.sh
The resulting csv file will be named "Network-Segments.csv" and moved to your Desktop when completed.
To do:
Currently this script does no error checking. If you supply incorrect credentials, or credentials that do not have access to the Network Segments object, it will simply not work. it will not currently report back with an error. A future version will add some error checking and validation.
Description:
The Install-Configuration-Profiles.sh script uses the Casper/Jamf Pro API along with supplied API credentials and one or more JSS IDs for Configuration Profiles stored on the server, to download and install them on the target Mac.
The script will use either hardcoded API values, if entered in the appropriate locations, or can obtain them as supplied in script parameters.
$4 for API Username
$5 for API Password
$6 (Optional) for the JSS URL
$7 for the Configuration Profile ID or IDs
$8 for the rename flag (explained below)
Special notes on the script parameters:
The $6 parameter for the JSS URL is optional, if you plan on using it on managed Macs. If not supplied, the script will determine the JSS URL from the com.jamfsoftware.jamf.plist file on the Mac. It can of course be supplied and may be useful for testing profiles that are hosted on a dev JSS for example.
If multiple IDs are supplied to the $7 script parameter, separated by spaces, the script will determine that it needs to install multiple items and loop over each supplied ID and download and install each one in the order supplied.
Rename flag
If the rename flag ($8) is supplied with a positive value (see script for types of accepted values) this setting will direct the script to rename the Configuration Profiles UUID string to something human readable. By default, Configuration Profiles from the JSS are given a unique UUID string that is not easily recognizable. For example, a profile given a display name such as "Office 2016 Settings" may end up with a Unique Identifier string like "A49E0GCF-D800-4B85-B8D4-E10FB6G83EBF" If the above setting is enabled, the script will reset the UUID in the profile xml to something such as "com.acme.office-2016-settings" making it more recognizable when viewed with sudo profiles -P in Terminal. The "com.acme" example string is obtained from a hardcoded value in the script called "IDStringStart". Please be sure to change this string if you plan on using the rename function.
User Level vs Computer Level Profiles
In addition to the above functions, the script will also attempt to install a profile in the correct space, based on how the profile was created in the JSS. For example, if the profile was set as User Level, it will try to install the profile for the current user. If it was set to Computer Level, it will install it instead as a Computer Level Profile. If no specific setting was set, it assumes Computer Level and installs it as such.
Requirements:
The API account must have read privileges to OS X Configuration Profiles, and you must have at least one Configuration Profile set up in the JSS.
Usage:
To use the script from a Jamf Pro/Casper Suite policy, upload or create the script in the JSS. Set up descriptions if desired for Parameters 4 - 8 as described above and in the script. When using the script, be sure to supply at least Parameters 4, 5 and 7 with values. These are the API Username, API Password and at least one Configuration Profile ID from the JSS. Keep in mind all of these can be supplied as hardcoded directly in the script, but you would lose the flexibility of being able to install any profile. It's also less secure to keep API credentials within a script. The script output will show which profile it downloaded and installed and the success or failure exit for each one. If the rename flag is enabled, it will show the renamed profile name in the script output.
Description:
The JSS-Package-Report.sh script was designed to help with building a spreadsheet of all packages in your JSS, and include information about associations of each package with Policies and Casper Admin Configurations.
The script works by accessing all policy xml data and all configuration xml data and then does an automated cross referencing of each Package ID from the JSS to those policies and configurations. Along the way it builds a local file that is, at the end, converted into a csv file for viewing in a spreadsheet application.
Requirements:
To utilize this script, the JSS API account must have READ access to the following objects:
- Packages
- Policies
- Configurations
What it builds:
The final spreadsheet will contain the following column headers:
| Header | Explanation |
| LINK | A link to the package in your JSS (Note that because it creates a csv, these are not clickable links) |
| ID | The JSS ID for the package |
| NAME | Equivalent to Display Name in your JSS |
| CATEGORY | The Category the package was added to in Casper Admin or within your JSS |
| FILENAME | The physical file name of the package. Often matches the Display Name, but they can differ |
| INFO | Any Info text entered for the package |
| NOTES | Any Notes text entered for the package |
| PRIORITY | The Priority value assigned to the package. Often used in Casper Imaging configurations |
| REBOOT REQUIRED | (Boolean) Whether the Requires restart option is checked for the package |
| FILL USER TEMPLATE | (Boolean) Whether the Fill user templates (FUT) option is checked for the package |
| FILL EXISTING USERS | (Boolean) Whether the Fill existing user home directories (FEU) option is checked for the package |
| BOOT VOLUME REQUIRED | (Boolean) Whether the Install on boot drive after imaging option is checked for the package |
| ALLOW UNINSTALLED | (Boolean) Whether the Allow package to be uninstalled option is checked for the package |
| OS REQUIREMENTS | Any values entered into the OS Requirement field |
| REQUIRED PROCESSOR | Indicates if the Install only if architecture type is: box is checked and the value chosen from the drop down menu |
| SWITCH WITH PACKAGE | Displays any value chosen from the Substitute Package drop down menu, or Do Not Install if none were selected |
| INSTALL IF REPORTED AVAILABLE | (Boolean) Whether the Install Only if Available in Software Update option was checked for the package |
| REINSTALL OPTION | Unclear, but may refer to if Autorun was enabled for the package |
| TRIGGERING FILES | Unclear what this option refers to. This will get updated once determined |
| SEND NOTIFICATION | (Boolean) Unclear what this option refers to. This will get updated once determined |
| POLICIES | A list of policy names the package is currently assigned to. Each policy name is surrounded by single quotes |
| CONFIGURATIONS | A list of Casper Admin configuration names the package is currently assigned to. Each configuration name is surrounded by single quotes |
Usage:
/path/to/JSS-Package-Report.sh
The script will output information in Terminal as it runs, explaining steps and indicating which items it is accessing. The final csv file will be moved to your Desktop and named in the format of:
your-jss-url_Packages_YYYY-MM-DD.csv
Disclaimer
This script should ONLY be used for reference purposes and not relied solely on for determining which packages can be safely deleted from your JSS. While the script should help you wittle down the package list to examine more closely, and I have made every effort to make the script generate an accurate report, I cannot gurantee 100% accuracy due to unknown variations in each JSS it may be run against.
I am not liable for any packages that are deleted which may have had dependencies, and which may cause these dependencies to fail afterwards. As should always be the case, use discretion when deciding which items to remove from your JSS.
Description:
This script was designed to run against a Casper Suite 9.x server to create a new Static Computer Group from a Smart Computer Group. The resulting Static Group will contain all the same computer members as the Smart Group.
To use it, you will need to supply API credentials (username & password) to the script by passing these in $1 and $2 respectively. The API account must have both Read and Write access to the "Computer Groups" object in the JSS Objects privileges category. When the script is run, assuming correct API credentials are passed to it, an Applescript dialog will present on screen with a list of all existing Smart Computer Groups in your JSS. (Note: only Smart Groups are presented in this dialog to avoid selecting any existing Static Group) Select one from the list and click OK to continue to create the new Static Group. The new group name will use the name of the selected Smart Computer Group as a base wtih _Static appended to the end.
Usage:
/path/to/Make-StaticGroup-From-SmartGroup.sh 'apiuser' 'apipassword'
The script will report results in the Terminal window (success or failure)
To do:
Currently this script only does some minor error checking. It will detect if the supplied credentials did not have the correct Read access permissions. It will also detect if the creation of the Static Group failed. A future version will add some additional error checking and validation for the various steps the script needs to work.
Casper-Report-Downloader.app
Synopsis: Download any saved Advanced Computer Search in your JSS as a csv file without needing to log into your JSS first.
Self Service Checker.app
Synopsis: View what Self Service.app would show for any Mac in your JSS. Locate the Macs using several different search methods.