How to Track Company Devices and Installed Software in the UAE and GCC

Which inventory questions should your IT team be able to answer?

Start with the decisions you need to make, rather than the appearance of a dashboard:

• Which company computers are enrolled in management?
• Which operating-system and application versions have they reported?
• Which devices have stopped reporting recently?
• Which company assets are missing from the management inventory?
• Which records need checking before an employee leaves or a device is retired?
• How do detected software installations compare with purchased entitlements?

These questions need different evidence. A device reporting an application does not prove the company owns a licence for it. A serial number in a management console does not, by itself, establish who purchased the device or who currently holds it.

Build the inventory around three kinds of information

Use the following framework when specifying your requirements. It describes what to reconcile, not a claim that every field is collected automatically by FileWave on every platform.

Decide which system is authoritative for each field. For example, an employee assignment may belong in an asset register, while software version information should come from a supported endpoint collection method.

In FileWave, business values such as an asset tag or department can be held as Custom Fields for use in reports and Smart Groups (device groups FileWave builds from criteria); a value an administrator enters is recorded data, not a device measurement (FileWave: Custom Fields).

Use a stable identifier to connect the records where possible, and review mismatches instead of silently overwriting them. Custom Field values can be imported from a CSV file matched on an identifier you choose, such as FileWave ID or serial number; FileWave notes that a serial number helps only where it is populated and unique, that device names can be duplicated or changed, and that the import updates only fields already associated with each device (Custom Fields).

Where FileWave fits in the process

FileWave’s inventory and reporting capabilities help IT teams examine the devices they manage. Its Reports match stored device records against criteria you choose, covering devices, installed applications and versions, or licences; a report reads the inventory the server already holds and does not guarantee a fresh measurement from the device (FileWave overview; creating a report; inventory reports).

The available details and collection behaviour should be checked for the operating systems and enrolment methods in your environment. For example, FileWave cannot inventory personal apps on an iPhone or iPad enrolled through Apple User Enrollment, the method for employee-owned devices (iOS and iPadOS app inventory).

During an evaluation, choose the exact fields your team needs and ask to see them collected from representative devices. Avoid accepting a generic dashboard demonstration as proof that every reporting requirement is met. FileWave itself calls its dashboard data a summary to check against the underlying records. Reports can be exported as CSV files or, once mail is set up, emailed on a schedule, though a scheduled report includes only the devices its owner’s account can see (Dashboard overview; exporting data; scheduled reports).

For the broader explanation of the platform, read our FileWave UEM and MDM guide.

Why a last-reporting check matters

An inventory screen can contain information about a device that is currently offline. FileWave’s technical documentation notes that older inventory can remain visible while a device is offline (FileWave reporting overview).

FileWave records two different times. Last Connect is the last time a device spoke to the server at all, and only the macOS and Windows clients update it. Last Connected is the inventory field: the last time the device sent information about its hardware, software and custom fields. When a report looks for devices with a recent change, such as a software update, FileWave recommends also requiring inventory data from the same time frame, which keeps devices with stale inventory out of the report (FileWave: Last Connect vs. Last Connected).

On Chromebooks, the inventory time comes from FileWave’s optional Inventory Extension, which by default reports once a day and only when a user is signed in with Chrome open (Chromebook Inventory Extension).

That distinction matters when deciding whether an application is installed, whether an update is complete or whether a laptop is still in active use.

Update status needs the same care. For Apple devices updating through declarative device management (DDM), FileWave’s Pending OS Version field shows the version being installed, not a finished update, and Windows update data, which FileWave documents as reported hourly, is only as current as the last report. Compare update results with the operating-system builds devices report in inventory (Apple OS updates; Windows update reporting; OS and software updates).

Agree a reporting-freshness rule that fits your operation. A laptop held in storage and a laptop used daily should not necessarily trigger the same follow-up process. Document the exception instead of treating every missing report as a lost device.

For a regional team working from Dubai, the goal is a clear view of which records can support today’s decision and which need investigation across the other offices.

Confirming that a software rollout actually completed is a separate check, covered in our guide to deploying software remotely across company computers.

Reconcile inventory before renewals and staff changes

Before a software renewal

Compare relevant installation records with your purchasing and subscription records. Investigate devices no longer in use and applications that appear outside the expected group.

Use this as an input to a licence review. Installation counts alone may not match a licence model based on users, concurrent sessions or another entitlement measure. Check the application’s actual terms and records.

FileWave’s License Management can support that review, but each count measures something different: Apple Apps and Books counts, synchronised from Apple Business (formerly Apple Business Manager) or Apple School Manager, show licences acquired and allocated, not apps installed or used; inventory-based records count installations that devices report; Fileset-based records count only deployments made through that Fileset. FileWave states that its compliance label compares only the records and counts configured in FileWave and is not independent legal proof of entitlement (FileWave: License Management).

When an employee leaves

Compare the employee’s assigned assets with management records and the physical return process. Record what was returned, what needs follow-up and which records require updating.

Keep physical return, account access changes and endpoint actions as separate checks. A management record cannot confirm that a laptop has been handed back to the company.

Before retiring a device

Reconcile the device identifier, business owner and intended next step. Follow your approved process for removing data and recording disposal, return or reassignment. Our guide to secure data erasure and drive decommissioning covers the data-removal step.

FileWave can send a remote wipe to MDM-enrolled Macs, iPhones and iPads, Android Enterprise devices, Chromebooks (as a Powerwash, with Google Admin Console still deciding whether the Chromebook stays managed) and Windows computers enrolled through Windows MDM, but not to Windows computers with only the FileWave Client or to user-enrolled devices, and a sent command is not evidence of erasure. Take the device out of management before deleting or archiving its record, then check that it does not reappear after the next check-in or platform sync: FileWave warns that an Apple device still assigned for Automated Device Enrollment can enrol again after a wipe unless it is released (wipe a device; Wipe Device for macOS; wipe a Windows MDM device; removing Android devices; Powerwash on ChromeOS; device actions; retiring a device).

Do not treat removing a record from an inventory system as proof that the device has been sanitised.

What to demonstrate in an inventory evaluation

Bring a sample of the real environment: different device platforms, a remote computer, an offline device and examples of the business records you want to reconcile.

When testing reports, count distinct FileWave IDs or reliable serial numbers rather than rows: an application report can return several rows for one device, and a report with no rows does not show that the fleet is fully inventoried (inventory reports).

Keep the agreed field list and sample results. They provide a more useful basis for a purchasing decision than a long list of reporting features without context.

Sources

Statements about FileWave cite FileWave’s website, documentation and announcement, checked on 22 September 2026. The table of information types is a planning framework, not a list of fields FileWave collects on every platform.

• FileWave: Unified Endpoint Management (product overview)
• FileWave knowledge base: How does FileWave work?
• FileWave knowledge base: Last Connect vs. Last Connected
• Reports and fields: creating a report; inventory reports; iOS and iPadOS app inventory; Custom Fields; Dashboard overview; exporting data; scheduled reports
• Reporting freshness and updates: Chromebook Inventory Extension; Apple OS updates; Windows update reporting; OS and software updates
• Licences, wipe and retirement: License Management; wipe a device; Wipe Device for macOS; wipe a Windows MDM device; removing Android devices; Powerwash on ChromeOS; device actions; retiring a device; FileWave 16.4.1 release notes; VPP and ADE preferences
• FileWave: PRO TECHnology and FileWave expand unified endpoint management across the Middle East, including Saudi Arabia (1 July 2026)

Frequently asked questions