![]() IF the machine is in DEP (only about 1/5th of our machines are) then Wipe and reimage from Recovery, have the PreStage Enrollment add our local support account, use Enrollment Complete to install our default user account, Pulse Secure and profiles, Bomgar, and run a couple of scripts (rename machine with serial number, etc). The workflow I'm testing now, which falls into the 'duh, why didn't I think of this sooner' category. I just pretend it's not there at this point. I'm lucky if it works one time out of ten. They should either get their ducks in a row for deployments or just flat-out tell us to look elsewhere.Īnd +1 on the enrollment complete trigger. And I'm supposed to rely on this thing to get computers enrolled? Pfft.Ĭall me crazy, but I like setting up a couple of near-complete images and laying them down on a machine rather than relying on config profiles for the seemingly few things it's good for, rather than relying on third party best-guess softwares and dirty terminal hacks that Apple will eventually, but definitely break for the rest. I get "stopped responding" errors more often than not and we can't even get a managed Apple ID to show our iOS apps in Apple's Configurator. ![]() I've been trying to set up Apple School Manager and so far I think it's a joke. Deploying software after the fact takes up even more time, especially if you have to run policies over and over because of laptop lid shuts, bad connections etc. ![]() Jamf brought up modular imaging which takes up more time and from what I've read isn't even officially supported. There are other ways to do what we're doing but they're all SO. Glad I'm not the only person reading about High Sierra, the new do's and don'ts and thinking "You want us to do what?!" I'm trying to figure out how we're going to proceed with this and I've been browsing around Jamf Nation and even asking Jamf support some things, and honestly I'm really, really nervous of the ability to just lay an image down on a machine and be done with it taken away from us. It's so bright I'm obviously missing the advantages as an administator. Then on reboot, DEP installs your management software, and then applications and settings are installed through an enrollment complete trigger (and hope that works, it doesn't reliably) or the user installs software from Self Service either as individual policies (hopefully in the correct order) or a train of policies that trigger the next policy in order to install your 30+ GB of required applications and settings, many of which have to be installed in a specific order. With Apple forcing everyone into their idea of the future, where everyone has Cupertino-style high speed internet, the user just simply (unlikely) boots to the Recovery partition (has to be done locally, no method to it remotely), wipes the primary partition (try explaining the difference between device and volume to someone who doesn't even know how to get to the Applications menu), reinstalls the latest OS (several hours in some cases for our users). We can then remote in, boot to a support partition on the machine, and reimage the primary partition from the repository stored on the local external drive. ![]() All they need is a usable internet connection so that we can remote to their machine and Casper Imaging can read the configuration. In our case we usually send out a drive containing a copy of the repository to our more remote users (Lagos, Nigeria, Beirut, Lebanon, Cairo, Egypt). Update: The backgrounditems.btm file is still the target file since macOS 10.13.1 and later.It works great as long as your client machines have easy access to your distribution server, and you don't have a lot of packages to install. Where "name" in the command is as show in the output of the following command: osascript -e 'tell application "System Events" to get the name of every login item' ![]() You can also delete a Login Item from Terminal using the following syntax: osascript -e 'tell application "System Events" to delete login item "name"' Which, by the way, is also a plist file, but with a btm extension. In macOS 10.13.1 it updated the following file: ~/Library/Application Support//backgrounditems.btm In OS X 10.8.6 it updated the following file: ~/Library/Preferences/ Then looking in System Preferences > Users & Groups > $USER > Login Items, EventScripts was added. Which is apparently the normal output with this command and was verified by preforming the same action in Script Editor. In Terminal, using the following syntax: osascript -e 'tell application "System Events" to make login item at end with properties ' I tested the following under macOS 10.14.6, macOS 10.13.1 and OS X 10.8.6. MacOS Catalina Update: While the information in this answer holds true as stated and tested in the versions of OS X/ macOS listed below, it does not work in macOS Catalina 10.15. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |