Tranquil IT Forum

Hello,

I currently have several secondary repositories in my IT infrastructure, configured to assign repository URLs to each of my client machines.
I've recently noticed that some of my client machines can take a few days (or even weeks!) to retrieve the correct repository URL. I've tried searching the documentation for a way to force a repository change on the clients or to get logs to better understand the source of the problem, but I haven't found anything.

Do you have a solution or the path to the logs that could help me find this?

WAPT version 2.5.5.15697.
The repositories are on Debian and the clients are on Windows 10/11.

Thank you !

Good morning,
It is during the update (checking for updates) that the agent must detect the deposit according to the established rules.
You can launch as an administrator on a problematic agent and analyze the logs.

Good day,
Bertrand

Hello,


that's fantastic, it's exactly what I needed!

Thank you very much.