GPO waptexit not taken into account
Published: March 24, 2017 - 2:27 PM
Hello everyone,
A big thank you already to the developers and users who provide feedback via blogs and forums. The wapt documentation makes setting up the server easy.
Currently, wapt is running on my VM via the Windows 10 Hyper-V Manager while I wait to transfer it to the Hyper-V server once everything is working.
However, I still have one problem, as the title suggests: the waptexit console fails to run on my test machine.
I've verified that the local GPO was correctly configured during the wapt agent installation.
If I launch it manually, it runs without any issues.
Even when creating a GPO during shutdown on the Active Directory server to launch a batch file that calls c:\wapt\waptexit, nothing happens.
I've checked the existing GPOs, and nothing seems to be preventing the policy from executing correctly.
Anyway, thanks for reading this long post.
Do you have any ideas?
A big thank you already to the developers and users who provide feedback via blogs and forums. The wapt documentation makes setting up the server easy.
Currently, wapt is running on my VM via the Windows 10 Hyper-V Manager while I wait to transfer it to the Hyper-V server once everything is working.
However, I still have one problem, as the title suggests: the waptexit console fails to run on my test machine.
I've verified that the local GPO was correctly configured during the wapt agent installation.
If I launch it manually, it runs without any issues.
Even when creating a GPO during shutdown on the Active Directory server to launch a batch file that calls c:\wapt\waptexit, nothing happens.
I've checked the existing GPOs, and nothing seems to be preventing the policy from executing correctly.
Anyway, thanks for reading this long post.
Do you have any ideas?