What does the install log show? (under BMCINSTALL folder)
And for troubleshooting purposes, have you tried an interactive/manual install on the server with the config that fails on first attempt when running via SCCM? (just to rule out SCCM as the cause of the failure)
We are going to test it today. So we started some test sequences to check if the agent itself will have a problem or if it is the SCCM framework. Right now we think it will be somewhere in the SCCM framework. Maybe there is a hard coded max ram value.
I will keep you informed as far as I will know more.
we finally figured it out. It is a case which could be handled inside SCCM. The Installation Routine now Transfers the package completly before running the Installation (as far as I understood the solution). So it is not a Pipeline anymore but a single package Installation.