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,
Windows restarts every 10-15 minutes
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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,
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,
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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=
`?
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=
`?
