Not administrator use RunAsCurrentUser. Exe installed msi failure

Usage and Config Platform
1

I come from China, for the first time to come here。

I met some problems when using 9.2.5 version，Windows Software Distribution Wizard Installed msi,

prefetch RunAsCurrentUser.exe sha1:ee47505ebfb2790b9da8a20ed70e67158e9753d0 size:342528 
http://software.bigfix.com/download/bes/util/RunAsCurrentUser-2.0.3.1.exe
sha256:1a9b518c775e2a85a7c47801e9b8221df338a65ad8df326485e4cd2aea22fe52  
utility __Download\RunAsCurrentUser.exe 

waithidden __Download\RunAsCurrentUser.exe --w --q cmd.exe /c  "{pathname of system folder & "\msiexec.exe"}" /i __Download\7z.msi /qn /norestart

If the current user terminal is “administrator”， then all OK, successfully installed
If the current logged in user is “Davy,” belong to the administrators group, log, console information is done tips, without any abnormal situation, but not installed

This is probably the reason why？

Thanks
(My English is not very good, sorry)

======================================================================
update：
Find a new situation

   waithidden __Download\RunAsCurrentUser.exe --w --q cmd.exe /c  "{pathname of system folder & "\msiexec.exe"}" /i __Download\7z.msi /qn /norestart
In the user Davy environment If you remove the" /qn /norestart",

 waithidden __Download\RunAsCurrentUser.exe --w --q cmd.exe /c  "{pathname of system folder & "\msiexec.exe"}" /i __Download\7z.msi
 So can appear installation interface for users to install, just can't silent installation ，Parameter(/qn /norestart) is no problem, because the use of the system permissions to install can be silent installation,

So the question now is focused on the Not administrator && /qn/norestart ？

2

I don’t understand why you are running this as the current user at all. In general, if you can install it as the system account, then you should.

You should just install it like this:

waithidden msiexec /i __Download\7z.msi /qn /norestart
3

We tested, some software to use the system account to install a failure, must use the current user to install, I think the system account and the current user would not be in a session, when some software installation involves some user information

waithidden msiexec /i __Download\7z.msi /qn /norestart

Can satisfy most of the software installed, but for us to specify the software will be failed ,

4

As far as I know, 7zip installs without issue through BigFix using the System account.

Which version of 7zip are you installing?

5

7 zip is I used to test the software,
Have test before using the system installation failure, but I through
the above methods in administrator cases was successful, but the other
users of the current user to the administrators group failed, screening
and appeared to be “/ qn/norestart parameters,” but I’m not sure

6

Thank you for your reply

Real distribution of software within a local area network (LAN), I also take not to come out, but I can confirm that sytem installation will fail, and through the administrator use RunAsCurrentUser. Exe installation was successful, and is silent installation,

Now the question in the administrators group users (not administrator) becomes no reaction, can only be installed, removed/qn/norestart but so there is a user manual installation.

7

I’m having trouble understanding what your saying.

What version of 7zip are you trying to install?

Can you provide a link to the file on the vendor site?

I know for certain that 7zip 9.20 can be installed without running as current user, and the newer version should be able to as well, which makes me think something else is the cause.

8

Sorry for my description。
Becausethe specified software there is no way out, I think if 7 z can also be spread by RunAsCurrentUser installation is successful, then other software should also can, here only to verify RunAsCurrentUser. exe, and 7z is just a random msi packages

9

Yes, that is my point. Any MSI should be installable as the SYSTEM account. You shouldn’t be using RunAsCurrentUser at all. The problem is that this requires that the user be present. If you instead do it without that, it will work on any system at anytime.

10

Thank you,
In the context of the current user home the normal system context, there are a lot of this kind of circumstance,
Now is not sure because the UAC, so temporary is so.

 if {(number of(names of logged on users) > 1)}
    waithidden __Download\RunAsCurrentUser.exe --w  --q cmd.exe /c  msiexec.exe /i __Download\XXXXXX.msi
else
        if  {(name of it = "Administrator") of logged on users}
             waithidden __Download\RunAsCurrentUser.exe --w --q cmd.exe /c msiexec.exe /i __Download\XXXXXX.msi /qn  /norestart
      else
            waithidden __Download\RunAsCurrentUser.exe --w --q cmd.exe /c msiexec.exe /i __Download\XXXXXX.msi
      endif
endif

In a few days is the Chinese New Year,
“新年快乐！”

11

Can you provide some examples of where running an MSI as the current user is required?

You should in about 99% of cases that I am aware of run the MSI as the SYSTEM using not using runascurrentuser.

Doing it the way you are showing is almost always a bad idea and not needed.

12

Use ONLY:

waithidden msiexec.exe /i __Download\7z.msi /qn /norestart ALLUSERS=1
1 Like
13

This situation has occurred for us. We have an Excel add on MSI that needs to be run as local user context.

However the MSI they built originally required Admin rights.

We showed the developer how to create a low privilege MSI and it works ideally…

This particular software does not create or install for all users, only the logged on user and thus needs that local user to run the software. And we didn’t want to have to provide admin creds for our mass deployment.

It basically copies template files to appdata\roaming .

The alternative would have been to force them to make an installer that works for ALLUSERS, then the SYSTEM account would have been fine.