Does the Deployment ID change at any time?

License holders should be aware that changes or updates to the hardware or network components of the system on which %product_name% is installed could result in changes to the Deployment ID.

Cause: NIC teaming, also known as Load Balancing/Failover (LBFO) or NIC bonding, allows you to combine multiple physical network adapters into a single logical network card

When using teamed NIC, because the primary team member (primary NIC) might change in a non-deterministic manner (e.g. at each boot, NIC disable/enable action, or other reconfiguration activities), the primary team member might change, and the MAC address of the team might vary.

• Since MetaDefender Core’s deployment ID is based partly on the MAC address of the network adapter, varying MAC address also leads to deployment ID changes and deactivation of license - causing service interruptions.

Example of a teamed NIC:

• Microsoft Network Adapter Multiplexor Driver is a kernel mode driver to team up with multiple network adapters to provide one unified device to utilize the entire network bandwidth and load balancing among underlying adapters.

Solution: To avoid MetaDefender Core service interruption due to changing deployment ID, please perform the necessary steps to ensure the teamed NIC’s physical address remain the same after reboot.

• One way to achieve this is by configuring a static MAC address for the teamed NIC.