Tranquil IT Forum

Hello,

I have two questions for you. I'm currently testing WAPT.

1 - Once a machine or group of machines is marked for a software update/installation, is the actual start of the installation (or update) managed automatically? Our machines are laptops and therefore frequently move around our network.

2 - I've just looked at WAPT's repository/package system, and it's good. BUT, to avoid duplication of effort, I'd like to be able to create a WAPT package/repository (or any other method) that uses our existing repository (Microsoft DeploymentShare$ SMB share, used for deploying our master images via WDS and MDT), which is located in our DFS space \\domain.local\dfs\DeploymentShare (e.g., \Applications\appli001\setup.exe). Is this possible with WAPT?

Thank you. These two conditions are essential for us to adopt this tool.

Good morning,

1 - The installation is not direct since we do not want to break production at 10:30 am by pushing the latest Firefox update (this is based on experience).
During the update, the WAPT agent caches the packages locally on the client machine; the WAPT agent then waits for an instruction to launch the installation of the updates (upgrade).

Possible instructions are:

• from the WAPT console by the administrator
• from the local workstation via command line
• at the end of the shift
• via a scheduled task

2 - A WAPT package repository is a directory WEB accessible via http and not an SMB share.

https://www.wapt.fr/fr/doc/Theorique/in ... e-de-depot

It is perfectly feasible to set up an additional repository on a Microsoft server, provided you have a good understanding of IIS configuration. The relevant documentation for this is:

https://www.wapt.fr/fr/doc/Installation ... index.html

Sincerely,

Alexander

Thanks Alexandre for your answers.

For question 1, I would have liked behavior similar to a login script (asynchronous: it runs once the user is connected to the network), meaning that upon connection (connection to the Active Directory network), the installation/update, defined in the WAPT console, would run.
The goal is to avoid having to manually manage the installation or update once the command has been given, once and for all, in the WAPT console.

Question 2:
I understand that we are using a Debian-style repository (apt), therefore web-based.
This allows me to set up a website on our NAS or Windows Server 2008 R2 servers that overlays the MDT share.

What I want to know is whether it's possible to use these MDT packages for WAPT without modifying them. Basically, a package is just an .msi file, so "msiexec.exe app01.msi /qn" or setup.exe /s.

Excuse my trivial questions, Wapt is quite new to me.

ledufakademy wrote: ↑Sep 29, 2017 - 11:25 AM Thank you, Alexandre, for your answers.

For question 1, I would have liked behavior similar to a login script (asynchronous: it runs once the user is connected to the network), meaning that upon connection (connection to the AD network), the installation/update, defined in the WAPT console, runs.
The goal is to avoid having to manually manage the launch of the installation or update once the order has been given, once and for all, in the WAPT console.

Wapt works as follows:

Every two hours, the wapt packages awaiting installation will be downloaded locally to the machine. Then the wapt agent will wait for an installation command.

This means that the installation can be done even if the server is unavailable, since All executables are contained in the wapt package

Software installation can then be easily done by launching c:\wapt\waptexit.exe, so you can launch it whenever you want... login, logout, computer startup... shutdown... scheduled tasks... icon on users' desktops... in short, no limits!

ledufakademy wrote: ↑Sep 29, 2017 - 11:25 Question 2:
I understand that we are using a Debian-style repository (apt), so it's web-based.
This allows me to set up a website on our NAS or our Windows Server 2008 R2 servers, using the MDT share.

What I want to know is if it's possible to use these MDT packages for WAPT without modifying them. Basically, a package is just an .msi file, so "msiexec.exe app01.msi /qn" or setup.exe /s.

Excuse my trivial questions; WAPT is quite new to me.

The wapt package does indeed include the executables directly, so it's very simple.

More information in the video: https://www.youtube.com/watch?v=fD2nOumPfPQ

You can also call us, we can offer you training on the product!

Simon