Hi Betty,

your best bet would be to just run a casper remote session on the effected machines, with the command

"rm -rf keynote.app".

this will remove keynote from the machine. This is ideal if you know keynote isn't in use.

You can then remotely re-install the correct version of Keynote for those machines.

It's a slight ball ache connected to each individual machine though, I was hoping to just run and uninstall policy but wasn't sure if it would work properly, then enable an install policy once all have completed, they physically can't open keynote anyway so it certainly won't be in use. Will the need to be a superuser to run the above?

Ok used casper remote added the computers in a list and used that command, they now seem to be picking up the policy to install 6.5.3, few keep failing but I will keep flushing and see how they get on, a few completed!

Wasn't too bad to be fair! Thanks!!

Removing the app bundle may be enough to allow an older version to be installed, but, JIC, I'd also run the following command to list what installers had been run on that Mac:

pkgutil --pkgs

Looks like the latest Keynote will show up as:

com.apple.pkg.Keynote6

I'd then run the following command to make the system forget that the package had ever been installed, before reinstalling the older version:

pkgutil --forget com.apple.pkg.Keynote6

You can do this as part of a policy, either as a command or a script.

--Robert

@RobertHammen provides some really good advice here. Sometimes simply deleting the app bundle isn't enough. Depending on how you pushed Keynote and what installer you used (whether its your own or the one straight from the MAS) you will most likely want to forget the package receipt.

And I could be wrong, but Apple bakes into their installers minimum OS requirements so I'm guessing you didn't push out the Apple installer in this case. In other words, if you used the installer from the MAS then there's no way Keynote 6.6.1 would have ever installed on a computer that wasn't running 10.10.4 or higher.

Yeah I just dragged my package to Composer and created a PKG from there, obviously removing the MAS stuff, then pushed out that PKG, and it just copies the .app to the Applications folder, so the original command line should actually be suitable - well it has actually worked.

Obviously the package receipts are now a different story!

Yea don't do that if you can get the packages provided from the vendor ( in this case Apple) directly. Here is a guide that explains the process: https://derflounder.wordpress.com/2013/10/19/downloading-microsofts-remote-desktop-installer-package-from-the-app-store/

@bpavlov Does that not create a MAS ticket of sorts that needs to be assign to a certain Apple ID though? Or is it good to straight push out?