[RESOLVED] Packets with Network Sharing Access

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
Locked
Yan
Messages: 4
Registration: January 24, 2024 - 3:23 PM

February 14, 2024 - 08:28

Hello :) ,
I need to retrieve configuration files as part of an .exe file installation.
Rather than placing the files in the WAPT package (to limit its size), I want to copy them to the client machine from a network share.
When I test the installation from the PC hosting the WAPT console, everything works. (Using PyScripter, WAPT:install)
When I distribute the package, I get a folder access error: Source directory not found.
The share access rights are correct because it works from the WAPT console server...
Is there some subtlety I'm missing? (Probably!)
Thank you for your help. :)
Yan
Messages: 4
Registration: January 24, 2024 - 3:23 PM

February 15, 2024 - 11:01

I found the solution.
The WAPT service runs under a local system account (NT_Authority\System) and may not have access to the network share specified in the WAPT package.
Simply adding the Everyone to the share fixes it.
The solution was actually quite simple... but not secure.
User avatar
dcardon
WAPT Expert
Messages: 1932
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

February 15, 2024 - 3:53 PM

Hi Yann,

indeed, the WAPT agent runs in LOCALSYSTEM and therefore uses the machine account to run. You can restrict access to network shares to only the machines (or a group of machines).
That said, we don't recommend this approach because a package should be self-contained. WAPT package installation often occurs when the machine is shut down, at a time when there may no longer be a network connection (e.g., a user working remotely with their VPN connection down once the session ends, a machine using wired or Wi-Fi 802.11x, etc.).
Furthermore, for traceability, it's easier to log package modifications to see who made the changes; on a remote share, this is a bit more difficult to manage.

If you have a large application with several different configurations, you can create one package for the application installation and several packages for the configurations.

Best 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
Locked