Hello,
A PowerShell file "scripttest.ps1" creates two different text files:
- one with a path on the machine's local hard drive (C:\test\coucou.txt),
- the other with a path to a server share (\\server-ip\share\salut.txt).
1) When I open and run "scripttest.ps1" from the Ps1_To_Exe_(x64).exe interface, both text files are created.
2) When I create the scripttest.exe file from Ps1_To_Exe_(x64).exe and then run it, both text files are created
(Ps1_To_Exe_(x64) settings: 64-bit Exe-Format | Windows (invisible), UAC Requires User Privileges).
3) When I run scripttest.exe from the PyScripter interface ("make and edit" then "Run Configuration / install / Run"), both text files are created.
4) When I create the wapt package (Run Configuration / -i build-upload / Run) and assign it to a machine, the script runs, the local text file on C:\test is created, but the remote text file on \\server-ip\share is not created.
It would seem, therefore, that this is a problem of lost user privileges. How could I fix this, please?
Thank you in advance.
WAPT server 1.5.1.23 on Debian Stretch, option 1 in Post-configuration "registration without authentication (As in version 1.3)".
User privileges stored in Package
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello,
Wapt is running under the system account.
Why not store the ps1 file directly in the package?
It is generally strongly discouraged, from a security standpoint, to store a script outside the Wapt package. This completely breaks Wapt's security.
Wapt is running under the system account.
Why not store the ps1 file directly in the package?
It is generally strongly discouraged, from a security standpoint, to store a script outside the Wapt package. This completely breaks Wapt's security.
Thanks for the reply.
That's exactly what's been done: the .ps1 script is integrated, as an executable, into the wapt package.
Perhaps I could integrate the .ps1 file directly into the package (I'll try), but the initial question concerns its executable, which works all the time except when it's inside a package.
That's exactly what's been done: the .ps1 script is integrated, as an executable, into the wapt package.
Perhaps I could integrate the .ps1 file directly into the package (I'll try), but the initial question concerns its executable, which works all the time except when it's inside a package.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
The machine account most likely does not have access to your share.
To better understand, you can run your script with psexec using the -s option:
https://docs.microsoft.com/en-us/sysint ... ads/psexec.
This will allow you to observe the problem.
To better understand, you can run your script with psexec using the -s option:
https://docs.microsoft.com/en-us/sysint ... ads/psexec.
This will allow you to observe the problem.
