Hi, I built and tested a script that takes the labour out of signing
PKGs (required for things like auto-mounting network shares via a script
and partner LaunchAgent, amongst other things). I call it 'ASP'
(Auto-Sign Packages). The dream is to get a ...
Good news! Is anyone aware if this is wholly compatible with all
licensing types (as an example, Office on the MAS isn't compatible with
the Office volume licence tool)? Could really simplify deployment,
hopefully the other CC apps follow suit.
Hi, I'm wanting to really take advantage of what the API offers (as an
example, adding one smart group of Shared iPads to all classes in the
JSS in one go) and am wondering how I can use Postman to help with this?
Is anyone using Postman with the cur...
Hi, I've built a configuration profile with the above preference set on
one of our Macs, then uploaded the launcservices plist from it into the
profile payload (omitting anything unrelated to Adobe) and deployed that
to another test Mac to confirm it...
Hi @j_allenbrand1, only just clocked that your reply was addressed to me
so I apologise for the delayed response.We aren't deploying Connect via
a PreStage PKG; I just deployed the Connect PKG as I would for any other
app install policy and it worked...
Just FYI, we resolved this by ultimately just pushing out PLISTs
generated from the JCCU app and adding them into a 'Custom Settings'
profile payload. I actually prefer the app to the UI in Jamf Pro for
configuring Connect, and think UI improvements ...
We have this exact issue as well. My understanding was that
configuration profiles would be auto-signed by the JSS. I have a case
with a senior Jamf engineer open and will update this with their
response. In the meantime, I've expoted the plists from...