By the way, version wapt-2.2.1.11957-da81836d has been out for a while now. Don't hesitate to upgrade from time to time; there are plenty of bug fixes with each new version.
WAPT version 2.2.2 should be released next week, also with quite a few minor fixes (see https://www.wapt.fr/fr/doc/wapt-changel ... 2022-07-12 ).
Best regards,
Denis
[RESOLVED] Slow Waptagent deployment
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
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
I think I've found the source of the problem.
Our Scribe server is quite well-organized; I'm working hard to ensure everything runs smoothly and without any buggy rules or scripts.
We don't use Active Directory, but Samba3.
I haven't tested it on a machine outside the domain and without the Scribe client. I also thought that might be the issue, but it
turns out WPKG was causing a conflict. WPKG is our application deployer integrated into Scribe
, and I was running waptdeploy before uninstalling WPKG.
Simply reversing the process and uninstalling WPKG first is all it takes. Although WPKG is configured to launch when the PC starts up (and not when it shuts down like Wapt), it seems to be causing a problem with this GPO. In any case, it significantly lengthens the Waptagent installation.
The difference is striking: if WPKG is still present on the client machine, the Wapt agent takes 12 minutes to complete, compared to 2 minutes if WPKG is uninstalled beforehand!
Our Scribe server is quite well-organized; I'm working hard to ensure everything runs smoothly and without any buggy rules or scripts.
We don't use Active Directory, but Samba3.
I haven't tested it on a machine outside the domain and without the Scribe client. I also thought that might be the issue, but it
turns out WPKG was causing a conflict. WPKG is our application deployer integrated into Scribe
, and I was running waptdeploy before uninstalling WPKG.
Simply reversing the process and uninstalling WPKG first is all it takes. Although WPKG is configured to launch when the PC starts up (and not when it shuts down like Wapt), it seems to be causing a problem with this GPO. In any case, it significantly lengthens the Waptagent installation.
The difference is striking: if WPKG is still present on the client machine, the Wapt agent takes 12 minutes to complete, compared to 2 minutes if WPKG is uninstalled beforehand!
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Thanks for the feedback, glad it's finally resolved 
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
