[RESOLVED] Deployment on workgroup workstations

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
Locked
florence_ufrsanté76
Messages: 2
Registration: February 1, 2024 - 5:40 PM

February 1, 2024 - 6:30 PM

Hello,
We would like to use our university's WAPT enterprise server to deploy operating systems and applications on workstations that will not be joined to the Active Directory domain.
Deploying Windows and WAPT packages installed via post-install script works.
I created a package that adds the variable `host_organizational_unit_dn=ourOutsideOU` to the global section of the `wapt-get.ini` file. This package does the job correctly, and a check of the `wapt-get.ini` file confirms this.
The problem is that the machine does not appear in the "inventory" tab of the console in the "ourOutsideOU" folder, except, ironically, if the machine is joined to the domain (which is not the objective).
We do not have control over the server configuration, and Kerberos authentication has been enabled on the server side... it seems that this is where the problem lies. What solutions can we consider?
Thank you in advance for your help!
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

February 2, 2024 - 11:12

You should try it, but it should normally work:

Add this to the post-installation scripts of the machines:

Code: Select all

C:\Program Files (x86)\wapt\wapt-get.exe register --not-interactive --wapt-server-user=register --wapt-server-passwd=password
Therefore, a user named "register" must be created in the console and given only the right to register machines.
florence_ufrsanté76
Messages: 2
Registration: February 1, 2024 - 5:40 PM

February 2, 2024 - 4:44 PM

Thank you so much for your reply, I will test it as soon as possible
Locked