and wanted to update this post with some information I've gathered (mostly through trial and error). I've been playing quite a bit these past few days with the. msi, there are a few more subtle changes, but that's about it). msi directly does embed the correct Property,Manufacturer data in the. msi output from InstallAware directly, but I haven't noticed any significant changes regarding this behaviour (building the. I have tried using the Native Engine and building an. msi is currently created using the pgplwiz.exe (with the ALLUSERS=TRUE addition to the command line) because we still want the. msi package)Īre there any pre-defined variables I'm missing, command line arguments that should be added or anything that would change this behaviour? (without manually deleting the key or building a new. I have so far found no way to influence this behaviour, much less actually enabled the installation again. Since SCCM seems to use these keys as a register of installed products, it will actively refuse to reinstall the package again while the outer. On an uninstallation, only the first key gets removed, the other, outer. I've tested this kind of installation with some other products and my installation is one of the few that get registered in this way, and the only one that does so twice. msi in notepad as plain text somewhere between all the binary data). msi as a different ProductCode in the Property table and that I can find using Orca (or even by just opening the. The original guids are the ProductCode as defined in InstallAware, and a random guid that gets embedded into the. I'm sad to say I do not understand why that is, but it's probably not important right now. msi, two keys get created under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserData\\Products\. From what I found, when SCCM installs this. The main issue is that the reinstallation of the package is currently not possible without fiddling with the registry. msi installation that should be used for packaging and deployment by SCCM.
0 Comments
Leave a Reply. |