You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the advantages of using Custom Schema's for Config. Profiles, is it makes the plist much more readible, so when I transfer a Config. Profile, it would be nice to have the matching Application & Custom Settings settings included, such as an External Applications Custom Schema.
The text was updated successfully, but these errors were encountered:
I do suspect this may require something for the Jamf API that may not currently be there. I'll happily supprt a request for them to add it, or create one if preferred.
Nice catch. Looks like there is nothing in the xml export that differentiates what's configured in 'External Applications' from 'Upload' within the Applications & Custom Settings payload for Configuration Profiles. As a result, from what I see, External Applications (current) settings get dumpted into the Upload section when the Config. Profile is migrated.
Unless I'm missing something I believe you're right in that some work needs to be done on the API.
Updated Limitations in the readme to call out the issue.
One of the advantages of using Custom Schema's for Config. Profiles, is it makes the plist much more readible, so when I transfer a Config. Profile, it would be nice to have the matching Application & Custom Settings settings included, such as an External Applications Custom Schema.
The text was updated successfully, but these errors were encountered: