Tranquil IT Forum

Hello everyone (hello Simon ),

I'm a Wapt user at a high school, and I'm encountering several rather annoying problems:

- Every morning when I arrive and launch the WAPT console, the first window asking for the password appears, but immediately afterward I get 503 Apache errors... I have to restart the server every day! I'm running an up-to-date Debian 8 system, so it's clearly an Apache problem, but I don't see how to solve it...

- The other problem is that when I ghost a PC with an image that already contains the WAPT agent, in the console, under the machine's packages, I see the new PC name but also the name of the PC that was used to prepare the ghost! So, some PCs have three hostnames...

- And lastly: on the first installation of my machines, the software updates correctly (I'm thinking in particular of Avast, which isn't in my image but is associated with my PCs in WAPT). However, the next few times I ghost the PCs again, Avast doesn't install! It remains green in WAPT as if it were installed, and no matter how many times I update the computer and restart it, nothing happens...

Any ideas?
Thanks
Matthieu

Hey Math, I'm reposting what we said off the record, it might be useful

Matthiman wrote:
As a Wapt user at a high school, I'm encountering several rather annoying problems:

- every morning when I arrive and launch the WAPT console, the first window asking for the password appears, but immediately afterward I get 503 Apache errors... I have to restart the server every day! I'm running an up-to-date Debian 8 system; it's clearly an Apache problem, but I don't see how to solve it... Matthieu

Check the Debian server graphical interface; it would match a message on the list:
http://lists.tranquil.it/pipermail/wapt...00994.html

Matthiman wrote: - The other problem is that when I ghost a PC with an image that already contains the WAPT agent, in the console, under the machine's packages, I see the new PC name but also the name of the one used to prepare the ghost! So I have some PCs with 3 hostnames...

The best way is to deploy without wapt, and once the machine is deployed, you deploy with fog snapping (I no longer use snapping) or even faster with ttp://wapt.tranquil.it/wapt/waptdeploy.exe via gpo.

If you want to install the packages in your master, install wapt (without registering it on the wapt server). Your master must not have a package host to avoid this. Then install the packages with "wapt-get install basegroup", then uninstall wapt and do not delete c:\wapt at the end of the uninstallation.

The first method remains the simplest and cleanest; I deploy my Windows images without software now, then the software is installed once the domain is joined, so that in addition the software has the correct PC name, and also the correct UUID.

Matthiman wrote: - and one last thing: on the first installation of my machines, the software updates correctly (I'm thinking specifically of Avast, which isn't in my image but is associated with my PCs in WAPT). However, the next time I ghost the PCs again, Avast doesn't install! It remains green in WAPT as if it were installed, and no matter how many times I update the machine and restart it, nothing happens...

In your console, when you click on the PC, you have the list of installed wapt packages with their version number, what is the most recent version of the wapt package in your private repository, and what version is installed on the machine (according to the wapt console)
[/quote]

I think the problem is related to the issue mentioned above.