• Home
  • Consulting
  • Contact Us
    • About this site
    • Contact Wayne
    • Media Room
    • Wayne’s Bio

SBSFAQ.COM

Supporting IT Pro's & MSP's since 2000

  • Blog
  • FAQs
  • Reviews
  • Downloads

Error applying Network Adapter changes on Live Migration or Hyper-V Replica

July 3, 2017 by Wayne Small 7 Comments

Recently I setup a new Windows Server 2016 Server with Hyper-V in my home lab environment.  I configured Hyper-V Replica to replicate some of the VMs from the older Windows Server 2012R2 system over to the new 2016 Server.  Replication went fine and today I attempted to failover to the new system so I could repurpose the old server hardware.  Planned Failover went fine and when I went to connect the Network cards of the VMs on the new server, I was greeted with the error below “Error applying Network Adapter changes”.

clip_image001

This error persisted with any of the VMs I had replicated to the new server.  I attempted to do a live migration of one of the non replicated VMs and got a similar error.

I jumped into the event viewer on the Server 2016 system and found the following two errors occurred when I was attempting to modify the Network Card settings.

Log Name:      System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:          1/07/2017 12:36:10 PM
Event ID:      82
Task Category: None
Level:         Error
Keywords:
User:          N/A
Computer:      DL380G7-2.domain.local
Description:
Failed to complete bandwidth policy operation ‘Policy Set’ on port FD853DBF-62EC-4B6C-B696-8DF50C5EB0B9 (Friendly Name: Dynamic Ethernet Switch Port) on switch 76E7111F-32C0-491E-88F5-8ACE9274CB32 (Friendly Name: Home LS) Reservation – 0, Weight – 10, Limit – 0, BurstLimit – 0, BurstSize – 0, Reason – The switch’s bandwidth reservation mode does not support this bandwidth configuration, Status = The request is not supported..

Log Name:      System
Source:        Microsoft-Windows-Hyper-V-VmSwitch
Date:          1/07/2017 12:36:10 PM
Event ID:      78
Task Category: None
Level:         Error
Keywords:
User:          SYSTEM
Computer:      DL380G7-2.domain.local
Description:
Failed to complete operation ‘Policy Add’ on port FD853DBF-62EC-4B6C-B696-8DF50C5EB0B9 (Friendly Name: Dynamic Ethernet Switch Port) on switch 76E7111F-32C0-491E-88F5-8ACE9274CB32 (Friendly Name: Home LS) Property Id {24ad3ce1-69bd-4978-b2ac-daad389d699c} Instance Id {07148245-ac3f-446a-b34d-f48aa0b67138}. Status = The request is not supported..

I did some further digging using the get-vmswitch powershell command and found that the underlying Virtual Switch had differences on the BandwidthReservationMode setting.  The old server had this BandwidthReservationMode setting configured as Weight, whereas the new server had this setting BandwidthReservationMode  configured as Absolute.  Now I’m not 100% certain why they are different, it could be related to the fact that I configured the old servers Hyper-V switches using SCVMM 2012R2 and the new 2016 servers Hyper-V switches were configured locally using the Hyper-V MMC.  Either way, I didn’t want to reconfigure the Hyper-V switch as there were machines running already on the new server.

I did some further investigation on the VMs on the new server and compared their network settings using the Get-VMNetworkAdapter “VMNAME” |FL.  I then found that the key difference was the MinimumBandwidthWeight setting.  Below you can see the failing machine.

image

I then figured to try to change that setting using the Set-VMNetworkAdapter “VMNAME” –MinimumBandwidthWeight 0 command from Powershell.

image

After running that command on the machine the setting changed as you can see below.

SNAGHTML245f439

I was then able to reconnect the VM to the local Hyper-V switch and got things up and running.  I need to do some further investigation into this as it challenges my thoughts on the ease with which we should be able to move VMs around using either Live Migration or Hyper-V replica, but for now I’ve solved this issue.

Hope this saves someone else the challenges I had with it today.

Share this:

  • Click to share on Facebook (Opens in new window)
  • Click to share on Twitter (Opens in new window)
  • Click to share on LinkedIn (Opens in new window)
  • Click to share on Reddit (Opens in new window)
  • Click to print (Opens in new window)

Filed Under: Blog Tagged With: Hyper-V, Replica, Windows Server 2012R2, Windows Server 2016

About The Author

Wayne has been working with Microsoft Server products in the SMB market for over 20 years. He has a passion for technology and been a Microsoft MVP for over 15 years. Read More…

Comments

  1. Khaled Baki says

    July 22, 2017 at 1:37 am

    I thought connecting to Hyper-V Switch was easier, but it has some technicalities. Great that you have shared your insights, and please keep your readers informed about Live Migration.

    Reply
    • Wayne Small says

      July 22, 2017 at 11:32 am

      Thanks for your comments.

      Reply
  2. Gold says

    November 21, 2017 at 3:52 am

    Hey Man,

    Thank you for this. This resolved my problem where I restored a VM into an Hyper-V that was not part of SCVMM infrastructure.
    Thank you for sharing your experience, much appraciated !

    Reply
    • Wayne Small says

      November 27, 2017 at 4:48 am

      Awesome – glad it helped!

      Reply
  3. RandomTechGuy says

    December 3, 2018 at 12:36 am

    Great writeup! Just what I needed during my early morning maintenance for modifying some virtual switches.

    Reply
  4. Shamseer says

    December 10, 2018 at 5:28 pm

    Excellent, thanks for sharing your insights. Saves my production migration.

    Reply
  5. Alex Lucini says

    September 6, 2019 at 6:50 pm

    This is exactly what’s happened to me. Did all previous stuff with SCVMM and just introduced a couple of new hosts via failover cluster manager. Your solution has worked well, thank you.

    Reply

Leave a Reply Cancel reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

Search

Connect Online With Us

  • Facebook
  • Twitter

Reviews

Splashtop – Cost Effective Remote Control Software

September 22, 2017 By Wayne Small 2 Comments

Western Digital DL4100 NAS

March 3, 2015 By Wayne Small Leave a Comment

SBS 2011 Configuring Certification Guide (70-169)

August 7, 2012 By Wayne Small 4 Comments

Site News

Exchange Bug Stops Mail Delivery in 2022

January 2, 2022

Huge bug found in Intel CPU that could permit hackers to steal your data

January 4, 2018

Recent Posts

  • MS Exchange Zero Day and RemotePowerShell Disabling on Admin accounts
  • Setup changes for Exchange 2016 and Exchange 2019
  • Bluetooth Mouse and Keyboard Randomly Stop Responding
  • Exchange Bug Stops Mail Delivery in 2022
  • How to open and search extremely large text log files

Tags

Antivirus Backup Business Focus Cloud Computing Community Conferences Disaster Recovery Exchange 2010 Exchange Server Future Products Hyper-V Installation Microsoft Migration Patches Personal Rants SBS 4.5 SBS 2000 SBS 2000 SP1 SBS 2003 SBS 2003 Premium SBS 2003 R2 SBS 2003 R2 Premium SBS 2003 R2 Standard SBS 2003 SP1 Premium SBS 2003 SP1 Standard SBS 2003 Standard SBS 2008 SBS 2008 R2 SBS 2011 SBS 2011 Essentials SBS 2011 Standard Security Service Packs ShadowProtect SMB Community Software Software I use StorageCraft Training TrendMicro Troubleshooting Virtualisation Windows Server 2012 Essentials

Terms of Use

Privacy Policy

Copyright © 2023 · Magazine Pro Theme on Genesis Framework · WordPress · Log in