Hello,
We are testing a new Windows 10 master image (our network is currently running Windows 7).
Yesterday, the master image installed successfully with the agent. The workstation registered correctly, and the packages were installed via the command line.
Today, we created a new master image with some modifications to the master image itself (Windows configuration). When installing a package via the command line, it displays: "
about to speak to waptservice...
waptservice User()".
The same message appears when running "wapt-get register", still as administrator.
The same agent installed on a standard Windows 7 workstation works perfectly.
Do you have any idea what the problem might be? Are there any steps we can take to identify the source of the problem?
Thank you in advance.
Windows 10 Agent Installation
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 :
The window:
Appears when the wapt agent detects that it does not have permission to start the installation.
It therefore tries to pass a service account and thus requests an authorized username and password to execute the command. (for example, the local administrator account.).
Launching the command prompt (cmd) even with an admin account does not necessarily mean that the command prompt has administrator privileges (especially under Windows 10)
You can use ele:
https://winaero.com/comment.php?comment.news.24
To ensure that wapt-get does not use the service, you can use:
Code: Select all
about to speak to waptservice...
waptservice User () :It therefore tries to pass a service account and thus requests an authorized username and password to execute the command. (for example, the local administrator account.).
Launching the command prompt (cmd) even with an admin account does not necessarily mean that the command prompt has administrator privileges (especially under Windows 10)
You can use ele:
https://winaero.com/comment.php?comment.news.24
To ensure that wapt-get does not use the service, you can use:
Code: Select all
wapt-get install blalbalba --direct