From: Troy V. B. <tba...@ca...> - 2022-02-09 17:36:16
|
> > Quick questions for Troy Barkmeier (or anyone that wants to chime in): > - Did settling the relative path to /System/Volumes/Data help simplify > your negative.T at all? > - Are you using any kind of MDM with this (e.g. to deploy a Privacy > Preferences Policy Control profile)? If so, what solution did you pick? Not only did setting the relative path to /System/Volumes/Data *radically* simplify my negative.T, it reduced the line count of my base macOS transcript from ~473,000 lines (10.14.x) to just over 15,000 lines (10.15.x)! This was huge for us, because we run radmind at every logout in the public lab spaces. Knocked at least 60 seconds or more off the run time. As for MDM, we're still cheating on that at the moment because, in the radmind labs, although users log in using their AD/LDAP credentials, once they successfully authenticate they are all passed in to the same local user account. Because everything at the OS level including the user account is 100% identical for every computer, I can still get away with distributing things like the tcc.db and even the contents of ./private/var/db/ConfigurationProfiles with radmind, and it still just works, up through 11.6.1 so far. Because of the radically different imaging procedures for Apple Silicon, however, I am looking into having our Jamf instance do the initial setup of our radmind machines starting next year using DEP like we do for faculty/staff Macs, and then just negging the tcc.db and profiles stuff and letting Jamf handle that part since it'll be there anyway. So nice to talk with other radmind users again. :) Best, TVB |