I am deploying a software to Windows XP Pro clients via SCCM 2007. During installation, a user with no administrative rights is logged on to the machine.

When setting the program to run "whether or not a user is logged on" (and "run with administrative rights" active), the installation fails, and the reason for that seems to be lacking permissions for the local system. I get a behavior very similar to the one described here: http://www.itninja.com/question/what-is-error-1603-trying-to-tell-me, and checking with DCOMCNFG.EXE revealed, that the failed part of the installation has indeed been run in the context of "interactive user", not "launching user".

Now, in SCCM I change the programs settings to "only when no user is logged on" ("run with administrative rights" still active). I take a clean machine, wait with the login until the advertisement is run, and this way it works.

Does anybody know, where the difference in these two settings is? In both cases, - to my understanding - the installation should be run (or at least be initiated) in the context of the local system. Why does is it not work in the first case, but in the latter all is ok?

The program itself is ok, I can install it manually using "run as" when a non-admin is logged on. The SCCM-installation fails, when Windows Installer installs ISScript from the wrapper Setup.exe.

0 Comments   [ + ] Show Comments


Please log in to comment



It seems the ISScript MSI does something 'funny' when running with a logged on user. have a look at this thread: http://www.itninja.com/question/sms-msi-fails-on-some-clients-with-1603-works-on-others

(AngelD's first response)


Answered 05/31/2012 by: pjgeutjens
Red Belt

  • Thanks for the hint, I suspected something like that. I'll try to install the ISScript-engine separately, instead of using the wrapper.
Please log in to comment

SCCM uses the SYSTEM account to install software... most likely the software you are installing is trying to edit the HKCU keys or a users profile keys which can have issues and is bad msi creation.

What happens if you install it as the logged in user then logon as a different user...? my guess is that the software will fail or try to repair itself.

Answered 05/31/2012 by: GAKIS
Second Degree Green Belt

  • I don't think that's the problem. It already fails, when setup.exe tries to install ISScript, because that installation is launched in the wrong context (DCOMCNFG revealed as much). The installation of the actual software thereafter is launched in the correct context, but since ISScript is missing, it terminates.
Please log in to comment

extend your MSI logging to verbose and watch the client SCCM log files...that will lock down the exact failure.  then resolve.  I'm not sure that knowing the answer to your question specifically will help you solve it.

Answered 06/11/2012 by: LordCruz
White Belt

Please log in to comment
Answer this question or Comment on this question for clarity