iOS - Pending - Application is not available to install

@St0rMl0rD I would encourage you to contact support for assistance if you are experiencing this issue. We can investigate what is causing this issue in your environment and help you work through it.

Two years and this issue has never been fixed through many updates and major version releases?? JAMF is not functional software, at all. Why has anyone bought this, and why has the company not been sued into the ground for have a product that doesn't work? Name handling is non existent so you can't manage systems because they're seen with the wrong names all the time, AD binding no longer works in v10, VPP doesn't work at all at user or device level, it's a non-product! Our institution set this up centrally because it was supposed to be this great thing. Apparently it's all marketing and doesn't work. We're going back to Profile Manager I guess, tons of fluff features are useless when base functions are entirely missing making management impossible.

@ebonweaver Did you ask for help for any of these problems? Jamf provides the best support out of all of the tech vendors that we work with. They're awesome. I have had none of these problems that you described.

I have no issues at all either.

Apparently you aren't using the functions involved, because they are issues and limitations of the product. These have been discussed with support, and there is no solution or explanation in most cases. Glad you're not having problems, but unfortunately these issues are real.

1. There is no pre-stage management of any kind, that's a fact. This causes a lot of limitation down the line where device name is concerned, and any management based on name. This is a fact. Their own settings step on themselves and prevent managing names from the console when you don't allow users to modify name. AD binding and smart groups are not reliable when a system can have the wrong or out of sync name for 20 minutes. If they had pre-stage management like Profile Manager many of these problems and limitations would not exist. Stepping on themselves is a design fault.

2. AD binding was broken in v10, it worked in v9. As of v10 JAMF is deleting the computer record and remaking it before binding. This is not an option, and it's not functional in a domain that has tight delegations that limits creation. We have worked around this by making even tighter delegations that do not allow the delete command to work, which by sheer luck does not fail out the entire bind action. Support was unaware this change had been made, it took us a week to nail down the issue, and another few days to come up with a solution when they couldn't help. A change of this nature with no notice or option was not a good choice.

3. VPP is overly complicated and has no reporting of configuration inconsistencies. Once it was figured out, and we got past issues in their invitation process (bugs have been reported), we at least have user and iOS VPP working (except it has a failure rate and never failed with Profile Manager, reasons still unknown). Mac OS deployment is not possible in educational multiuser type settings, because they don't do device based VPP, and the user based VPP at the Computer level is not very functional.

A list of about 4 dozen other bugs, deficiencies, and issues has been submitted, but these were the biggest walls we hit. It's just very disappointing for a product of this size and age. We had expected a quick easy transition with lots of new features and enterprise robustness. Instead the transition has taken countless hours over 2 months and we are unable to have fully automated deployments and are still working around other problems. It has been anything but smooth and time saving.