Mass deploy with Intune, GPO, SCCM, Jamf or Linux

Create a multi-use code

In Organization › Downloads, “Mass deployment” block, choose “Maximum uses” (up to 1000), “Valid for” (1 day to 30 days) and “Target group”. Click “Create multi-use code”.

Expected result: You see the “Multi-use code”, its expiry and the “Installer (silent)” and “MSI (Intune, GPO, SCCM)” commands ready to copy.

Tip: Set the uses slightly above the number of devices you'll deploy, but not much more: that way the code can't be used for unrelated devices.

Create a multi-use code

Copy the MSI command

Copy the “MSI (Intune, GPO, SCCM)” command: it includes your code and, if you chose a group, GROUP=. Download the MSI of the same version as the installer. The example code isn't real.

msiexec /i NextAnalyzerSetup-1.0.0.msi /qn ENROLL_CODE=ABCD-EFGH

Expected result: You have the exact command for your tool.

Tip: Step-by-step instructions for each tool are also in the dashboard, under “Deployment instructions”.

With Microsoft Intune

In Apps › Windows › Add, choose “Line-of-business app” and upload the MSI. In “Command-line arguments” enter ENROLL_CODE= and your code. Assign it as “Required” to the device groups.

Expected result: Intune installs the agent on each device at its next sync.

With Group Policy (GPO)

Copy the MSI to a shared folder the devices can read. Create a GPO linked to the organizational unit and add a startup script with the command. Restart the devices or run gpupdate /force.

Expected result: Each device installs the agent on its next boot.

With Configuration Manager (SCCM)

Create an application from the MSI and change the installation program to the command with your code. Distribute the content and deploy it as “Required” to the collection.

Expected result: In Monitoring you see the deployment status on each device.

On Mac with Jamf or another MDM

Upload the universal package to Jamf Pro and create a policy that installs it. The code can go in the environment variable, in a com.nextanalyzer.agent profile (EnrollCode and Group keys) or in /Library/Application Support/NextAnalyzer/enroll.conf.

sudo NEXTANALYZER_ENROLL_CODE=ABCD-EFGH installer -pkg NextAnalyzer-1.0.0-universal.pkg -target /

Expected result: The Macs install the agent and are linked when it finishes.

Tip: With Intune for Mac, use “macOS app (PKG)” and a “Preference file” with the code. Screen Recording, for remote access, must be accepted by someone on each Mac.

On Linux with your scripts

Install the .deb or .rpm package with the NEXTANALYZER_ENROLL_CODE variable, or put the code in /etc/nextanalyzer/enroll.conf beforehand (ENROLL_CODE= and GROUP=). Any tool that runs commands as root works, such as Ansible.

sudo NEXTANALYZER_ENROLL_CODE=ABCD-EFGH apt install -y ./nextanalyzer-1.0.0-x64.deb

Expected result: The nextanalyzer service is running and the device is enrolled.

Read the exit codes

0: enrolled, or pending connection. 1: unexpected error. 2: invalid, expired or used-up code. 3: the organization reached its plan's device limit. 5: the platform rejected the enrollment. 6: agent version not supported.

Expected result: You know why each device failed without having to go to it.

Tip: With the MSI, any failure shows as 1603: install with /l*v log.txt and look for the real code in that log.

Check the result

Devices start appearing in Devices, already in their group. Under “Enrollment codes” you see the code's uses and those rejected by the plan limit.

Expected result: The list shows, for example, “12 of 50 used” and the devices “Online”.

Check the result