Tranquil IT Forum

Hello,

we regularly install/reinstall client workstations.
When the WAPT agent has already been deployed, there's no problem; the workstation automatically installs the required software because it's present in the console.
But when it's a new workstation, we automatically install the OS and the WAPT agent. Is there a way to provision the workstation in the console to assign it packages upon installation and avoid waiting for manual addition?

Thank you for your help!

Hello,

in the enterprise version you can use profile or unit (OU) packages.

Are you using the enterprise version?

sfonteneau wrote: ↑August 17, 2020 - 4:32 PM Hello,

In the enterprise version, you can use profile or unit (OU) packages.

Are you using the enterprise version?

No, we are on the community version.
In the enterprise version, we therefore create a machine group to which we apply one or more package groups?
This allows, I imagine, during installation, whether the machine is new or not, to install all the packages in this group.
Is it also possible to add a machine manually in the enterprise version?

Hello Geovariances,

I am replying as I am using the enterprise version; all the features of the community version are present in the enterprise version, there is just an addition of functionality.

jonathan.k wrote: ↑August 24, 2020 - 09:58 Hello Geovariances,

I am replying as I am using the enterprise version, all the features of the community version are present in the enterprise version, there is just added functionality.

Good morning,

Is it possible to manually add a workstation via the console (before its installation, for example)? Or does the workstation need to be installed with the agent to be visible in the console?

The update necessarily involves the installation of the agent.

In its current state, WAPT relies by default on the BIOS UUID to identify a machine, which the server cannot know a priori. Furthermore, during registration, the workstation creates a CSR (Certificate Signing Request) to obtain a client certificate, something the server cannot do on its own.

This is a much more secure approach than what is found on other systems, but it also comes with its limitations, even if it is generally quite transparent. If you use the machine name as the identifier (a parameter to add when creating the agent), it is possible to have a pre-created machine, but there is currently no function in the console for this; it must be done using the Python API.

The usual operating method for users on the Enterprise version is to define OU packages (which are applied according to the machine's position in Active Directory), and once the machine is joined and correctly positioned, the packages are assigned directly.

Profile packages (AD group) are also frequently used. (enterprise)

dcardon wrote: ↑August 25, 2020 - 8:54 AM As it stands, WAPT uses the BIOS UUID by default to identify a machine, which the server cannot know a priori. Furthermore, during registration, the workstation creates a CSR (Certificate Signing Request) to obtain a client certificate, which the server cannot do on its own.

This is a much more secure way of working than what is found on other systems, but it also comes with its limitations, even if it is generally quite transparent. If you use the machine name as the identifier (a parameter to add when creating the agent), it is possible to have a pre-created machine, but there is currently no function in the console for this; it must be done using the Python API.

The usual way of working for people in the Enterprise version is to define OU packages (which apply depending on the positioning of the machine in the AD) and once the machine is joined and correctly positioned, the packages are assigned directly.

Good morning,

Thank you for your clarification.
We use the addition via the machine name and not the UUID.
We are currently developing/testing the addition of a machine via the Python API.
Currently, in the community version, we manage our "groups" via package groups. The enterprise version allows management directly in Active Directory.