RunAsCurrentUser and Win7?

(imported topic written by deschodt91)

Is this supported for Win7 ?

I’m trying to run a reg file to modify a key in HKEY_Current_user to set a value we need set when users login.

By hand, no problem, it takes everytime. With BigFix, the action “completes” but does nothing…

I suspect a Win7 rights issue, so since it works by hand, tried runascurrentuser… That one also does nothing, no matter how I try to run it… --w, local, from __Download, nothing…

I’m just running a waithidden on runascurrentuser.exe for regedit.exe /S “path of my reg file” (tried 10 kinds of syntax and scripts, nothing doing)

Any ideas if I’m going at this the wrong way ???

(imported comment written by SystemAdmin)

Since you are using Runascurrentuser, does the logged on user have appropriate permissions to edit the registry?

Do you have UAC enabled? Does it work if disabled?

Finally, does it work if you set the BESclient to interactive? (Default changed to non-interactive in v8.x)

waithidden cmd /C sc config besclient type= own type= interact

(imported comment written by MattBoyd)

http://forum.bigfix.com/viewtopic.php?pid=24363#p24363

(imported comment written by tgladden91)

I am trying to us runascurrentuser to execute a VB script that will move the computer account from one OU to a different OU. The Fixlet/action script will execute in Windows XP but does not execute in Windows 7 (32 or 64 bit). I do two things in the action:

waithidden RunAsCurrentUser.exe --w --q cmd.exe /c cscript c:\windows\MoveToOU-test.vbs

move “c:\windows\MoveToOU-test.vbs” “c:\windows\MoveToOU-test.vbs.old”

Both the VB script and the runascurrentuser EXE are already on the system in the c:\windows folder. The first line of is not doing anything. The second line does execute and copied the vb script to .old What am I missing??

(imported comment written by BenKus)

What happens when you run

RunAsCurrentUser.exe --w --q cmd.exe /c cscript c:\windows\MoveToOU-test.vbs

from the commandline?

Ben

I have a .exe that added file to a user’s profile which has
script in the .exe to ido InstallPath=“c:\users%username%” .
In tem I have to run this as a current user and I am using the following
command to run the file that was already added to a fixed location on the user
computer.

prefetch
RunAsCurrentUser.exe sha1:ee47505ebfb2790b9da8a20ed70e67158e9753d0 size:342528 http://software.bigfix.com/download/bes/util/RunAsCurrentUser-2.0.3.1.exe

waithidden __Download\runascurrentuser.exe --w cmd.exe /c
"C:\office15\icons.exe"

The issues I am having is that UAC comes in to play and stop the
.exe from running. If I raise the level to admin then the wild card command
inside the exe install the file under the computer admin computer name. (i.e.
if the computer is called justice and user is eddiet instead of adding the
files to eddiet it creates a file called Justice$) is there a way of by passing
the UAC command in windows through tem or is there a better relevance I could
be using.

RunAsCurrentUser runs with the rights of the current user. You could try to disable UAC before and reenable it after, but if the user does not have sufficient rights to run it, then it still will not work. This isn’t recommended but the only option would be to temporarily make the user an Admin.

What is it that this EXE is doing? It is possible that you could do it using actionscript without needed to run the EXE at all.