Blog Post

Storage at Microsoft
2 MIN READ

Storage Migration Service October 2020 Update

NedPyle's avatar
NedPyle
Bronze Contributor
Oct 20, 2020

Heya folks, Ned here again. We've released our next set of features and fixes for the Windows Server 2019 Storage Migration Service, as part of cumulative update KB4580390 (Windows Server 2019) & KB4580386 (SAC 1903, 1909) This update comes optionally in the third week of October and then as part of the normal "Patch Tuesday" on November 10. Read on for details.

 

We also have big new SMS features coming in early 2021 that I'll be talking about at the Windows Server Summit on Thursday, October 29, 2020. Register now, it's free!

 

What's new

Installing these KBs on your SMS orchestrator and any WS2019 destination servers gives you:

 

  • Significant file transfer and especially re-transfer performance improvements
  • Significant inventory performance improvement with large number of files and folders 
  • Inventory validation
  • Fix for transfers failing if a source computer had an extremely large number of shares
  • Fix for the "Source not available" error when migrating account was missing permissions on shares
  • Fix for cluster network migrations
  • Fix for Windows Server 2003 inventory failure (yes I said 2003!)
  • Test for Windows Server 2008 R2 required update
  • Various Samba-Linux migration fixes
  • Various database and reliability fixes

There is also a new Windows Admin Center releasing into the feed. It includes:

 

  • A new prerequisites page to help you get ready for a migration

 

  • Inventory validation option



  • Automatic install of the cluster management tools on the orchestrator if not installed

 



  • Various ease of use and layout changes based on customer feedback
  • Note: we're also going to add automatic installation of the SMS Proxy on the destination server if not already installed, but it will be in another WAC update a few weeks after this one.

 

Sum up

I'll be updating the official SMS docs on some of these points, I know your boss doesn't believe in blogs even though I wrote both articles. 😄 

 

The  KB4580390 (Win10 1809, Windows Server 2019) & KB4580386 (1903, 1909) cumulative updates are available on the Microsoft Catalog for download, and will automatically install via Windows Update in the November patch Tuesday release. Let me know how it goes. And remember, more big features coming early next year, come watch the Windows Server Summit on Thursday, October 29, 2020 to learn more

 

- Ned "grind grind grind" Pyle

Updated Nov 13, 2020
Version 5.0

46 Comments

  • OT_Pilzz's avatar
    OT_Pilzz
    Copper Contributor

    NedPyle thanks for the update and quick reply.  Please advise once the fix has been pushed out. 

  • OT_Pilzz's avatar
    OT_Pilzz
    Copper Contributor

    Hello NedPyle 

     

    Ever since installing this above patch I can no longer validate the source.

     

    Validation error is as follows:

    We can transfer data from the source computer at maximum speed. This might fail when required software updates are not installed on the source.
    Fail: Error HRESULT E_FAIL has been returned from a call to a COM component

     

    If this is by design and the source machine needs to have all of the current updates how will that work for EOL servers.  My source machine is a server 2008 R2 and I currently do not have the ESU purchased on this server.  Please advise 

  • Paul_Brock's avatar
    Paul_Brock
    Brass Contributor

    NedPyle In DPM the volumes showed as available in the Management / Disk Storage section but when a backup tried to happen DPM said the volume was not available. I could be proved wrong that the update didn't cause the problem but when I uninstalled the update the problem went away. I didn't save the specific error message.

  • Paul_Brock's avatar
    Paul_Brock
    Brass Contributor

    Hey Ned,

     

    I applied KB4580390 to a Windows 2019 running System Center Data Protection Manager. We are leveraging "Modern tiered storage" within DPM. I know DPM does some ReFS magic to get tiered storage to work so I was suspicious that this update might have broke something and indeed once I removed the update all was good again. It might be worth hitting up the System Center folks to see if they have tested this update.