Please helpwith runas over network

[hacksawbob]

Hopefully quite simple but I have been trawling the forum for at least the last hour. I am trying to run a batch file at logon as an admin by a non admin user.

RunAs(adminuser, @computername, XXXXPASS, 0, \\server\share\batch.bat, @SystemDir)

The batch file has can be viewed by all authenticated users

I get a syntax error whenever it comes accross the \\ in the UNC. I have tried mapping the drive but with no luck although I understand that UNC are supposed to work better than mapped drives. I am sure there is some "" quotes issue somewhere but I cant for the life of me work it out! Newb in need!

Edited January 12, 2010 by hacksawbob

[nfwu]

Hopefully quite simple but I have been trawling the forum for at least the last hour. I am trying to run a batch file at logon as an admin by a non admin user.

RunAs(adminuser, @computername, XXXXPASS, 0, \\server\share\batch.bat, @SystemDir)

The batch file has can be viewed by all authenticated users

I get a syntax error whenever it comes accross the \\ in the UNC. I have tried mapping the drive but with no luck although I understand that UNC are supposed to work better than mapped drives. I am sure there is some "" quotes issue somewhere but I cant for the life of me work it out! Newb in need!

RunAs("adminuser", @computername, "XXXXPASS", 0, "\\server\share\batch.bat", @SystemDir)

String literals, or string data in source code, needs quotes: "".

[hacksawbob]

Thanks for the quick reply heres the full code that I have pasted from the help file and modified, with the quotes in in it around the UNC I would expect to see a dos box pop up but i dont it doesn't complete the operation (a simple file copy for now)

; Fill in the username and password appropriate for your system.
Local $sUserName = "USERNAME"
Local $sPassword = "PASSWORD"

; Run a command prompt as the other user.
Local $pid = RunAsWait($sUserName, @ComputerName, $sPassword, 0, "\\server\share\batch.bat", @SystemDir)
; Wait for the process to close.
ProcessWaitClose($pid)

; Show a message.
MsgBox(0, "", "The process we were waiting for has closed.")

[nfwu]

I'm pretty sure you can't run a batch file directly but need a shell to do so, so here:

; Fill in the username and password appropriate for your system.
Local $sUserName = "USERNAME"
Local $sPassword = "PASSWORD"

; Run a command prompt as the other user.
Local $pid = RunAsWait($sUserName, @ComputerName, $sPassword, 0, @ComSpec & " /c " & "\\server\share\batch.bat", @SystemDir)
; Wait for the process to close.
ProcessWaitClose($pid)

; Show a message.
MsgBox(0, "", "The process we were waiting for has closed.")

EDIT: Typos

Edited January 12, 2010 by nfwu

[hacksawbob]

Brilliant thanks that seems to be working ok now!

[TigerKnee]

Hi all.  Would rather just raise this thread than to create another one.  Trying to run it through the network.  What is the proper command?  I tried:

#RequireAdmin
RunAsWait(John.Smith, FakeDomain, PaSsW0Rd, 0, @ComSpec & " /c " & "\\server\share\folderinshare\anotherfolder\install.cmd", @SystemDir)

And (desperate attempt...)

; Fill in the username and password appropriate for your system.
Local $sUserName = "John.Smith"
Local $sPassword = "PaSsW0Rd"

; Run a command prompt as the other user.
Local $pid = RunAsWait($sUserName, FakeDomain, $sPassword, 0, @ComSpec & " /c " & "\\server\share\folderinshare\anotherfolder\install.cmd", @SystemDir)
; Wait for the process to close.
ProcessWaitClose($pid)

; Show a message.
MsgBox(0, "", "The process we were waiting for has closed.")

To no avail.  Command prompt pops up and disappears.  What did I (obviously) do wrong?

Edited April 25, 2014 by TigerKnee

[BrewManNH]

First, remove the /c and replace it with /k so you can see any errors. Second, don't use RunAsWait if you're going to use ProcessWaitClose, the 2 are redundant. RunAsWait will pause the script until the process you start has closed, so the next line will never see the process. Also, RunAsWait returns an exit code not a PID, so your processwaitclose won't ever see the process anyways, because it's looking for a process PID that probably doesn't exist.

More than likely the issue is because of permissions, but without being able to see what's in the command console, you'll never know.

[TigerKnee]

First, remove the /c and replace it with /k so you can see any errors. Second, don't use RunAsWait if you're going to use ProcessWaitClose, the 2 are redundant. RunAsWait will pause the script until the process you start has closed, so the next line will never see the process. Also, RunAsWait returns an exit code not a PID, so your processwaitclose won't ever see the process anyways, because it's looking for a process PID that probably doesn't exist.

More than likely the issue is because of permissions, but without being able to see what's in the command console, you'll never know.

 

Here's my script

#RequireAdmin
RunAs("John.Smith", "FakeDomain", "PaSsW0Rd", 0, @ComSpec & " /k " & "c:\install\install.cmd", @SystemDir)

I got this error:

'C:InstallLync2013.cmd' is not recognized as an internal or external command,

operable program or batch file.

 

C:WindowsSysWOW64>

 

Tried @HomeDrive and got System32 instead of SysWOW64

 

Any ideas?

Edited April 25, 2014 by TigerKnee

[TigerKnee]

Anyone?  At whit's end here.  I put the /k and the script still disappears

[Gianni]

what happens with this?

#RequireAdmin

            _Wow64FsRedirection(False)
            RunAs("John.Smith", "FakeDomain", "PaSsW0Rd", 0, @ComSpec & " /k " & "c:\install\install.cmd", @SystemDir)
            _Wow64FsRedirection(True)

Func _Wow64FsRedirection($state)
    ; Disables or reverts the filesystem redirector for a 32 bit process running on 64bit OS
    If Not @AutoItX64 And @OSArch = 'X64' Then
        If $state Then
            DllCall("kernel32.dll", "int", "Wow64RevertWow64FsRedirection", "int", 0)
        Else
            DllCall("kernel32.dll", "int", "Wow64DisableWow64FsRedirection", "int", 0)
        EndIf
    EndIf
EndFunc

edit:

anyway
would you run a task on a remote machine??
I think you will not achieve that goal in >that way.

Edited April 25, 2014 by PincoPanco

[jguinch]

TigerKnee, in your script, you are running c:installinstall.cmd, and you say the error is about C:InstallLync2013.cmd.

So, is it a mistake, or Lync.cmd is launched from install.cmd ?

[TigerKnee]

TigerKnee, in your script, you are running c:installinstall.cmd, and you say the error is about C:InstallLync2013.cmd.

So, is it a mistake, or Lync.cmd is launched from install.cmd ?

 

No it was an error on my part.  I should've put a PAUSE in my script so I can see what I did wrong.  Thank you for your reply!