Munki is a very robust software management tool, period. Casper is that (with pain points), plus many other very nice things.

You cannot compare them equally like that and use one or the other exclusively.

This will help handle your DMG issue. Works fine.

https://www.jamf.com/jamf-nation/third-party-products/files/547/installpkgfromdmg-sh-install-a-pkg-wrapped-inside-a-dmg

Why not use both? You can add an extension attribute in your JSS for your Munki Client Identifier and build off your existing munki infrastructure.

It would be nice to see Jamf Pro 10 offer this functionality as an option at upload.

On upload of a DMG, get prompt to choose between a Composer and Drag install.

Select the later, and any *.app at the top level of the mounted DMG gets put into /Applications.

We use both - Jamf handles the configuration of clients and users. Munki hands Patch management and Software deployments.
Works really well - get the best of both systems ;)

Having used both, the one thing JAMF has to offer is which Munki does not is readily available customer support. I found myself in a pre-configured Munki environment where I had to learn on the fly and while there are many blogs available, the lack of availability of a human being to speak to for technical support made my task more challenging.
Policy Dependencies would be an excellent feature for Casper. Having also worked with Altiris, creating chains of linked dependencies was very useful in that we could be certain that applications and plug-ins were applied in a structured sequence.
I still give a strong nod to JAMF. Excellent customer support and very reliable product.

@donmontalvo I don't think they are actually going to have a choice on this one, 10.12 allows developers to force checking of the DMG when copying into /Applications this means copying in from anything other than the vendor provided DMG causes problems later down the line, so far only a couple of developers seem to be using this but Google Chrome for example does and it causes dock issues etc... if you use a Composer captured install.

@Look Thanks, interesting, wasn't aware of that. I'd suppose both Munki and Jamf would have to circumvent that function if it'll be possible, else accommodate it some other way.

For example, Jamf can bypass Gatekeeper on unsigned packages. Or maybe allow upload of the DMG and offer the option for Jamf to deploy the DMG, mounts it, and cp/ditto the app to /Applications.

@donmontalvo Thats pretty much how I dealt with it, wrapped the DMG in a PKG that had a script to mount and copy from the DMG.

We moved to Casper Suite 18 months ago, and I initially stopped using Munki to try and keep everything in one place (JSS). However, I immediately went back to using Munki to run Apple software updates because it 'just works' - installs updates at the log in screen. Patching software was also a pain, so I've ended up setting up Munki again and using it with AutoPKGR to update apps etc. So yes, using both does work fine!

We use JAMF Pro with our iPad too, so it's really nice to manage everything in one place. JAMF Pro also offers lots of thing that Munki doesn't, such as building and pushing out configuration profiles, as well as policies for managing printers and all sorts. Integration with Device Enrollment is also brilliant, and completely cuts out the need for imaging new machines. I've only used it one new machine, but it's worked great so far.