Managing Dock Manager with Intune#
This page covers advanced configuration of Dock Manager using Microsoft Intune ADMX policies and OMA-URIs. For basic deployment steps, see Dock Manager Deployment Guide.
Note
If new policies have been introduced, you will need to ingest the updated ADMX file. The policies documented here are based on the latest ADMX template. New policies may be added in future releases, so check the Lenovo Tools for Administrators page for updates.
Prerequisites#
Before configuring Dock Manager policies, you must:
- Download the ADMX file – Available in the Dock Manager section on Lenovo Tools for Administrators
- Create a custom Intune profile – Navigate to Devices > Windows > Configuration Profiles and create a new Custom profile
- Ingest the ADMX – Import the template using the OMA-URI procedure in the ADMX Ingestion section below
- Understand OMA-URI format – Each policy is configured via an OMA-URI path and XML value
Introduced in the 2208 Intune Service release, custom ADMX and ADML templates can be imported, created, and managed directly in Intune.
ADMX Ingestion#
Sign in to the Microsoft Intune admin center
Navigate to Devices > Windows > Configuration Profiles. Click Create
- Select New Policy > Windows 10 and later for the platform.
- Select Templates for Profile Type and choose Custom from the list and click Create
Enter the required information for the new profile, for example:
-
Name: Lenovo Dock Manager Configuration
-
Description: (Optional)
On the Configuration Settings screen, click Add and enter the following:
-
Name: Dock Manager ADMX Ingest
-
Description: (Optional)
-
OMA-URI: ./Device/Vendor/MSFT/Policy/ConfigOperations/ADMXInstall/DockManager/Policy/DockManager
-
Data Type: String
-
Value: Copy the contents of the Dock Manager ADMX file into this field
Note
The Group Policy Template File that contains the ADMX can be found under the Dock Manager section on Lenovo Tools for Administrators page.
Policy Overview#
Quick Reference#
Use this table to quickly find the policy you need by category. Click any policy name to jump to its detailed configuration section:
| Policy Name | Category | Type | Purpose |
|---|---|---|---|
| Command | System | Action | Send commands to Dock Manager (e.g., check for updates) |
| Ask Before Firmware Update | General | Boolean | Prompt user before firmware installation |
| Auto Update | General | Boolean | Enable automatic Dock Manager software updates |
| Enable Notifications | General | Boolean | Show notifications during firmware operations |
| Firmware White List | General | String | Restrict firmware updates to approved versions |
| Hide Update Software Button | General | Boolean | Remove update button from UI |
| Log File Age to Cleanup | General | Integer | Auto-delete log files older than N days |
| Log File Max Size | General | Integer | Rotate logs when size exceeds N KB |
| MAC Address Clone Enabled | General | Boolean | Enable MAC address cloning feature |
| Port | General | Integer | Proxy server port (default 8080) |
| Proxy Server | General | String | Proxy address for firmware downloads |
| Repository Location | General | String | UNC or local path to firmware repository |
| Update Firmware on First Connection | General | Boolean | Auto-update when dock first connects |
| Update Firmware Without Disconnect | General | Boolean | Update supported docks without unplugging |
| Frequency | Scheduler | Enum | Task schedule frequency (Daily/Weekly/Monthly) |
| Run At | Scheduler | Time | Time of day for scheduled task (24-hour format) |
| Run On | Scheduler | String | Days of week (Sunday–Friday) |
| Run Days | Scheduler | String | Days of month (1–31) for monthly tasks |
| Run Month | Scheduler | String | Months (January–December) for monthly tasks |
| Run Monthly On | Scheduler | String | Week pattern (First/Second/Last) for monthly tasks |
Policy Categories#
Firmware Update Control#
Control how and when firmware updates occur.
Ask Before Firmware Update#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/AskBeforeFirmwareUpdate
Purpose: Prompt user before installing firmware updates on connected docks.
Values:
<enabled/> <!-- Show prompt, user can decline -->
<!-- or -->
<disabled/> <!-- Install firmware silently without prompting -->
Auto Update#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/AutoUpdate
Purpose: Enable automatic check for Dock Manager software updates.
Values:
<enabled/> <!-- Auto-check and install Dock Manager updates -->
<!-- or -->
<disabled/> <!-- Manual update only -->
Update Firmware on First Connection#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/UpdateFWOnFirstConnection
Purpose: Automatically update dock firmware when a dock is connected for the first time after Dock Manager installation.
Values:
<enabled/> <!-- Auto-update on first connection -->
<!-- or -->
<disabled/> <!-- Manual update only -->
Update Firmware Without Disconnect#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/UpdateFWWithoutDisconnect
Purpose: Allow specified dock models to update firmware without disconnecting from the computer (if supported by dock firmware version).
Only enable this after upgrading docks to a supported firmware version that handles live updates.
Example – Enable for Thunderbolt 3 Dock Gen 2:
Example – Multiple dock types:
Firmware White List#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/FWWhiteList
Purpose: Restrict firmware updates to approved versions only. Devices can only upgrade to whitelisted versions.
Format: DOCK_TYPE:VERSION1,VERSION2;OTHER_TYPE:VERSION3
Example:
Dock types are 4-character codes found on the dock label or in the Supported Docks list.
Network & Repository Configuration#
Manage firmware download sources and proxy settings.
Repository Location#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/RepositoryLocation
Purpose: Specify where Dock Manager should download firmware (internet or local repository).
Example – Network share:
Example – Local path:
Proxy Server#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/ProxyServer
Purpose: Configure a proxy server address for downloading firmware over a corporate proxy.
Example:
Port#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/Port
Purpose: Configure the proxy server port for firmware downloads.
Example – Use port 3128:
User Experience & Display#
Control how Dock Manager appears and interacts with users.
Enable Notifications#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/EnableNotifications
Purpose: Show user notifications during firmware download and update operations.
Values:
<enabled/> <!-- Display notifications -->
<!-- or -->
<disabled/> <!-- Silent operation, no notifications -->
Hide Update Software Button#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/HideUpdateSoftwareButton
Purpose: Remove the update button from the Dock Manager UI.
Values:
Logging & Maintenance#
Manage Dock Manager log file behavior.
Log File Age to Cleanup#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/LogfileAgeToCleanup
Purpose: Automatically delete log files older than the specified number of days.
Example – Delete logs older than 30 days:
Log File Max Size#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/LogfileMaxSize
Purpose: Rotate log files when they exceed the specified size in KB.
Example – Rotate when logs reach 1024 KB (1 MB):
Hardware Features#
Enable or disable hardware-specific features.
MAC Address Clone Enabled#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~General/MacAddressCloneEnabled
Purpose: Enable or disable MAC address cloning functionality on supported docks.
Values:
Scheduling Configuration#
Define when Dock Manager checks for and installs firmware updates.
Configure these policies together to define a complete schedule. They are interdependent based on the Frequency setting:
- DAILY – Uses only Run At
- WEEKLY – Uses Run At + Run On (days of week)
- MONTHLY – Uses Run At + Run Month + Run Days, OR Run At + Run Monthly On + Run On
Frequency#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~Scheduler/Frequency
Purpose: Set how often the firmware check runs: Daily, Weekly, or Monthly.
Values:
Run At#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~Scheduler/RunAt
Purpose: Set the time of day (24-hour format) when the scheduled task runs.
Example – 2:00 AM:
Run On#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~Scheduler/RunOn
Purpose: Specify days of the week for the task (used with WEEKLY or MONTHLY frequency).
Example – Sunday and Friday:
Run Days#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~Scheduler/RunDays
Purpose: Specify days of the month (1–31) when the task runs (MONTHLY frequency only).
Example – 1st and 15th of each month:
Run Month#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~Scheduler/RunMonth
Purpose: Specify which months the task runs (MONTHLY frequency only).
Example – Every other month (Jan, Mar, May, Jul, Sep, Nov):
Run Monthly On#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~Scheduler/RunMonthlyOn
Purpose: Specify week pattern for monthly tasks (e.g., "First Monday", "Last Friday"). Used with Run On.
Example – First and Last day of the month:
Example – First and second Tuesday (used with RunOn: Tuesday):
System Commands#
Send direct commands to Dock Manager for remote management.
Command Policy#
OMA-URI: ./Device/Vendor/MSFT/Policy/Config/DockManager~Policy~LenovoCompany~DockManager~Command/CommandString
Purpose: Send commands to Dock Manager for remote management. Currently supports:
- 1 – Check for Dock Manager software updates and install if available
To resend the same command, update the timestamp in SendTime_Prompt.
Example – Check for updates:
<enabled/>
<data id="CommandString_Prompt" value="1"/>
<data id="SendTime_Prompt" value="2024-06-01 03:12:05Z"/>
To disable:
Format Reference#
| Setting | Format | Examples |
|---|---|---|
| Time (Run At) | 24-hour HH:MM:SS | 02:00:00, 14:30:00, 23:59:59 |
| Days of Week (Run On) | Full day names, comma-separated | Monday,Friday / Sunday |
| Days of Month (Run Days) | Numbers 1–31, comma-separated | 1,15 / 5 |
| Months (Run Month) | Full month names, comma-separated | January,March,May / December |
| Week Pattern (Run Monthly On) | First/Second/Third/Fourth/Last, comma-separated | First,Last / Second |
| Dock Types | 4-character code (dock label) | 40AY, 40B0, 40AN,40B7 |
| Dock Firmware | Version numbers, comma-separated | 3.0.85,3.0.92 |
| Frequency | Enum: DAILY, WEEKLY, MONTHLY | WEEKLY |
| Port | Integer | 3128, 8080, 80 |
| Path | UNC or local | \\share\path / C:\path |
| URL | HTTP or HTTPS | http://proxy.company.com |
Common Scenarios#
Scenario 1: Enable Auto-Updates with Weekly Firmware Checks
Check for firmware updates every Sunday at 2:00 AM without user prompts.
Policies to configure:
- Auto Update – Enable
- Ask Before Firmware Update – Disable
- Frequency – Set to WEEKLY
- Run At – Set to 02:00:00
- Run On – Set to Sunday
Configuration example:
<!-- Auto Update -->
<enabled/>
<data id="AutoUpdate_Prompt" value="1"/>
<!-- Ask Before Firmware Update (disabled) -->
<disabled/>
<!-- Frequency: Weekly -->
<enabled/>
<data id="Frequency_Dropdown" value="WEEKLY"/>
<!-- Run At 2:00 AM -->
<enabled/>
<data id="RunAt_Prompt" value="02:00:00"/>
<!-- Run On Sunday -->
<enabled/>
<data id="RunOn_Prompt" value="Sunday"/>
Scenario 2: Restrict Firmware Versions with White List
Only allow specific firmware versions for supported docks.
Policies to configure:
- Firmware White List – Enable with dock types and approved versions
Configuration example:
Note: Dock model codes are 4-character identifiers (see Supported Docks)
Scenario 3: Internal Repository with Proxy Download
Configure Dock Manager to pull firmware from a local network share via proxy.
Policies to configure:
- Repository Location – Set to network share path
- Proxy Server – Set to proxy address
- Port – Set to proxy port
Configuration example:
Next Steps#
After configuring Dock Manager policies in Intune, see these related topics:
- Dock Manager Deployment Guide – Deploy Dock Manager with ConfigMgr and Intune
- Dock Manager Troubleshooting – Troubleshoot deployment and scheduling issues
- Dock Manager FAQ – Frequently asked questions and support resources