Hello,
I'm not sure if I'm in the right section, but as the saying goes, nothing ventured, nothing gained.
I've known about WAPT for a while and decided to use it a week ago.
Here's the problem: my package installations don't start when Windows shuts down. I have several machines, including Windows 7 (no problem) and Windows 10, where the problem persists. I've disabled hybrid shutdown as I saw at this link: https://www.wapt.fr/fr/doc-1.3/Frequent ... d-shutdown. The installations start correctly when I do them manually using the notification icon.
Here are the versions:
[*] WAPT server version: WAPT server community: 1.7.4
[*] Server operating system: Windows Server 2016
[*] WAPT client problem observed: Windows 10
Thank you in advance for your help!
[SOLVED] Unable to launch installations when Windows 10 is shut down
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
-
mathias.lec
- Messages: 2
- Registration: Oct 28, 2019 - 10:53
Last edited by mathias.lec on Oct 28, 2019 - 2:22 PM, edited 1 time.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
I recently noticed a problem with Windows 10.
If the `gpupdate /force` command doesn't work correctly (gpresult /h result.html)
, then local GPOs aren't being applied.
It's worth investigating if that's the issue.
If the `gpupdate /force` command doesn't work correctly (gpresult /h result.html)
, then local GPOs aren't being applied.
It's worth investigating if that's the issue.
-
mathias.lec
- Messages: 2
- Registration: Oct 28, 2019 - 10:53
Thank you for your reply. The problem was indeed that the DNS address had been changed on the client machine, even though Windows is under Active Directory, making it impossible to update the Group Policy Object (GPO).
Problem solved!
Problem solved!
A cool thing for you would be to make a WAPT package with a def_audit() (If you are on the Enterprise version) which would check on your network that the DNS is correctly configured and which would return the audits as errors for the machines whose DNS is not correctly configured, and then share your package on the forum.mathias.lec wrote: ↑Oct 28, 2019 - 2:21 PM Thank you for your reply. The problem was indeed that the DNS address had been changed on the client machine, even though Windows is under Active Directory, so it was impossible to update the GPO.
Problem solved!
In any case, congratulations to you and Simon for the diagnosis that led you directly to the resolution.
Vincent
Vincent CARDON
Tranquil IT
Tranquil IT
