Tranquil IT Forum

Hello,

I'm starting this thread because we're facing a problem that, for the moment, seems inexplicable.
We have a WAPT server, version 2.5.5.15591, with the agents running the same version.

When the machines are no longer communicating with the domain (remote work without a VPN), they restart every 10-15 minutes.

The diagnostics that lead us to believe there's a link with WAPT are as follows:

We created a clean machine, which, when in the same state (no domain connection), works perfectly.
As soon as WAPT is installed on it, it restarts after 10-15 minutes. If we remove WAPT, the machine works normally again.
We also tested removing the machine from the domain, with WAPT installed, and it works even when it's outside the domain.
If the machine is in the domain, but has no internet access (no access to the WAPT Web repository), it doesn't restart either.

The problem seems to be the following: When the workstation, with WAPT installed, is in the domain but can no longer communicate with it, it restarts every 10-15 minutes.

For your information, the domain is a Synology DSM 7.2-64570 Active Directory with a 2008 R2 forest version.

Have you ever encountered this type of problem? Any ideas?

Sincerely,

Hello,

in your tests, do you have any WAPT packages installed on the machine?

If so, could you please try again on a clean PC without any WAPT packages?

Simon

Hello Simon,

In our tests, we also tried with the WAPT agent installed, but without any packages.
The PC still restarted.

Regards,

This is the first case of this type that has been reported to us; do you have anything in the WAPT logs and in the Windows event viewer?

Hello,

After analysis, here's what we observed:
The WAPT agent was deployed via GPO, with the `--force` option added to the WAPT deploy options.
This option was forcing a restart when the PC couldn't contact Active Directory.
After removing the option, the restarts stopped, so the problem is "solved."

Any idea why the option caused the workstation to restart only when it couldn't contact the domain?

Sincerely,

Generally, the `force` option should not be used in a GPO, otherwise it will force a reinstallation every time waptdeploy is launched.

I've done several tests here without being able to reproduce your issue.

Can you specify your deployment method?
GPO -> startup script?
GPO -> scheduled task? (With or without file copying?)

And in both cases, what is the value of `--waptsetupurl=

`?