Patch My PC Feature and Application Request

A community where customers and the community can provide feedback to make a better product for everyone! For more details on how we prioritize request, please see:

142 Vote

Allow multiple copies of app for different configurations

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.

  • Guest
  • Feb 20 2020
  • SUBMITTED
  • Attach files
  • Paul Carter commented
    20 Jun 03:14am

    +1

  • Guest commented
    17 Jun 09:18am

    I'm really looking forward to this. Rolling out an application, which is maintained by PMP, with different parameters would be very useful. And sometimes also for testing purposes.

  • Guest commented
    17 Jun 09:03am

    Looking forward for this one. Much needed in our company also.
    It would aleviate the ned for pre-scripts with different settings.

  • Simon Stancikas commented
    19 May 10:36am

    Looking forward to this feature as it would be beneficial to have different conflicting process settings for different deployments.

    I use PMPC to update my SCCM apps and some apps have available + required deployments. I don't want to interrupt presentations for the users having the app as required, so if Focus Assist is on, the prompt for conflicting process is suppressed. That makes things challenging for the users who have app as available. If they try to install when Focus Assist is on (Teams call, etc), installation fails due to the same Focus Assist setting.

  • Will Power commented
    16 Feb 02:44pm

    This feature would be very useful!
    We would like to be able to deploy multiple TeamViewer Host deployments with custom CMD line parameters for controlling which TeamViewer account and group the device will be assigned to.

  • Scott Erickson commented
    3 Dec, 2021 09:49pm

    This would be extremely useful for licensed applications and for apps with different configuration in general for different groups.

  • Kara Herring commented
    2 Nov, 2021 01:22pm

    It is very taxing to have to redo these configurations to allow for 'Automation' of third party patching from servers vs workstations. It's not really automation if you have to redo every setting each time.

  • Terry Stringer commented
    2 Aug, 2021 03:52pm

    Is it possible/permissible to run a second copy of the application using the same license but on a different device in the organization so that a different set of updates and schedules could be run? For example, target a more frequent update of Chrome only on the secondary instance.



  • Nic W commented
    4 May, 2021 05:35pm

    I'm out of updoots, but this would be great for exactly the reason you specified: departments have separate license keys for the same apps.

  • Guest commented
    15 Apr, 2021 07:25pm

    This is necessary for when I have multiple licenses for the same product.


  • Guest commented
    29 Mar, 2021 08:14pm

    Upvoting in March 2021 :)

  • Guest commented
    18 Aug, 2020 01:10pm

    This would be useful as sometimes we want an app to be required, but also available in case there are any issue with it installing as a required app (connectivity, Intune glitches)

  • Michael Haferkamp commented
    29 Jun, 2020 04:30pm

    This should be another Right-click option in the publisher settings..

    "duplicate" .. which then asks you to select a "scope" and/or "tag" that is added to the new object name. (verifying that it is unique)

    "scope" should also be assigned to the new object (in addition to Default scope).

    scope should also be used to restrict/allow an admin from editing the properties of these application installs. (from the publisher tool)... or move these option directly into the sccm interface with a custom UI integration.

  • Claudio Mendes commented
    20 May, 2020 09:42pm

    +1

  • +77