I have previously used the Windows Server 2008 R2 migration cmdlets and they
worked fine. I am trying them again but this time trying to migrate to
Windows Server 2008 R2 RC that was just released. I have them all working
except for the part of the File Server migration where you migrate the data
(shares, files). This is also the only migration that uses these two cmdlets,
Send-SmigServerData and Receive-SmigServerData. When running these I get an
error message from both stating that they can't connect to the destination
and source servers, respectively.
I have verified my steps and connectivity between the two servers. I have
followed the 5 Troubleshoot data migration connectivity troubleshooting steps
located here
http://technet.microsoft.com/en-us/l.../dd379486.aspx. I have
even turned off both firewalls just to be sure.
Here are the steps from the guide that I am using:
Make sure that users are notified that they should stop using the source
server at this time to prevent any possible data loss. You can run the
following command to list all the currently open files to determine the
potential impact of performing this step.
net file
Disconnect all users from the source server by stopping the LanMan server
service.
Stop-Service LanmanServer -force
Use the following command to run the Receive-SmigServerData cmdlet on the
destination server. Use a Windows PowerShell session that is running with
elevated user rights.
Receive-SmigServerData
Use the following command to run the Send-SmigServerData cmdlet on the
source server to migrate data and shared folders. Use a Windows PowerShell
session that is running with elevated user rights.
Send-SmigServerData –ComputerName <DestinationServer> –SourcePath d:\users
–DestinationPath d:\shares\users -Recurse -Include All -Force
Any ideas? Does anyone know if this even works on the latest Windows Server
2008 R2 RC?
-dm