During (re)Enrollment

During enrollment or re-enrollment, teams reset, configure, unbox, assign, and redistribute devices. Run the process in controlled batches so you can correct a physical, network, or enrollment problem before it affects the full fleet.

FileWave groups, placeholders, custom fields, Deployments, and inventory help organize the work and show which devices have completed each stage. The practices below apply whether you are preparing a new fleet or refreshing devices for another user.

Start Small

Your process was written as 1) Unbox, 2) Assign Asset Tag, 3) Affix Tag, 4) Put device in case.  But you find out with your first batch of devices that the user needs to read the asset tag in a later step, but they can't see it because of the case being in the way.  Finding that problem with five devices is easier than finding it with 500 students waiting. Start with a small batch, correct the sequence, and scale up after the process is proven.

Employ Efficient (re)Enrollment

Once the sequence is proven, organize devices into batches based on your operational needs, such as department, device type, destination, or user role. FileWave groups let staff apply and monitor the same enrollment actions across each controlled batch. For example, a school can process one grade, classroom, or device cart at a time and hold completed devices separately from units that need another pass.

Set a Safe Batch Size

Do not assume that 5,000 devices should enroll at once. Account for the number of devices staff can physically prepare, the requests sent to Apple or another enrollment service, FileWave Server capacity, internet bandwidth, Wi-Fi capacity, and the traffic generated by app and profile downloads. Measure physical throughput too: how many boxes can staff open, tag, charge, and hand off in a fixed interval?

Every environment has a practical enrollment-concurrency limit. Start with a small representative batch, increase the batch size while monitoring each dependency, and stop below the point where errors or delays begin.

Device Preparation

Taking a cue from our previous section on 'Preparing for Enrollment', remember to reset devices to factory settings before initiating (re)Enrollment. This will ensure that any residual data or settings from previous users do not interfere with the new user experience.  For new devices, make sure to consider the physical steps of unboxing, dealing with recycling, affixing asset tags, and even the ability to plug the device in. (And of course, you can use FileWave to send "wipe" commands to devices in preparation)

Automate Where Possible

FileWave's automation capabilities can significantly reduce the time and effort spent on (re)Enrollment tasks. Here are some areas where automation can be beneficial:

• Device Naming: Use FileWave's custom fields and scripts to automatically generate and assign device names based on your organization's naming convention.

• Placeholders: Mentioned in the last article, placeholders are a great way to pre-assign content based on smart groups and custom fields.

• App Installations: Leverage FileWave's app deployment features to automatically install necessary apps and updates during the (re)Enrollment process. This ensures all devices are equipped with the necessary tools right from the start.

• User Preferences: Set user preferences and settings in advance using FileWave. These can be applied automatically during (re)Enrollment, reducing the need for manual configuration and ensuring a consistent user experience across all devices.

Monitor Progress

FileWave's device monitoring features allow you to keep track of the (re)Enrollment progress. Use custom fields to mark devices as "(re)Enrolled" or use FileWave's dashboard to monitor device status in real time. This can help identify any issues early on and allow for quick resolution.

Record the completed batch, any failed step, and the corrective action before the next group begins. This creates a repeatable handoff for IT staff and keeps users from receiving partially configured devices.