Hello,
when deploying WADS on a physical PC, the WAPT agent fails to install, even though it's checked in the deployment configuration, and it doesn't execute the post-installation script.
However, I have no problem when I perform this operation with a VM on an ESX host...
it doesn't seem to be a driver issue, as no drivers are missing in Device Manager...
I'm having trouble understanding this...
[SOLVED] WADS - Install WAPT agent - post install script
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 :
It's strange that it works in a VM but not on a real PC.
The concept of the post-install script is very simple; it's based on this:
https://docs.microsoft.com/en-us/window ... windows-11.
Furthermore, the network doesn't need to be up for Wapt to install since the Windows image already contains waptagent.exe and waptsetup.exe.
You can verify that your script is indeed located in c:\windows\setup\scripts\Setupcomplete.cmd on the deployed machine at the end of the installation. You can even run it yourself to see what's wrong.
The concept of the post-install script is very simple; it's based on this:
https://docs.microsoft.com/en-us/window ... windows-11.
Furthermore, the network doesn't need to be up for Wapt to install since the Windows image already contains waptagent.exe and waptsetup.exe.
You can verify that your script is indeed located in c:\windows\setup\scripts\Setupcomplete.cmd on the deployed machine at the end of the installation. You can even run it yourself to see what's wrong.
Thanks for the link, Simon, this MS article is super interesting!
Server: WAPT Enterprise 2.6.1.17786 on Debian
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Consoles: Windows 10 & 11
Infrastructure: Windows
Did you know? When parrotfish undergo smoltification, their osmoregulation mechanism is reversed!
Ah yes, I also used that method with my sysprep!sfonteneau wrote: ↑May 18, 2022 - 10:05 PM It's strange that it works in a VM but not on a real PC
. The concept of the post-install script is very simple; it's based on this:
https://docs.microsoft.com/en-us/window ... windows-11
Furthermore, the network doesn't need to be up for Wapt to install since the Windows image already has waptagent.exe and waptsetup.exe.
You can verify that your script is indeed located in c:\windows\setup\scripts\Setupcomplete.cmd on the deployed machine at the end of the installation. You can even run it yourself to see what's wrong.
I'll take a look and keep you posted.
According to Microsoft:
%Windir%\Setup\Scripts\SetupComplete.cmd: this script runs with local system permissions and starts immediately after the user sees the desktop.
So apparently, an autologon is needed...
But that still doesn't explain the difference between my VM and a physical machine....
%Windir%\Setup\Scripts\SetupComplete.cmd: this script runs with local system permissions and starts immediately after the user sees the desktop.
So apparently, an autologon is needed...
But that still doesn't explain the difference between my VM and a physical machine....
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Here, I don't need the session to open for the script to work, so that's strange.
Could you send your answer file so we can see what the problem is?
I admit I don't understand the difference between a VM and a physical PC in the tests.
Could you send your answer file so we can see what the problem is?
I admit I don't understand the difference between a VM and a physical PC in the tests.
Hi Simon,
so I think I've figured out why...
In my answer file, I removed the ProductKey provided by the template and enabled automatic activation.
As a result, on a physical PC, it activates the UEFI OEM license, but on my VM, Windows doesn't activate because there's no valid license.
So, from what I understand, SetupComplete only runs on an unactivated Windows 10...
so I think I've figured out why...
In my answer file, I removed the ProductKey provided by the template and enabled automatic activation.
As a result, on a physical PC, it activates the UEFI OEM license, but on my VM, Windows doesn't activate because there's no valid license.
So, from what I understand, SetupComplete only runs on an unactivated Windows 10...
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hmm, during our tests here our Windows systems weren't activated and it worked
