WAPT Version: 2.6.0.16937 - Enterprise Edition
Server OS: Debian 12
Target Machines: Windows
OS Administration Machine: Windows Server 2022
Hello,
we have just upgraded our WAPT version to 2.6.0.16937. It appears that the drivers we added to the WinPE of the previous version (2.6.0.16881) were not retained, which is quite problematic. Is this normal behavior?
Thank you.
[RESOLVED] WinPE: Driver not retained during WAPTServer version upgrade
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
-
bkolovljanovic
- Messages: 23
- Registration: Apr 20, 2022 - 2:26 p.m.
Hello,
Currently there isn't really a "lightweight" way to do this, since the drivers are injected into the WinPE using the DISM command, which is then sent to the server.
However, there's a little "extra" to make it a bit easier.
If you create a new driver bundle and name it "winpe" (as long as the bundle name contains "winpe"),
and then add drivers from the deployment section when creating the WinPE, it will automatically filter the available bundles containing the term "winpe".
Then, following the usual procedure, you confirm your selection, which will download the drivers locally for insertion with DISM when the WinPE is validated.
We'll look into this to see how we can further simplify and improve this part.
Currently there isn't really a "lightweight" way to do this, since the drivers are injected into the WinPE using the DISM command, which is then sent to the server.
However, there's a little "extra" to make it a bit easier.
If you create a new driver bundle and name it "winpe" (as long as the bundle name contains "winpe"),
and then add drivers from the deployment section when creating the WinPE, it will automatically filter the available bundles containing the term "winpe".
Then, following the usual procedure, you confirm your selection, which will download the drivers locally for insertion with DISM when the WinPE is validated.
We'll look into this to see how we can further simplify and improve this part.
Yes, we were using the "+" button, but it came at a bad time: we were upgrading our computer equipment (new PC, new model, new brand, which requires adding drivers to WinPE) and upgrading Wapt.
We just wanted to know if we had missed a step (like the ability to export WinPE, for example).
Thanks for the feedback
We just wanted to know if we had missed a step (like the ability to export WinPE, for example).
Thanks for the feedback
-
dcardon
- WAPT Expert
- Messages: 1929
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hi Cédric,
thanks for the feedback.
I'm closing this thread, and we'll look into how to simplify driver re-injection during upgrades internally.
Regards,
Denis
thanks for the feedback.
I'm closing this thread, and we'll look into how to simplify driver re-injection during upgrades internally.Regards,
Denis
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
