Okay, so... I'm lost. Let me start from the beginning:

I don't have a certificate in C:\Program Files (x86)\wapt\ssl\server.
It's in C:\Program Files (x86)\wapt\ssl\.

Indeed, it doesn't match /opt/wapt/waptserver/ssl/cert.pem.

What I don't understand is that on a machine that...

Here is the result of wapt-get testperf:

Server: https://srvwapt.my.domain
Authentication required for server:
Server CABundle: C:\Program Files (x86)\wapt\ssl\server\srvwapt.my.domain.crt
Server client certificate:
Server client key:

Waptserver https://srvwapt.my.domain Admin User: admin ...

Hello,

I just upgraded my server to version 2.6.1.17576.
I have a workstation that isn't showing up in the console despite installing the new agent.

The installation is OK and the `wapt-get register` command is successful:

`wapt-get register` output:

Agent registration with server in queue...`

Hello,

I just upgraded my server to version 2.6.1.17576.
One workstation isn't reporting despite installing the new agent.

I've tried:
- uninstalling the agent and deleting its files
- deleting the workstation (and removing it from the database) in the console
- installing the new agent...

Not the very latest one, I think; I'm on version 2.6.0.16552

Good morning,

Thank you for your response.

Yes, I had seen that, but I can't find the option when I create a configuration package: Am I required to deploy a manual modification to wapt-get.ini?

Hello,

I need my users to install updates manually, so I need to disable automatic package installation when their PCs shut down.

How can I properly disable this feature?

Thank you in advance.

Hello and thank you for your reply

. The problem is now resolved.
I was missing `use_repo_rules=1` in the agent configuration.

This topic can be closed.

Finally, I managed to get the repositories to synchronize 100% by forcing this value in the repositories' wapt-get.ini file (not to mention wusa):
remote_repo_dirs=wapt.

Last step: I created my rules based on the agents' IP addresses, but the workstations are still...

Hello,

this happens when you disable WADs on the WAPT server and enable WADs synchronization on the secondary repository.

It tries to download the WADs files but gets a 404 error because the server returns a 404 if WADs is not enabled.

The simplest solution in your case is to enable...