Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (2)

Resolved CloudAppPublisher: centralized deployment

  1. How-to
0
Votes
Undo
  1. Thomas Rolseth
    Thomas Rolseth
  2. PowerBuilder
  3. Wednesday, 4 August 2021 14:47 PM UTC

I am working on a PB migration project and as part of that effort, I demonstrated how to use PowerClient to deploy the application.  The client is very interested but asked a question that I don't know the answer to.  They are wondering if the CloudAppLauncher component could be packaged into a centralized distribution mechanism like Software Center so that their IT department can have some control over how it is accessed and/or made available to end users.  This is a large company.

Is this possible?  If so, any idea how it would be done?  Since I've used PowerClient I have a CloudAppPublisher folder in inetpub\wwwroot -- see attached.  Is it just a matter of giving this folder to IT?  Is this even advisable?  If there is a new version of the CAL I'm not clear on how they would get it.

Thanks, Tom

Attachments (1)
cal.JPG cal.JPG
  1. Deployment
  2. Installation
  3. PowerBuilder (Appeon)
  4. PowerClient
Debugger Code is Out Of Sync!
Are there issues running PB2019 on MS Server 2008 ...
Responses (2)
Donald Clayton
Donald Clayton Accepted Answer Pending Moderation
  1. Wednesday, 4 August 2021 21:59 PM UTC
  2. PowerBuilder
  3. # 1

Yes there is an .MSI in C:\inetpub\wwwroot\CloudAppPublisher\CloudAppInstall after deploying locally to .IIS.  What the client hopes to do is "push" the CloudAppPublisher to the user base ahead of time, have it installed as a service for all machine users (which I think requires elevated privileges on Win 10), register/start the service, and also present the users with desktop and/or start menu shortcuts so that when they run the app it self-installs to \user\%USERNAME%\AppData, with the runtime having already been provisioned.

These desktops are _very_ locked down.  So what we're hoping to do is help the client configure the package for centralized deployment, IT installs the underlying service, and register the App shortcut/icon on the desktop that points to the appropriate web server.  If the last part's not feasible then we can pass out a URL once the runtime is installed.

Perhaps it's as simple as doing the launcher packaging in the PowerClient Project, making the appropriate choices a priori, and then using that in a centralized push.  

Don

Attachments (1)
Capture.JPG Capture.JPG
Comment
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 5 August 2021 00:06 AM UTC
I'm a little confused why your client can't push the .MSI ahead of time? I'm not a system admin expert, but it has been my understanding that you can use group policies or something like that to preintsall .MSI. https://docs.microsoft.com/en-us/troubleshoot/windows-server/group-policy/use-group-policy-to-install-software

As far as the two modes the launcher can run under, I don't recommend installing it as service because then it will require elevated privileges. Without service works great and that is our default setting.

As far as shortcut, that will not get created until the launcher is used and a URL is entered at least one time. It is the initial download of the app by the launcher that the shortcut gets created.
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 4 August 2021 16:06 PM UTC
  2. PowerBuilder
  3. # 2

Hi Tom, There should be an .MSI installer of the Cloud App Launcher.  Would an .MSI solve your issue?

Comment
Thomas Rolseth
  1. Thomas Rolseth
  2. Thursday, 5 August 2021 20:16 PM UTC
Yes, it might. Where is the MSI installer for the CAL? Thanks!
  1. Helpful
Armeen Mazda @Appeon
  1. Armeen Mazda @Appeon
  2. Thursday, 5 August 2021 20:25 PM UTC
As Don mentioned, you can obtain the .MSI from C:\inetpub\wwwroot\CloudAppPublisher\CloudAppInstall\
  1. Helpful
Thomas Rolseth
  1. Thomas Rolseth
  2. Thursday, 5 August 2021 21:50 PM UTC
That's the problem. It's not there for me. I've uninstalled/re-deployed several times but the only files there are a .exe and an .json. See the attached with my original post.

  1. Helpful
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.