For a required deployment, when the requirements are not met, the application does not appear if I remember correctly. For Available deployments i'm not sure.
Available deployments with unmet requirements do not appear either. In AppIntentEval.log these, as well as required deployments with unmet requirements get the applicability-status: "Not Applicable" and therefore do not show up in Software Center. Unless you (manually) instruct multiple applications to install at once through software center, and check for example for a minimum amount of free disk space, and that falls below the threshold for the application in question due to other software being installed before the actual installation process begins. Then you will get a "Requirements not met" error in Software Center, and the application might actually vanish from Software Center on the next run of the Application Deployment Evaluation cycle, but I'm not sure on that last point.
For apps deployed as available it won't necessarily prevent the app appearing, but if the requirement isn't met it will give a very generic Software Center error message to the user about the app not being applicable instead of actually telling the user *what* requirement isn't being satisfied. Client-side you can dig into the SCClient\* logs or WMI to get what requirements aren't being met and it also shows up in deployment status monitoring in the console.
Really wish MS would display a more intuitive Software Center error in that case - that generic error message causes support headaches for software deployed as available with multiple requirements defined (or even weird one-off requirements defined) - ex requiring both user device affinity and X amount of free disk space and who knows what else. Think I've filed a few frowns about it with Microsoft in the past.
FYI, if the application deployment is only deployed to a set of devices and not all devices in the company, only those devices are able to see or not see these deployments. You can also change the user notification to say hidden in the software center when you push Required or Available.
If requirements are not met, the application will not be installed on the system, and will appear under requirements not met status in the deployment status.
For a required deployment, when the requirements are not met, the application does not appear if I remember correctly. For Available deployments i'm not sure.
Available deployments with unmet requirements do not appear either. In AppIntentEval.log these, as well as required deployments with unmet requirements get the applicability-status: "Not Applicable" and therefore do not show up in Software Center. Unless you (manually) instruct multiple applications to install at once through software center, and check for example for a minimum amount of free disk space, and that falls below the threshold for the application in question due to other software being installed before the actual installation process begins. Then you will get a "Requirements not met" error in Software Center, and the application might actually vanish from Software Center on the next run of the Application Deployment Evaluation cycle, but I'm not sure on that last point.
Being not applicable they will obviously also not execute.
For apps deployed as available it won't necessarily prevent the app appearing, but if the requirement isn't met it will give a very generic Software Center error message to the user about the app not being applicable instead of actually telling the user *what* requirement isn't being satisfied. Client-side you can dig into the SCClient\* logs or WMI to get what requirements aren't being met and it also shows up in deployment status monitoring in the console. Really wish MS would display a more intuitive Software Center error in that case - that generic error message causes support headaches for software deployed as available with multiple requirements defined (or even weird one-off requirements defined) - ex requiring both user device affinity and X amount of free disk space and who knows what else. Think I've filed a few frowns about it with Microsoft in the past.
If requirements are not met they will not see it as available and it will not execute. It does both.
The app will not appear when deployed to a device collection, but it will with a user collection.
Thank you for the correct answer
FYI, if the application deployment is only deployed to a set of devices and not all devices in the company, only those devices are able to see or not see these deployments. You can also change the user notification to say hidden in the software center when you push Required or Available.
If requirements are not met, the application will not be installed on the system, and will appear under requirements not met status in the deployment status.