RunAs ...

[caramen]

Func _PsExec1()
;~  local $iResult

    Run( @ComSpec & ' /c mkdir \\PC-Portable\c$\temptest', @SystemDir, @SW_SHOW )
        If @error <> 0 Then MsgBox(16, "Erreur", "Erreur: @error = " & @error & ", @extended: " & @extended)

    RunAsWait( "Caramen" , @ComputerName , "@jhgjfjhf" ,$RUN_LOGON_PROFILE , @ComSpec & '/k /c dircopy '&@ScriptDir&'\Data\Source1'&' \\PC-Portable\c$\temptest', @SystemDir, @SW_SHOW)
        If @error <> 0 Then MsgBox(16, "Erreur", "Erreur: @error = " & @error & ", @extended: " & @extended)

    RunAsWait( "Administrateur" , @ComputerName , "" ,$RUN_LOGON_PROFILE , @ComSpec & '/k /c PSEXEC \\PC-Portable -u Caramen -p XXXXXX "c:\temptest\test.txt"', @SystemDir, @SW_SHOW)
        If @error <> 0 Then MsgBox(16, "Erreur", "Erreur: @error = " & @error & ", @extended: " & @extended)

EndFunc

 

Hello,

 

Why the both commands RunAsWait doing this error please  ? I think I had the same problem before. I can't remember how we solved it. 

 

 

 

Edited October 9, 2020 by caramen

[caramen]

Oh wow... I discovered this can fail if I have no password set on the system account. 

A policy say : Don't allow empty password. 

And then if you use RunAs with empty password when this policy is (by default (Is that new WTF ?)) enable then RunAs will fail. <Good info for help file. 

Edit : Windows 10

Edited October 9, 2020 by caramen

[Subz]

You also have no space between @Comspec & '/k...', also is PsExec.exe been added to a searchable path?  From memory Windows has always required a password (for connecting to shares) otherwise it would be a major security risk.

Edited October 9, 2020 by Subz

[pixelsearch]

Hi caramen
I found a web site indicating thirteen different extended error values, related to RunAs and RunAsWait.
It includes your extended error value 1326 : "1326 (0x0000052e) ERROR_LOGON_FAILURE - The user name or password is incorrect."

Here is the link, in case it may help anyone in the future :
https://www.vanstechelman.eu/content/meaning-of-the-extended-flag-value-when-using-autoits-runas-and-runaswait

[caramen]

Yo @Subz yeah I forgot about that, it's now all corrected. but still same issue. 

Hi @pixelsearch yeah it return 1326 with policy enable and 1327 is the policy not enable but password isn't same as on target computer with the same account. 

So my way to correct was to change my password and add " " before "/k" to enable my test environment. And not to disable the policy because I don't have empty password anymore, but the same as my target computer with same account. 

It was Microsoft related so... 

Edited October 10, 2020 by caramen