Tranquil IT Forum

Hello,

I'm using Wapt Enterprise v1.8 on Windows Server 2016 (server) and Windows 10 (client).

I wanted to create a secondary repository on another Windows Server 2016 machine by assigning it the "remote-repo-ngninx" and "remote-repo-conf" packages (based on the documentation and your YouTube videos).
However, when I go to the "Repositories" tab, the synchronization status is "NO INDEX" with the following error: "You must first create the file index on the server."
What steps should I take?

Thank you for all the support you provide on this forum; it's great to get quick and efficient help.

Hello,

on the server, in the waptserver.ini file,

in the options section, you must add:
remote_repo_support = True.

Once this is done, you can restart the wapttasks and waptserver services (using services.msc).

You can then run "create file index" again; be aware that this will take some time the first time.

I've modified the waptserver configuration file in wapt/conf/ and restarted the services.

Now, in the Repositories tab, I have access to the "Sync selected", "Sync all", and "Update index" buttons. I've tried refreshing them all, but nothing happens...

Try restarting the remote agent's waptservice?

That didn't work, I restarted the services and machines but the problem remains...

Can your secondary repository see the primary repository (via the firewall)? Is a WebSocket connection established between the two? What status does your secondary repository show in the console?

Vincent

Can your secondary repository see the primary repository (firewall)?
--> Yes, I was able to install the remote-repo packages remotely on the secondary repository without any problems (and I also performed a test installation locally using wapt-get update/upgrade). Just to be sure, I removed the firewall from the server, but it didn't change anything, even after restarting the machines.

Is a WebSocket connection established between the two?
Yes, I was able to deploy packages to the secondary repository, and the inventory is correctly uploaded to the server.

What status does your secondary repository show in the console?
Status: OK, Reachable: OK (for inventory)
Sync status: NO SYNC, Connection status: OK (for repositories)

Hello

, could you please contact us directly by phone?

Simon

Hello,

Problem solved: the agent in the secondary repository was still in the Community version! Thank you, Mr. Fonteneau!

Procedure:
1) On the secondary repository, go to "Programs and Features" to check the WAPT agent version (which is indeed Community).

2) On the WAPT server, click on the secondary repository > "Edit Machine".

3) Add the "waptupgrade" package as a dependency (this package updates the WAPT agent based on the last agent you generated, so you must have generated the Enterprise version agent beforehand).

4) Run the package installation. This takes a few minutes.

5) On the secondary repository, go to "Programs and Features": the WAPT agent should now be upgraded to Enterprise.

6) On the WAPT server, go to "Repositories" and click "Sync all". Wait a few minutes.

7) That's it!