Tranquil IT Forum

Hello,

We are currently using a WAPT 1.3.12.13 server installed on a Windows 7 machine to manage our network.

We are in the process of deploying the latest WAPT version, 1.6.2.7, on a Windows Server 2016
(WAPT-01) server (server + repository for site 1)
and a second Windows Server 2016 server with WAPT 1.6.2.7 on site 2 to simply act as a repository
(WAPT-02).


We installed the WAPT-01 server and the agent on the machines at site 1, and there were no problems; the machines communicate with the server, and the packages install.

We installed WAPT-02 using the WAPT-01 key and created an agent for the machines at site 2 with the WAPT-01 server URL and the WAPT-02 repository URL.
We copied the repository folder from WAPT-01 to WAPT-02 (copy/paste for now, and we will use it later). (Syncthing then)

The workstations on site 2 register correctly on the WAPT-01 server and are visible on the console, but when a package is added to a workstation from the console, it is not installed on the client. However, a package update task is visible. On the other hand, installation directly from the workstation (http://127.0.0.1:8088/) works perfectly, and the installed package is visible on the WAPT-01 console.

I have searched the documentation and the forum but have not found an answer.

Thank you for your help.

Have you synchronized the host packages?
https://www.wapt.fr/fr/doc/wapt-concept ... t-packages

sfonteneau wrote: ↑January 22, 2019 - 9:42 AM Have you synchronized the host packages?
https://www.wapt.fr/fr/doc/wapt-concept ... t-packages

Thank you for the quick reply. I hadn't resynchronized the host package on WAPT-02 after adding a package on the WAPT-01 console; I thought it was using the one from WAPT-01

I'm running more tests and I'll keep you updated

THANKS

The package updates and installations are now working perfectly thanks to the synchronization of the "c:\wapt\waptserver\repository" folder with Syncthing.

Thanks again for the very quick response.