A user came in with a disabled iPhone (too many password attempts) and couldn't factory reset it. We tried to get it into DFU mode, but we couldn't easily.
Turns out, if you just plug it into a computer that has Apple Configurator 2 installed, you can use Configurator to restore the device (without having to hold any buttons on the device—particularly helpful if some of the buttons are broken/finicky).
In macOS 10.12 (Sierra) and earlier, you could go to System Preferences > Security & Privacy > General > Require password ________ after sleep or screen saver begins, and that would populate the askForPassword and askForPasswordDelay keys in ~/Library/Preferences/com.apple.screensaver.plist for the user.
In macOS 10.13 (High Sierra), setting that preference in the GUI will not make it appear in the relevant .plist file. However, setting the preference with
defaults write com.apple.screensaver askForPassword -bool TRUE
defaults write com.apple.screensaver askForPasswordDelay -int somenumber
will make the change reflect in the GUI, and setting a .mobileconfig profile will also override what's set in the GUI.
Oddly enough, Apple's own documentation makes it sound as if those two keys exist only in 10.13 and later:
Acknowledgements: This is a slightly modified workflow based on one proposed by Taz on MacAdmins Slack. Thanks, Taz!
You can use Mosyle to install Munki.
Switch to the macOS platform (if you're not already in there).
Then, click on Management.
Scroll down to and then click on Custom Commands.
Click Add new profile.
Name it whatever you want (e.g., Install Munki), and then put in a modified version of this code:
# Go to the /tmp directory
# Download the latest Munki tools .pkg
/usr/bin/curl -L -O https://github.com/munki/munki/releases/download/v3.1.0/munkitools-18.104.22.16830.pkg
# Install the Munki tools .pkg
/usr/sbin/installer -allowUntrusted -pkg /tmp/munkitools-22.214.171.12430.pkg -target /
# This part is optional--if you're using basic authentication, you may want to add that part here
# Add in basic auth info
/usr/bin/defaults write /private/var/root/Library/Preferences/ManagedInstalls AdditionalHttpHeaders -array "Authorization: Basic BASICAUTHCODE"
Assign this profile to whatever devices or groups you want, and then click Save.
If you want to validate your FileVault recovery key from the terminal, you can do
sudo fdesetup validaterecovery
and then be prompted for the recovery key.
But what if you want to use a .plist to validate the recovery key instead of getting prompted for the key? This is where it's a bit counterintuitive, at least as far as I've tested on macOS 10.12.6 and 10.13.1.
When you enable FileVault using a command like
sudo fdesetup enable -outputplist > /PATH/TO/RECOVERYINFO.plist
it generates a .plist at RECOVERYINFO
.plist with the recovery key and some other keys (EnabledDate
, and SerialNumber
But if you try to validate the recovery using that .plist, the command will just hang.
The reason it hangs is it's looking for the Password key in the .plist instead of the RecoveryKey key (which is the one fdesetup generated!). From the the man page for fdesetup:
fdesetup validaterecovery -inputplist < /fvinput1-recoverykeyonly.plist
Gets the existing personal recovery key in the "Password" key value of the plist and returns
"true" if the recovery key appears to be valid
The Crypt project actually takes the RecoveryKey out and then temporarily creates a .plist with the Password key in order to validate.
So, yeah, if you're not using Crypt, you'd essentially have to do that—copy the RecoveryKey key to be a new Password key in order for this command to work:
sudo fdesetup validaterecovery -inputplist < /PATH/TO/RECOVERYINFO.plist
If you upgrade to macOS High Sierra, third-party kernel extensions you had previously installed will be fine.
But if you didn't already have those installed and want to install them, you'll get an error like this:
There isn't a way to script that away—the user must actually click Allow.
Probably the most practical way to deal with this for large deployments is to make sure your client machines are all enrolled in an MDM.
The MDM doesn't have to do anything to the client or push any special profiles. The clients just have to be enrolled. If they're enrolled, there won't be a prompt to allow installation of third-party kexts.
Update: Apparently, a real fix for this is on the way.
Acknowledgements: thanks to elios and bochoven on MacAdmins Slack for figuring out what was going on.
If the icons in your Munki repo looked fine on your 10.12 and 10.11 clients, and then a few of them suddenly look sort of faded (for example, Word and Excel in this screenshot) in 10.13 clients, it's apparently because of a change in the way 10.13's Safari webkit displays .png files missing the ColorSync profile in the Get Info context menu (you'll still see the ColorSync profile if you open the .png with the ColorSync Utility).
The simple fix is to do the following:
- Mount the Munki repo share using a Mac running macOS 10.13.
- Delete the offending icons from /PATH/TO/MUNKI/REPO/icons/
- Regenerate new icons with
Note: Icons generated using MunkiAdmin or sips will be fine, too, even if generated using a machine running macOS 10.12.
If LockDown Browser on your iPad opens and immediately crashes, the way to fix it is to uninstall and reinstall the app. Swiping away the app, updating the app, updating iOS, doing a home-power reset all do not fix this issue (at least not at the time of this writing).
Acknowledgements: Full credit to Tom Case on the MacAdmins Slack for this tip.
It's not immediately obvious that you can import custom .mobileconfig profiles into Mosyle MDM, but apparently you can if you go to Management > Certificates > (click on profile or add new one) > Select the file.
Those can be any .mobileconfig files—they do not have to be actual certificates.
If you use pycreateuserpkg to create a user or change its password, that will work great... except with Printopia Pro, which will prompt for a local admin username and password, and your local admin username and password will not work, and you'll get a login not accepted error message instead.
Deleting and re-adding the local admin account using the GUI (System Preferences > Users & Groups). You'll have to use the terminal to delete the user and then re-add (through the GUI is fine for this second part).
Then Printopia Pro will launch up just fine and not prompt you for a username or password.
Acknowledgements: Thanks to Roger Sprik on the PowerSchool forums for this tip.
I have a custom page that uses the last name field:
The only problem with that is if the last name has an apostrophe in it, that can lead to unexpected stuff when used in jQuery.
Apparently, you can strip out the variable to show only the letters and numbers: