Problem:
Some application that are incompatible with our elevation service might need to be elevated manually (on top of a correctly configured elevation ProfileUnity rule).
Resolution:
Step 1. Create an elevation rule in the ProfileUnity module that matches the application to be elevated (among other options it is possible to use a path for the application).
Option 1. Create a script text file and save it as elevationScript.bat
Include the below in the script file (make sure to replace the below application path).
"C:\Program Files\ProfileUnity\FlexApp\lwl_userapp_trigger64.exe" "\\Server\Share\Application\application.exe” /elevate >> “%temp%\ProfileUnity\elevationScript.log”
Option 2. (if .bat file does not launch the application)
a) Create a .ps1 file with following command:
Start-Process "C:\Program Files\ProfileUnity\FlexApp\lwl_userapp_trigger64.exe" "\\Server\Share\Application\application.exe” /elevate
b) Create a shortcut with this command: (Try to create one with shortcut creation tool)
powershell.exe -executionpolicy bypass -NoProfile <\\server\share\newfile.ps1>
Step 2. How to trigger the script. There are multiple ways to use this script.
Save the shortcut to a script (bat or ps1) on a desktop, and run it form there. The elevated application will open.
Note: If an icon is required, using a shortcut pointing to that script is a better option. To do that, create a shortcut, and point to the elecationScript.bat. Once the Shortcut is created, navigate to the Shortcut tab and click the "Change Icon" button.
Product: ProfileUnity-FlexApp
Product Version: 6.8.x