- Daryl Foster
- PowerBuilder
- Thursday, 2 September 2021 07:50 AM UTC
Hi, I've got a question which is a little bit similar to this one https://community.appeon.com/index.php/qna/q-a/cloudapppublisher-centralized-deployment. I've been testing the new PowerClient deployment for our apps and I'm still not 100% sure how the CloudAppLauncher service/non service thing works?
We've deployed a few test PowerClient apps with the non-service installation and we had issues because our PCs are pretty locked down with application whitelisting. I managed to overcome that now just for testing, but going forward we are considering installing the CloudAppLauncher_Installer.msi via group policy ahead of time and then giving the users the URL to our PowerClient applications. So my questions are:
1. Will this work correctly? Will the files served via the URL find the pre-installed CloudAppLauncher
2. If we install CloudAppLauncher_Installer.msi via Group Policy, or some other automated central software deployment will that install the CloudAppLauncher as a service?
3. We are building the applications in the latest version of PB 2019R3, but when we migrate to PB 2021 or later, will we need a different version of the CloudAppLauncher installed? How are updates to CloudAppLauncher applied, either when we deploy with the msi, or when it is installed locally via the URL?
Thanks.
Find Questions by Tag
Helpful?
If a reply or comment is helpful for you, please don’t hesitate to click the Helpful button. This action is further confirmation of their invaluable contribution to the Appeon Community.