Tranquil IT Forum

Hello,

- WAPT version installed: 1.6.2.5
- Server OS: Debian Stretch
- Administration/package creation machine OS: Windows 10

I'm stuck on creating a new package. The problem is as follows:

The setup runs perfectly silently, except that during the setup process, an executable file for a dependency (Viewpoint Media Player) is copied to the Program Files (x86) folder and then called at the end of the initial program's installation. Obviously, this new file isn't executed silently, and the package therefore waits for the timeout.

Based on my tests, this dependency is useless (the program works without installing it).

Do you have any idea how to bypass this second installation?

Thank you

https://en.wikipedia.org/wiki/Viewpoint_Media_Player

Viewpoint Media Player is sometimes marked as adware[7] due to the program commonly being installed without user notification or intervention.[8] If Viewpoint is whilst removed a program requiring it remains installed, it again re-installs silently without notifying the user.[9] The Viewpoint Media Player itself does not directly collect user identifiable information, unless the user enters it. The license agreement states that the software collects information about the user's interactions with advertisements, and also the browser and operating system in use. The privacy policy also states that the plug-in collects some browsing history by way of referrer information. This information is collected by Viewpoint along with a unique identifying code.[10]

Thanks for the info!

All the more reason to bypass its installation, or else I'll tell the professor that the software is infected with adware and therefore there's no way I'm installing it.

But since I know that during a manual installation I have the option to install the software without the adware, I'm still interested in finding a solution via Wapt.

Problem solved! The teacher has a portable version of the software, so no installation is needed

olaplanche wrote: ↑Oct 17, 2018 - 2:16 PM Problem solved! The teacher has a portable version of the software, so no installation is needed.

It's a complete victory if the portable software is placed in a standard path, like C:\Program Files (x86).

If the portable software is deployed in the user's home directory, it is a Pirrhus' victory; your opponent is defeated today, but you will be defeated in the long run.

Indeed, you may want to implement Software Restrictions (SRP) downstream, which state that anything not in C:\Program Files (x86)\ or C:\Program Files\ is not allowed to run, in the Linux style.

In my opinion, SRPs in Windows are the most effective methodologies against computer viruses today.

After all, a teacher's happiness is precious, and so is yours, so doing what needs to be done right away while thinking about the next step is the best approach.

See you soon.

Vincent

We've been using SPR for many years, and all I had to do was "drop" the software into a shared folder that I approved and where no one has write access.

Indeed, I could also create a package that copies the file to C:\Program Files (x86) and create a shortcut on the desktop/Start menu.

Thanks,
see you soon.