Installer built with LabVIEW 2017 is "calling home"

[cpschnuffel]

Hi forum,

using LabVIEW 17.0.1f3 (2017 SP1) I built an application and an installer for a project. Everytime I execute the installer it tries to open a tcp connection to <2.19.38.59:80>; blocking this attempt (resulting in a short delay during installation) does not harm the installation process.

Due to this behavior I contacted the NI support; the answer was that either a signature check or a license check was made during this connection and that you cannot disable it (e.g. with an entry in <setup.ini>).

Dear NI developers: If you put those kind of functionalities in your code you should keep in mind that some customers doesn't like "home calls" at all, especially when distributing code to people who are allergic to those unwanted connections.

Regards,

cpschnuffel

[Intaris]

The IP address is owned by Akamai.

Microsoft, Apple and a lot of major software developers use Akamai services as part of their content delivery.

It could very well be a check for software updates (for run-time engines and so on) that is causing this.

[cpschnuffel]

Ok, but why? There's no need for an update check; the setup contains everything needed (that's the deeper sense of a setup I guess).

The only thing it does: it unsettles my customers.

Any idea to circumvent this smartly (without pulling the ethernet cable)?

Does anybody know whether LabVIEW 2018 behaves similarly? I know that LabVIEW 2015SP1 does NOT have this "feature".

cpschnuffel