Software Deployment

Is that fails to install if a standard user is logged in? Then there is probably an issue with the installation account that SCCM is using. Maybe the account doesn't have permissions on the machine it's installing to. Or the way the deployment is set, maybe to use the local users credentials.

If it fails to launch as a standard user then there is something restricted permission-wise, such as registry or files, that need to be investigated and relaxed in your customisation.
If you contact the vendor they may be able to advise, otherwise, to quote VBScab:
- Don't know why 'x' happened? Want to know why 'y' happened? ProcMon will tell you.

Hope that helps,

Dunnpy

Yes, the application fails to installs when standard users login. But in SCCM we try to deploy the application with admin rights so that the application is installing with admin rights irrective of the user who ever logs in.

Thank You.

Yuvaraj.

How are you deploying the 4 MSI files?
Are they separate packages chained together?
Is it particular one that has an issue, or all of them?
Have you checked that the service account SCCM is using is part of the relevant groups on the local machine to allow the deployment?
You could try ProcMon to monitor the machine as SCCM attempts an install to see what's going on.
What does the verbose log say?

Dunnpy

Hi Dunnpy,

Yes they are four seperate packages chained together. Could you please let me know how to check that the service account SCCM is using is part of the relevant groups on the local machine to allow the deployment?

Thanks,
Yuvi.

Well, you have to check that computer has the group/account in it's administrator group and that the SCCM is using to install the software.

Dunnpy

I'm really sorry and I mean no offence but asking that question means you're in the wrong job. How can you do (or, more correctly, your employer expect you to do) a professional job when you have not even a rudimentary grasp of Windows and how to use its built-in tools?

Couple that with the fact that, in a membership of this forum lasting almost 2 years, you still cannot perform basic trouble-shooting (hint: PROCMON)....

I despair, I really do.

As to the problem...it seems to me that you have either Active Setup executing, or self-healing/repair taking place. Strictly speaking, this is not an install, since SCCM has already installed the package. Not saying (or knowing) which it is points again to a basic lack of knowledge. Either is designed to handle user-level data. If it's failing, then the package is actually trying to write machine-level data so should be handled in the main package. If necessary, add a transform to one of the MSIs. If your investigation reveals that it is supposed to be user-level data, then your user profile permissioning is broken.

Thanks Ian,

I was working up to this, maybe in a more subtle way, but I think the message would have been the same.

I don't get to play with SCCM in my current role and I like to try and keep my hand in, but I was beginning to think that I was being trolled :)

Dunnpy

Guys,

am I remiss in saying whatever you end up doing, first step is to LOG THE 4 INSTALLS (I'm being conservative with font size here) and analyse the resulting logs?
Would probably allow a slightly more granular approach than "the install is failing"...

/L*V isn't that hard to type...

PJ