There is not a way to force the apps to update, the delay is normal.
I would suggest not using the Jamf App Catalog for "provisioning" a new system, and instead use it only to keep existing apps up to date. Instead, for setting up a new machine, stick to regular policies or other more immediate methods, like scripts if you're comfortable with those, to get those applications installed. As you found out here, installing apps over the MDM method is not fast.
No-one would complain much if an update to an already installed app took 2-3 days to arrive, but few are going to be ok with waiting 2-3 days (or even 1 day) for their Mac to get set up so they can start using it. That's just unreasonable.
I would suggest not using the Jamf App Catalog for "provisioning" a new system, and instead use it only to keep existing apps up to date. Instead, for setting up a new machine, stick to regular policies or other more immediate methods, like scripts if you're comfortable with those, to get those applications installed. As you found out here, installing apps over the MDM method is not fast.
No-one would complain much if an update to an already installed app took 2-3 days to arrive, but few are going to be ok with waiting 2-3 days (or even 1 day) for their Mac to get set up so they can start using it. That's just unreasonable.
How can I get this?
If I use installomator for policies and keep "deploy" active on app installers, I will have two identical installations available on self service... what am I missing?
How can I get this?
If I use installomator for policies and keep "deploy" active on app installers, I will have two identical installations available on self service... what am I missing?
Oh, Just avoid selecting where to show in self service. Dumb question :D
Sorry!