How to install MCR 2012b as an application in SCCM 2012 R2?

I am trying to install MCR 2012b silently using the following syntax: setup.exe -agreeToLicense yes -mode silent.

When I run this command manually from a command prompt, it installs fine. When I try and install it as an application from SCCM 2012, it fails.

I believe the issue lies in the fact that the setup releases focus BEFORE it has actually completed, thus telling SCCM that it has completed, when it really hasn't.

Anyone have any ideas?

Answer 1

[Doug]

I have the same issue with 2013b (32-bit). Oddly enough 64-bit doesn't have this issue. I set up the installer to log to a file and this is the only thing i've seen that might cause an issue for whatever reason. Did you ever find anything out ?

Error running [C:\WINDOWS\system32\regsvr32.exe, /s, /u, "C:\Program Files (x86)\MATLAB\MATLAB Compiler Runtime\v82\bin\win32\mwcomutil.dll"]status = 3

[Eric]

No luck at all. I can't get it to install via automated methods at all. Using the x64 or x86.

Answer 2

[Dooley Do]

We use a Powershell script to launch it:

$proc = Start-Process "bin\win64\setup.exe" -ArgumentList "-if installer_input.txt" -NoNewWindow -PassThru

do {start-sleep -Milliseconds 5000}
until ($proc.HasExited)

This waits for the process to end correctly.

Answer 3

[Guy J]

This procedure has worked over the last several versions where you use the installer_input.txt file to configure your setup. Simply running setup.exe -inputFile installer_input.txt does the rest. This is now documented everywhere I've looked.

Your problem could be also that the default cache size for SCCM on the client is 5GB I think. Increasing this from the control panel to something like 20GB solves this problem. At least this was an issue with Matlab 2016a because it was bigger than 5GB. Increasing this size isn't easy if you don't want to touch every machine. There is an article out there somewhere using a vbs script to do it.

However, my problem to this also is that it reports back to SCCM immediately that it's finished successfully when it's clearly not finished. It does complete, but the false completion return code causes problems I did not foresee. Any way to fix that reporting issue and have the matlab installer submit the completion code when it's actually finished? I'm tying to figure out what Dooley's script is doing, it looks like it's using a counter to create a false delay?

This problem may seem trivial once you get it installing successfully (still with the false early completion), but now you cannot use the package in an OS installer task sequence, and sccm continues to the next task too early and either matlab fails or the following tasks fail because of multiple installations running. Also, when deploying just the package, if the installer is running in the background, the machine's default "sleep timeout" of 30 minutes now interrupts the matlab installation most of the time. (or users reboot because SCCM "Says" it's already installed)

Is there a better way to do this than just injecting an arbitrary waiting period?