27928: Acronis Snap Deploy 4: Deployment Fails if the OS Deploy Server Is on a Machine with Multiple NICs

As a workaround, disable one of the NICs in Device Manager

This article applies to:

  • Acronis Snap Deploy 4

Symptoms

  1. You have Acronis OS Deploy Server installed on a machine with multiple NICs and only one of the NICs is plugged in the network;
  2. A deployment attempt (both multicast and unicast) fails with the following error:

    In the product:

    Failed to start multicast session
    Failed to connect to FileServer

    In the Acronis OS Deploy Server logs (ProgramData\Acronis\snapdeploy\FileServer\Logs) there is the following error:

    StartMulticast: Failed to bind on specified address 169.254.XXX.XXX

Cause

The NICs not plugged in the network have internal IP Addresses that confuse the Acronis OS Deploy Server.

(!) The issue does not reproduce on all machines.

Solution

As workaround, do the following:

  1. Disable the unused NICs Windows Device Manager;
  2. After disabling the unused NICs, restart the Acronis OS Deploy Server service and Acronis PXE Server service:
  3. Hit Start-Run and type in services.msc
  4. Right-click on the following services and select Restart:
    • Acronis File Server service
    • Acronis PXE Server service

More information

See also Acronis Snap Deploy 4.

Components:

Provide feedback on this information

Please use the form below to send us your comments. We read all feedback carefully.

Please note that we cannot individually respond to all comments. We do read, analyze and work to improve our content, products and services based off the feedback we receive. Should you need technical or customer service assistance please use our Contact Support Wizard.

Thank you for taking the time to send us your thoughts, we truly value your input.

To protect your privacy, do not include contact information in your feedback.