Package delivery "ALLUSERS" not working as normal

[KeithDib]

Hi all

 

I have a package to deliver through SCCM. It is a vendor supplied .msi.

 

If I install using a USB pen drive on a client machine it installs fine, installs as a per-machine install, shortcuts go in All Users desktop and "Start Programs" etc and shows in "Add Remove Programs"

 

If I deliver through SCCM however it seems to install per-user but also is only appears int the "Add Remove Programs", the shortcuts are put into the current user profile and nothing is in "Start Programs".

 

Also this application should put some files in "C:\Documents and Settings\All Users\Application Data", however when through SCCM these go into the current users Application Data.

 

I have checked all switches etc and all are as normal. I am not sure why the swithces used from the command prompt on a desktop machine will work fine while the same ones wont through SCCM?

 

I have tried both ways in SCCM, to deliver once to machine and for each user who logs on, with same results.

 

Any ideas please?

 

Oh were using

SCCM 2007 v4.00.6487.2000

XP SP3 clients

[Peter van der Woude]

It depends on two things, what did you configure as the Program and Advertisment settings and what command line are you using.

[KeithDib]

HI

 

All settings are to install per machine, command line is below [changes app name and server name etc]

 

I have also tried adding both ALLUSERS=1 and ALLUSERS=2, neither made any difference if installed through SCCM, but they did if installed using same command line localy.

 

msiexec /i Application.msi /passive SYSTEMSCONFIG="\\ServerName\appclientconfig\EPDT"

[KeithDib]

No ideas anyone?

[Peter van der Woude]

There are some things you should keep in mind... By default SCCM installs with the SYSTEM account, so first test the installation behavior with something like psexec to see if it will behave as you expect it to. If you want to install as the current user, then it should be specified and the user needs enough rights.

[KeithDib]

After long talks with the software vendor, it now seems there is something in their .msi that does not work if delivered through SCCM, although it does work if ran from the client machine from command prompt!