Vista - Can only execute gpg from powershell under MY account

I've built a powershell script that calls gpg and encrypts a file.
Basically, when I run the script in the powershell window, it runs and
encrypts the file. When I run it from Task Scheduler under ANY
ACCOUNT other than my own (even local admin), the encrypt doesn't
work. Unfortunately, gpg doesn't have a logging mechanism so I can't
see what it's actually doing and the Event log doesn't help either.
In the task manager, I don't see gpg.exe popping up in either case,
but maybe the task manager refresh is too slow? I do see "dwm.exe"
come up when run under my account and not an admin.
I checked all permissions using cacls and my account doesn't come up
anywhere on its own, so it doesn't appear to be an issue where just my
user has access to something.

What should I try next?

On Jan 23, 11:58*am, Blargh <kri...@xxxxxx> wrote:I should mention I'm running Windows 2008.

What you actually run in Task Scheduler and how (show us full command line
string)?

--
WBR, Vadims Podans
PowerShell blog - www.sysadmins.lv

"Blargh" <kripes@xxxxxx> rakstīja ziņojum�
"news:94455d73-0db4-476f-8c34-85e89c134d71@xxxxxx"...

On Jan 23, 1:49Â*pm, "Vadims Podans" <vpodans> wrote:Here is my code (with some maneuvering to anonymise it)



# Input: Required: mydir, which is the directory that the source files
are in. It is also used to determine
# the destination dir. Therefore, both must be identical. ie
"filedir\subdir" (without quotes!)

# Grab passed in variable
$mydir = $args[0]

$sourcedir = "c:\outbound\myproject\my\" + $mydir + "\*.*"
$filearray = get-item $sourcedir
if ($filearray.length -gt 0)
{
# mysys is the ID for the pgp key
$filearray | foreach-object { c:\dev\gpg\gpg.exe --encrypt --
recipient mysys $_ }
# Copy source files to archive folder
copy-item c:\outbound\myproject\my\$mydir\*.* -destination c:\outbound
\myproject\my\archive\$mydir
# Move encrypted files to ftp
move-item -path c:\outbound\myproject\my\$mydir\*.gpg -destination \
\serverftp\ftp$\1234\$mydir
# Remove all leftover files (for a clean run next time)
remove-item -path c:\outbound\myproject\my\$mydir\*.* -force

}
else
{"There are no files to process"}

On Jan 23, 1:49Â*pm, "Vadims Podans" <vpodans> wrote:Oh, and Task Scheduler runs "powershell" (no quotes) with an argument
of "c:\scripts\myscript.ps1" (with quotes)

I see $args[0] variable in script (where you pass a path to script). However
in call line you don't pass any data to script. Here should be something
like this:
C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe
"c:\scripts\myscript.ps1 data"

where Data - your data that will passed as $args[0].

--
WBR, Vadims Podans
PowerShell blog - www.sysadmins.lv

"Blargh" <kripes@xxxxxx> rakstīja ziņojum�
"news:0baaed59-69f9-4e1a-b66e-e44ea0ce57db@xxxxxx"...

On Jan 23, 5:15 pm, "Vadims Podans" <vpodans> wrote:I messed up. It's calling it with the argument: "c:\scripts
\myscript.ps1 parentdir\childdir"

I figured out the problem. gpg imports keys for use only on a per-
user basis. So I had to log on as the other user and re-import they
key.

In addition, some directories on the server were not accessible for
file deletion by my script under ANY account (even though they had
access in the security tab). So I changed the task to run under the
highest privileges.