Hello and Happy New Year to all,
I've noticed that on one of the domains I manage, the workstations aren't applying the update on shutdown. I must have made a mistake during deployment, but since it was a while ago, I can't figure out where the problem lies.
The domain runs on Windows 7 Pro with a Linux server (no GPO). WAPT is installed on my machine. The agent was deployed using PsTools, and manual installations work correctly.
I tried using the command `wapt-get add-upgrade-shutdown`, which returns "none" on one client and "FATAL ERROR: IndexError: list index out of range" on the machine hosting the WAPT server.
Is there a command I can add to a WAPT package to force this setting or reinstall the `wapt-exit` service?
No installation required when the workstations are switched off
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 :
Argh, I hadn't read the entire documentation. By deleting the gpt.ini file as indicated in the corrupted local GPO resolution guide, I managed to fix it.
For those who don't want to use PsTools and scripts to correct the problem, you can manually push the package attached to this message from the WAPT console. It only fixes the corrupted local GPO issue, but this would be a good opportunity to offer a dedicated package to address common problems.
For those who don't want to use PsTools and scripts to correct the problem, you can manually push the package attached to this message from the WAPT console. It only fixes the corrupted local GPO issue, but this would be a good opportunity to offer a dedicated package to address common problems.
- Attachments
-
- vh-wapt-exit_0-0_all.zip
- Package to fix wapt-exit
- (2.27 KB) Downloaded 383 times
