![]() A copy of the iLok License Manager installer package (“License Support.pkg”), grabbed from here (yes it’s in a DMG, in a ZIP file).Found in the “Driver Installers” directory. The “Install Avid HD Driver.pkg” installer package.Found in the “Codec Installers” directory. The “Install Avid Codecs LE.pkg” installer package.The “Install Pro Tools 12.x.x.pkg” installer package.So, you’ve downloaded your Pro Tools 12 package from Avid and it looks little like this: Neil Martin of UEL on Mac Admins Slack), who pointed me to the right areas to dig into.Please Note: These notes have been written on the assumption of using an iLok licensing management solution and so doesn’t deal with any licensing models outside of this.Ĭredit where credit is due (aka standing on the shoulders of giants)īefore I start, I have to confess I have pulled most of what I needed from work others have done for Pro Tools 11. This one revolves around turning the Pro Tools 12 installation into something that can be deployed by your Mac deployment / patching solution of choice. Maybe I should start a new series on these □ Again, this is gonna be another one of those “I had to do something for a client and so I thought I’d share” blogs. I will not suggest a product that causes me more work and headaches than is necessary.Hi All. All going well, I have no intention of renewing our service. I have had serious talks with both Mosyle and Kandji to move our fleet in the next 12 months. ![]() This is such a shame because the engineers at Jamf are so beyond incredibly talented. Continuing down this path will not end well. You are making terrible decisions which are causing serious detrimental regressions in management services. Your consistent path of destroying useful features and buying out other companies to smash in to your own isn’t what made you good. To prove it’s not only me on one of my usual rants: If you’re one of those people, head over and give Jamf the feedback: Perhaps it’s a sector/environmental thing. ![]() Others, like me, found the tool incredibly useful. There are ways you could have solved that particular problem, but let’s not get into that. Some found Jamf Remote completely useless and were never able to connect to their users devices as they were all over the place, and not necessarily on a wired connection. Or, I could rely on Jamf Remote to do exactly what I asked it to do at 3:33am on the dot.Ĭan TeamViewer do that, Jamf? No, no, it bloody can’t. Sure, I could have made a policy, set some specific client run restrictions and hoped the devices checked in, the binary hadn’t crapped its pants, and it ran. I would leave a Remote window open on the Mac Mini and have it do various things at obscene hours in the morning. Something else I often used it for was scheduled functions at a specific time. It gave our Windows using techs a level of support parity. If I wasn’t available to push a package, or restart a machine, another tech could do it, regardless of the physical location. Jamf Remote was available on a Mac Mini that they could remote in to and sign in to Jamf Remote with their credentials. One of those was for other technicians who didn’t use macOS devices. I could use it on short notice to produce fast results, but it also has other use cases.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |