I have a thick msi. Wanted to do some testing and change it to thin. Using Wise under Media changed Compression Options from Compress files inside msi to Uncompress external files.
1. I dont see the size of the msi getting much smaller
2. Getting an error 2920. Source directory not specified for the file...
What am i missing?
Thank you.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

1
Huh, what.

Thick is not a term common in Windows Installer packaging. Are you talking about a uncompressed MSI, which is also similar to a Administrative Point (I think that's the correct term).

Anyway your best to have it compressed, either as an external CAB, or for best practice internal CAB (inside the msi). Having it internal will allow the self-heal, repairs to be robust - just think windows installer moaning for the cab file when its missing.

Probably doesn't answer your question though.
Answered 08/24/2016 by: rileyz
Red Belt

Please log in to comment

Answers

0
I been looking into it and i think having uncompressed "Thin" is a better option.
Quicker install and saving space as it does not need to make a local copy and then cache the msi "speed is not an issue but space is on VM's"
I am also finding that not during self heal uncompressed will only copy missing components and not a whole msi.
Do you have any link as why compressed is a best practice?
I am trying to define new standards,
Thank you,
Answered 08/24/2016 by: ogeccut
Black Belt

  • The problem is if your installer source is missing, ie your 'thin' uncompressed files are missing, the self heal will fail. Where as if its in the msi, its more resilient as its cached locally.
    *When a msi gets installed the msi gets cached, but not any external CAB files or other uncompressed files.

    You can test this will your thin. Just install it, delete the source files, delete some keypath files from the installer. Hit the repair and see what happens.

    See this link for more info.
    http://www.itninja.com/question/msi-cache-locations-and-deploying-with-sccm
Please log in to comment
0
You broke the MSI.

Thick to Thin, do you mean you are installing on a Terminal Server for delivery via Citrix?

There is no need to alter the media (CAB Files; Compressed/uncompressed)

more info needed....

Answered 08/25/2016 by: wynnem
Orange Belt

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