
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-27-2017 11:00 AM
Hi,
we have a simple powershell script for testing, which is not working.
Here is the script:
Write-Output "TEST" >> \\ngde-invent\logs$\Printers.txt
And the deployment package has just this command:
powershell.exe -executionpolicy bypass -file "{PackageShare}\Scripts\test.ps1"
The deployment runs successfully, but I see no file. I changed the location of the script and the output, but without success.
we have a simple powershell script for testing, which is not working.
Here is the script:
Write-Output "TEST" >> \\ngde-invent\logs$\Printers.txt
And the deployment package has just this command:
powershell.exe -executionpolicy bypass -file "{PackageShare}\Scripts\test.ps1"
The deployment runs successfully, but I see no file. I changed the location of the script and the output, but without success.
Labels:
- Labels:
-
Custom Actions
2 REPLIES 2

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎06-19-2017 09:06 PM
Did you check the security permissions to confirm the user has write ability to the share you are trying to write to?

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-27-2017 01:13 PM
Hi,
it’s working with an additional parameter:
powershell.exe -noprofile -executionpolicy bypass -file "{PackageShare}\Scripts\test.ps1"
and running as Currently Logged On.
Is there a possibility to run with Scanning Credentials?
it’s working with an additional parameter:
powershell.exe -noprofile -executionpolicy bypass -file "{PackageShare}\Scripts\test.ps1"
and running as Currently Logged On.
Is there a possibility to run with Scanning Credentials?
