Current Situation:
- We have 2 MSI files distributed and installed silently in the background through SCCM for all users as upgrades to monthly releases.
- The MSI compilation and SCCM distribution are handled by an external team for us once we provide them with the files (including chm, icons, pdf, images and other resource files along with the dlls) and the registry changes to be done during the install.
What we’re thinking to do:
- The 2 MSIs have become too big that we’re considering regrouping them in 5 separate installer files based on functionality and get them to the users according to their necessary access rights.
- We want to handle this internally in our own team and let that team handle only the SCCM part.
Newbie on Installer files:
We are unaware of anything related to the internals of an MSI file. Tried looking at InstEd and Orca to open an MSI file and it looks overwhelming for a newbie like me. We know which files need to be placed where in the Program Files folder and the registry settings during the install.
Questions:
- If we start afresh and create completely new installers without worrying about the GUIDs, will that work? (through some superficial searches on the internet, I read something like GUIDs of the components inside MSI will be tied to upgrades but I couldn’t clearly understand).
- If the answer to the above question is yes, is it possible to move to self-extracting EXE installers using Inno Setup? (Even if not, we can invest on learning WIX but just asking this question to see if we can reduce the investment with the learning curve that comes with MSIs).