Tranquil IT Forum

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!

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.

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!

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!

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.

In any case, congratulations to you and Simon for the diagnosis that led you directly to the resolution.

Vincent