![]() ![]() ![]() The PKG installers that you grab using this method do not have any MAS receipts to worry about deleting. You can actually use instructions created by for grabbing the PKG installers for these apps before they actually get installed by the App Store. Just an FYI for You don't need to repackage. The MAS 9.5.1 update for iPhoto is still there after a restart as well.Īt this point I'd like to turn this question out to you all to see what are some best practices and the most reliable way to package, update, and distribute MAS apps. It opens fine, runs great, but MAS on the client still shows that the 9.5.1 update is available. I used Casper Remote to install the latest version and opened it on the client to ensure that it is in fact reporting 9.5.1. So after a successful updated rebuild of the iPhoto package (9.5.1) I sent it over to the client that originally received the 9.5 install. I've read multiple suggestions that I should not simply update the app and re-package. ![]() On the original machine that packaged iPhoto, I deleted iPhoto and re-downloaded it to obtain the newest build. In testing I've found that to not be true and now my client is stuck with an iPhoto update that it cannot run for obvious reasons. I've read that doing so would prevent MAS on the client end from picking up updates. I've been testing deployment of iPhoto 9.5 and packaged it up without the _MASReceipt folder. We haven't yet signed up for the new VPP and we currently don't have MAS apps available for deployment. In searching JAMF Nation I've found bits and pieces to the answer to my question, but I'd like to put the question out there to see how you're handling this. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |