Forum Discussion
New ContributorQuartus Prime Standard 20.4 silent installation with SCCM
Hi Thomas,
I've spent 2 months fighting this myself and had a breakthrough. It seems that the Quartus installer uses 'Bitrock', and installer technology I have also been fighting when trying to install Microchip's MPLAB X IDE 5.5.
Long story short, this forum post helped: https://docs.microsoft.com/en-us/answers/questions/397336/different-behaviour-required-vs-available-applicat.html
Use the checkbox on the Programs tab of the Deployment Type, to 'Run installation and uninstallation as 32bit on 64 bit clients'. Once I ticked that, my script actually managed to install quartus on a couple of machines last night.
I've written a long winded powershell script that pre-installs the usb blaster drivers (and puts their certs in machine trusted), installs quartus, then modelsim, then the patch for 20.1, and finally does the firewall entries for the right bits.
The command line that now works as 32 bit process is:
...
23/09/2021 05:43:43 Started Step2 Install
Executing 'C:\WINDOWS\ccmcache\36\app\QuartusSetup-20.1.1.720-windows.exe --mode unattended --unattendedmodeui none --installdir "C:\Program Files\IntelQuartusV20" --accept_eula 1' at 23/09/2021 05:43:43
23/09/2021 05:49:35 finished Step2 Install...
Have a go with that, hope it helps. It's been driving me up the wall for years since Intel took this over.
Doug.
Super ContributorHi @ThomasH
I sent 'debug-1-core.txt' to the vendor, but they found it was not the one generated by the updated installer. Could you help to double check? You will need to run:
QuartusHelpSetup-20.1.1.720-windows.exe --mode unattended --unattendedmodeui none --installdir C:/intelFPGA/20.1 --accept_eula 1 --parallel-decompression-cores 1 --syncdebugtrace debug-1-core.txt
within SCCM, send us back the debug output file: debug-1-core.txt
Below is the reply from vendor:
The installer you shared seems correct (it includes the debug and is built with the provided InstallBuilder version) but the debug file sent by your customer does not match.
We see the uploaded installer is named: QuartusHelpSetup-20.1.1.720-windows.exe while the debug file from your user seems to correspond to QuartusSetup-20.1.1.720-windows.exe. Apart from the difference in the name, we see it seems to be much bigger. In addition, recent versions of InstallBuilder include the version string from the used builder in the debug file, which does not appear in your customer debug file, so it seems they did not use the latest installer to recreate the debug file. Could you ask them to verify if that is the case? You could suggest invoking the installer first with --version to confirm the builder matches.
Best Regards,
Richard Tan
p/s: If any answer from the community or Intel support are helpful, please feel free to give Kudos.
Super ContributorHi @ThomasH
I sent 'debug-1-core.txt' to the vendor, but they found it was not the one generated by the updated installer. Could you help to double check? You will need to run:
QuartusHelpSetup-20.1.1.720-windows.exe --mode unattended --unattendedmodeui none --installdir C:/intelFPGA/20.1 --accept_eula 1 --parallel-decompression-cores 1 --syncdebugtrace debug-1-core.txt
within SCCM, send us back the debug output file: debug-1-core.txt
Best Regards,
Richard Tan
p/s: If any answer from the community or Intel support are helpful, please feel free to give Kudos.
ThomasHSorry for the mistake. I have attached the new log, thanks for looking into this.
- RichardT_altera
Hi @ThomasH
Did the installer hang this time? According to the debug file, it was completed. Could you share us the installation log if you still have it?
Best Regards,
Richard Tan
p/s: If any answer from the community or Intel support are helpful, please feel free to give Kudos.- RichardT_altera
