M.A.

My feedback

  1. 2 votes
    Sign in
    (thinking…)
    Sign in with: Facebook Google
    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  Storage  ·  Flag idea as inappropriate…  ·  Admin →
    M.A. commented  · 

    For anyone else landing here with the same issue, it's a Server 2019 bug when using the same server for the migration job and the destination. The workaround is to use a second 2019 server as the management server, pointing to your separate destination server. The validation then passes.

    https://docs.microsoft.com/en-us/windows-server/storage/storage-migration-service/known-issues

Feedback and Knowledge Base