Skip to main content

I am using the JSS ability to create configuration profiles a lot. I push them over the air and it simply works.
Now I have some machines not connected to the internet - not reachable by APN.
I tested using the "download" button from the JSS` configuration profiles GUI. The downloaded .mobileconfig I installed with "profiles -I -F /path". It looked good - the profiles show up as they should. They are also device profiles as they should, but strangely enough they do not work!
e.g. I tested a simple .plist: com.microsoft.office 14/FirstRun/SetupComplete=1



It is the same payload generated with JSS but one time OTA - one time downloaded and manual installation.
Thank you for your thoughts!

The only downside here is that if you ever pull that config profile out of the scope of client machines, the JSS will send the command to remove the profile and won't be able to. The JSS can't remove the profile unless it installed it in the first place. I think a better idea is to spin up Profile Manager and create a similar profile on there that you can deploy using /usr/bin/profiles.



Guess it all depends on your scale too. If this isn't hundreds or thousands of machines it's probably not a big deal.

...totally right! Thanx !!!



and of course as I found out with my stupid example: If you need "once" or "often" (like com.microsoft.office) then the options are also limited
https://jamfnation.jamfsoftware.com/discussion.html?id=6050

Terms & ConditionsCookie settings