How to stop windows file shares during migration

Solution : http://service1.symantec.com/support/ent-security.nsf/854fa02b4f5013678825731a007d06af/684e821eb0b394f8882575070060f2a4?OpenDocument

To manually enable clients to browse for files and printers

1. In the client, in the sidebar, click Status.
2. Beside Network Threat Protection, click Options > Configure Firewall Rules.
3. In the Configure Firewall Rules dialog box, click Add.
4. On the General tab, type a name for the rule and click Allow this traffic.
5. On the Ports and Protocols tab, in the Protocol drop-down list, click TCP.
6. In the Remote ports drop-down list, type 88, 135, 139, 445.
7. Click OK.
8. In the Configure Firewall Rules dialog box, click Add.
9. On the General tab, type a name for the rule and click Allow this traffic.
10. On the Ports and Protocols tab, in the Protocol drop-down list, click UDP.
11. In the Remote ports drop-down list, type 88.
12. In the Local ports drop-down list, type 137, 138.

13. Click OK.

    To manually enable other computers to browse files on the client

14. In the client, in the sidebar, click Status.
15. Beside Network Threat Protection, click Options > Configure Firewall Rules.
16. In the Configure Firewall Rules dialog box, click Add.
17. On the General tab, type a name for the rule and click Allow this traffic.
18. On the Ports and Protocols tab, in the Protocol drop-down list, click TCP.
19. In the Local ports drop-down list, type 88, 135, 139, 445.
20. Click OK.
21. In the Configure Firewall Rules dialog box, click Add.
22. On the General tab, type a name for the rule and click Allow this traffic.
23. On the Ports and Protocols tab, in the Protocol drop-down list, click UDP.
24. In the Local ports drop-down list, type 88, 137, 138.
25. Click OK.

Somehow I missed that during my initial searching. The version I'm using (5.1) didn't match the steps exactly, but once I implemented the rules, I was able to access my share.

I basically ended up creating 4 rules rather than the one that I was trying to do as well as adding the rules for port 88 (according to wikipedia this is Kerberos, which seems a little odd). Once this was done I was able to access my share as intended..

Novell have a product called PlateSpin PowerConvert that will do P2P, P2V and V2P reliably across a very wide range of platforms and operating systems. It's not cheap (list price is $200 per conversion) but it will do both hot (live, minimal downtime) and cold migrations.

You can prepare all of your migrations in advance, scanning both the source and target systems, defining the parameters for the migration and it will give you a very comprehensive analysis highlighting any issues that need to be resolved before you start.