SCCM 2007: where is the difference (regarding permissions) between running a program "only when no user is logged on" and "whether or not a user is logged on"?
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.