Hi. I am trying to migrate hundreds folders that are allocated in a Windows Server 2008 Server (file server). I am migrating to Windows Server 2008 R2 on a new server. I followed this guide:

https://technet.microsoft.com/en-us/library/dd379474.aspx

Everything seemed right and got not errors during deployment. Both servers are fully updated, even with the optional patches. Both servers are part of the same domain and they don't have any issues while authenticating or connecting to the domain. They are both on the same subnet with gigabit connectivity. None of them are using the ports that are used for the migration tools. Firewalls are off, and antivirus solutions are off (AV is MS Forefront Protection 2012). Servers can ping each other by name and FQDN.

When I try to begin the migration, it fails with this error:

"Send-SmigServerData : Starting the connected transport failed. The cmdlet cannot connect to the destination server". The entire error is below on the pics:

Error on source server:

https://www.dropbox.com/s/6mqsvzxthmvm283/Error%20on%20Source%20Server.PNG?dl=0

Migration logs on source server:

https://www.dropbox.com/sh/p6se3xehatcb7ko/AABU_NhnQXwrbrkxxdhqLjYma?dl=0

Error on destination server:

https://www.dropbox.com/s/jx488rnmtr3i4ou/Error%20on%20Destination%20Server.PNG?dl=0

Migration logs at destination server:

https://www.dropbox.com/sh/zxfldxu3tbskmg7/AADvWcSKudREa1O9BVNDvMuCa?dl=0

Anything else I could check?

Regards,

Jose Angel Rivera

Hi Jose Angel Rivera,

Thanks for your post.

According to your description, you have followed the section "troubleshoot data migration connectivity" right? ( If you haven't seen before, you may refer to)

https://technet.microsoft.com/en-us/library/Dd379486(v=WS.10).aspx

Please also check your network connectivity,

Ping the IP address of the computer.

Ping the IP address of the default gateway.

Ping the IP address of the DNS server.

For more details, you could take a loot at the article.

https://technet.microsoft.com/en-us/library/cc961803.aspx

In addition, if the purpose is to migrate a folder, a quick workaround is to have a try with Robocopy. Run Robocopy /? for more information.

https://technet.microsoft.com/en-us/library/cc733145.aspx

Best Regards,

Mary Dong

Hi Mary,

Yes I already did all of the basic tests for IP connectivity. I also read that link for the troubleshooting, that's where I got the log file paths from.

I see most people are recommending to just drop this functionality and use Robocopy or Richcopy instead. As per the threads on some forums it seems that the File Server Migration toolkit isn't very reliable anymore. Not a very good thing when we need to migrate a lot of folders/servers, as those other tools can copy data and keep the attributes, but I remember I could do it all and even get the folders all shared automatically and DNS entries done by the File Migration Tool, that was years ago from a migration from 2003 to 2008R2. I thought it was going to be a nice experience...

Thank you anyway.

Regards,