RunAsAdmin issue

[n0t0r10u5]

Hello Forum,

I'm new to using Autoit and your help will be very much appreciated.

I have written a script to install software automatically on to a PC where the user doesn't have admin rights, when testing the script with my account which does have admin rights the script works fine, the setup.exe is called and runs as the specified account. However, when run as a domain user without admin rights the script doesn't call the setup.exe and the msgbox is shown at the end.

The user's do have access to the network location and the secondary logon (RunAs) service is enabled.

The script is below, thanks in advance for your help

; Fill in the username and password appropriate for your system.
Local $sUserName = "username"
Local $sPassword = "password"
Local $sDomain = "DOMAIN"
Local $sLocation = "\\MYserver\setup.exe"

;Run program as another user
RunAsWait($sUserName, $sDomain, $sPassword, 0,($sLocation), @SystemDir,"","")


; Show a message.
MsgBox(0, "", "Completed.")

[mentor]

Hi,

I am having problems with this command as well but I am unable to run the command at all. I am using a variable to capture the output to see if the command has ran OK but it returns a zero every time. What am I doing wrong? Some help would be great. I am new to AutoIT.

$test = RunAsWait("user", "domain", "password", 0, "filepath", @TempDir,"","")

[mentor]

n0t0r10u5,

I found a solution to my problem here - http://www.autoitscript.com/forum/index.php?showtopic=118567&st=0&p=824933&hl=runaswait&fromsearch=1&#entry824933

I was using an MSI file which is why it wouldn't run. I had to add 'Msiexec.exe /I' before the path. This is my current working script -

; script to install Express metrix agent

$username = "administrator"

$domain = "domain"

$password = "password"

$program = 'Msiexec.exe /I "\\Server\path\install.msi" /qn'

;$test = RunAsWait ($username, $domain, $password, 2, $program, @TempDir)

RunAsWait($username, $domain, $password, 0, $program, @SystemDir," "," ")

Hope this helps.

Q

Hello Forum,

I'm new to using Autoit and your help will be very much appreciated.

I have written a script to install software automatically on to a PC where the user doesn't have admin rights, when testing the script with my account which does have admin rights the script works fine, the setup.exe is called and runs as the specified account. However, when run as a domain user without admin rights the script doesn't call the setup.exe and the msgbox is shown at the end.

The user's do have access to the network location and the secondary logon (RunAs) service is enabled.

The script is below, thanks in advance for your help

; Fill in the username and password appropriate for your system.
Local $sUserName = "username"
Local $sPassword = "password"
Local $sDomain = "DOMAIN"
Local $sLocation = "\\MYserver\setup.exe"

;Run program as another user
RunAsWait($sUserName, $sDomain, $sPassword, 0,($sLocation), @SystemDir,"","")


; Show a message.
MsgBox(0, "", "Completed.")

[n0t0r10u5]

Hi Mentor,

Thanks for the reply, however I'm using a setup.exe not a msi, I have tried your suggestion by converting the exe to a msi without any luck, I get an error when running the msi.

Thanks Again

[AdamUL]

Try DriveMapAdd to connect the network share before running the EXE. Your script updated.

; Fill in the username and password appropriate for your system. 
Local $sUserName = "username" 
Local $sPassword = "password" 
Local $sDomain = "DOMAIN" 
Local $sShare = "\\MYserver"
Local $sLocation = $sShare & "\setup.exe"  

;Connect to network share.
DriveMapAdd("", $sShare, 0, $sDomain & "\" & $sUsername, $sPassword)

;Run program as another user. 
RunAsWait($sUserName, $sDomain, $sPassword, 0, $sLocation, $sShare, "", "") 

; Show a message. 
MsgBox(0, "", "Completed.")

;Disconnect from the network share.
DriveMapDel($sShare)

Adam

Edit: Replaced @SystemDir with $sShare in the RunAsWait function.

Edited October 7, 2010 by AdamUL

[BrewManNH]

@ n0t0r10u5

Instead of using @SystemDir, which the user might not have write access to, you might want to try using @TempDir which they definitely will have write access to.

@AdamUL

The RunAs command sometimes has issues running programs on a mapped drive so that brings up another whole load of problems. I just discovered this yesterday about the RunAs command that I didn't realize before. Better to just point to the share location without mapping a drive to it.

[n0t0r10u5]

Thanks for all the help, I have now resolved the issue, I moved the folder containing the setup.exe to a top level share after reading in the forum that autoit sometimes doesn't like long UNC paths.

Thanks again.

[AdamUL]

@BrewManNH

When you had trouble using RunAs with DriveMapAdd, did you pass a drive letter or a blank string for the "device" parameter? Passing a blank string as quoted in the help file:

If you pass a blank string for this parameter a connection is made but not mapped to a specific drive.

If you look at the code I posted, that is what I did.

DriveMapAdd("", $sShare, 0, $sDomain & "\" & $sUsername, $sPassword)

It works the same as

RunWait('net use "' & $sShare & '" /USER:' & $sDomain & '\' & $sUserName & ' ' & $sPassword, @SystemDir, @SW_HIDE)

but with less typing. I have not had trouble with either solution, but prefer using DriveMapAdd with a blank string to connect to a network share.

Adam

[BrewManNH]

If you look HERE you will see that MS acknowledges that you might have problems running programs on a mapped drive under RunAs. If you look at the thread "Fun With Batch Files" you will see how not using a mapped drive fixed the OPs problem. Just thought I'd give a heads up regarding this because it's actually easier to not map the drive first and then have to delete it, especially if the script end prematurely and never gets to the deleting part.