Video Screencast Help

Software Library Command Lines for .MSP files

Created: 25 Jan 2013 • Updated: 30 Jan 2013 | 5 comments
This issue has been solved. See solution.

I need help...I am new to the Software Management Framework and have set up my software library.  I am now attempting to import a package to install MS Visio 2010 professional using an .MSP file with it.  I imported the package successfully and verified that it replicated to my Site Server.  I am able to add the package and the command line to the package and then add the package to a Managed Software Policy.  This is where I run into issues.  The job fails when running it on the client computer with the following error:

"Path or file specified with /adminfile was not found or did not contain any patches."

This is my command line:

"visio2010\setup.exe" /adminfile "visio2010\updates\SCCVisioPro.msp"

I also tried putting the .msp file into the same folder as the setup file and modified the command line to read:

"visio2010\setup.exe" /adminfile "visio2010\SCCVisioPro.msp"

Same error.  I am assuming that I am not defining the command line correctly, but I am not sure what the path should be to get to the msp file since it first live in the library and then on the site server and finally on the local workstation it is being installed on. 

Please help!

Comments 5 CommentsJump to latest comment

AngelD's picture

The command should be:

visio2010\setup.exe /adminfile .\visio2010\updates\SCCVisioPro.msp

note the ".\" at the beginning of the msp path, it needs a fully qualified path

Dmitri Dragunov's picture

or if you put the msp file into the same folder with the setup file do not need to define folder for it

"visio2010\setup.exe" /adminfile "SCCVisioPro.msp"

mclemson's picture

When you create the command line, choose Installation file type: MSI Software Installation file, and Command type: Install, then click Edit.  In the first section, Transform options, click add to select the transform.  In the second section, UI options, select the interface level (e.g. /qn for totally silent, /qb for unattended with status bar).  Then click 'Generate command line.'

This will ensure it's always correct and you needn't worry about where the file resides within the  package resource.  Altiris will write the command line for you.

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner

AngelD's picture


Have in mind that office (these days) is not using a transform in this case but a customization patch.

mclemson's picture

Ah, perhaps I should read the posts before I start replying to them!

Mike Clemson, Senior Systems Engineer, ASC
Intuitive Technology Group -- Symantec Platinum Partner