1. Marcin Jurkowski
  2. PowerBuilder
  3. Friday, 14 May 2021 14:23 PM UTC

Hi,

I just want to check if there is any update on few things from this post as I'm installing PowerClient for some clients this month: PB2019 R3 beta - C/S Deployment (appeon.com)

1. Various AV software still complains about the launcher during setup.
I need to manually approve the application but it can be a problem for if a non-technical clients are doing this.
The same applies to Windows Protection SmartScreen - it needs manual approval.
Can I do anything about it?

2. I cannot run my applications anymore when the server is down:

2021-05-14 15:11:57.618 ERROR [20748] Application terminated.
2021-05-14 15:11:57.600 ERROR [21428] Failed to download the file. URL: https://myurl.com:443/powerclient/app/deploylist.ini.zip, Error description: HTTP error.(error code: 404)

The application is fully downloaded at this stage.
Is there an update for that or some option that I can enable?
Can it not just show an error about the update but still launch after that?

 

3. Question - when I have an update/ new version for clients, do I always have to include "deploylist.ini.zip" file or is it only required when I add new file(s)?

Regards,
Marcin

Kai Zhao @Appeon Accepted Answer Pending Moderation
  1. Monday, 17 May 2021 03:37 AM UTC
  2. PowerBuilder
  3. # 1

Hi Marcin,

To update your application on web server, you need to at least update the following two items on the web server.
1 The file deploylist.ini.zip.
2 The latest version folder.

It’s suggested that you use the function of packaging the PowerClient project as it will package the latest version folder only and files required to run the PowerClient application. Please refer to the article below for details.
https://docs.appeon.com/pb2019r3/pbug/ch07s03.html#packaging_the_PowerClient_project

Regards,
ZhaoKai

Comment
  1. Marcin Jurkowski
  2. Monday, 17 May 2021 08:16 AM UTC
Thank you Zhao. I'll try the packaging option.

Regards,

Marcin
  1. Helpful
There are no comments made yet.
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Friday, 14 May 2021 17:18 PM UTC
  2. PowerBuilder
  3. # 2

Hi Marcin;

  In addition to what Armeen has stated - this may cause your users runtime issues as well ...

Make sure that you choose the Single User option to be safe.

HTH - Regards ... Chris

Comment
  1. Armeen Mazda @Appeon
  2. Friday, 14 May 2021 17:52 PM UTC
Hi Marcin, I want to make sure Chris is not confusing you with these additional comments. The "Launcher without background service" supports multiple users WITHOUT admin rights. So that's why you should follow my recommendation of only checking "Launcher without background service". Do NOT check "Launcher with background service".
  1. Helpful
There are no comments made yet.
Armeen Mazda @Appeon Accepted Answer Pending Moderation
  1. Friday, 14 May 2021 15:55 PM UTC
  2. PowerBuilder
  3. # 3

Hi Marcin,

#1 Anti-Virus False Positive

We have tested PowerClient with the top 20 AV software without problems.  Please report to the AV vendor their software is erroneously flagging PowerClient.  

Another thing important is that you deploy PowerClient using the "without background service" option and digitally sign both the launcher and your app using a trusted certificate.  If it is not signed or the certificate is not a trusted one, Windows will give security warning.

#2 Cannot Run When Server Down

You didn't configure your PowerClient project correctly.  You MUST select the option "Update when connected" on the "Deployment" tab if you want the app to be able to run when the Web server is down.  Did you not read the documentation?  https://docs.appeon.com/pb2019r3/pbug/ch07s03.html#defining_an_ica_project

#3 Procedure to Update

You MUST always do updates to the Web server either by directly deploying from the PB IDE or by creating the standalone package.  Do NOT manually manage the files individually!  Once the Web server is updated, the correct files will be automatically and incrementally updated to each end user when they start your app.  Please follow the documentation instructions how you should deploy. https://docs.appeon.com/pb2019r3/pbug/ch07s03.html#packaging_the_PowerClient_project

Best regards,
Armeen

Comment
  1. Marcin Jurkowski
  2. Friday, 14 May 2021 16:13 PM UTC
Hi Armeen,



Thank you for your comments.



1) It blocked me on Sophos and McAfee today but I understand that it's hard to test all possible AV software versions.

I'll have a look at the trusted certificate for Windows Protection SmartScreen (maybe it'll help with AV as well).



2) Great that this option is there now. It was my mistake. I haven't used that option during deployment package configuration.



3) What I'm doing is deployment to a local folder and then I manually copy the latest version to the web server e.g.

In my folder I have sub folders e.g. version 1.01, 1.02, 1.03, etc...so I take the latest version folder and put it on the web server.

In my local folder I have also "deploylist.ini.zip" file which gets updated after each build so I understand that I have to update it as well on the web server for each build?



Regards,

Marcin
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Friday, 14 May 2021 16:39 PM UTC
Hi Marcin,

#1 Please do me favor report these false positives to Sophos and McAffee since you are their customer, but also open support ticket with Appeon team so we can also look into these: https://www.appeon.com/standardsupport/newbug These are two top AV software they should not be reporting false positive.

#3 Sorry, I misunderstood you. I don't know the answer, but I'll have one of our support staff respond here about this. Thanks.
  1. Helpful
  1. Armeen Mazda @Appeon
  2. Monday, 17 May 2021 03:50 AM UTC
Hi Marcin, Please take a look at Zhao Kai's response about your point #3. He provided doc link. Please follow those instructions carefully.
  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.