Re: File Server Migration Toolkit - relocating shares correction

Wait a minute, let me correct myself. After rereading the documentation yet
again...I finally understood.
"If a file is deleted on the source file server, and you run this step
again, the file is not deleted from the target file server until the
Finalize phase." It all makes perfect sense to me now.

"dc3dog" <dc3dog@xxxxxxxxxxx> wrote in message
news:e1K$ZGOWGHA.1192@xxxxxxxxxxxxxxxxxxxxxxx
Which version of the tool are you using? I have recently been working with
the 1.0.436.0 version and when you click on a share in the right window
appears the properties of the source and the destination. Here you can
edit
the destination to be what ever you like.

Also, this version WILL migrate shares and permissions.

The problem I have found is that files/folders that are new in the
destination. folder are deleted. For example, the documentation refers to
pre-staging, copying data to the destination and then doing another copy
before Finalizing. If in between the first and second copy new
files/folders
are added to the DESTINATION that are not in the source these destination
files/folders will be deleted when Finalizing.

It is a serious bug if you ask me. There is nothing in the documentation
that warns of files/folders being deleted. Furthermore I have never known
a
COPY operation to delete anything.

Am I missing something here. Anybody else seen similar issue?


"paoutdoorsman" <paoutdoorsman@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CE8F8C85-68BE-4B4A-9A20-332C0B635F3E@xxxxxxxxxxxxxxxx
I've found the problem and what I've found may help someone else so I'll
post
it here. The doco in the FAQ states that you should use Wordpad or
Notepad
to modify the XML file, so for no reason I just chose Wordpad and stuck
with
it, using find/replace to replace the variables I wanted to change. I
did
this for hours changing this, changing that, trying different servers,
etc.
but always the xml file would revert to it's original content.

On a whim, I switched to notepad and everything works just as stated. I
was
able to eliminate the unwanted _servername share name tag, and the
servername
top level folder. Maybe there is something about Wordpad that I'm
missing,
but that is what worked for me.

It would be a great enhancement if this tool allowed me to move shares
to
a
seperate volume on the same physical server, remove the old share
information, and create the new share information without changing the
share
names. But I've found it can be done with two moves, move once from
Server A
to Server B, then move from Server B to Server A.

Hope this helps someone!
Dana

"paoutdoorsman" wrote:

Hi all, I've been trying to relocate 1200 shares on a Windows 2003
Enterprise
file server and I'm really struggling to make this happen.

Here is my scenario; My shares are currently located on local drives
on
the
file server. I now have a fiber connection to a Hitachi SAN and need
to
relocate these shares to the SAN - preferably without having to
recreate
every share.

When I test moving a smaller number of shares with the file server
migration
wizard, a new top level folder is added equal to the file server name,
and
each share name is appended with _file server name. I really do not
want
this to happen and this is the behavior I'd like to change.

After reading the FAQ, I've tried numerous times to modify the .xml
file
to
eliminate the both the share name changes and the top level folder
addition,
but is still adds them in regardless of the fact that I eliminated
them
from
the xml file.

Link to FAQ


http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_faqs.mspx

I must really be missing something because I can't imagine this should
be a
difficult task. Can anyone help?




.

Relevant Pages

  • RE: File Sharing in 5.0
    ... You don't want the remote admin UI to prompt you to set the device's name ... I answered another post just last month called "File Server on ... Note that under the AdapterList documentation it mentions that "*" can used ... to serve on all adapters. ...
    (microsoft.public.windowsce.platbuilder)
  • Domain Controller Best Practice
    ... I am in need of some supporting documentation relating to Domain ... A medium sized school would like their single DC ... along with another file server and an email server. ... They like to poke and prod. ...
    (Focus-Microsoft)
  • Re: [9fans] Proposal*: A Cousin for man(1)
    ... lack of examples (a simple 9P file server being the most notorious ... That said, more and better documentation is always welcomed, of course. ... I'm a newbie on Plan9 - and have been reading manuals and following this ... Bickley Consulting West Inc. ...
    (comp.os.plan9)
  • Re: Thinking about a linux server
    ... The file server is ... Whats better Fedora or Ubuntu as the OS for such a server? ... The reason for the choice between those two is the documentation. ... But I see no overriding reason to select one over the other. ...
    (alt.os.linux)
  • RE: File Server Migration Toolkit - relocating shares
    ... FSMT also will not migrate the shares. ... Windows stores all share information in the registry. ... you must copy the folder to the same location on the destination ... File Server Migration Toolkit - relocating shares ...
    (microsoft.public.windows.server.migration)