Hm... i tryed it but hotfixes doesnt get applyed for some reason.... What it did was admin install, then i copyed all *msp hotfixes in to that directory after i added all hotfixes to .msi with msiexec /a <msi_name>.msi /p NDP40-C.msp /qb (KB971891 first). after it took netfx_core_x64.mst and tryed to install .net with netfx_core_x64.msi TRANSFORMS=netfx_core_x64.mst no luck... it installs .net without updates. What im doing wrong? How you convice it to update .mzz ?
I hate sysprep and as you say not worth it for one PC; however, I anxiously await your tutorial video on how to slipstream oh great one.
None of the download links are working. Can somebody link me to a working download link please? or point me in the right directioin on where i can download the Solors Post Sp1 Repo Ty
Thanks Works Now,, i had to switch my dns server, cause my internet provider one doesnt work on some sites which is odd. Thanks
Regarding .NET 4.0 admin deploy issue, since rick has asked me so I think I'd better post my points here: This symptom is the same as the .NET 3.5 deploy issue, as I mentioned here(!!!.ryanvm.net/forum/viewtopic.php?t=7525) (or msfn link(!!!.msfn.org/board/topic/137477-tutorialmodify-an-offline-msi-installer-for-administrative-install/), The method I provided is also used in strel's SNM Synth). The installer just don't use the "admin" files and uses the file from original msi, because when you performs an admin install, the destination msi is first converted to a really admin msi, then overwritten by the original msi copied along with other setup routine files. So renaming(saving in a new name) is actually the key point that rick eventually solved this issue. The easiest way to make an msi admin and let Windows looking for the files outside the cabinet is changing the "Image Type"(offcialy "Word Count" by M$) to "Admin External" in Summary Info(InstEd: Main Menu - Tables - Summary Info). The _stream AdminProperty is not necessary. Another efficient way to avoid this issue is to rip off the setup routine, so that setup routine files are not copied during installation. I have a guide here: !!!.ryanvm.net/forum/viewtopic.php?t=8512 -----------edit---------- ok I'm still not allowed to post links so please manually change "!!!" to "www"
This indeed works... however i think all this process is to complicated. You can batch half of the process but all that transform thingie and insted is bit to much. Now what i need to try is to do whole process with only 1 MSP (KB97189) and then additinaly add rest of them (before step 8), if this works then i guess its fine, otherwise it bit bleh... dunno why MS didnt do simple msu update route for .net 4.0...
Neet, I am currently using a moded version of your script to integrate the patches, first I use dir/b to get a list of all kb9* files (this guarantees KB971891 will be integrated first) the i do the kb2* patches Code: for /f %%A in ('dir /b NDP40-KB9*.msp') do ( echo Integrating Patch "%%A" ... start /wait msiexec /a netfx_extended_x64.msi /p %%A > nul ) for /f %%A in ('dir /b NDP40-KB2*.msp') do ( echo Integrating Patch "%%A" ... start /wait msiexec /a netfx_extended_x64.msi /p %%A > nul )