WAPT and MDT

hasop · January 11, 2018 - 4:11 PM

Hello,
I have a somewhat complex question to help us think this through:
currently, our Windows machines are installed from a single master image (via MDT) and customized according to user needs.
With WAPT, how would you approach this?
a minimal master image installation with only a WAPT agent be suitable?
Could MDT force the addition of packages to the computer via command lines?
Is it possible for a newly added workstation to automatically inherit packages based on the Active Directory groups it belongs to (without any specific intervention)?

Thank you in advance for your suggestions.

January 11, 2018 - 5:24 PM

hasop wrote: ↑Jan 11, 2018 - 4:11 PM Hello,
A somewhat complex question to help us think things through:
currently, our Windows machines are installed from a single master image (via MDT) and customized according to user needs.
With WAPT, how would you do it?
A minimal master image installation with only a WAPT agent?
Could MDT force the addition of packages to the computer via command lines?

You can absolutely deploy wapt with software packages already installed in the image, along with wapt packages if you want; it's possible

Alternatively, launch the installation of the wapt agent in the mdm installation and then launch command lines in the mdm installation.

Code: Select all

wapt-get install tis-bureautique

hasop wrote: ↑Jan 11, 2018 - 4:11 PM Is it possible for a new workstation that is brought up to date to automatically inherit packages based on the AD groups to which it belongs (without any particular intervention)?

This will be possible in the enterprise version with the ORs
In the enterprise version you will be able to assign a wapt package to an OU.

hasop · January 12, 2018 - 9:30 AM

Thank you for the feedback.

We're going to experiment with command-line installations; that seems the most promising approach.

January 15, 2018 - 7:07 PM

hasop wrote: ↑Jan 12, 2018 - 9:30 AM Thank you for this feedback.

We will experiment with command-line installations; this seems the most promising approach.

We have clients who use MDT in conjunction with WAPT. They use a command line at the end of their MDT scripts to push the core packages. They are very satisfied with it!

Denis

hasop · January 22, 2018 - 11:30

A follow-up question: Is the package actually installed (assuming the return code is 0, I imagine) when the command "wapt-get install package-name" returns?

In other words, is there a guarantee that the packages are correctly installed at the end of the MDT installation process (assuming we use command-line installations), and therefore that the installation is complete and the computer can be shut down?

Thank you in advance.

January 22, 2018 - 8:49 PM

hasop wrote: ↑Jan 22, 2018 - 11:30 Subsidiary question: is the package actually installed (subject to a return code of 0, I imagine) when the command "wapt-get install package-name" returns control?

It all depends on how the packets are encoded

The command `wapt-get install groupe-debase` will complete.

But if one of the wapt packages in the group returned an error, the package in question will appear as an error in the console.

Wapt also performs additional checks at the end of the package; at the end of a package installation, Wapt will check if the uninstallkeys mentioned in the package are indeed present on the machine

In this way, even if the installation command returned 0, the wapt package will check if the uninstallkey is present. If it isn't, wapt will intentionally flag the package as an error since the software doesn't appear to be installed.

hasop wrote: ↑Jan 22, 2018 - 11:30 AM In other words, is there a guarantee that the packages are correctly installed at the end of the MDT installation procedure (assuming we use command-line installations), and therefore that the installation is complete and the computer can be shut down?

Thanks in advance.

If an error occurred, the package will show an error in the console. The installation will be attempted again in a future update!

hasop · January 23, 2018 - 09:02

So, to summarize:
When a return value of 0 is received, either the package is fully installed, or there was an error (for example, an error in the uninstallkey verification) and the package is marked as failed.
Is there a command line after installing the package that can definitively verify whether the package is showing as failed or not in the console (without having to open the console itself)?

I imagine the behavior is the same whether installing a group or a package with dependencies?

January 23, 2018 - 10:12

Hello,

if an error occurred, the package will show an error.
Therefore, an installation is still pending.

To see pending installations, you can run the command:

`wapt-get list-upgrade`.

If software is waiting to be installed, you can run the command `wapt-get upgrade`.

Simon

hasop · January 23, 2018 - 10:27

Sorry, I wasn't clear.

The idea is to be able to verify, within a script, that the installation is complete and successful.
If a return value of 0 doesn't guarantee a successful installation, can another command guarantee it?

Does the command "wapt-get list-upgrade" with an empty list return a specific return code?

olivetree · March 1, 2018 - 10:11

Sorry to jump into the thread.
With MDT, installing WAPT is very easy. You don't need an image that includes WAPT. You edit the task sequence you're using by adding the WAPT application, just like you would add the Visual C++ Redistributable, etc. Then you add the command line to the application so it launches during installation.
If you've configured your MDT to join the machines to the network, then the GPO is what works; then you refine the process so the packages are downloaded automatically.