Patch My PC Ideas & Feedback
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize requests, please see:
Allow creating multiple copies of an application so that you can have different configurations of the application.
For example, if an application is licensed with a post-script, but different departments have a separate license for the app, it would be useful to be able to have two different configurations for the app that can then be deployed to different collections in SCCM.
It would also be nice to be able to set the security scopes of each configuration to potentially prevent different groups from being able to see or accidentally deploy each other's licenses.
This feature is currently available in Patch My PC Cloud.
We have a shared tenant and really need this
must have
This would be useful for us. We'd like to deploy the Nessus agent, but assign the group, based on an SCM Boundary/OU/AD Group. At the moment, we're maintaining three separate applications/deployments to work around this limitation, each with an identical MSI.
One potential use-case I'd like to use something like this for is to have a Zoom application configured to detect user-based installs, remove them, then install the machine-wide version. I already have the script to remove user-based installs I could attach as a pre-install script, but I wouldn't want to do that for the sole application configured by PMPC.
I'm able to get around this in ConfigMgr by using a task sequence that first removes the user-based install and then installs the PMPC Zoom app in the machine context. However, with Intune, it's going to be harder/impossible to use the PMPC packaged Zoom app (or update) to do this. Only recourse would be to repackage the latest version of the Zoom app myself each time a new version is released, which is antithetical to the mission of PMPC.
+3
+3 - This would be extremely useful for managing multiple slightly different deployments of TeamViewer in our org!
This would be a great feature to have in Intune for different Sonicwall NetExtender deployments.
Would be great to have some traction on this one.
+1 - it is needed for deploying multiple TeamViewer Host deployments with custom CMD line parameters for controlling which TeamViewer account and group the device will be assigned to, different install template configurations etc.
Came here looking for this feature for Zoom, which someone mentioned below. We are changing our vanity url, and during the transition need both configurations available.
I'm guessing I can just copy it and modify the params on the program, but it would be nice to have that ability in PMPC.
I would like this feature in Intune as well. Need test the updated version of Citrix and GlobalProtect before I push it to all my clients. Sometimes I want to try different configurations, like SSO or other command line switches without impacting the production package.
+3
Very much needed for deploying Citrix Workspace with various configurations. Some departments use with SSO while others do not
We have several sites where we need variation of the deployment type or application for different proxy settings for an application. Hoping that if this functionality was added it might assist with future applications like perhaps the Office Deployment Tool and having different XML configurations.
I suggest .. on the publisher.. add a "custom configurations" this would save a multiple configurations into a single package.xml file.
You would have multiple <Package> options.. the last would be the default choice..
New choices would be added at the begining of the file.. with a <required> property that looks up a Collection or Device property value to test if it will be applicable.
The publisher UI should allow these choices to be re-arranged.. but always put the default choice (no <requrement>) at the bottom of the list.
At installation.. it would check each <Package> and use the first applicable choice.
A good use case for this would be when you're deploying Zoom, you'd want to deploy the MSI version with all the flags for automatically logging in via SSO for users with licenses, but for unlicensed users who just need it for joining outside meetings you could deploy a package without all the auto-login flags.
+3 We're in a shared tenant with multiple agencies. This feature would allow us to control our own application assignments and provide us with automation. I would appreciate the option to add a Prefix in the package names to easily identify which applications belong to each group. Thanks!
Just a question would this be possible to achieve by having multiple deployment types.
+1