![]() Seems like a good suggestion, I just wanted to hear more before I actually try it. I might be overthinking this, but I was just worried about things colliding somehow. Even if you are not a Mac user, you have likely heard Apple is switching from Intel CPUs to their own custom CPUs, which they refer to collectively as 'Apple Silicon.' The last time Apple changed its computer architecture this dramatically was 15 years ago when they switched. How will patch management know to install the silicone version on ARM computers and the intel version only on intel? Or will both run on all machines and the version is isn't compatible will just fail. A Python Data Scientist’s Guide to the Apple Silicon Transition. I guess I'm just worried about things colliding? Our Creative Cloud desktop app policies are setup with smart group targets/exclusions so that intel will only show up if you have intel, apple silicone will only show up if you have apple silicone. So now I would attach the Intel package to one, and the Apple Silicone package to the other. It has ingested data from our fleet from both, looks identical as it should. I've setup the secondary patch source for Apple Silicon software. Probably need to drop the from the url, see below he responded to someone with that suggestion and a I would like to give this a try. VideoProc Vlogger, a new leader in free video editor software, helps you create cinematic videos and vlogs on Windows and Mac. usr/sbin/installer -pkg $dirintel/Cisco_Webex_Meetings.pkg -target /Įcho "Architecture did not match arm64 or x86_64, aborting install." ![]() usr/sbin/installer -pkg $dirarm64/Cisco_Webex_Meetings.pkg -target /Įcho "Intel Mac detected, installing x86_64 Webex package." If anyone needs help borrowing this method let me know.Įcho "ARM Mac detected, installing arm64 Webex package." Here's what my postinstall script looks like and the referenced payload structure. Using this method for Webex Teams & Meetings until they come up with a universal package.
0 Comments
Leave a Reply. |