RE: FSMT - Default Share and Location



Hi Mike,

Thanks for the response and the info. My question refers to the following:

"The File Server Migration Wizard eliminates this problem by using default
target shared folder names that have the format Sharename_SourceServerName,
where Sharename is the name of the shared folder on the source file server,
and SourceServerName is the name of the source file server. You can modify
the default target shared folder name for each source folder prior to
beginning the migration."

The server I'm migrating from is called SUPREMEFNP1. The FSMT will
automatically insert this server name into the target share and target
location name for each share that's being migrated. For example, the
following will be created for the target share and target location where
abriv1$ is the share name and f:\home is the new target location:

abriv1$_supremefnp1$
f:\home\supremefnp1\abriv1$

This is not our standard setup. I'd like the source server name to be
removed and just have the following as the target share and location:

abriv1$
f:\home\abriv1$

Can I do this automatically so when the FSMT generates the new share and
locations - "supremefnp1" is removed?

Thanks,
- A.

"Mike Luo [MSFT]" wrote:

Hello,

Thank you for using newsgroup!

From your post, I was unable understand "globally change the default share
and default location entries". Is your means that user can use the older
UNC to access the File Server after migrating? If so, the FSMT is exactly
for you.

Abstract from the FSMT whitepaper:
Consolidates shared folders with the same names from different servers
Migrating shared folders from multiple source file servers to a single
target file server can result in name conflicts if two or more shared
folders have the same name. For example, a shared folder called Teams on
source file servers named FS1 and FS2 will cause a conflict if they are
both copied to the same target file server named Corp-FS-1 because the UNC
path \\Corp-FS-1\Teams can represent only one of the shared folders. The
File Server Migration Wizard eliminates this problem by using default
target shared folder names that have the format Sharename_SourceServerName,
where Sharename is the name of the shared folder on the source file server,
and SourceServerName is the name of the source file server. You can modify
the default target shared folder name for each source folder prior to
beginning the migration.

Maintains UNC paths and eliminates broken shortcuts and links
Using DFS consolidation roots to maintain the original UNC paths of files
ensures a transparent migration experience for end users. There is no need
to use a separate utility that can identify and fix broken links on client
computers, such as OLE links or application-related links in the registry.
Users can continue to access shared folders just as they did prior to the
migration, and line-of-business applications continue to work correctly.
Thanks & Regards,

For more information, you can refer to the following:
Downloading FSMT white paper link:
http://download.microsoft.com/download/9/6/3/963f5b22-6304-4f15-a2af-35e0b81
046af/FSMT%20Whitepaper.doc

If you have any concerns, please feel free let me know.

Mike Luo

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.


.



Relevant Pages

  • RE: FSMT
    ... >>I already do the Change of target Share Name. ... >>> Q. In the File Server Migration Wizard, why is the source file server ... >>> and SourceServerName is the name of the source file server. ... >>> editing the name shown in Target share for each source shared folder. ...
    (microsoft.public.windows.server.migration)
  • RE: File system migration tool question
    ... target shared folders are named by FSMT as ... folder on the source file server, and SourceServerName is the name of the ... 1.Create the migration project and add the source file servers. ... 3.Locate the .xml project file for the migration project. ...
    (microsoft.public.windows.server.migration)
  • RE: File system migration tool question
    ... the target name and IP to the source as you had mentioned. ... folder on the source file server, and SourceServerName is the name of the ... 1.Create the migration project and add the source file servers. ... 3.Locate the .xml project file for the migration project. ...
    (microsoft.public.windows.server.migration)
  • RE: nt4 bdc migration to win2003 member file server
    ... both robocopy and FSMT can achieve your goal to ... FSMT will append the source file server name to the target ... following article, in the snippet "Q: In the File Server Migration Wizard, ...
    (microsoft.public.windows.server.migration)
  • RE: FSMT
    ... Q. In the File Server Migration Wizard, why is the source file server name ... By default, target shared folders are named Sharename_SourceServerName, ... 2.Close the File Server Migration Wizard. ...
    (microsoft.public.windows.server.migration)