It would be nice to have the ability to specify the content location of the 'Detection Method Scripts' so that it can be saved to a trusted folder location.
For example, all unapproved scripts are blocked via BIT9 in our environment, but, if we're able to save them to a trusted location, they could be automatically approved.
This feature shipped in build 1.4.8 you can use:
HKEY_LOCAL_MACHINE\SOFTWARE\Patch My PC Publishing Service:DetectionMethodScriptsAddtionalSavePath = \\server\examplefolder
Type = String value
Attachments Open full size
We can look at making it a registry value configuration. I'm not sure if a UI piece would be right if there aren't many other customers requesting this option. I will bring this to our engineering team. I don't think it would be too complex and time consuming from an engineering side.
Attachments Open full size
Yes those are the scripts, which is great, but it would be really helpful if there was a way to change this location to a UNC path in the GUI. Similar to how Licensed Products are handled. As I assume these will be updated with every sync, so manually approving/copying these would become a chore.
If it's not a popular idea, then perhaps a reg or ini hack would suffice!
Attachments Open full size
In build 1.4.7 (https://patchmypc.com/publishing-service-setup-documentation#releasehistory), we save all detection method scripts to the "<InstallDir>\Detection Method Scripts". is this what you are looking for?
Improvements
Powershell detection method scripts are now saved in the <InstallDir>\Detection Method Scripts folder.
Attachments Open full size