By providing the SCCM GUI with an MSI you are provided with so much improvement in the deployment process that doing it manually just seems like a lot of hardwork.For example, you get autodetection if the component is placed on the machine already.Review the registry and find the following keys (these examples are for x64); HKEYLOCALMACHINESOFTWAREMicrosoftWindowsCurrentVersionUninstallA2CB1ACB-94A2-32BA-A15E-7D80319F7589.Is there something i have to do with the MinimumAdditional MSICab Files.
Silently Vcredist_X64 .Exe As IWhere will I put ADDEPLOY1 My purpose is not to run setup.exe as I want to deploy it via sccm 2012. Instead of an InstallSource of C:ProgramDataPackage CacheGUID, InstallSource is something like C:RandomlyNamedTemporaryDirectory. After installation completes, the temporary directory is cleaned up (deleted), and I never actually see the directory after running vcredistx64.exe. It must wait until I confirm the install to extract to the directory, and the install happens so fast by the time I check for the directory, its gone. On the details tab of the properties for my vcredist file: File version 11.0.60610.1. The registry entry still pointed to some temporary directory on C:, but this time, there were folders in C:Program DataPackage Cache. I get a warning box when uninstalling the x64 version: If you continue with ths uninstall, 2 or more products may stop working properly. Do you want to continue with this uninstall anyway I usually use QN but the uninstall didnt happen, when I tested with a QB I saw this message and I have to click yes or no. Something is already installed which now relies on it but I only just installed it and everything was happy before this Ive been using these lines to uninstall: MsiExec.exe X37B8F9C7-03FB-3253-8781-2517C99D7C00 qb. Since you need to add ADDEPLOY anyhow on every msi that is no big deal. Burn uses the package cache to cache all the components (e.g. Silently Vcredist_X64 Software Source ToMSI, EXEs,) so yoiu dont need the software source to do a repair to change features for instance. I can install both MSIs manually via command line by adding the ADDEPLOY1 property. However, when i create a transform in ORCA Im able to install the minimum but not the additional package I get the message that tells me I need to run setup.exe. Is this case sensitive I cant seem to get this to work on the second package. As one would expect, I had a typo when testing the transform from command line. Other software looks this up for prerequisites and fails to install because it does not find the prerequisite. This is probably not ideal for SCCM 2012 R2 deployments because it does not use the msiexec.exe. I found this board and I find It really useful amp it helped me out much. I hope to give something back and aid others like you helped me. His resulting mis-steps send the world back to the Dark Ages.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
October 2020
Categories |