/build/static/layout/Breadcrumb_cap_w.png

Acrobat 6 Reader via Altiris

I have an installation point and .mst for Adobe Acrobat 6 Reader that I created using Adobe's InstallShield Tuner 6.0.1 for Acrobat. It has been perfectly portable, and I have carried it around from client to client. I never had a problem deploying it through Active Directory/Group Policy on any network.

Now I am trying to use the same installation point/.msi/.mst with Altiris, and guess what - NO JOY. If I call it via an Altiris script (eg: msiexec.exe /i <UNC_path_to_msi> transforms=file.mst), I get an error that says my command line parameters are not correct. If I skip the transform and just point to the .msi, I get an error 193 and no more information.

Anyone have experience or ideas with this one?

craig --<>.

0 Comments   [ + ] Show comments

Answers (3)

Posted by: craig16229 20 years ago
Third Degree Brown Belt
0
For those of you who are interested in the solution to this issue, I found that simply putting quotes around the UNC path to my .msi resolved the issue. The context ends up being:

msiexec.exe /i "<full_UNC_path_to_the_msi>" TRANSFORMS="<full_UNC_path_to_mst>" <appropriate_q_switch>

What is curious to me and what I still do not understand is why some packages do not require the quotes, while others will return an "invalid parameters" error if the quotes are not present.

My Altiris package for Office XP is also deployed via UNC, lacks the quotes, and works without any apparent issues.

I have noticed the same varying behavior when applying .msp's to Microsoft administrative installation points.

craig --<>.
Posted by: ewall 20 years ago
Purple Belt
0
That's what I was going to suggest... quote all the parameters.

Presumably you understand that if the unquoted path contained spaces, Windoze would treat that latter part of the path as a separate (broken) parameter. However, think about this: if your servers are using DFS, your UNC path to a DFS map point might not contain any spaces--but when the redirector rewrites the path to the actual DFS-enabled share point, maybe that contains some spaces? Furthermore, tools like SMS and Altiris could be using multiple distribution points with different share names, possibly with spaces in them...

Anyway, to avoid this kind of thing I just make sure to always quote the parameters, even if it's just a single MST file name or what-have-you.
Posted by: craig16229 20 years ago
Third Degree Brown Belt
0
Yup, I do know about the spaces. In this particular case though, the path to my Office XP .msi contains spaces as well. I think your practice of "quotes for everything" is one I will use from here on out.

craig --<>.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
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