Lenovo Device Orchestration is compatible with:
This includes both Lenovo-branded products and third-party
PCs.
The UDC Agent is provided as a .exe file. It can be deployed either by running it directly on the devices or using a third-party MSI distribution tool. The installation is transparent, does not require a reboot, and does not include any kernel-mode components.
For detailed instructions, refer to the LDO Knowledge
Base.
The Lenovo Device Orchestration platforms’ UDC (Universal
Device Client) agent is a patented, ultra-lightweight solution. It collects
device data and transmits it securely to the Lenovo Device Orchestration solution’s
cloud service, generating minimal network traffic.
The agent runs as a background service, remains invisible to the end user, and
does not include any kernel-mode components.
Network usage is minimal, with only a small bandwidth
overhead—typically just a few megabytes per day.
CPU usage depends on the specific processor, but testing has
shown it typically remains below 2%, with occasional spikes up to around 5%.
These results were observed on a device with an Intel Core Ultra 7 165U @ 1.70
GHz.
LDO’s UDC agent uses approximately 75 to 100 MB of storage once installed.
The LDO solution includes several built-in plugins, each
designed to perform specific functions.
Plugin Name |
CPU Percent |
Memory Virtual Mb |
Memory Physical Mb |
dmsivantiplugin |
0 |
62 |
63 |
dmsplugin |
0 |
95 |
89 |
dmstccplugin |
0 |
40 |
34 |
dmsthinbiosplugin |
0 |
50 |
48 |
dmsutilitiesplugin |
0 |
42 |
34 |
dockmgr |
0 |
39 |
2 |
dockmgr.svc |
0 |
24 |
32 |
Once the agent is installed, it typically takes 2 to 3 minutes for data to begin appearing in the portal.
Yes. LDO is only compatible with systems that have a unique serial number defined in their BIOS.
If a device is powered on but not connected to the internet, it will accumulate data locally in a "queue." Once the device reconnects to the internet, the UDC will send all accumulated data to the cloud.
For Patch users:
If the device is not connected at the time of the daily scan (6 PM ET), the data for that day will be missed.