During (re)Enrollment

TheDuring actualenrollment (re)Enrollmentor phasere-enrollment, isteams wherereset, configure, unbox, assign, and redistribute devices. Run the rubberprocess meetsin controlled batches so you can correct a physical, network, or enrollment problem before it affects the roadfull regardingfleet.

your

FileWave planninggroups, effectiveness.placeholders, custom Nofields, planningDeployments, isand everinventory perfect,help butorganize the morework preparedand youshow are,which thedevices morehave successfulcompleted each stage. The practices below apply whether you are goingpreparing toa be.

new

Duringfleet theor enrollment and (re)Enrollment phase, the process becomes more hands-on asrefreshing devices are reset, reconfigured, unboxed, assigned, and redistributed.  That is a lot of steps, but this doesn't mean that the task has to be overwhelming or complicated. With FileWave, you can utilize a range of tools and features to make the (re)Enrollment process smooth and efficient, and we have a list of best practices for youanother to follow too.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.  Now, do you want to findFinding that outproblem with five devices is easier than finding it with 500 students waiting. Start with a 500small studentsbatch, incorrect the room, or 5?  It is by far best to approach the day in small batches,sequence, and scale up asafter the systemprocess is proven effective.proven.

Employ Efficient (re)Enrollment

Once yourthe systemsequence is proven, batching or grouping (re)Enrollment is an effective way to manage the process without becoming overwhelmed. FileWave provides capabilities to organize devices into logical groupsbatches based on your organization'soperational needs, such as by department, device type, destination, or user role. ThisFileWave allowsgroups forlet batchstaff operations,apply enablingand monitor the same enrollment actions across each controlled batch. For example, a moreschool organizedcan process one grade, classroom, or device cart at a time and efficienthold (re)Enrollmentcompleted process.devices separately from units that need another pass.

Don'tSet Bitea ofSafe MoreBatch than You Can ChewSize

IDo havenot 5000assume devices,that surely5,000 Idevices should enroll at once. Account for the number of devices staff can enrollphysically themprepare, allthe atrequests once, no?  No.  There are many considerationssent to theApple or another enrollment process.service, FileWave SomeServer arecapacity, physical...forinternet instance,bandwidth, Wi-Fi capacity, and the traffic generated by app and profile downloads. Measure physical throughput too: how many boxes can actuallystaff beopen, openedtag, bycharge, 3and peoplehand off in 10 minutes?  But others are more subtle.  For instance, enrolling Apple Devices concurrently means a lotfixed of requests going to Apple at the same time, and there could be processing bottlenecks both on your local server and in the cloud.  And the thing everyone forgets about is the actual network itself...can it handle all of that traffic at the same time? interval?

InEvery mostenvironment environments, there ishas a naturalpractical "upper limit" to enrollment enrollment-concurrency thatlimit. youStart don'twith wanta tosmall gorepresentative beyond.batch, increase So,the startbatch small,size getwhile biggermonitoring untileach you run into an issue,dependency, and thenstop back off a bit to a comfortable pace.  Slow and steady winsbelow the race!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.

Remember,Record the goalcompleted isbatch, toany makefailed the (re)Enrollment process as seamless as possible for both your IT teamstep, and the end-users.corrective Withaction carefulbefore planning,the efficientnext batchgroup processing,begins. This creates a repeatable handoff for IT staff and thekeeps extensiveusers usefrom ofreceiving automation,partially FileWaveconfigured can help you achieve this.devices.