I've been looking at some threads, one where the introduction of runnas.exe was discussed through several pages.

Also I've read runnas with parameters

The last one is doing exactely what I want to do:

implement the /quiet switch into the runnas execution.

I've tried every possibility (I think) I first thought that ver 1.14 of runnas.exe was an old one, but it seems this is the last?

The syntax in the script is as follows:
-----------
$winpath = "c:\delnvc.exe /quiet"
$user = "/user:jen"
$pass = "/pass:xxxx"
$runaspath = "c:\runnas.exe" +' $user' + '" $winpath"' + ' $pass'

Shell $runaspath
----------
The syntax seems to work, no errors, but the delnvc /quiet doesn't appear as a process in the overview, and doesn't run.

If I run the command directly from the cmd, the process appear in the process-overview.

I've tried with and without the /quiet- bit in $winpath, instead using it in the $runpath (as suggested as a solution in the thread mentioned above), like this:
----------
$winpath = "c:\delnvc.exe"
$runaspath = "c:\runnas.exe" +' $user' + '" $winpath /quiet"' + ' $pass'
----------
But the same problem

If I run the runnas directly from cmd like this:
--
runnas.exe /user:jen "c:\delnvc.exe /quiet" /pass:xxxx
same thing happens: No errors, but the process doesn't start
--

If I remove the /quiet in that last sentence: like this:
--
runnas.exe /user:jen-265-6910P\jen "c:\delnvc5_1.exe" /pass:xxx
--
then everything works as intended. But since it doesn't run in the backgroud, it isn't working like I want.

What am I doing wrong, anybody??
Or isn't it possible to make the script do what I want?????

Regards Jon
_________________________
I was placed on earth to do a job. Right now I have so much to do, I will never die..