Video Screencast Help
Symantec to Separate Into Two Focused, Industry-Leading Technology Companies. Learn more.

import a folder as a package creates incorrect msi command lines

Created: 20 Aug 2012 • Updated: 12 Nov 2012 | 7 comments
jlawson's picture
2 Agree
0 Disagree
+2 2 Votes
Login to vote
Status: Implemented

If I import a folder with an MSI inside of it as a software package the generated command lines never include the folder and will cause a 1619 error code when you try to deploy the msi.

You have to manually go in and edit each command line and add the folder name before the msi in order for it to work.

Example:

Generated:

msiexec.exe /i "software.msi"

Should Be:

msiexec.exe /i "FolderName\software.msi"

I searched but did not see a current idea on this problem if there already is one please let me know I will vote that one up.

Comments 7 CommentsJump to latest comment

KSchroeder's picture

ARggghhh...Connect lost my big reply to this.

In summary, we've seen the same thing when we select the Software Library as the source of the package, then add the folder to the library.  Maybe we're doing it wrong...?  And it isn't just MSIs, most of our packages run .vbs scripts and when you select that file as the "installation file" (err, whatever that button says), it still doesn't sort out the proper command line.  Very frustrating!

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

0
Login to vote
Mistral's picture

You should import the content of the folder, not the folder itself (like in Altiris 6.x).

Altiris 7.x will create a folder (with the package GUID) for the package.

+1
Login to vote
KSchroeder's picture

Mistral,

Thanks, I missed your comment on this, but you are exactly correct in my testing so far.  I set the location of the Package as Software Library, then browse to the package files.  If I just stop there (without the .msi and any sub-folders selected) then I get this issue mentioned above with the msiexec.exe /i 'foldername\myinstaller.msi" or wscript.exe "foldername\myscript.vbs" problem, however if in the file selection dialog I shift-select or ctrl-click the contents, then it is added properly!

I guess I was just expecting the same folder-based package approach from 6.0, vs this new capability to select individual folders and files within a directory to define the package.

@JLawson  try it and you'll see; it was very counter-intuitive to me as well, coming from the 6.0 way of things!

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

0
Login to vote
jlawson's picture

I understand that if you have a single file yes the commands work if you just do the file.  I though I have a whole mess of stuff to upload it is easier to just do a folder and it allows this.  The problem is the command generated is incorrect.  It is not incorrect that I use the folder but the autogenerated commands are not programmed to recognize this.

This is the reason for the idea it is not to know how it could be done to work with the autogenerated commands.  I already understood this.

0
Login to vote
Mistral's picture

My bad ... didn't see it's an "idea".

After i read first post i thought you need help ... sorry for this.

0
Login to vote
jlawson's picture

This appears to have been resolved with MP1 for 7.1 SP2.  Is there a way to close an idea since it appears they have implemented this idea?

0
Login to vote
KSchroeder's picture

I will notify Ohzone, the community manager to mark the idea Implemented.

Thanks,
Kyle
Symantec Trusted Advisor

For Forum threads, please click "Mark as Solution" if answered.
For all content, please give a thumbs up if you agree with or support the post.

0
Login to vote