Tranquil IT Forum

Hello,

After installing the Cygwin package with WAPT, I'm stuck on the following issue:

The first Cygwin package was installed from the console, and the successful installation occurred under the 'system' user.

My second configuration package contains the command: ssh-host-config and doesn't install correctly if I deploy it from the console. However, it installs normally if I launch the WAPT package installation from the PC via the command line, because the installation then occurs under the user account that is logged in.

Is there a way to force the deployment of a package from the console, with a user from the 'administrator' group present locally on the PC?

Regards,
Michel

You can try running the command (ssh-host-config) in the wapt session setup...

However, if your command requires an administrator account, then it won't work.

Another thing I haven't tried is modifying the waptservice properties ((services.msc)) to require it to start with the administrator account (see attached file).

In theory, I suppose that should work.

Yes, changing the account for the WAPTService to an administrator account solved everything and resolved many of my problems. Is there a way to deploy this service, which is integrated into the agentsetup.exe file, using an administrator account by default?

A possible answer can be found here:

https://blogs.msdn.microsoft.com/amanta ... edentials/

Please keep us updated on your findings!

Hello,

I'm the original poster.

I can confirm that by changing the execution account for the WAPT service from "System" to "Administrator," the "ssh-host-config" script that follows the Cygwin installation works perfectly.

I didn't change any other settings during execution. The problem was indeed due to the System account.

My question is: Why is the default user account for the service set to "System"?

I haven't noticed any side effects after making the changes.

Thank you for any replies.

Regards,
Michel

I'm not a Wapt developer, but from my point of view, it seems complicated.

Not everyone has an administrator account enabled, and sometimes the admin account name changes.

Silent deployment also seems complicated.
It would involve putting the local administrator password in waptagent.exe.

And since waptagent is public, it would be enough to retrieve it to get the local administrator password. (I think)
It's a major security issue.

So far, I've always managed to work around the problems of software that doesn't support the system account.

One method for you would be to install Wapt on a Windows image (template), change the service account to Wapt, and then redeploy (with Fog, for example).

If a developer happens to see this, they might have a more appropriate answer.

Simon

Hello,

After further consideration, I agree with those who suggested I continue using the System account.

The Administrator account does indeed require a password, and its name can vary from one PC to another.

Thank you for all these very constructive comments.

Regards,
Michel