Anyone having issues deploying Dot net 4.5.2 as a post install task on K2000?
Hi all,
I am trying to install MS dot net 4.5.2 as a postinstall task on K2000, task is set as an application, runtime envor set as windows and command line is
NDP452-KB2901907-x86-x64-AllOS-ENU.exe /q /norestart
it always prompts for the Eula and a finish button, I want it to be silent and seamless..
0 Comments
[ + ] Show comments
Answers (5)
Answer Summary:
Zip it, launch with batch file, use "/q /norestart"
Zip it, launch with batch file, use "/q /norestart"
Please log in to answer
Posted by:
SMal.tmcc
10 years ago
3 solutions I know of to install with other management systems.
using /passive instead of /q
run it from a batch file
or extract the package with 7zip and run the setup.exe silently
using /passive instead of /q
run it from a batch file
or extract the package with 7zip and run the setup.exe silently
Posted by:
EdT
10 years ago
If you run the exe from a command line with the /? switch, it will give you the available command switches to extract the content. Running an extracted MSI is usually cleaner than running the EXE.
Posted by:
ma034001
10 years ago
Thanks both, after much Googling I tried extracting and running the various MSI's that are contained , also tried setup /? but all to no avail. it seems to install as expected on a normal client, but when run as a posttask it prompts for Eula, very annoying for a silent build ! I'm currently trying the batch script method so fingers crossed
Posted by:
ma034001
10 years ago
Well , its very early and not fully tested but zipping the dotnet452 file and a batch file that copies it to C drive and runs it (I know an overkill - but its a tried and tested method documented on this site - and works well for me for so far !) then I ran the dotnet452.exe with /passive and it seems to have so far installed silently with no message box, so thanks to SMal.tmcc (again !)
Posted by:
cblake
10 years ago
Zip it, launch with batch file, use "/q /norestart" - that should take case of any possible cause.
Ultimately it comes down to how it's being called and executed most of the time.
Comments:
-
:) many thanks, yeah it does seem to be a tried and tested option for deploying apps.. - ma034001 10 years ago