Configuring wapt-get.ini for multiple repositories

[btravers]

Hello,

I just updated my server to version 1.5.1.21, along with the eight remote site repositories. Everything went smoothly. Syncthing is working. From the main site, I created the agent, which replicated and deployed correctly via GPO to the client machines. I'd like to take this opportunity to congratulate you on version 1.5.

As a result, in my console at the main site, I have all the machines from the eight sites; it's fantastic and works perfectly.
My machines at the eight remote sites are configured with the main site's repository, not the local one. The repository can be changed via the wapt-get.ini file on the machines using "repo_url=".

My question is:
Is it possible to have a "repo_url=" with the local address and a "wapt_server=" with the main site's address in the ini file? The goal is to manage the machines at the eight sites from the main site's console.

Thank you.

[dcardon]

Hello,

I just updated my server to 1.5.1.21 along with the 8 remote site repositories. Everything went smoothly. Syncthing is working. From the main site, I created the agent, which replicated and deployed correctly via GPO to the client machines. I'd like to take this opportunity to congratulate you on version 1.5.

So, in my console at the main site, I have all the machines from the 8 sites; it's great and works well.
My machines at the 8 remote sites are configured with the main site's repository, not the local one. The repository can be changed via the wapt-get.ini file on the machines with "repo_url=".

My question:
Is it possible to have a "repo_url=" with the local address and a "wapt_server=" with the main site's address in the ini file? The goal is to manage the workstations across all 8 sites from the main site's console.

Thank you.

Absolutely, the two parameters `wapt_server` and `repo_url` don't have to point to the same address. To set up remote repositories, you simply need to install Apache or Nginx and configure replication (using rsync, syncthing, etc.).

One side effect, however, is that when an update is applied directly to a machine from the console, the "machine" package may not yet be replicated to the remote site. We're considering adding a third parameter to tell the WAPT agent to point to the waptserver rather than the repo_url for machine packages.

To anticipate the next question, you can take a look at the following packages to modify the configuration of your machines on remote sites. These packages do not include a service restart after the configuration changes are applied. Therefore, they will take effect at the next startup
* https://store.wapt.fr/package_details?p ... 4_all.wapt
* https://store.wapt.fr/package_details?p ... 6_all.wapt

Sincerely,

Denis

[htouvet]

For machine packages, the parameter already exists, you just need to define a repository named 'wapt-host' whose URL repo_url is that of the main server / main repository.

https://github.com/tranquilit/WAPT/blob ... n.py#L2653

If a [wapt-host] section exists in the wapt-get.ini file, it is used for configuring the machine package repository instead of simply adding '-host' to the end of the main package repository URL.

https://github.com/tranquilit/WAPT/blob ... n.py#L2670

->

Code: Select all

[global]
repo_url=https://site1.mondomaine.lan/wapt
waptserver=https://mainrepo.mondomaine.lan

[wapt-host]
repo_url=https://mainrepo.mondomaine.lan/wapt-host

[btravers]

Okay, great, so if I make my little package like below, that's good? I don't understand what `waptwua_enabled a true` does.

Thank you for your quick response.


def install():

inifile_writestring(WAPT.config_filename,'global','repo_url',https://site1.mydomain.lan/wapt')
inifile_writestring(WAPT.config_filename,'global','wapt_server','https://mainrepo.mydomain.lan')
inifile_writestring(WAPT.config_filename,'wapt-host','repo_url','https://mainrepo.mydomain.lan/wapt-host')

inifile_writestring(WAPT.config_filename,'global','waptwua_enabled','true')


print('Modify max_gpo_script_wait')
inifile_writestring(WAPT.config_filename,'global','max_gpo_script_wait',180)

print('Modify Preshutdowntimeout')
inifile_writestring(WAPT.config_filename,'global','pre_shutdown_timeout',180)

print('Disable Hyberboot')
inifile_writestring(WAPT.config_filename,'global','hiberboot_enabled',0)

print('Disable Notify User')
inifile_writestring(WAPT.config_filename,'global','notify_user',0)

[dcardon]

Hello btravers,

Okay great, so if I make my little package like below, it's good? I don't understand what `waptwua_enabled a true` is for.

This is to enable support for Windows updates through the WAPT agent, basically a WSUS integrated into WAPT; it's a feature we're preparing for the WAPT Enterprise version.

Sincerely,

Denis

[btravers]

Hello,
I suspected as much, but I wasn't certain. I think this feature will lead me to upgrade to the enterprise version.

Thank you.

[Patrice69]

Hello,

I updated my server to version 1.5.1.21 along with my three remote site repositories. Synchronization via Rsync works.
Everything seems to be working correctly except for the remote repositories.

The agent was deployed to all machines via a login script.

I then manually modified some remote site machines to use the local site repository configuration instead of the main site repository, based on the

wapt-get.ini file: adapting it to the local context:
[global]
repo_url=https://site1.mydomain.lan/wapt
waptserver=https://mainrepo.mydomain.lan

[wapt-host]
repo_url=https://mainrepo.mydomain.lan/wapt-host

When I assign a package to a remote machine via the console, it considers its configuration to be up-to-date. The same happens when I force a manual synchronization of the repositories, and also when I restart the remote machine.

What step do you think I missed?

Thank you in advance for your ideas...

Best regards,

[vcardon]

Hello,
I suspected as much, but wasn't certain. I think this feature will make me upgrade to the enterprise version.

Thank you.

And there will be plenty of other things in the Enterprise version:

- Simplified management of remote repositories => under development
- Simplified multi-repository management => under development
- Strong integration with Active Directory (MS or Samba) => this already exists
- Management reporting => under development
- Simplified management of role separation => this already exists

1.5 is a very beautiful princess, already perfectly refined, of noble lineage, cultured, and of great dignity. She just needs a quick visit to the hairdresser and tailor, and she'll be 100% ready to reach out to her most demanding princes for their first waltzes

A++

Vincent

[btravers]

Hello,

do you have a public roadmap? The resumption of WSUS functionality and the connection with GLPI are two things we're eagerly awaiting. If you had a date, it would help me plan accordingly.

Thank you