Alternating between primary and secondary customer deposits.
Published: February 11, 2026 - 08:13
Hello,
I'm going to reuse part of one of my posts to avoid rewriting everything.
I'm connecting to a corporate console on a remote primary repository (WAN) which is using HTTPS, which I'll call Principal01.fr.
Principal01.fr has the IP address 192.1.1.3.
A GPO on a Windows domain deployed the WAPT agent on the machines with the following settings in wapt-get.ini:
repo_url=//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 which 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 clients' IP addresses:
If the client belongs to the 192.168.1.0/24 network, then the repository used should be http://Secondaire02.fr/wapt
. I checked WAPT, WUA, and WADS and disabled fallback.
This is where things get complicated. Randomly, on my console (on Principal01.fr), when I go to the Inventory section and select a client from the 192.168.1.0/24 range, in the Repositories tab, I sometimes see the primary repository and sometimes the secondary repository. I can't find an explanation for why sometimes my clients stop connecting to the secondary repository.
Thank you for your help.
I'm going to reuse part of one of my posts to avoid rewriting everything.
I'm connecting to a corporate console on a remote primary repository (WAN) which is using HTTPS, which I'll call Principal01.fr.
Principal01.fr has the IP address 192.1.1.3.
A GPO on a Windows domain deployed the WAPT agent on the machines with the following settings in wapt-get.ini:
repo_url=//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 which 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 clients' IP addresses:
If the client belongs to the 192.168.1.0/24 network, then the repository used should be http://Secondaire02.fr/wapt
. I checked WAPT, WUA, and WADS and disabled fallback.
This is where things get complicated. Randomly, on my console (on Principal01.fr), when I go to the Inventory section and select a client from the 192.168.1.0/24 range, in the Repositories tab, I sometimes see the primary repository and sometimes the secondary repository. I can't find an explanation for why sometimes my clients stop connecting to the secondary repository.
Thank you for your help.