Page 1 of 1

Windows 10 Agent Installation

Published: January 23, 2018 - 10:13 AM
by hasop
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.

Re: Windows 10 agent installation

Published: January 23, 2018 - 12:00 PM
by sfonteneau
The window:

Code: Select all

about to speak to waptservice...
waptservice User () :
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

wapt-get install blalbalba   --direct

Re: Windows 10 agent installation

Published: January 23, 2018 - 1:58 PM
by hasop
Actually, disabling UAC fixed it.

Thanks for your help.