This article assumes that you already have a working SCCM deployment and an understanding of how to configure and deploy applications using SCCM.
There are two methods of doing this; 1) deploy the enrolment bundle together with the MSI and 2) put the bundle on a file share and point the installer to it.
Method 1 - deploy enrolment bundle and MSI together
- Generate and enrolment bundle with max_uses set to (At least) the number of machines to which you need to deploy.
- Create a batch script as follows (assuming the enrolment bundle is called jazz.bundle);
msiexec /qn /i agent_x64_release_signed.msi BUNDLE_FILEPATH="%cd%/jazz.bundle" /noreboot REBOOT=R
- Deploy the batch script, MSI and bundle together, and run the batch script to complete the agent install
Method 2 - point MSI installer to enrolment bundle on file share
- Generate an enrolment bundle and upload to a network share, ensure the system account of the machines that will be installing the agent can access this;
- Create a new application in SCCM for the Jazz Agent, set the installation command as follows;
msiexec /i “agent_x64_release_signed.msi” /qn BUNDLE_FILEPATH=\\WIN-ERPE397BMI9\software\bundles\agent.bundle /noreboot REBOOT=R
Where \\WIN-ERPE397BMI9\software\bundles\agent.bundle is the absolute path to the enrolment bundle on the network share from the previous step (relative paths are not supported).
- In order to prevent the immediate reboot upon deployment of the MSI; the return code 3010 should be edited to “Success (No Reboot)” in the “Return Codes” tab;
Under the user experience tab, the action based on return codes should be set to “No specific action”;
(source and image credits: http://www.freetechanswers.com/2018/03/sccm-preventing-restarts-during.html)
- Check the enrolment logs at %PROGRAMDATA%\Jazz Networks\agent\logs\enroll.log - if this reports the it isn’t possible to open the bundle file then check the path is correct and the system user is able to access this file. “The system cannot find the file specified.” errors can also be indiciative of permissions errors if the system user does not have file list permissions to the enclosing folder.
- The installer can be run locally on the PC with system permissions for troubleshooting purposes using the “psexec” utility; for example -
Psexec64.exe -s msiexec /i c:\agent_x64_release_signed.msi /qn BUNDLE_FILEPATH=\\WIN-ERPE397BMI9\software\bundles\agent.bundle /noreboot REBOOT=R
Note that in this case it is necessary to specify the full path to the MSI file. You can also use psexec.exe to run cmd.exe and check that you are able to open the bundle file outside the installer - this is a good way of verifying that the system user has the appropriate permissions.
Agent auto-update (directly pushed from the Jazz Platform) is not possible if deploying via SCCM. Do not attempt to enable auto-update as this will trigger multiple versions to be installed concurrently and lead to agent instability. Agent software updates should be pushed by SCCM directly in these deployments.