Did you configure the CAL to run as a background "Service". If so, it will require local Admin privileges. If you configure the CAL to run "without" a service, it will install under your "user" MS-Windows profile.
Thanks, I know! And this is the problem. Actually, we faced two problems when we were trying this feature. The first one was that running self-extracting archives is blocked by the group policy (so, the launcher is never installed when you click that button on the welcome page). We worked this around by manually unzipping the installer file and running it. The second problem was what I described in the initial post: the installer installed the launcher under the user profile, and running exe from that path is blocked by the group policy.
As a side note, we really could use some kind of a troubleshooting guide from Appeon, because when you do as you were told and nothing happens you don't really know what you can do next.
Sorry that it is not supported to install cloud app launcher on the client to a custom folder at the moment.
Please try the following workaround to copy the launcher to another folder. 1. Install Cloud App Launcher. 2. Copy Launcher from C:\Users\%windows user%\AppData\Local\Launcher to C:\Launcher. 3. Refer to the attached cloudapp.reg to modify the registry item to reference to C:\Launcher. 4. Refer to the attached CloudAppLauncher_withoutservice.reg to modify the registry item ’Location’ to reference to C:\Launcher and change registry item ’CloudAppHome’ to refer to C:\PBApps.
Then you can run the application via browser, the application files and runtime files will be download to C:\PBApps. You can also start the application via a command like below. C:\Launcher\CloudAppShell.exe %your application URL%