Hello Everyone!

I'm having trouble when creating a new "Package from Definition". Everything seems to work fine, but the command line that's generated from the .msi references an old .msi filename. I have been through the .msi endlessly without successfully tracking down the erroneous data. Could it be coming from a cached setting in SMS?

I feel like I'm missing something obvious on this one, but it's still eluding me. Any help you can provide would be truly appreciated.


Command Line Examples

Version 7.8.0 generates as: msiexec.exe /q ALLUSERS=2 /m MSGHMCJ /i "Phoenix 7.8.0.msi"

Version 7.8.0.1 generates as: msiexec.exe /q ALLUSERS=2 /m MSIUBNCW /i "Phoenix 7.8.0.1.msi"

Version 8.0.0 generates as: msiexec.exe /q ALLUSERS=2 /m MSIUBNCW /i "Phoenix 7.8.0.1.msi"
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

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

Answers

0
Check the cash from client side first.
It should be c:\windows\system32\ccm\cash\
Answered 06/26/2011 by: isaac.lex
Senior Yellow Belt

Please log in to comment
0
I hate to state the obvious [flame me if I am :)] but have you checked the definition file itself, you may be able to address the correct msi by simply adjusting the definition file you are importing as it may be incorrectly listed in the .sms file, these files I have found can be opened and edited in any text editor.

Cheers
Answered 06/26/2011 by: rich0864
Orange Belt

Please log in to comment
0
I welcome all responses obvious or subtle. So fear no flame here.

isaac.lex
I import the software to be installed from our primary fileshare server. I've checked both the fileshare server as well as my own machine where I run the SMS client and neither one have a cash folder.


rich0864
All the definition information is automatically populated by the .msi that I import into SMS. I don't have a standalone definition file that I'm aware of.
Answered 06/27/2011 by: kungphule
Senior Yellow Belt

Please log in to comment
0
ORIGINAL: kungphule


Version 7.8.0.1 generates as: msiexec.exe /q ALLUSERS=2 /m MSIUBNCW /i "Phoenix 7.8.0.1.msi"

Version 8.0.0 generates as: msiexec.exe /q ALLUSERS=2 /m MSIUBNCW /i "Phoenix 7.8.0.1.msi"

Something wrong there, it should not generate the same mif file "MSIUBNCW", I would suggest ensuring that it is really version 8.0.0 by installing the package manually on a virtual or a physical machine.
If it really is a different version, change folder name slightly, add a .txt file in the folder and import again.
If none of the above resolves the issue, delete the package and restart both sql server and SCCM.
Answered 06/27/2011 by: admaai
Orange Senior Belt

Please log in to comment
0
Have a look at: http://www.codeproject.com/KB/system/SMSPackageFromMSIFile.aspx?display=Mobile

It may help, though admittedly I have not done this before, I have only worked with existing .sms files.

Cheers
Rich
Answered 06/27/2011 by: rich0864
Orange Belt

Please log in to comment
0
Thanks everyone for your help. I'm still not sure what caused the problem in this particular package, but the next one that I built (version 8.1) works normally. If I ever have time again to revisit the one misfit package I'll let everyone know what I find out.
Answered 07/18/2011 by: kungphule
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity