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
Answers (4)
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
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
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.