File Server Migration Tool share name overlapping issue

Discussion in 'Windows Server' started by study, Mar 3, 2008.

  1. study

    study Guest

    Hello all,

    We have a mix of NT4/2003 File Servers that need to be migrated/consolidated
    to a single 2003 file server in an NT4 domain environment.

    The issue we've noticed is that because our current file servers all have
    \\servername\profiles$ share and thus, the sharename profiles$ overlap with
    one another so FSMT complains about it during the copy phase.

    ex) \\server1\profiles$, \\server2\profiles$, and \\server3\profiles$, when
    trying to copy the data using FSMT to the to-be new 2003 file server:
    to target share: e\profiles$
    target location: e\profiles
    it errors out due to the overlap in share name.

    Is there a work around for this? We don't intend to use DFS.
    I'd guess we can change the target share/location for each source server but
    they ultimately all need to go to the e\profiles folder.
    study, Mar 3, 2008
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.