[SOLVED] Problem editing remote packets on workstations

[x-davidl]

Hello,

WAPT Enterprise version 2.40.0.14031

and I've been having a problem for a few days. When I edit a remote package on a workstation, for example, to add only one piece of software to that workstation, everything seems to go smoothly (I edit, then select my package, then click "Add dependencies to package," then "Save," then "Apply," and then receive a confirmation message that the action has started).

However, in the "Current task" window, the number displayed on the "Updating list of available packages" line hasn't changed.
As a result, the workstation doesn't "see" any changes and remains in "OK" status.

This occurs on a remote site,

but the global policies at the Organizational Unit (OU) level are being applied correctly. For example, an Edge update was successfully applied to my remote site. There are no issues with secondary repository rules (the remote workstations successfully downloaded Edge from the remote repository).

This only happens with packages specific to the remote workstations.

Best regards

[x-davidl]

Hello,

I think I've found the reason why...
in my remote repositories, the wapt-host directories are empty.
In my rules, the Host box was checked, so when I modified the individual packages on the remote machines, wapt would look for the configuration files in wapt-host, which were unfortunately empty.

So, in the rules, I unchecked the Host boxes so that wapt would look for the configurations on the central server.

What's strange is that this worked until now... (I must have accidentally set 'no fallback' to true...

Regards,

[dcardon]

Hi David,

thanks for your feedback!

Indeed, for machine packages, it's best not to sync with remote repositories and to tell workstations to connect directly to the central server because machine packages are very lightweight, and this allows for better responsiveness when making configuration changes.

Best regards,

Denis