Manufacturer Specific Considerations

Apple Specific Considerations

FileWave loves Apple, and so do our customers.  If you happen to be one of the organizations that have chosen to incorporate Apple devices into their infrastructure, from iPads to MacBooks, here are some crucial considerations for a successful refresh and (re)Enrollment:

The Apple Program Considerations

You no doubt already know about the various Apple Programs, such as ABM/ASM/VPP/DEP/MDM and even APN.  Each of these programs, explained below, provide critical roles during device enrollment.  As with everything else (re)enrollment, pre-work is good work, and each program has it's own pre-requisites (and sometimes lead-time).  You'll want to review the specifics of each below:

Apple Push Notification (APN)

Apple Push Notifications are the method by which FileWave initiates communication with your devices through the Apple MDM framework.  Every FileWave server must have a valid APN token assigned, and it must be refreshed annually.  Before any major project, you should make sure your APN has plenty of life left (and you can renew early).

Apple School Manager/Apple Business Manager Integration (ASM/ABM)

Apple School Manager (for educational institutions) and Apple Business Manager (for businesses) are central to the administration of Apple devices. When integrated with FileWave, these platforms provide granular control and enhanced capabilities. They allow you to:

But, you can't use these programs if they aren't established and integrated with FileWave.  So, in particular if you are setting up a new environment, you'll want to give yourself plenty of time before your project to enroll.

Volume Purchase Program (VPP) and Device Enrollment Program (DEP)

The VPP ( Volume Purchase Program ) and DEP ( Working with Apple’s Device Enrollment Program ) play a critical role in managing applications and automating device enrollments. Their integration with FileWave allows for:

VPP and DEP also require initial setup, and shouldn't be left to the last minute.  DEP profiles control device configuration at setup time, and you'll want to make sure you procure all licenses through VPP well ahead of time to avoid last-minute congestion on Apple systems.  (Remember you aren't the only organization enrolling 5,000 devices today).

Using FileWave's DEP profile assignment wizard is a great way to pre-configure your devices automatically, even before they leave the box.

Apple MDM Framework (and known issues)

Apple were very innovative with the creation of the MDM framework, and it allows for controlled management of endpoints through known, controlled mechanisms.  It is very structured, and means that MDM vendors provide support in very common and defined manners.  Knowing for instance that an MDM command to InstallApplication X won't be able to run until the push notification is able to be sent to the device plays into your capacity planning for (re)enrollment.  So, it is structured, but it (like any other system) isn't perfect and there are some additional recommendations we'd make to ensure success:

Non-VPP Apps

Everyone has  some apps that aren't in VPP that they need to push out.  If filesets, fileset magic, .APP installs and custom filesets aren't quite enough options for you :), take a look at Installomator - The one installer script to rule them all (macOS Script) to easily push out over 450 different applications. Completely opensource, and completely super!

Use the Kiosk

With all platforms, but particularly iOS/iPadOS, using the Kiosk ( Kiosk ) to allow your customers to easily and effectively install pre-approved applications and profiles will help you both:

Microsoft Specific Considerations

FileWave may love Apple, but we also love Microsoft Windows.  (In the same way that you don't have a favorite child)

Microsoft's Windows platform is widely used in various organizations due to its versatility and familiarity. For a successful device refresh or (re)Enrollment of Microsoft devices, these factors should be considered:

Windows Autopilot and MDM

Windows MDM ( Microsoft Windows MDM ) offers an advanced set of capabilities that allow IT teams to pre-configure Windows devices for immediate deployment. With FileWave and Autopilot working in unison, you can:

Imaging Systems when you can't get to MDM-only

Depending on your situation you may not be able to simply enroll devices in Windows MDM and let Filesets install and configure everything. If that's where you are at then take a look at:

Client Deployment

If dealing with enrollment of an existing fleet of devices, but one not yet under FileWave's care, remember that you can create a custom FileWave Client installer at custom.filewave.com.  This client installer is a standard MSI installer and can be distributed manually, through a GPO, or even through a legacy management system.  It is very flexible, and when combined with the use of placeholders and custom fields, you can pre-assign all device content to deploy automatically on enrollment.

Active Directory Integration

It isn't isolated to only MSFT of course, but Active Directory (AD) or AzureAD are usually an integral part of user management in the Microsoft ecosystem. By integrating AD with FileWave, you can enhance user and device management, including:

Updates and Patch Management

Microsoft consistently releases updates for Windows OS and their suite of office applications. An effective patch management strategy is crucial to maintain security and productivity. FileWave can:

By considering these manufacturer-specific aspects and leveraging FileWave's integrations and capabilities, you can ensure a smooth and efficient device refresh or (re)Enrollment process.

Utilize solutions like Microsoft winget to patch 3rd party applications. 

Google Specific Considerations

FileWave supports two distinct Google device platforms, Chromebooks and Android devices. Each platform has its own setup and management considerations.

Chromebook Integration

FileWave support for Chromebooks is primarily focused on device visibility and organizational unit (OU) management. That makes it useful for finding devices quickly, checking where they belong, and moving them between OUs so the correct settings and extensions are applied.

Chromebooks still need to be enrolled before FileWave can manage them. The Google integration is configured once at the organization level, so after that setup is complete, FileWave can work with the Chromebooks in your environment without touching each device individually.

Chrome Education Upgrade / Chrome Enterprise Upgrade and Android Enterprise

These services extend device management for education and enterprise environments. When they are integrated with FileWave, they can provide:

Android and Google Play management

Google Play's large app catalog can be difficult to manage manually. FileWave can help you:

Google as an identity provider

FileWave admins can also authenticate through Google's identity provider services.

Keeping these Google-specific considerations in mind can make device refresh and re-enrollment projects go more smoothly.