Add or Retain Requirements to Application When Published
It would be great if when an app is created (for app deployment, not updates) by the publishing service, it could add requirements to the app. In our case, User > Primary Device = True as a requirement for some of the applications published by the service
Sorry for the confusion, I know this thread was aimed at persistence of requirements,
I was just expanding on the functionality you have provided to more of the options available within ConfigMgr.
The option to run as 32-bit is not part of Requirements on the deployment type that's part of the deployment type's Program. Can you please explain the scenario? We test the applications against running as a x64 process on x64 machine?
I can confirm that the setting I outlined does not carry forward after an application is updated. The scenario I was thinking of was when you need a 32-bit installer to run as a 32-bit process on a 64-bit machine. This blog article explains it much better than I ever could:
Not sure, what is the scenario? We usually populate the uninstall.
One question... will the application retain any other settings?
Run the installation and uninstall program as a 32-bit process on 64-bit clients
Awesome! Thank you...
If you add any custom requirements, that should be retained when the app is updated in place when running build 1.6.4 or newer. Thanks for the feedback!
This update will address the retaining of requirements. If you are interested in the ability to create requirements within our tool, please submit a new idea for the option of adding requirements.
Good news, the next preview update should be able to retain requirements added to the deployment type in the console. I don't know if we will add a UI to add requirements in our tool (Probably not) directly. I think just setting it once in the console should suffice if we retain any custom requirements for future in-place app updates.
Thanks for the update, Justin! Even if we can't set the requirements in the PMPC app itself, being able to specify an option to carry any requirements set on an app from version to version would probably be sufficient.
Thanks for the info. We will see what we can do around this feature. We probably wouldn't be able to look more into this until late Q1 / Q2 based on current workload.
We use custom conditions on all our applications, would like to see this feature added.
No, we need to be able to set OU and OS requirements on applications to prevent them from installing on Servers and on some of our VDI machines.
@David, is primary user your main requirement rule you need?
This is a must have in our environment to continue using Patch My PC to create applications. Are there any updates on this?
This would be really useful for user-based deployments, I'd love an update on it
I'm also interested by this feature