When FileWave Support Refers an Issue to Apple Enterprise Support
Why FileWave may involve Apple
Some FileWave support cases depend on Apple hardware, software, or service behavior that only Apple can investigate directly. In those cases, FileWave Support may ask you to open an Apple Enterprise Support case and share the case number so both support teams can coordinate.
When this referral is appropriate
You may be referred to Apple Enterprise Support when:
-
FileWave has identified that the issue involves components of Apple hardware, software, or services.
-
Collaboration between FileWave and Apple is required for resolution.
Engaging directly with Apple ensures they are fully aware of your issue's impact and urgency. Sharing your Apple Enterprise Support ticket information with FileWave enables our team to collaborate effectively with Apple on your behalf.
How to open and share the case
When FileWave Support asks you to involve Apple:
-
Visit enterprise.apple.com.
-
Open an official support ticket with Apple Enterprise Support.
-
Provide detailed descriptions, relevant logs, screenshots, and clearly state the impact of the issue.
-
After creating the ticket, share the Apple Enterprise Support ticket number with your FileWave support representative.
If you don't currently have Apple Enterprise Support:
-
Check if your organization has an assigned Apple Systems Engineer (SE). In some cases, the SE is able to escalate the issue within Apple, but this is not always possible.
-
Consider obtaining Apple Enterprise Support for direct official engagement.
Note: Apple Education Support and Apple Enterprise Support are distinct services. Only Apple Enterprise Support facilitates direct collaborative troubleshooting between Apple and FileWave Support.
Enhanced device logs for an AppleCare case (FileWave 17.0+)
When AppleCare requests enhanced device logs, FileWave Central can start and cancel the collection remotely. This workflow requires FileWave 17.0 or later and a supervised, MDM-enrolled device running iOS 27, iPadOS 27, macOS 27, or tvOS 27 or later. It is not available for visionOS, User Enrollment, or placeholder devices.
The AppleCare token authorizes the collection for a support case. Obtain that token from AppleCare; FileWave does not generate it. The token is not the Apple support case number you share with FileWave Support. Ask AppleCare to confirm your support agreement and the token appropriate to the device and session before starting collection.
Before requesting logs: Confirm the intended device and the collection request with AppleCare, and follow your organization’s privacy and approval requirements. This is a diagnostic collection and upload to Apple, not a local-only export. Keep the token, diagnostic data, and identifying screenshots within approved support channels.
Plan for user consent
Ask AppleCare for the token appropriate to the device and session. An interactive session prompts the device user for consent; the user can approve collection and upload, choose to review information before uploading, or cancel. A non-interactive session displays a notification and collects and uploads in the background. Do not assume every session requires a user to approve an upload: the permitted flow depends on the device and the AppleCare token.
Request collection in FileWave Central
- In Clients, select the device for the AppleCare case.
- Right-click the device and choose MDM > Trigger Enhanced Log Collection….
- In the Enhanced Log Collection dialog, enter the AppleCare token for the requested session, then click Trigger.
- If the device requests consent or a follow-up response, have its user review and respond to the prompts. An accepted MDM command is not confirmation that collection or upload has finished.
- Open Client Info > Device Details and review Enhanced Logging Status, Enhanced Logging Timestamp, and Enhanced Logging AppleCare Token. The timestamp records the last status change. The status, token, and timestamp can arrive in separate device reports, so do not assume that newly displayed values already describe the same request. Check that the reported token and status timing correspond to the requested session; if they do not, wait for further reports or contact Support. Central also displays notifications when the device reports a changed status.
Check the result and follow up
| Status | What to check |
|---|---|
| Waiting for consent | The device is waiting for the user to consent to collection. |
| Collecting | Collection is in progress. |
| Follow up question | The device is waiting for a user response. |
| Upload consent | The device is waiting for the user to approve uploading the logs. |
| Uploading | Upload is in progress; it has not yet finished. |
| Finished | The device reports that the session has finished. Follow up with AppleCare to confirm the diagnostics are available for the case. |
| Failed | The session failed. Record the reported status and timestamp for Support. |
| Cancelled | The session was cancelled. |
| Declined | The user declined the session. |
Cancel a running session
To request cancellation, right-click the same device and choose MDM > Cancel Enhanced Log Collection. No AppleCare token is required for the cancellation command. Check the device’s reported status afterward; sending the command alone is not confirmation that the device has cancelled the session.
Keep AppleCare diagnostics separate from FileWave Server bundles
Enhanced Log Collection gathers diagnostics from the selected Apple device for AppleCare. Server > Upload Support Bundle instead collects FileWave Server logs, diagnostics, and a database dump and uploads them to FileWave Support. Use the workflow requested for your case; one does not replace the other. See FileWave Support Resources for the Server-bundle procedure, or FileWave Log File Locations when Support requests individual FileWave logs.
Current known issues involving Apple
The following table lists known issues currently under investigation by FileWave in collaboration with Apple. Please note that even if your issue is listed here, opening an Apple Enterprise Support case helps communicate customer impact more clearly to Apple.
| FileWave DSL Ticket | Description | Workarounds | Apple Enterprise Ticket | Status |
|---|---|---|---|---|
| DSL-1292 |
When attempting to re-enroll an Apple device previously associated with a DEP profile into FileWave, the device may bypass the expected Automated Device Enrollment (ADE) workflow, enrolling instead as an unmanaged device. |
Currently, the recommended workaround is to remove the device’s DEP association in FileWave, perform a DEP sync with Apple, then re-apply the DEP association within FileWave and perform an additional DEP sync. |
102529820471 | In Progress |
| DSL-1366 |
Clients stuck at Handled via MDM and require a reboot of the entire OS to successfully finish installing profiles |
Rebooting the client. | 102592078127 | In Progress |
|
Unable to enroll iOS 16 or older devices via ADE/DEP |
None at this time. Apple is investigating and is aware of this. | 102613991439 | In Progress |
No comments to display
No comments to display