SCCM Command Line Imports Incorrectly From MSI
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"
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
Answers (6)
Please log in to answer
Posted by:
isaac.lex
13 years ago
Check the cash from client side first.
It should be c:\windows\system32\ccm\cash\
It should be c:\windows\system32\ccm\cash\
Posted by:
rich0864
13 years ago
Cheers
Posted by:
kungphule
13 years ago
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.
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.
Posted by:
admaai
13 years ago
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.
Posted by:
rich0864
13 years ago
It may help, though admittedly I have not done this before, I have only worked with existing .sms files.
Cheers
Rich
Posted by:
kungphule
13 years ago
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.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.