I've found that a restart is usually needed before the dummy receipt takes affect.

@cbrewer sorry to bring this back up. But can you just delete the receipt? or do you need the dummy receipt?

IIRC - The dummy receipt keeps users from being prompted by the App Store to reinstall the applications. Depending on your environment, you might be okay without it.

I've seen a couple instances lately where the package with dummy receipt is still showing an update in MAS. I could not replicate 100% either way. But it seems most of the time it works as far as installing and being usable. Only one I've not been able to build yet that works right is GarageBand due to the extra content. But there is another thread where someone has a process I've not yet tested. https://jamfnation.jamfsoftware.com/discussion.html?id=10327

Post by @pbenham has the process.

Hey guys,
For iLife and iWork apps - dragging the .App into Composer seems to work well for most apps except Garageband.
We usually delete [_MASReceipts]. This works fine for most AppStore apps. However Garageband v.10.0.2 doesn't like it. Error: "damaged and can't be opened".

If I keep [_MASReceipts] in the app bundle, it works fine.

I have deleted the _MasReceipts from all apps. But the App is still tied to a apple ID. Is there a way that you can untie a App from a Apple ID?

Hello,

I created the pkg via Packages using a never booted machine apps.

Best regards

Kostas

You can try this script. It'll perform the painful process described in other posts and should yield you a clean PKG.

https://jamfnation.jamfsoftware.com/viewProductFile.html?fid=690

@cdenoia if you deploy the dummy receipt from @cbrewer right after iLife is installed, garageband will open and not be tied to a apple id account

@cbrewer do you have that dummy receipt in a smart group?

I am a bit confused by this process and not sure if it works any more.
It seems this process just ignores the receipts and doesn't work correctly with garage band and additional instruments. Is that correct?

Honestly, you should probably talk to your Apple Rep regarding transferring your existing iLife/iWork licenses to VPP codes that you can assign to users via their Apple ID and revoke when you need them back. That's how we're doing it with our machines and we have yet to have any issues. All apps are pushing out to users App Store accounts and are updating the version that was included on their MBA to the latest from Apple.

Joseph,
What process are you using to get the VPP codes? Our rep suggested the same thing, told us to fill out the a VPP support form and select "iOS fullfillment" even though we are using MB Airs as well. VPP support then told us to use the Up-to-Date program. We filled that out, and we have yet to get a response. Plus, it seems to only cover Keynote, Pages, and Numbers. We seem to just be getting a little bit of the run around.

Is anyone packaging up the instruments in Garageband 10 for classroom/lab use where the App store is unavailable to students? I know I tried this back in May and was unsuccessful, not sure if I was missing something or what. Thanks!

Hi Everyone,

I've been using this method for a long time and haven't had any issues. I've been able to keep updates from showing in the AppStore by using the dummy receipt method. Today, though, after upgrading a couple machines to 10.11.5, it appears that the dummy receipts are no longer been honored by the AppStore and I'm getting iLife and iWork updates showing even though I'm up to date on all those apps. Just wanted to see if anyone else is noticing this behavior, and if you have a work around?

Thanks,
Andy

No answer as of yet but I am worried that Apple may have implemented receipt checking on their apps...can you verify if the launch after 10.11.5?

@blackholemac Yep, they seem to stick around even after launch. I'm worried that they may have changed it as well.

We've seen this for a while now, and I tend to prefer this behavior. The reason why we use the 'Dummy Receipt' method is so that we can quickly re-distribute these applications to imaged BYOD computers, without converting the users own apps to OUR VPP account. Instead, we make all iLife/iWork updates available via Self-Service, yet encourage users to re-associate their Apps with their own AppleIDs by updating via the MAS.

I captured the installers from the app store then I turned off the Updates in the app store.
My users get all bent out of shape and start calling Service Desk to "to do the updates" when they see updates are available.

I'm also seeing this change with 10.11.5. It's probably time to get managed VPP licenses for these apps and start using device based assignments.

For those that don't know, device based licensing didn't exist until OS X El Capitan.

@blackholemac I had a 10.11.3 machine with dummy receipts for iLife and iWork, confirmed they dont show in the App Store Updates tab, then I updated that machine to 10.11.5 and the apps have re-appeared in the Updates tab. Re-ran the script to put in the dummy receipts, but the iLife and iWork apps are still visible in the Updates tab.

Definitely looks like something has changed in 10.11.5