Windows 8 - RunAs

[furian]

I am trying to do a quick runas script to start various programs with an admin account (not run as administrator though). For some reason i am unable to get the program to start. My password prompt seems to work, but after entering, it just goes away, and nothing starts. The script is very simple... what am I missing?

$sa_user = "username_sa"
$sa_pass = InputBox ("Password", "Please enter your SA password", "", "*")
$user_domain = "domainname"
$app = "C:\Program Files (x86)\Citrix\Citrix Delivery Services Console\Framework\CmiLaunch.exe"

RunAs ( $sa_user, $user_domain, $sa_pass, 1, $app)

[water]

What is the return value of RunAs?

Could you specify a working directory and try again? According to the help file: "It is important to specify a working directory the user you are running as has access to, otherwise the function will fail."

[guinness]

Did you also try on Windows 7 or another OS?

[furian]

I changed it slightly, but same results.

This works:

Local $sUserName = "username"
Local $sDomainName = "domain"
Local $sPassword = InputBox ("Password", "Please enter your SA password", "", "*")
Local $sApp = "notepad.exe"
Local $sWorkingDir = "c:usersusername"
RunAs ($sUserName, $sDomainName, $sPassword, 0, $sApp, $sWorkingDir, @SW_SHOWMAXIMIZED)

This does not:

Local $sUserName = "username"
Local $sDomainName = "domain"
Local $sPassword = InputBox ("Password", "Please enter your SA password", "", "*")
Local $sApp = "cmilaunch.exe"
Local $sWorkingDir = "c:usersusername"
RunAs ($sUserName, $sDomainName, $sPassword, 0, $sApp, $sWorkingDir, @SW_SHOWMAXIMIZED)

cmilaunch.exe is a valid executable and its path is in my global path variable. I tested by clicking start run, and it executes.

I have to be missing something very simple here! I'm not sure how to check output of runas, my scripts tend to be very simple, so i don't get that deep into the code.

I tried on both Win 8 and 7 and same results

Edited November 26, 2012 by furian

[BrewManNH]

Try using the full path to the exe as well as it's file name. I can run Word from the Run box but I can't run it from a script without the full path in front of the "Winword.exe"/

[furian]

Try using the full path to the exe as well as it's file name. I can run Word from the Run box but I can't run it from a script without the full path in front of the "Winword.exe"/

still doesn't work.

Local $sUserName = "username"
Local $sDomainName = "domain"
Local $sPassword = InputBox ("Password", "Please enter your SA password", "", "*")
Local $sApp = "C:Program Files (x86)CitrixCitrix Delivery Services ConsoleFrameworkCmiLaunch.exe"
Local $sWorkingDir = "c:usersusername"
RunAs ($sUserName, $sDomainName, $sPassword, 0, $sApp, $sWorkingDir, @SW_SHOWMAXIMIZED)

I also tried various other executables, such as mmc.exe, and "mmc.exe test.msc" files, with and without paths. i can't get those to work either. Seems only notepad works!

Edited November 26, 2012 by furian

[jazzyjeff]

Try changing this variable to this:

Local $sApp = '"C:Program Files (x86)CitrixCitrix Delivery Services ConsoleFrameworkCmiLaunch.exe"'

Surround the string with this ' '. The string also needs to contain " ", because you have spacesin your path.

Edited November 26, 2012 by jazzyjeff

[furian]

Try changing this variable to this:

Local $sApp = '"C:Program Files (x86)CitrixCitrix Delivery Services ConsoleFrameworkCmiLaunch.exe"'

Surround the string with this ' '. The string also needs to contain " ", because you have spacesin your path.

Doesn't work!

I tried this as well:

Local $sUserName = "username"
Local $sDomainName = "domain"
Local $sPassword = InputBox ("Password", "Please enter your SA password", "", "*")
Local $sApp = "C:Progra~2CitrixCitrix~1Framew~1CmiLaunch.exe"
Local $sWorkingDir = "c:usersusername"
RunAs ($sUserName, $sDomainName, $sPassword, 1, $sApp, $sWorkingDir, @SW_SHOWMAXIMIZED)

I have a work around - I just put the path in the cmd file and it will launch this way.... i really need to start saving my scripts for future reference. I have fought this before.

Local $sUserName = "username"
Local $sDomainName = "domain"
Local $sPassword = InputBox ("Password", "Please enter your SA password", "", "*")
Local $sApp = "C:AdminStartscitrixconsole.cmd"
Local $sWorkingDir = "c:usersusername"
RunAs ($sUserName, $sDomainName, $sPassword, 1, $sApp, $sWorkingDir, @SW_SHOWMAXIMIZED)

Edited November 26, 2012 by furian

[BrewManNH]

is there anything showing when it doesn't work? Is there an error message or does it just end?

I don't have Windows 8 to test it so I can't really help much if it's a Windows 8 problem only, does it work on Win7 or Vista?

[JohnOne]

If the user you are running as is not administrator "(not run as administrator though)" then that could course problems.

[rudi]

@Furian, Reply #6:

Start, run does *NOT* check, if the program will run, because it's included in the %path% statement (user or system).

Try this:

Start, Run, notepad, OK -> will execute

start, Run, scite, OK -> will execute

Open a CMD.EXE box, working dir = "C:", then...

Type notepad <enter> -> will execute (in path, usually @windir or @systemdir)

Type scite <enter> -> it will *NOT* execute

type start scite <enter> -> it *WILL* execute, amazing at the first glance, isn't it?

The important information for the "Start" functionality is stored here:

[HKEY_LOCAL_MACHINESOFTWAREMicrosoftWindowsCurrentVersionApp Paths]

There you will find an entry for many executables (including SciTE.exe, when "setup installed"). These keys/vals do the trick, that the named executables *WILL* run from start, run, ... , but *ONLY* from start, run (or "CMD-BOX", "start programname <enter>"), and not from any random "working directory" (implying the EXE's path is not included in the %path% statement)

Regards, Rudi.

<edit: grammar, typo>

Edited November 27, 2012 by rudi

[furian]

No errors... just doesn't start. I am running as an administrator. It doesn't work on Windows 7 either. I tried adding it to the App Paths and it doesn't work afterwards.

This is in 64bit key as well

[HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftWindowsCurrentVersionApp PathsCmilaunch.exe]
@="C:Program Files (x86)CitrixCitrix Delivery Services ConsoleFrameworkcmilaunch.exe"
"Path"="C:Program Files (x86)CitrixCitrix Delivery Services ConsoleFramework"

cmilaunch.exe runs from the start>run menu, as well as from a command line (I added path to global path variable).

While i can get around this, it would be nice to know what is going on. I'm curious as to why notepad.exe works, and mspaint.exe works as well (with no paths), but mmc.exe does not.

Edited November 27, 2012 by furian

[jazzyjeff]

So just to verify, at the start of your script you using the code #RequireAdmin ?

[Jon]

notepad.exe/mspaint.exe is manifested as "AsInvoker" so you can run them from any level of user. The other programs are probably "RequireAdministrator" or "HighestAvailable". Basically if the program brings up a UAC prompt, you can't start it directly from RunAs.

[furian]

I did not have #RequireAdmin in the front of script. I added, with the same results. UAC is off.

On a whim, i changed the login flag to 0 and got the same result. However, it WORKS when using 2 as the login flag AND #RequireAdmin.

I had picked 1 because I thought I needed a profile. The tool I am using has some discovery options and I need those settings to be retained the next time I launch it. Using 2 appears to retain those settings, so it looks like this resolved.

Final working script:

#RequireAdmin

Local $sUserName = "username"
Local $sDomainName = "domain"
Local $sPassword = InputBox ("Password", "Please enter your SA password", "", "*")
Local $sApp = "C:Progra~2CitrixCitrix~1Framew~1CmiLaunch.exe"
Local $sWorkingDir = "c:usersusername"
RunAs ($sUserName, $sDomainName, $sPassword, 2, $sApp, $sWorkingDir, @SW_SHOWMAXIMIZED)

Edited November 27, 2012 by furian