Hey Guys -
I've got to update hundreds of systems from .NET 4.0 to .NET 4.5.2. The catch is that I am trying to slipstream 4.5.2 and all it's updates into a single installation due to the unique environment I have. The source must use an MSI or MSP installer - not BAT or CMD as I plan to make it into a deployable software update with SCCM.
.NET 4.5.2 is obviously downloadable as an offline installer / full installer package. It comes as an EXE, but running an admin install yields MSI files. As of writing, I've found 4 separate updates (8 if you include x86 & x64) for 4.5.2 which also come as EXEs for which you may perform admin installs of.
I'm trying to find a way to slipstream these updates into the .NET 4.5.2 offline installer to create a single source which will install .NET 4.5.2 fully patched? I've got a unique situation which I'm trying to do this for.
I played around with it myself by downloading and performing an admin install of 4.5.2. The admin install produced a total of 10 MSI files (5 of each OS type) varying in sizes. I then tried performing admin installs of these MSIs, but was only able to do it to 4 of them:
I downloaded the updates and extraced them to get the MSP for each. I then tried to patch the admin installs using msiexec, but it wouldn't work.
1. I'm trying to patch the admin installs of the 4 files above by using "msiexec /a filename.msi /p update.msp Why isn't it working?
2. If I can patch the admin installs of the above files, will installing the patched version of them be able to be used as a source to install .NET 4.5.2 with the 4 updates slipstreamed onto a system?
3. Which of the two should I use? GDR as it's the "General Release"?
4. Will either of them be able to only install .NET 4.5.2 on a system which currently has no .NET installed or also be used to upgrade systems which have 4.0 installed?
5. If you know a method to this this that works and is different, what is it?
Any suggestions would be appreciated - Thanks!