Same WAPT command for two outputs

[LukaPibo]

Good morning,
I installed and configured WAPT at the beginning of this week; it's a very good piece of software that works very well, by the way. I just have one question:
during a

Code: Select all

 wapt-get register "nom du poste" 

Some positions require a login/password and others do not.
The workstations that ask me for a login/password do not send their description to the server, which is quite annoying because I use this description to sort my workstations in the administration console.

The workstation that does not request a workstation creates this line in the log file:

Code: Select all

 [pid: 4319|app: 0|req: 583/866] 127.0.0.1 () {44 vars in 620 bytes} [Tue Sep 12 14:51:55 2017] POST /add_host => generated 3013 bytes in 192 msecs (HTTP/1.1 200) 2 headers in 73 bytes (19 switches on core 0) 

And the computer that asks me for my login details returns these two lines in the log:

Code: Select all

 [pid: 4319|app: 0|req: 584/867] 127.0.0.1 () {38 vars in 505 bytes} [Tue Sep 12 14:52:57 2017] HEAD / => generated 0 bytes in 524 msecs (HTTP/1.1 200) 2 headers in 81 bytes (0 switches on core 0) 

Code: Select all

 [pid: 4319|app: 0|req: 585/868] 127.0.0.1 () {44 vars in 620 bytes} [Tue Sep 12 14:53:10 2017] POST /add_host => generated 3018 bytes in 195 msecs (HTTP/1.1 200) 2 headers in 73 bytes (18 switches on core 0) 

hoping you can shed some light on this for me

thanks in advance

Luka

[sfonteneau]

Good morning

https://www.wapt.fr/fr/doc/Utilisation/ ... e-commande

I quote:

By default, the command line will attempt to perform the requested actions using the account that launched the cmd.exe console.
If the user is not an administrator of the machine or if cmd was not launched with administrator privileges, WAPT will use the WAPT service.
For security reasons, some actions require a username and password.

Therefore, you can use "run as administrator" when you want to register.
The register with the service apparently does not take the argument for the description.

Another solution: edit the description manually (in the same place as the job name change).

[LukaPibo]

Thank you for your reply.

However, both commands were executed using two non-admin accounts, and then sent with administrator credentials via psexec.

You mentioned manually modifying the settings; I assume you're referring to the window that appears when double-clicking on a computer?
I modified the description field, but it doesn't update in the computer list.

Is there a file containing the computer information on the server itself that could be modified?

Thanks again,

Luka.

EDIT: I'm on a Debian server.

[htouvet]

The job description is not specific to Wapt but is the one recorded in the job's registry when it is modified using the standard Windows function (for example, right-click on Computer / Properties / Change settings / System properties).

Setting the description during registration is simply a shortcut for the Windows function.

And this shortcut only works if you are an administrator (so launch your command prompt as an administrator with elevated privileges).

The server only stores information that the jobs themselves have sent.

[LukaPibo]

Perfect!
I thought the configurations were stored in a file on the server,
but what I still don't understand is that my `wapt-get register` commands are sent under the same conditions to non-admin machines, but with the `psexec` utility and administrator credentials as parameters. Therefore, the commands are executed with administrator privileges on exactly identical machines.

Thank you very much,
Lucas.