BigFix - Setup Bulk Enrollment to automatically utilize agentless API's

🚀 Simplify Bulk Enrollment & Device Management with BigFix 🚀

Managing Windows devices at scale? Learn how to set up a bulk enrollment task that seamlessly integrates both agent-based and agentless management—all from a single interface with BigFix!

🔹 Why This Matters:

✔️ Automatically enroll devices as they are added

✔️ Leverage agent-based control where the agent performs better like large software deployments or large patching actions

✔️ Utilize agentless actions for tasks such as remote wipes

✔️ Access both APIs from one platform—no need for multiple tools

While agentless management is still evolving, BigFix ensures you’re always ahead by bridging the gap between both technologies. Whether deploying software to a remote workstation or executing quick, agentless tasks such as remote wiping a device, BigFix makes device management more efficient than ever.

📌 Why juggle multiple interfaces when BigFix can do it all?

Check out the full guide on setting up bulk enrollment and optimizing your device management workflow! ⬇️

#BigFix #EndpointManagement #ITAutomation #Agentless #BulkEnrollment #WindowsManagement

Open Webui and go to Apps – MCM

Select Admin

Select Enrollments – Designate Provisioning Package Generation

Target the Device you want to stage the provisioning package on

Once the Provisioning package is complete go to Enrollments – Bulk Enrollment

Select your MDM Server

Select the device you setup the provisioning package on

Select the Expiration of the package

Once the action completes go to your BigFix Console and Go to Tools – Create a new Task

Name the Task and Select the Action Tab and Add the following to the action script and Save the Task

On you BigFix Server go to the folder C:\Program Files (x86)\BigFix Enterprise\BES Server\wwwrootbes

Note the Bulk Enrollment Package Name you just created

Update the Task so the following lines to your provisioning package to reflect the name of the provisioning package on your server

Save the Change and you can now deploy your MDM enrollment package to a machine now enrolled in MCM