/build/static/layout/Breadcrumb_cap_w.png

urent question...

Hi All


I have an application when installed manually like click on .msi and install, it installs some files in a folder under "C:\programe data\xyz" but when trying to install same application with command line as ....  {msiexec.exe /I ".MSI NAME" /qn} does not install files in a folder under "C:\programe data\xyz" instead these files get installed under

"C:\programe data" and due to this behavior of .msi application does not launch properly. So just want to know how I can point those files to install under right folder while attempting to install application silently using qn switch?

Also I observed application gets installed properly with "qr" switch. using command line {msiexec.exe /I ".MSI NAME" /qr}.


Any suggestion /advice?


Thanks



0 Comments   [ + ] Show comments

Answers (4)

Posted by: jagadeish 9 years ago
Red Belt
0
There will be some custom action in InstallUISequence which will not be executed when you install the msi with /qn. You will have to identify those custom actions and copy/move them to InstallExecuteSequence (ExecuteImmediate)
Posted by: EdT 9 years ago
Red Belt
0
Log an installation that works, and then look for the property that gets set to c:\programdata/xyz
Then add a "set property" custom action to the InstallExecute sequence, before InstallInitialize, that sets that same property to the installation path you want to use.
As jagadeish points out, the InstallUI sequence does not run at all during a silent (/qn) installation, so your problem is most likely caused by a public property not being set in the UI sequence when it does not run, and a default value being used instead.

Comments:
  • observed some thing different. works fine with qr switch and the result is as expected means files will be installed under "C:\programe data\xyz" . So my question is will SCCM accepts qr switch? I have seen some applications works completely silent under system context/ installing through SCCM. - jay25oct 9 years ago
  • so if this works through SCCM, no need to add any property or custom action etc... - jay25oct 9 years ago
    • Did you tried installing with system context (at command sometime back or may be psexec ). if that work as expected then deploying software using SCCM would fetch the same result. - rock_star 9 years ago
      • yes I tried it. but it runs when copied locally, but do not run from network share..it shows message as "access denied" when trying to running through network share.. - jay25oct 9 years ago
Posted by: EdT 9 years ago
Red Belt
0
That is because SCCM, like other deployment systems, uses a local system account to install apps. Local system accounts do not have network access. That is why SCCM has a local cache folder where apps are copied from the server before installation commences.

Comments:
  • got it. so if application shows message as "access denied" when trying to running through network share but when copying locally and run through psexec if works is that means a positive test and application will work the same way in SCCM? - jay25oct 9 years ago
Posted by: anonymous_9363 9 years ago
Red Belt
0
Provided the SCCM deployment is set up correctly - with the installation performed in System context - then yes.

Once my installations have been tested with a local administration account, then the application run with a user account, I *always* do the same thing using PSExec before adding the package to SCCM.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ