Good evening,
After updating the server from 1.5 to 1.6 and regenerating the agent, the WAPT clients are not updating to 1.6.
They remain on version 1.5 with the status "OK" and reachable as "DISCONNECTED".
How can the WAPT agent be updated automatically? (without using GPO because the PCs are remote)
Regards
WAPT agent that does not update after upgrading from 1.5 to 1.6
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
-
troublestarter
- Messages: 15
- Registration: September 5, 2018 - 10:30
- Location: Villeneuve d'Ascq
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Can you add
`allow_unauthenticated_connect = True`
conf/waptserver.ini` while the workstations are being migrated to version 1.6?
`allow_unauthenticated_connect = True`
conf/waptserver.ini` while the workstations are being migrated to version 1.6?
-
troublestarter
- Messages: 15
- Registration: September 5, 2018 - 10:30
- Location: Villeneuve d'Ascq
It seems to be working.
I need to understand where I went wrong. Is there a particular reason?
Should I change the value back to "False"?
Regards
I need to understand where I went wrong. Is there a particular reason?
Should I change the value back to "False"?
Regards
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
We simply didn't take the time in the 1.5 -> 1.6 upgrade documentation to note certain things:
https://www.wapt.fr/fr/doc/changelog.html#changes
https://www.wapt.fr/fr/doc/Configuratio ... tie-option
We changed the WebSocket authentication method. By default, they are not authenticated if `allow_unauthenticated_registration = True`.
When you are coming from version 1.5, if `allow_unauthenticated_registration = False`, then you must switch `allow_unauthenticated_connect = True` to use WebSockets.
Once all clients are updated, you can switch `allow_unauthenticated_connect = False` again.
https://www.wapt.fr/fr/doc/changelog.html#changes
https://www.wapt.fr/fr/doc/Configuratio ... tie-option
We changed the WebSocket authentication method. By default, they are not authenticated if `allow_unauthenticated_registration = True`.
When you are coming from version 1.5, if `allow_unauthenticated_registration = False`, then you must switch `allow_unauthenticated_connect = True` to use WebSockets.
Once all clients are updated, you can switch `allow_unauthenticated_connect = False` again.
