Allow non-admin to install app from Self-Service

If you're using standard VPP managed distribution it will want to associate the app to an Apple ID when it deploys via Self Service (or automatically).

The newest version allows you to deploy to devices rather than Apple IDs, although (and I could well be wrong here), I was under the impression this is only available through Casper for iOS devices at the moment.

Not sure if 9.81 has added the capability for El Capitan as well.

The traditional (alternative) route has been to use this method to create the installer package: https://derflounder.wordpress.com/2013/08/22/downloading-apples-server-app-installer-package/

Although that would tie it to a single Apple iD.

Hi @esheldon76 ,

From what I have seen and done you won't be able to use the AppleID that you have associated with VPP. You will need to invite users to your VPP, which will associate their AppleID with the one that you are using to purchase apps. They can setup a new account to associate their work email or have them use their personal AppleID. If they setup an ID with their work account you can recover the account after they leave by resetting the password.

As long as you use the managed distribution and have the policies in the JSS setup correctly, they won't need admin rights. If they are logged into the App Store with their AppleID they won't be asked for their password.

With the managed distribution, you can assign the apps to your users and retrieve the licenses when they leave or no longer need it. This way the licenses are assigned under your company and aren't under their AppleID.

Let me know if this helps or if you have any other questions.

A method that we've used is to install the software while using Composer and create a package to deploy via self service. We do this with many app store apps, we just make sure to maintain all of the updates and ensure that we have purchased enough licensing for any paid apps.

@esheldon76 - The easiest way I've found to do this is to use Apple Package Maker. The process is like this:

1. Download the Application you want on whatever AppleID using the App Store.
2. Package it up using Package Maker.
3. Upload that pkg file to your distribution point
4. Create a Self-Service policy

Then, you don't need to bother with VPP at all, they just download a standard app package via Self Service. This works perfectly for any free apps from the Apple App Store.

You can download Package Maker here using whatever free Apple Developer ID you have:

Package Maker Download

For simple things like Microsoft Remote Desktop, Package Maker is really straightforward - just drag the application into the left sidebar, pick a destination, then build the package. It'll look like this:

Hope that helps, let me know if you have any questions!

Thanks,
Jason

@jkuo Pretty sure PackageMaker has been deprecated for quite sometime now and Apple recommends pkgbuild, productbuild, and pkgutil accordingly to do their packaging. Other apps that are more updated and similar to PackageMaker would be Composer and Packages: http://s.sudre.free.fr/Software/Packages/about.html

Also, your method would leave the _MASReceipt inside the app bundle which means that during updates it will prompt the user for the password for the Apple ID that downloaded the apps. That's no good and should be avoided.

Follow the post by @davidacland. Although he says that it ties the app to one Apple ID, the MAS installer does not contain the _MASReceipt which is what ties it to an Apple ID on the computer. This way the app isn't picked up by the Mac App Store as an app needing updates from another Apple ID account.

@bpavlov - yep, it hasn't been updated in a long time, but for simple deployments like this one it'll work, especially if you manage the whole software process using Self Service. All updates would happen directly with Self Service, which would avoid the App Store altogether.

Thanks for the tips though regarding the _MASReceipt, I'll have to revisit my process!