Hello,
what steps should be taken on the agent before running sysprep on Windows 10?
Thank you for your feedback.
Regards.
[SOLVED] WAPT agent with sysprep
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
- Stop the WAPT service: net stop waptservice
- Delete the file: C:\Program Files (x86)\wapt\db\waptdb.sqlite
- Delete the files and subfolders in C:\Program Files (x86)\wapt\private\
Code: Select all
net stop waptservice
del /f /q "C:\Program Files (x86)\wapt\db\waptdb.sqlite"
del /f /q "C:\Program Files (x86)\wapt\private\*"I was wondering if it wouldn't be better to just run `wapt-get reset-uuid` followed perhaps by `wapt-get register`.
Because if we delete the database, we delete the history of installed packages:
if we add dependencies back to the machine, it will download them and try to reinstall them unnecessarily.
But at the same time, with your method, if we modify packages afterward, we won't automatically push them to those machines, and that might be a good thing too.
Because if we delete the database, we delete the history of installed packages:
if we add dependencies back to the machine, it will download them and try to reinstall them unnecessarily.
But at the same time, with your method, if we modify packages afterward, we won't automatically push them to those machines, and that might be a good thing too.
