script to suppress application shortcut which is running in admin mode
Answers (1)
Do it properly (as the software vendor clearly can't be bothered to code properly...)
- Run the software using ProcMon to determine which protected area of Windows the idiot developer has chosen to use.
- In your deployment package, use your favoured permissioning tool (e.g. SetACL) to open up permissions to allow users (Domain Users, Everyone, Users...whatever) to 'Modify' the location.
- Send a strongly worded email to the vendor, asking when it's likely that he'll realise it's 2017, not 1987.
EDIT, after a re-read:
It seems likely that the application is writing to a protected area only at first launch so you might be able to simply add the file/folder/registry value(s) to your deployment package. In which case:
- Run the software using ProcMon to determine which protected area of Windows the idiot developer has chosen to use.
- In your deployment package, add the file/folder/registry value(s) that you discovered.
- Send a strongly worded email to the vendor, asking when it's likely that he'll realise it's 2017, not 1987.
