Frequently Asked Questions (FAQ)
General
Policy Deployment
The order of priority when multiple file access settings policies are deployed to an endpoint is as follows,
Allow Temporary Access > Allow Trusted Device > Allow Device policy > Block Device.
If a laptop without built-in LAN has a wireless-block policy applied, you cannot use the standard LAN-recovery method. Use one of these alternatives:
Option 1: External USB Ethernet Adapter (Recommended)
- Connect a USB Ethernet adapter to the laptop
- Connect the adapter to a wired network
- Log into the Device Control Plus console
- Go to Device Control → Policies
- Revoke the wireless-block policy
- The policy revokes within the next 90-minute refresh cycle (or immediately if you manually trigger a check-in)
- Disconnect the adapter once wireless is restored
Option 2: Manual Unenroll via Command Line
- Obtain the unenroll.exe and logger.conf files from your environment
- Transfer these files to the affected laptop via USB or email
- Extract the files to a folder
- Open Command Prompt (Administrator) and run:
unenroll.exe - This removes all Device Control policies and MDM profiles immediately
- After recovery, re-enroll the device and redeploy policies
Option 3: Bulk Deployment of Unenroll (Multiple Systems)
- Go to Configurations → Custom Script → Computer Configuration
- Create new configuration: Name = "MDM Unenroll"
- Execute Script from: Select Command Line
- Command Line:
unenroll.exe - Dependency Files: Upload unenroll.exe and logger.conf
- Check Enable Logging for Troubleshooting
- Select target computer groups needing recovery
- Click Deploy

Create separate policies for macOS and Windows devices and deploy them to the computer group together.
When two policies conflict, the "Allow" option is always given priority.
Windows portable devices include cameras, mobile phones, and media players.
- Operating System (OS) Protection: If the internal hard disk is the designated OS Drive, the system will automatically skip it to prevent a system crash. The drive will remain functional even if the SCSI port block is active.
- Secondary Internal Drives: If you have additional internal hard disks that do not contain the OS, they will be blocked by default under this policy.
- To keep additional internal hard disks active while still blocking the SCSI ports for other devices, you must add those specific drives to the Trusted Devices List.
Compatibility
No. Device Control Plus is designed for endpoint peripherals on Windows and Mac computers only. It does not manage mobile devices or display mobile-specific identifiers such as IMEI.
Device Control supports USB devices (flash drives, external drives, printers), removable storage, portable media devices, and other peripherals connected to Windows and Mac computers.
For mobile device management: Use Mobile Device Manager Plus or the MDM module to manage mobile devices and view IMEI numbers.
Audits and Reports
Use the Device Audit report to identify systems where USB devices are allowed:
- Go to Device Control → Reports → Device Audit
- Look for entries with device type USB or Removable Storage
- Check the Last Action column:
- Allowed = USB device was permitted on that system
- Blocked = USB device was denied on that system
- Filter by Last Action = Allowed to show USB-enabled systems
- Export the report as PDF, XLSX, or CSV
Device Control Plus provides an API endpoint to retrieve blocked device data programmatically.
Endpoint:/api/v3/device-control/blocked-devices
Documentation:Blocked Devices API Reference
Before using the API:
- Ensure your authentication token is valid (tokens expire; re-authenticate if needed)
- Review the full API documentation for request parameters and response format
- For additional API endpoints, see Device Control Plus API Reference
Device Control provides visibility into connected peripheral devices and file operations on external devices, but it has important limitations:
Device Control Captures:
- Device Audit: All connected devices, connection timestamps, users, and Allow/Block actions
- File Tracing: File create, open, modify, copy, move, delete, and rename operations (on-premises only, requires active policy)
- File Shadowing (On-Premises Only): Backup copies of files transferred to external devices
Device Control Does NOT Capture:
- Local file operations: Files deleted directly in Windows Explorer without external device involvement are NOT logged
- Actions unrelated to Device Control: General Windows system actions not involving peripheral devices
- File Tracing without policy: File operations are only captured when an active Device Control policy is deployed
- Pre-policy actions: Activity before Device Control policy deployment or File Tracing enablement is not available
To investigate specific activities:
- Check Device Audit: Go to Reports → Device Control Reports → Device Audit and filter by endpoint, user, and date range
- Check File Tracing: If available, go to Reports → Device Control Reports → File Tracing and search for file operations on the target endpoint
- Check Event Viewer (On-Premises Only): Navigate to Tools → System Manager → [Computer] → Manage → Event Viewer for local Windows logs
- Contact the user: If audit logs are inconclusive, verify the action directly with the user.
Integration
No. Device Control policies are managed only through the console. The built-in Temporary Access feature allows users to request time-limited device access without policy creation.