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:
Add the ability based on device type (laptop, desktop, etc.) to set the refresh cycle using the warranty information. Example: Ship date of a desktop was 1/1/2020 and we have our desktop refresh cycle of 5 years, so the refresh date would show as ...
Could AI add visibility into the Windows activation status of all managed devices. This would help ensure compliance with Microsoft licensing, reduce manual checks, and support proactive remediation. Key data points could include activation status...
It would be useful to see information for the TPM module installed on the device view page: such as: Manufacturer
Manufacturer Version
Interface Version
TCG Specification
Activated
Enabled
Owned
Would it be possible to add another column in the Administration - Users screen to show when a user last accessed the console. This would ensure we can see who is actively using the console and also remove any accounts that haven't accessed for a ...
Kindly add the ability to add multiple pre or post install/uninstall scripts and the ability to manage their execution priority. This would simplify the onboarding for new customers when trying to migrate their existing packages to PMPC; it would ...
Add ability to replace user context installs with system context installs
Similar to this request: Replace EXE installation by MSI https://ideas.patchmypc.com/ideas/PATCHMYPC-I-3771 There is a need to be able to replace a user-context installation with a system-context installation. For example, detecting user-context i...
Update the manage conflicting process dialog using PSADT
The current manage conflicting process toast that the end users see is, well, not as good looking as it could be, especially compared to the dialog boxes that PSADT 4.1 presents. Consider moving to using PSADT or at least a more modern looking int...
Skip installation X times when conflicting process are running and then start to notify the user to close the application
We don’t want our users to spam them with too many toasts/notifications when we want to patch and the application is in use. Could this idea be implemented? If the upgrade process begins and encounters a conflicting process, it will automatically ...