Archive for November 10, 2017

Downloading macOS Sierra from the Mac App Store

November 10, 2017 3 comments

Now that macOS High Sierra has been released, it’s become more difficult to access the macOS Sierra installer in the Mac App Store (MAS) for those who still need it.

Previous versions of OS X and Mac OS X which were purchased by an Apple ID will appear in the MAS’s Purchased list for that Apple ID, but macOS Sierra is an exception because it did not need to be purchased using an Apple ID.

Screen shot 2015 11 19 at 2 43 08 pm

Fortunately, Sierra has not been removed from the MAS and it is still available for download. Apple has a KBase article, available via the link below, which shows how to access the macOS Sierra page in the Mac App Store:

To access the macOS Sierra page directly, please click on the link below:

That link should open the MAS and take you to the macOS Sierra download page.

Screen Shot 2017 11 10 at 11 06 58 AM

In the event that you’re blocked from downloading macOS Sierra, you should be able to download it in a virtual machine. I have a post on how to do this, available via the link below:

Categories: Mac administration, macOS

Session videos from Jamf Nation User Conference 2017 now available

November 10, 2017 1 comment

Jamf has posted the session videos for from JAMF Nation User Conference 2017, including the video for my Apple File System session.

For those interested, all of the JNUC 2017 session videos are available on YouTube. For convenience, I’ve linked my session here.

Adding installer package code-signing to AutoPkg workflows

November 10, 2017 2 comments

As part of building an AutoPkg workflow to create installer packages, one of the requirements I was given was that any packages that weren’t already signed by the vendor needed to be signed using a Developer ID Installer signing certificate.

Screen Shot 2017 11 09 at 9 58 53 PM

Signing installer package is not usually an outcome of most AutoPkg workflows, since code signature verification can be used at the download end to make sure that the application is what it is supposed to be. However, there were several good reasons for adding a package signing step to the workflow, including:

  1. It is now necessary to sign packages before you’ll be able to use them as part of NetInstall sets
  2. The InstallApplication MDM command requires that macOS installer packages be signed with an appropriate certificate

After some research and testing, I was able to incorporate installer package signing into my AutoPkg workflow and am now able to automatically sign installer package as they’re generated by my package creation workflows. For more details, see below the jump.

Read more…

%d bloggers like this: