When selecting the target volume mapping on the 'Select Volume Mappings' dialog, NDS Migrator does not show the cluster virtual server name as one of the computers to expand. NDS Migrator shows the actual physical node names of the clustered servers. This article describes how to configure NDS Migrator to migrate data to the virtual server, instead of the physical cluster node.
1. Close NDS Migrator.
2.. Publish an Active Directory share that points to the cluster's virtual server. For example: \\ClusterName\ShareName
NDS Migrator has the ability to create Data Migration Mappings to a share published in Active Directory. The published share can be managed by GPO's for security purposes, and safely be deleted after the data has been migrated to the cluster.
Refer to Microsoft's Knowledge Base Article Q234582 for information on how to publish a share in Active Directory:
Publishing a Shared Folder in Windows 2000 Active Directory: http://support.microsoft.com/kb/q234582
You can publish any shared network folder, including a distributed file system (Dfs) folder, in Active Directory. Creating a Shared folder object in Active Directory does not automatically share the folder. It is a two-step process; you must first share the folder, and then publish it in Active Directory."
3. Once the share has been published, open NDS Migrator and on the 'Volume Mapping' tab, select the 'Add Volume Mapping' button.
4. Expand the Active Directory structure on the right side of the 'Select Volume Mappings' dialog.
5. Select published share that was created above for the data migration component, for the target server location.
6. If desired, remove the published Active Directory share when the data migration component is complete.
Waiting for fix in a future release of NDS Migrator.