Apple

0

Apple DEP/Apple Device Enrollment Debug Log

Posted on 16th June 2020

When building DEP Pre-Stage enrollments, you may wish to have eyes on some advanced logging output. We can turn on Debug mode for DEP/ADE on a per-machine basis by doing the following to that machine.

  1. Boot the machine into recovery mode after you have completed a clean install of the OS. (CMD + R at boot).
  2. Once booted, go to Utilities -> Terminal.
  3. Run the following 4 commands:
    • defaults write /Volumes/Macintosh\ HD/Library/Preferences/com.apple.apsd EnableDetailedLogging -bool TRUE
    • defaults write /Volumes/Macintosh\ HD/Library/Preferences/com.apple.MCXDebug debugOutput -2
    • defaults write /Volumes/Macintosh\ HD/Library/Preferences/com.apple.MCXDebug collateLogs 1
    • touch /Volumes/Macintosh\ HD/var/db/MDM_EnableDebug
  4. Quit Terminal and reboot the machine and begin your enrollment process. You will see a new log that will output to /Library/Logs/ManagedClient/ManagedClient.log

Once you have generated the log, you can disable the debugging mode by opening terminal while normally booted and logged into the OS.

  • sudo rm -f /var/db/MDM_EnableDebug
  • sudo rm -f /Library/Preferences/com.apple.MCXDebug.plist

Hopefully this helps you easily discover what is causing your enrollment process to fail.

2

Generating Manual Manifests for Jamf PreStage Enrollment Packages

Posted on 11th June 2020

It has been a long time coming that in Jamf and Apple land, that we can pre-install packages to the Mac during the enrollment process (DEP, now called Apple Device Enrollment). In our environment, we are switching from the old, bind to the AD domain method and allow password syncs to break even while using Nomad era, to the new (re-branded Nomad) Jamf Connect (See: https://www.jamf.com/products/jamf-connect/). Naturally, we would like to reply the Jamf Connect Login before anything else and use it’s Notify script to streamline the install progress and provide the user information as the installs complete.

The specific error that you see under the Management Commands for the specific computer you are trying to enroll is “No manifest could be created for the package.”

Jamf Pro 10.19-10.21 have an issue that seems related to PI-007954 where Jamf Admin is not automatically calculating the size of the package and creating a correct manifest for it. The manifest is required in order for macOS to install the packages defined in PreStage Enrollments. Since this does not get generated automatically correctly, we must manually build one and upload it for each package we are going to use during the PreStage Enrollment.

There was not much information about this in the community forums on Jamf Nation, nor from Jamf themselves. After talking to support, here is what you need to do:

0

iPhone 8 (Plus) and iPhone X – Opinion

I have not spent much time in the consumer end of the technology market in the last few years due to my enterprise role I currently have, but did manage to follow the developments leading to the release of Apple’s new products yesterday.

I still remember 10 years ago. I was living in New York City, and Apple had announced that they were making a smart phone. Even with the success of the classic ipod (not so classic at the time), it was hard to imagine what the new phone would look like. I remember people posting online (pre-reddit?) mockups of what it would look like. Basically, it was suppose to look like an iPod with a slightly bigger screen and all the other things needed to make it a phone. Various mockups can be found here. The mockup I remember the most, is the third one; the Blackberry look alike.

4

OSX 10.10.4 with Handoff – Insignia NS-PCY5BMA Bluetooth 4.0

Posted on 14th July 2015

Following the guide of Insignia NS-PCY5BMA Bluetooth 4.0, Macintosh Yosemite 10.10.2, and Handoff, Handoff is still working well, even on Apple’s current 10.10.4. One issue that will creep up, is that every time the system is updated, the Bluetooth kext is replaced/updated. Luckily, only 2 things need to happen to restore functionality.

28

Insignia NS-PCY5BMA Bluetooth 4.0, Macintosh Yosemite 10.10.2, and Handoff

Posted on 19th May 2015

Insignia NS-PCY5BMAWith the release of Yosemite and iOS 8.1, came a new way to connect the many Apple devices that one person can have. This method known as Continuity and Handoff allows a phone call to be answered on a Macintosh computer and transferred to an iPhone along with access to continuing to edit an email from one device to another. These are just a couple of examples of Apple’s new feature set. See Apple’s explanation here.

The feature is designed to work only with newer model Macs and can leave some of us, including Hackintoshers, out of the mix. The requirements call for Bluetooth 4.0 and certain WiFi chipsets to natively enable the feature. Some work from the community has given us the “Continuity Activation Enabler” for older Macs and can even work for some Hackintoshes that have a Bluetooth 4.0 adaptor that is natively support Out of the Box in Yosemite. A cheap Bluetooth adaptor can be found in a lot of places online, but local availability of a solution can be limited.

Best Buy sells at least one Bluetooth 4.0 dongle under their in-house brand Insignia model NS-PCY5BMA. Luckily for us, it sports the Broadcom BCM20702A0 chipset which OS X Yosemite supports, but just not in the Insignia flavor. To enable Handoff, we must get a working Bluetooth 4.0 adaptor at the start. The Insignia one can be used after it is enabled in OS X. What we will look at today is how to get OS X to recognize this adaptor, and then activate the Handoff feature. This guide should work for any adaptor that has the BCM20702A0, but is not recognized under the Bluetooth section in the System Information window.