Post-Enrollment Operations

After enrollment or re-enrollment, verify that devices have the expected software, policies, inventory, and support path. This operational phase turns a successful enrollment into a usable, maintainable fleet.

Verify software and update status

Confirm that required applications, operating-system updates, and security patches reached the re-enrolled devices. Use FileWave Reports to identify failed installations, outdated versions, and devices that have not checked in rather than assuming an empty deployment queue means every device is current.

Build proactive maintenance checks

Use inventory, Custom Fields, Reports, and Smart Groups to find conditions that will create support problems. Low free disk space, stale check-in times, missing security software, and repeated installation failures are useful examples. For each check, define the expected value, exception threshold, review cadence, owner, and response. Pilot criteria against known-good and known-bad devices before using a Smart Group for automated targeting. This prevents a self-healing Fileset from repeatedly changing the same state that its Smart Group uses for membership.

Restore self-service access

Confirm that FileWave Kiosk shows the applications and resources users are expected to install without local administrator rights. Test one required and one optional item so licensing, targeting, download, and installation behavior are all covered. Include a large application in the pilot when network or Booster capacity matters. Verify that users can retry a failed or removed optional app through Kiosk and that support staff know when an administrator must issue a reinstall instead.

Provide User Training

Tailor user guidance to the device type and role. Cover how to open FileWave Kiosk, install optional content, respond to update or restart prompts, report a lost device, and contact support. Include any changed sign-in, Wi-Fi, VPN, or application steps introduced by re-enrollment. Keep the instructions short enough to use during the rollout, then maintain a longer support reference for recurring questions. Test the guidance with a representative user instead of assuming the administrative workflow matches what users see.

Confirm the support handoff

Give users a clear support route and give support staff the FileWave views, Reports, remote-support tools, and escalation details they need. Document who owns enrollment failures, application failures, lost-device actions, and upstream Apple, Google, or Microsoft account problems. Where a ticketing integration is used, test the device identifier and inventory fields that connect a ticket to the correct FileWave record. Confirm that support staff can distinguish a device that has not checked in from one that checked in but failed a specific deployment.

• Incident IQ FileWave Asset Integration - Incident IQ, often styled as iiQ and sometimes written as IIQ, is one example of a ticketing and asset-management platform that integrates with FileWave. Use the linked FileWave KB article for the FileWave-side setup values.

Feedback and Review

Review the rollout with users, support staff, and the device-management owner. Combine direct feedback with FileWave check-in data, deployment results, inventory exceptions, Kiosk usage, and recurring ticket categories. Separate one-device failures from repeated workflow failures, then turn repeated issues into a corrected profile, Fileset, Deployment, instruction, or readiness check. Record the sample size and date range so the next refresh team can judge whether the findings apply to its fleet.

Record the resulting checks, exceptions, and owners as the closeout for the refresh. Reuse that checklist for the next enrollment wave, then adjust it from support trends and user feedback.