On Mac devices that use Apple Silicon (M1 and M2 chips), the Flexera Inventory Agent may report the hardware model as VirtualMac2,1 instead of the physical model name.
This happens because Apple’s Virtualization framework presents virtual hardware identifiers to the operating system, which the agent accurately collects. Intel-based Macs continue to report their physical model identifiers as expected.
This article explains why this behavior occurs and how you can verify the hardware model that the Mac operating system provides to the inventory agent.
Why this happens
Apple’s Virtualization framework abstracts hardware details for both physical and virtual environments on Apple Silicon devices. Because of this, system calls return a virtual model identifier (for example, VirtualMac2,1), even on physical machines.
The Flexera Inventory Agent reports this information exactly as provided by the operating system.
To verify the hardware model, run the following command on the host machine or virtual machine to confirm what the operating system reports:
system_profiler SPSoftwareDataType SPHardwareDataType
Check the Model Identifier and Chip fields in the output.
Example on Apple Silicon (M1)
Hardware Overview:
Model Name: Apple Virtual Machine 1
Model Identifier: VirtualMac2,1
Model Number: VM0001LL/A
Chip: Apple M1 Pro (Virtual)
Total Number of Cores: 8
Memory: 4 GB
Example on Intel Mac
Hardware Overview:
Model Name: MacBook Pro
Model Identifier: MacBookPro16,1
Processor Name: 6-Core Intel Core i7
Processor Speed: 2.6 GHz
Memory: 32 GB
When you compare the operating system output with the agent’s NDI data, you can confirm that the reported model identifier reflects Apple’s Virtualization behavior.
Related Articles
Application usage metering using the FlexNet inventory agent 195Number of Views Understanding Flexera One UI session timeout behavior 13Number of Views VMware stand-alone inventory agent esxquery.exe for FlexNet Manager Suite & Flexera One ITAM 121Number of Views FlexNet Inventory Agent behavior for detecting Java installations 20Number of Views Common causes of high CPU usage by the ndtrack component of FlexNet inventory agent 410Number of Views
Hi, I am Reva - Ask me anything.
No new updates
Thanks for the feedback!
Your feedback has been saved.Rate this response:
Add Additional feedback ( Optional )
Are you sure you want to cancel
the case creation?
Are you sure you want to cancel the case creation?
Are you sure you want to close this case
| Products | Region | Phone Numbers |
|---|---|---|
| FlexNet Operations FlexNet Embedded FlexNet Publisher FlexNet Connect FlexNet Code Insight InstallAnywhere InstallShield |
North America * |
+1 630-332-2513 (toll) +1 877-279-2853 (toll-free in North America) |
| Europe * |
+44 1925 944367 (toll) +44 800 047 8642 (toll-free in Europe) |
|
| Japan * | +81 3-4540-5335 (select option 2) | |
| Australia * |
+61 3 9895 2177 +61 1800 560 603 (toll-free in Australia) |
|
|
Usage Intelligence (formerly
Revulytics) Compliance Intelligence |
Please use the Case Portal to submit your support ticket or reach out to your Revenera contact. | |
Revenera Assistant
Case id: 00001065
Activity: Status change: 2 hours ago