This is an interesting issue that I have seen recently. When migrating cluster resources from Windows Server 2003 to Windows Server 2008 R2, some of the resources may not migrate successfully. It works from 2003 to 2008, or 2008 to 2008 R2, but not from 2003 to 2008 R2. There is an article that describes this issue and the available workarounds noted below.
The workarounds unfortunately all have negative impacts depending on the size and criticality of the implementation we are dealing with. The 3rd method states to ‘manually recreate’ the file shares. This may not be a viable option if you have a very large number of shares and lots of varying permissions configured. The 2nd method recommends to migrate the shares using the File Server Migration Toolkit. Unfortunately, this may not work for people who are planning to utilize the existing storage. Method 1, which is also the ‘recommended’ method, is then going to be the most ideal method for most people.
The thing that is not mentioned in the 'recommended' workaround however, is that the resources must be brought online on the 'interim' 2008 cluster server before they can be successfully migrated to the R2 system. This could be inconvenient for anyone that does not want to take the time to actually copy the files over or mount the storage on the 2008 server simply to make this migration work. This was the issue that I ran into recently. We have numerous file share clusters configured that are running hundreds of individual file share resources in each cluster group. This would be a huge undertaking to have to copy the shares or manually recreate them. And, since the existing storage would be used and there are loads of permissions setup, the only method that is really applicable for us was method 1.
So, I devised a plan to make this go as smoothly and painless as possible.
This can be done simply by using a Virtual machine for the 'interim' 2008 cluster server node which is what we did.
robocopy <Source Drive Letter>:\ <Destination Drive Letter>:\ /e /z /xjf /xjd /tee /xf * /lev:2 /loc:v:\RobocopyLog.txt
For more information on this issue, see the article:
983840 Not all resources are migrated from a Windows Server 2003-based failover cluster to a Windows Server 2008 R2-based failover cluster http://support.microsoft.com/default.aspx?scid=kb;EN-US;983840