When installing Bentley Connection Client via SCCM 2012 it is failing, I have tried a few different switches and options to no avail. I also used /layout to create an installation but the issue persists. If I run the same switches from an admin command prompt on a test PC the same installation command works. Please see the below options I have used and the SCCM logs from the install. I have installed previous clients without issue using the same method via SCCM.
So, the previous version I had installed via SCCM successfully was 10.00.18.25, using the following command line
"blg6410001825en.exe" /S InstallDesktopShortcut=0 NoStartPostInstall=1
Here are the methods I have tried with Connection Client 10.00.19.27
"blg6410001927en.exe" /S InstallDesktopShortcut=0 NoStartPostInstall=1
"blg6410001927en.exe" InstallDesktopShortcut=0 NoStartPostInstall=1 /q
"blg6410001927en.exe" InstallDesktopShortcut=0 /q
"blg6410001927en.exe" /S
"blg6410001927en.exe" /q
And the same error resulted with " Process xxxx terminated with exitcode: 4294967295" and in Software Center "0xFFFFFFFF(-1)"
I also performed the layout with "blg6410001927en.exe" /layout choosing noui and no desktop shortcut the using the install files;
{316a7d44-0919-4912-a9e7-a0d67965485e}.lyt
NDP462-KB3151800-x86-x64-AllOS-ENU.exe
Setup_CONNECTIONClientx64_10.00.19.027.exe
In the distribution point and using just "Setup_CONNECTIONClientx64_10.00.19.027.exe" for the installation command with the following result;
"Process 15808 terminated with exitcode: 4294967295" in the AppEnforce.log
Though if I run the command via an elevated command prompt it works.
Please help. Is there an issue with this installer?
Regards, Simon.
Hello Simon,
I have replied to you one Service Request 7001086054. Please check and provide me required details.
Regards,
Sheetal
What was the resolution to this issue as I am experiencing the same problem with 10.0.19.27.
Paul Andrews
Bentley Support were of no assistance.
What I ended up doing was start a manual installation on my computer, then before proceeding with the install I located the extracted MSI file and used that in SCCM.
The MSI file was extracted to "C:\ProgramData\Package Cache" and was called "CONNECTIONClientx64.msi"
I hope this assists.
Simon.
Thanks Simon much appreciated. I did reach out to Bentley as well and according to them they are aware of the issue and are currently investigating. They did say that they have narrowed it down to a problem with installing using a system account. We can install with an admin account as that works but as you know that is not an option for ConfigMgr deployments. I will take a look at your suggestion and see fi that will work for us for now.
Is any explanation given to the large increase in installer size from the Bentley Downloads from version 18 to these latest version 19 Connection Client installs?