Supermicro DCMS Virtual Media Licensing

Provisional: This issue currently has evidence from 7 tickets. Treat entitlement guidance as support-history-backed, but verify purchased options, firmware level, and platform capability before giving a final virtual-media answer (#20099, #21022, #24583, #25797, #42881, #45098, #46239).

Summary

Customers trying to use Supermicro BMC/IPMI virtual media, BMC update workflows, or DCMS/OOB functionality may discover that the required Supermicro Node/DCMS/OOB license was not included with the system or was not activated after firmware work (#20099, #24583, #25797, #42881, #46239). However, virtual-media/local ISO failures are not always entitlement problems: older platforms may still fail to mount local ISO media after BIOS/BMC updates due to age or platform restrictions (#45098). Support resolves these as entitlement/order-record checks, firmware/platform validation, purchase or activation routing, or alternate non-licensed/non-BMC workflows such as local firmware update or bootable USB media (#21022, #25797, #45098, #46239).

Frequency

• 7 tickets cite Supermicro DCMS, virtual-media, OOB license entitlement/activation handling, or platform-age virtual-media limitations (#20099, #21022, #24583, #25797, #42881, #45098, #46239).

Common Causes

1. Virtual media may require a paid add-on license. Customers can open the remote console but may be unable to mount virtual media unless the Supermicro DCMS/Node license was purchased and activated (#20099, #24583, #46239).
2. Firmware or BMC workflow exposes missing entitlement. A firmware update or BMC firmware-update page can prompt for a license/product key even though the system did not originally include that add-on (#25797, #46239).
3. Order records do not show the add-on. Support must verify whether the license was requested on the quote/order before promising an activation key (#24583, #25797, #46239).
4. Platform age or firmware limits can mimic licensing. An older Supermicro blade micro server regained HTML5/iKVM access after BIOS update and BMC update from 1.58 to 1.68, but local ISO virtual-media mounting still did not work; Support treated this as likely age/platform restriction and provided bootable USB guidance instead (#45098).
5. Activation can become a cross-functional commercial follow-up. When a customer purchases the license later, Support/Sales may need to track quote, PO, and activation status until the customer confirms success (#21022).

Diagnostic Steps

1. Collect identifiers used for entitlement lookup. Capture system model/serial, board serial when relevant, and BMC MAC address because the license key may be generated against the BMC MAC (#46239).
2. Confirm the blocked function and platform level. Distinguish virtual-media mounting, BMC firmware-update page licensing, DCMS activation, Java-console failure, HTML5/iKVM console access, and unrelated remote-console access because the remedy differs by feature and firmware/platform age (#24583, #25797, #42881, #45098, #46239).
3. Check quote/order records before giving a key. Verify whether a Supermicro DCMS/Node/OOB license was included, separately purchased, or absent from the original quote discussion (#24583, #25797, #46239).
4. Separate entitlement from warranty and platform limits. Warranty status can affect support scope, but the decisive license question is whether the paid add-on was purchased or requested; if no license prompt/entitlement path appears, validate whether old firmware or platform capability is the blocker (#25797, #45098, #46239).

Solutions

1. Provide the activation path when entitlement exists or is purchased. After purchase/PO handling, Support can coordinate activation guidance and close once the customer confirms DCMS activation succeeds (#21022).
2. Route unpurchased licenses to Sales/quote path. If records show no included license, explain that DCMS/virtual media is a paid add-on and offer Sales Engineering quote routing rather than issuing an activation key (#20099, #24583, #46239).
3. Use an alternate firmware-update method when only the licensed BMC workflow is blocked. For BIOS updates blocked by a licensed BMC page, Support can advise the standard firmware mechanism or built-in UEFI Shell/flash.nsh path with the correct package and README instead of treating the missing license as the only update path (#25797).
4. Use physical media when virtual media remains unavailable for non-license reasons. If BIOS/BMC updates restore console access but do not make local ISO virtual media work on an older platform, provide a bootable USB path for OS installation rather than continuing to treat the case as a licensing issue (#45098).
5. Set expectations carefully for out-of-warranty systems. If the system is outside standard warranty and the license was never ordered, frame continued help as best-effort or commercial routing, not as lost included entitlement (#25797, #46239).

Edge Cases

• A BMC firmware upgrade can make the customer believe a license file was lost, but order review may show the system never included the Supermicro Node/DCMS license in the first place (#46239).
• Remote console access and virtual-media mounting are not the same entitlement; a customer may have remote console access while virtual media remains license-gated, or may regain HTML5/iKVM console access after firmware updates while virtual-media/local ISO mounting remains unavailable because of platform limitations (#24583, #45098).
• Firmware-update licensing gates do not always mean firmware is impossible to update; the supported workaround can be a local/UEFI update path (#25797).

Related Issues

• BIOS BMC Issues
• BIOS Firmware Update
• Warranty Inquiry
• Sales Quote Follow-up