![]() For more information, see below the jump.Īs part of working on a project recently, I ran into an unexpected problem with ESXi-hosted Mac VMs. It’s also possible to leverage this technique to update the User and Location section of a particular computer managed by a Jamf Pro server. usr/bin/security find-generic-password -l "Enterprise Connect" $HOME/Library/Keychains/login.keychain | awk -F "=" '/acct/ ' | tr -d "\"" This can be accomplished by running the following command as the logged-in user: While mobile Active Directory accounts will use the username and password of the person’s AD account, there is no such certainty with local user accounts.įortunately, my colleague Joe Chilcote recently let me know that it’s possible to query the logged-in user’s login keychain and get the username of the Active Directory account which is logged into Enterprise Connect. ![]() The AutoPkg recipes are available via the links below:Īs more Mac environments move away from binding Macs to Active Directory and using AD mobile accounts, and towards using local accounts in combination of tools like NoMAD and Apple’s Enterprise Connect, it’s become more challenging to identify which people are logged into which computers. If you do need to use these installers, setting the system clock on your Mac to a date and time before the October 24th 2019 expiration date will allow these certificates to appear as valid again and any expiration-related issues should go away. If Apple does choose to re-sign these certificate with valid non-expired signing certificates, I’ll add code signature verification to the recipes. One of the consequences of this is that I cannot use AutoPkg’s code signature verification as part of the AutoPkg recipes, since AutoPkg’s current code signature verification will error when it hit the expired certificates. As of June 30th, 2021, I do not know if Apple is planning to re-sign the installers with the current Software Update signing certificate. Instead, they install the Install.app for that version of OS X into the /Applications directory.Īnother thing to know is that the downloaded installers are signed using Software Update signing certificates which expired in 2019. One thing to be aware of is that the downloaded installers do not themselves install the relevant version of OS X. These recipes will download the disk images linked to the relevant KBase articles, extract the installer packages stored inside the disk images and rename the disk images and installer packages with the OS name and version number. pkg recipes for the following OS X installers: Now that Apple has made direct download links available for Lion and Mountain Lion, I’ve written AutoPkg.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |