Community
- Command Central
- MVP Program
- Monthly Mission
- Blogs
- Groups
- Events
- Media Vault
Products
- Observability
- Network Management
- Application Management
- IT Security
- IT Service Management
- System Management
- Database Management
Content Exchange
- SolarWinds Platform
- Server & Application Monitor
- Database Performance Analyzer
- Server Configuration Monitor
- Network Performance Monitor
- Network Configuration Manager
- SQL Sentry
- Web Help Desk
Free Tools & Trials
Store

Pointing to a .mst file in the package with the command line parameters

I am getting ready to start testing Adobe Acrobat Reader DC, and I want to modify the default Adobe package to include a .mst file that I am going to create and add to the package. I just want to ensure that I use the right command line parameters to point to the file in the package.

In a normal command line install it would look something like this - AcroRdrDC1500720033_en_US.exe /sAll /rs /msi TRANSFORMS=\\Server.fqdn\share\ReaderDC.mst

Beings that the install is from the package and the .mst file is in the package, would this work for the command line parameters of the install - /sAll /rs /msi TRANSFORMS=ReaderDC.mst

or this - /sAll /rs /msi TRANSFORMS=%MODULEPATH%\ReaderDC.mst

Find more posts tagged with

Accepted answers

jbaits

It is likely both formats would work. I have always used relative pathing without issue (ex. TRANSFORMS=ReaderDC.mst).

All comments

jbaits

It is likely both formats would work. I have always used relative pathing without issue (ex. TRANSFORMS=ReaderDC.mst).

frgpugs

Can you post back if you get reader DC to update clients from reader 10 and 11? For some reason all my clients detect as not needed even though it says its supposed to update from 9, 10, or 11.

kellytice

Yes, as you said, both should work.

%MODULEPATH% is basically the temp location that the files get copied to, so as long as you've included the file as an 'additional file' in the package editor, that should work.

The KB on adding a transform to a Patch Manager package just has the simpler version:

Back on the Package Wizard window, find the Command Line (silent install) field.
In this field, enter TRANSFORMS= in all capital letters, followed by the complete filename of the MST file. For example, enter <strong>TRANSFORMS=someTransform.mst</strong>.

dfoli

Thank you jbaits and Kellytice, I will let you know how it goes. frgpugs, my first test running just the package the way it is I had the same problem "Not Applicable", but I had this same problem with both 10 and 11 for the first month or so of each release. With 11 the package wasn't recognized as being needed until I published the package without building it first. I let the package be built as it was being published and it worked fine. The problem that I am having now with Reader DC is that when I try to build the package it states "Download failed. The underlying connection was closed: an unexpected error occurred on a receive.". So, I downloaded it to the server and uploaded it to the package, but once published "Not Applicable". I will keep working it.

frgpugs

thanks for the feedback dfoli. I have tried many ways to get the applicability rules to detect as needed but so far am not able to. If you do figure it out let me know as I have pretty much given it up as a useless patch

dfoli

So, I have created the .mst file and added it to the package. I have put '/sAll /msi TRANSFORMS=ReaderDC.mst' in the Command Line (silent install) field. I looked at the Applicability rules and found that they had FFFF in the String Value field. I changed that to the Value that is actually in the key. It is now published and I will let you know if it seen as needed.

dfoli

After about an hour systems are showing up as needing the package.

frppugs, if you go to the registry key that the Applicability rules point to, and copy that value into the 'String Value' field of the Applicability rules in the package (replacing the FFFF) you should be good-to-go.

I will test installing the package next week.