Type Name Latest commit message Commit time Failed to load latest commit information. JSS Recipes A collection of recipes that helps administrators use to automate their software testing workflow. Table of Contents • • • • • • • • • • • • • • • • • • • • • Introduction This repository of recipes strives to represent a collective expression of best-practices in automated software patch management for administrators of Jamf Pro (Casper Suite). Let us unpack that statement!

Package payload for the Policy is the Skype for Business.pkg download from Microsoft. Test deployment didn't reveal any problems. Put into production and start to see reports install doesn't work for some users. Checking policy log shows no errors, but end result is no Skype for Business installed. Keeping Skype up to date on your business’ MacBook computers is a good way to make sure you have both the latest security updates and access to the most up-to-date features.

First and foremost, the contributors of this repository aim to agree upon a standard software testing workflow that mirrors community-supported standards in use by other deployment frameworks. While it is possible to upload and deploy software in many ways using JSSImporter, the workflow reflected in these recipes will be safe, consistent, and sane. Next, we aim to promote this standard workflow by peer-reviewing all recipes in this repository. This process will ensure that the recipes can be relied upon to faithfully realize the standard workflow, and administrators will be able to extend and override these recipes with predictable and consistent results. We strive to include the most common apps expected to be part of the AutoPkg domain, including but not limited to those of the 'standard'. Finally, we want to make the style of JSS recipes consistent, as set forth below in the. Standard workflow for JSS recipes Software packages are uploaded to distribution points and made available through a Self Service policy to members of the Testing group who do not already have the latest version of the software.

The following pieces work together to accomplish this workflow: • JSS recipes use recipes that produce standard Apple package (pkg) files as parents. This ensures that a pkg can be uploaded to the distribution points. • The resulting package file's name includes the software's name and version number (e.g. • The package file's metadata includes any OS version restrictions that govern that product's installation. • The JSS recipe specifies the category for the package file itself, which is chosen from among a limited set of approved categories. (See the list of categories in the below.) If the category doesn't exist, it will be created. • JSSImporter uploads the package file to all configured distribution points.

• The SmartGroupTemplate.xml file tells JSSImporter to create or update a smart group called [SoftwareName]-update-smart. The criteria of this group are: • the computer has the software in question installed • the version does not match the newest version that AutoPkg found • the computer is a member of a group called 'Testing' (which is created and maintained manually by the Jamf admin) • The PolicyTemplate.xml file tells JSSImporter to create a single Self Service policy for each product, called Install Latest [SoftwareName]. The policy: • installs the latest package file. • is scoped to the smart group mentioned above. • includes a Self Service icon and description. • category is Testing.

This groups policies together under the Testing category on the Policies page of the JSS web interface to separate and distinguish them from other policies. If the Testing category doesn't exist, it will be created. • has an execution frequency of 'Ongoing' to allow multiple runs should tests fail. However, following a successful installation, the Self Service policy performs a recon run, which will drop the computer out of the smart group, thus preventing further executions until the next update is made available. This also enables reuse of the same policy without needing to 'Flush All' the policy logs. • No groups other than the smart group mentioned above are created or modified.

• In the rare case of needing an extension attribute to determine whether a package is out-of-date, and thus used to determine membership in the smart group, extension attributes will be created and/or updated. Download message app for iphone on mac. A separate [SoftwareName]ExtensionAttribute.xml file is required for this. This is most commonly the case with apps that either don't live in /Applications or report different version numbers for CFBundleShortVersionString and CFBundleVersion (Jamf only uses CFBundleShortVersionString for inventory). The cumulative effect of all this is that software managed with AutoPkg and JSSImporter will be uploaded and configured for deployment only to computers which have clearance to install it, and will require user interaction to install.