Tranquil IT Forum

Hello,

I've set up a WAPT (Debian) server on about fifty workstations in a company, and it generally works well.
However, on some PCs, packages don't install when the machine shuts down, while on others, it works without any problem. All the workstations are running Windows 7 Pro, the firewall is disabled, and the antivirus software is the same for everyone.
The package is downloaded correctly to the machine.
If I force the installation from the console, the package installs (but that's not ideal because it disrupts the users).

Can you give me any suggestions? Are other users experiencing the same problem?

Hello,

the shutdown installation is launched using the computer's shutdown script (local GPO).

The shutdown script runs: c:\wapt\waptexit.exe. You can check if it's working.

To verify that the shutdown script is installed correctly, you can open a command prompt and run:

gpedit.msc

Computer Configuration --> Windows Settings --> Scripts --> System Shutdown.

Normally, waptexit.exe should be listed here.

If it's not, you can run the following commands in a command prompt:

wapt-get add-upgrade-shutdown to add the shutdown script or

wapt-get remove-upgrade-shutdown to remove the shutdown script.


Simon

Hello

, thank you for the quick reply. I did check with gpedit.msc and there's nothing in the shutdown script.
If I type the command on the PC (even in administrator mode):
`wapt-get add-upgrade-shutdown`,
I get the following FATAL ERROR: IndexError: list index out of range.

Even using `--force` in waptdeploy to reinstall Wapt on the PC doesn't change anything.
Is there a bug I should report? Is there a PC configuration that could be causing this error?

Is there anything else I could do (remotely?) to fix this?
(A GPO to install that forces `waptexit` in the script? But that would be a workaround.)
On some PCs, there's no problem, on others I have this issue, and they are all PCs configured the same way in a domain-based enterprise environment...

Thank you.

I don't have an explanation for your "FATAL ERROR: IndexError: list index out of range" error; we'd need to look into it in more detail.

The quickest solution, if these are domain-joined PCs, is to add waptexit.exe to the system shutdown scripts in a GPO on your Active Directory. Go to

Computer Configuration --> Windows Settings --> Scripts --> System Shutdown and add waptexit.exe.

On machines that are already working, this will run waptexit twice, which isn't really a problem.

Simon

Thank you for the clarification.

Would it be possible to report this as a bug, for example? So that it can be fixed in a future version? Should I do that?

Thank you.

This might not be a bug.

I've installed around 800 WAPT clients across several sites and haven't encountered this problem.

WAPT is now installed on over 109,000 workstations and there have been few reports of this kind.

We would therefore need to determine the exact cause of the problem to consider it a bug.

I would also need other information:

OS:
Architecture: x86/x64;
WAPT version?

We need to be able to reproduce the bug on our end.

Simon

Hello,

thank you for the reply.
I also have a few PCs that won't install. They do install if we force the update from the WAPT console, but even if waptexit is correctly executed during the PC shutdown, it still doesn't work. Could it be a DNS problem? I've seen that WAPT has issues if the DNS is misconfigured. Any suggestions on how to check this?

My
PC configuration: x64 (all) on a Windows Server 2008 R2 domain,
WAPT Server running Debian.

WAPT Server version: 1.3.5,
WAPT Agent version: 1.3.5,
WAPT Setup version: 1.3.5,
WAPT Deploy version: 1.3.5.0.

Thank you.