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:
Sometimes different applications can share the same executable name. PMPC doesn't care where the process originates from when "name.exe" is specified in "Manage conflicting processes", it just wants to shutdown whatever application is running that process. This can cause problems, for example:
Node.js executable is called node.exe. I deployed it via PMPC yesterday to 400 computer lab clients. In our computer labs Adobe Creative Cloud is also installed and has a library that runs a different node.exe for all users immediately when they log in. This means Adobes node.exe is a conflicting process when Node.js tries to install. This causes the installation to always show a shutdown/defer notification for 15 minutes if someone is logged in, and if no one interacts it it automatically defers with error 0x642(1602) User cancelled installation. This causes delay of the Node.js application.
If running in a RDS/Terminal Server multisession environment there could be two users running different applications with the same executable name. If one of them chooses to shut down the application via the PMPC notification window it will shut down both applications for both users, which could result in unsaved work being lost.
Today we solve this with a PowerShell pre-script checking if the specific node.exe from the "incorrect" Adobe path is running and then kill it.
It would be great if you could specify the path for the executable and not just the executable name in the "Manage conflicting processes" list.
