It's been a while, but how I did our Wacom deployment was:
1. Create Wacom Push + Self Service policy that includes a jamf recon command at the end
2. Create Wacom PPPC config profile that gives Accessibility / ListenEvent / SystemPolicyAllFiles / etc permissions for com.wacom.TabletDriver, com.wacom.FirmwareUpdater, etc.
3. Create Smart Group 'Has Wacom Driver Installed'
4. Scope PPPC config profile to the above smart group.
So in practice, you push the driver .pkg to a lab (or an individual installs it from self service) - it does a recon after installing which pops the computer into the smart group. Their computer being moved into that smart group kicks off the config profile getting installed to them. So ultimately, they never even get a 'Wacom needs you to allow access to...' pop-up.
Thanks for this will give it to the systems and report back.
Sorry for asking such a question. I`m quite new to the scene. I couldn`t find where the jamf recon command goes to. Actually I`ll need help for the second step too. Thank you
Sorry for asking such a question. I`m quite new to the scene. I couldn`t find where the jamf recon command goes to. Actually I`ll need help for the second step too. Thank you
Jamf recon is in a Policy, scroll down to Maintenance and add it. The "Update Inventory" will be ticked by default.
The second step talks about a Config Profile with the PPPC payload.