[RESOLVED] Inventory only displays the main repository: normal behavior?
Published: Dec 2, 2025 - 12:21
Hello,
I have a question I can't seem to find the answer to.
I'm connecting to a corporate console on a remote primary repository (WAN) that uses HTTPS, which I'll call Principal01.fr.
Principal01.fr has the IP address 192.1.1.3.
A Group Policy Object (GPO) on a Windows domain deployed the WAPT agent to the machines with the following settings in wapt-get.ini:
repo_url=https://Principal01.fr/wapt
wapt_server=https:/Principal01.fr.
I then set up a secondary repository (LAN) using HTTP, which I'll call Secondary02.fr, and it seems to be working correctly: it synchronizes properly with Principal01.fr.
Secondary02.fr has the IP address 192.168.1.3.
I added a rule based on the clients' IP addresses:
If the client belongs to the 192.168.1.00/24 network (I put "00" in the subnet mask because that's what the documentation I'm supposed to follow indicated), then the repository used should be:
http://Secondaire02.fr/wapt.
I checked WAPT, WUA, WADS, and disabled fallback.
However, on my console (on Principal01.fr), when I go to the Inventory section and select a client from the 192.168.1.00/24 range, in the Repositories tab, I only see the primary repository, and not the secondary one.
Package downloads from the clients seem very slow for a LAN deployment, and I suspect the clients are connecting directly to Principal01.fr.
My questions are therefore as follows:
Is it normal that, in the machine inventory, the displayed repository is Principal01.fr and not Secondaire02.fr (is this simply a reflection of the wapt-get.ini file)?
How can I verify that my clients are correctly retrieving packages from the secondary (LAN) repository?
Thank you in advance for your help.
I have a question I can't seem to find the answer to.
I'm connecting to a corporate console on a remote primary repository (WAN) that uses HTTPS, which I'll call Principal01.fr.
Principal01.fr has the IP address 192.1.1.3.
A Group Policy Object (GPO) on a Windows domain deployed the WAPT agent to the machines with the following settings in wapt-get.ini:
repo_url=https://Principal01.fr/wapt
wapt_server=https:/Principal01.fr.
I then set up a secondary repository (LAN) using HTTP, which I'll call Secondary02.fr, and it seems to be working correctly: it synchronizes properly with Principal01.fr.
Secondary02.fr has the IP address 192.168.1.3.
I added a rule based on the clients' IP addresses:
If the client belongs to the 192.168.1.00/24 network (I put "00" in the subnet mask because that's what the documentation I'm supposed to follow indicated), then the repository used should be:
http://Secondaire02.fr/wapt.
I checked WAPT, WUA, WADS, and disabled fallback.
However, on my console (on Principal01.fr), when I go to the Inventory section and select a client from the 192.168.1.00/24 range, in the Repositories tab, I only see the primary repository, and not the secondary one.
Package downloads from the clients seem very slow for a LAN deployment, and I suspect the clients are connecting directly to Principal01.fr.
My questions are therefore as follows:
Is it normal that, in the machine inventory, the displayed repository is Principal01.fr and not Secondaire02.fr (is this simply a reflection of the wapt-get.ini file)?
How can I verify that my clients are correctly retrieving packages from the secondary (LAN) repository?
Thank you in advance for your help.