Posted on 09-13-2016 07:40 AM
So this seems to be a computer specific issue, some laptops can install the DMG's and some cant. Removing the MDM and re-enrolling corrects the issue. Was wondering if anybody could possibly shed some light on this issue?
Posted on 09-13-2016 07:56 AM
maybe that's what 9.97 or 9.998 or 9.99 are for ;)
Posted on 09-13-2016 11:12 AM
@feszg Since removing MDM is part of the fix....any chance there is a config profile restricting access to Disk Images (Restrictions payload)? Maybe there is a profile that was applied to the machine but isn't when you re-enroll....just a thought.
Posted on 09-14-2016 04:20 AM
Hi!
Seriously appreciate the response. I have excluded the computer from all off the configuration profiles other than the base MDM.
Posted on 09-14-2016 05:49 PM
@feszg Have you tried running the policy from the command line and perhaps running it in verbose mode to watch what is happening? You may be able to gather a bit more information to help you narrow down the cause.
jamf policy -id <id#> -verbose
What does the policy log say when it fails like this? What else does the policy do besides install the DMG? I have seen policies report failure from Self Service because a script failed. The software was installed, but something a script did was not completed.
Posted on 09-17-2016 12:37 PM
Looks like a 2 year old configuration profile was the issue. Under restrictions read only was checked for disk images.