- Docs
- Client Apps
- Desktop App
- Large Scale Deployments
- Microsoft Intune
Microsoft Intune
For organizations using Microsoft Endpoint Manager or Microsoft Intune to manage devices, Files.com provides a downloadable pre-packaged .intunewin
binary file of the Desktop App for Windows. This format is designed for use with the Windows app (Win32) deployment model within Intune.
Download the Files.com Windows Desktop App for Microsoft Intune.
Files.com also offers a signed .pkg
installer for macOS, compatible with Intune’s Line-of-Business (LOB) app deployment model for Mac, enabling remote installation on managed macOS devices.
Use the .intunewin
or .pkg
binaries if you plan to deploy the Files.com app at scale across enrolled devices, manage installation status and updates from a central console, enforce silent installations with detection and remediation rules, or standardize app deployment across multiple teams and locations.
Intune Configuration to Deploy Windows Desktop App
Here are the recommended configuration values to deploy the Files.com Windows Desktop App using Intune.
Application Installation Settings
Install command: "Files.com Desktop v6.exe" /s /norestart /v/qn
Uninstall command: "Files.com Desktop v6.exe" -uninstall /s /norestart /v/qn
Install behavior: System
Device restart behavior
Leave as Default. Intune will interpret the installer’s return codes and may require a restart if the application setup requests one.
Requirements
Supported OS: Windows 10 (64-bit, version 22H2 or later) or Windows 11; Architecture: 64-bit only.
Detection Rules
Detection rules are required in Intune to confirm the app is installed and to prevent repeated reinstall attempts. For the Files.com Desktop App, set Detection mode to Manual and Rule type to Custom, then use the PowerShell script shown below. Set Run script as 32-bit on 64-bit clients to No and Enforce signature check to No.
$exePath = "C:\Program Files\Files.com\Files.com Desktop v6\Files.com Desktop v6.exe"
if (Test-Path $exePath) {
Write-Output "App found at $exePath"
exit 0 # Success: Detected
} else {
Write-Output "App not found"
exit 1 # Fail: Not Detected
}
Troubleshooting Microsoft Intune Deployments
The most common errors when deploying the Files.com Desktop App via Intune include app installation failure, detection rules not confirming installation, silent install/uninstall errors, and configuration profile mismatches.
The most efficient approach to determine what has gone wrong with an installation is to start with the Intune Admin Center for a high-level view, then drill down to device-side logs for detailed troubleshooting when needed.
Common Error Codes
Status/Code | Meaning | Possible Causes |
---|---|---|
0x87D1041C | Detection rule failed | Detection rule logic incorrect or app not installed |
0x80070002 | File not found | Installer path or file missing |
0x87D103E8 | Timeout expired | App taking too long to install or blocking behavior |
0x87D1041F | Script returned a non-zero exit code | Installer exited with error |
0x87D1041B | Requirement rule not met | Incorrect OS architecture or prerequisites missing |
Using Intune Admin Center to Locate Errors
Within the Intune Admin Center, use the Device view to locate the affected device and see detailed error codes. Alternatively, use the App Deployment view to review the Device install status to view error codes.
Using Intune Management Extension Logs
You can review IME logs on the client machine. These are typically located in %ProgramData%\Microsoft\IntuneManagementExtension\Logs
.
The IntuneManagementExtension.log
provides information about the IME itself, including IME check-ins, policy requests, policy processing, and reporting activities.
The AgentExecutor.log
contains information about App and script deployments from Intune.
The log file AppWorkload.log
captures Win32 app management events on the client. This log file contains all logging information related to app deployment activities conducted by the IME.