moving data from win 2000 file server to win 2003 file serve
Windows Server Forum Index Windows Server
Server discussion on Windows platform.
 
 FAQFAQ   MemberlistMemberlist     RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 
 
Google
 
Web winserverhelp.com
moving data from win 2000 file server to win 2003 file serve

 
Post new topic   Reply to topic    Windows Server Forum Index -> Migration
Author Message
gary
Guest





Posted: Mon Oct 24, 2005 4:51 pm    Post subject: moving data from win 2000 file server to win 2003 file serve Reply with quote

we had outgrown our old file server, so we have purchased a newer one with
much more harddrive space.

the old one was running windows 2000, the new one windows 2003. I am going
to use the old one as a file server at one of our offsite plants, so they do
not have to go across a VPN to access their files.

I have a mixed domain, we have clients from windows 95, 98, 2000, and XP,
currently have 2 windows 2000 servers (file server, email) and 1 NT 4.0.


I have been looking at the Microsoft file migration wizard, but was
wondering how it would work for me, as I was reading about it looks like
most people were using this to move files from old server to new server,
and then renaming the new server to have the same name as the old server?

will I run into any curves since not all my clients can participate in
active directory?

I was thinking that the migration wizard might at least enable me to move
files over to the new server so that I would only have to re-map drives on
the windows 98 or 95 PCs, is that correct?
Back to top
Vincent Xu [MSFT]
Guest





Posted: Tue Oct 25, 2005 7:50 am    Post subject: RE: moving data from win 2000 file server to win 2003 file s Reply with quote

Hi Gary,

Let me explain something about File Server Migration Tool.

FSMT helps the system administrator easily migrate and consolidate shared
folders from servers running Windows NT? Server 4.0 or the Windows 2000
family of servers, to a server running Windows Server 2003 or Windows
Storage Server 2003.For example, you can:

" Copy permission, auditing, and ownership information that is associated
with files and folders.

" Resolve invalid security descriptors on the target files and folders.

" Stop sharing the shared folders on the source file servers after the
copying is finalized.

" Prestage the target file server-for example, by restoring a backup of the
source file server-and then use the File Server Migration Wizard to recopy
changed files and share the target folders.

" Specify the DFS root server that hosts DFS consolidation roots that are
created by the DFS Consolidation Root Wizard. When you select this setting,
the DFS links that correspond to each copied folder are updated with the
new Universal Naming Convention (UNC) paths of the target folders.

" Specify an existing DFS namespace where you want to add DFS links for
each copied shared folder. You can select this setting even if you do not
use the DFS Consolidation Root Wizard.

For more information, please refer to
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_over
view.mspx

Hope it helps.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security


--------------------
Quote:
From: "gary" <garym_jacksonfurniture_dontspamme_@hotmail.com
Subject: moving data from win 2000 file server to win 2003 file server
Date: Mon, 24 Oct 2005 11:41:36 -0400
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-ID: <uQfo0EL2FHA.3712@TK2MSFTNGP09.phx.gbl
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: 68-114-160-34.dhcp.kgpt.tn.charter.com 68.114.160.34
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:12453
X-Tomcat-NG: microsoft.public.windows.server.migration

we had outgrown our old file server, so we have purchased a newer one
with
much more harddrive space.

the old one was running windows 2000, the new one windows 2003. I am
going
to use the old one as a file server at one of our offsite plants, so they
do
not have to go across a VPN to access their files.

I have a mixed domain, we have clients from windows 95, 98, 2000, and XP,
currently have 2 windows 2000 servers (file server, email) and 1 NT 4.0.


I have been looking at the Microsoft file migration wizard, but was
wondering how it would work for me, as I was reading about it looks like
most people were using this to move files from old server to new server,
and then renaming the new server to have the same name as the old server?

will I run into any curves since not all my clients can participate in
active directory?

I was thinking that the migration wizard might at least enable me to move
files over to the new server so that I would only have to re-map drives
on
the windows 98 or 95 PCs, is that correct?


Back to top
gary
Guest





Posted: Fri Oct 28, 2005 12:51 pm    Post subject: Re: moving data from win 2000 file server to win 2003 file s Reply with quote

since I dont have windows 2003 advanced, I cannot run the DFS consolidation
root wizard (or so it said when I tried). I have standard 2003 server.
so what do I do without that ability?

gary



"Vincent Xu [MSFT]" <v-xuwen@online.microsoft.com> wrote in message
news:Nkzwk7Q2FHA.3220@TK2MSFTNGXA01.phx.gbl...
Quote:
Hi Gary,

Let me explain something about File Server Migration Tool.

FSMT helps the system administrator easily migrate and consolidate shared
folders from servers running Windows NT? Server 4.0 or the Windows 2000
family of servers, to a server running Windows Server 2003 or Windows
Storage Server 2003.For example, you can:

" Copy permission, auditing, and ownership information that is associated
with files and folders.

" Resolve invalid security descriptors on the target files and folders.

" Stop sharing the shared folders on the source file servers after the
copying is finalized.

" Prestage the target file server-for example, by restoring a backup of
the
source file server-and then use the File Server Migration Wizard to recopy
changed files and share the target folders.

" Specify the DFS root server that hosts DFS consolidation roots that are
created by the DFS Consolidation Root Wizard. When you select this
setting,
the DFS links that correspond to each copied folder are updated with the
new Universal Naming Convention (UNC) paths of the target folders.

" Specify an existing DFS namespace where you want to add DFS links for
each copied shared folder. You can select this setting even if you do not
use the DFS Consolidation Root Wizard.

For more information, please refer to
http://www.microsoft.com/windowsserver2003/upgrading/nt4/tooldocs/msfst_over
view.mspx

Hope it helps.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security


--------------------
From: "gary" <garym_jacksonfurniture_dontspamme_@hotmail.com
Subject: moving data from win 2000 file server to win 2003 file server
Date: Mon, 24 Oct 2005 11:41:36 -0400
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-ID: <uQfo0EL2FHA.3712@TK2MSFTNGP09.phx.gbl
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: 68-114-160-34.dhcp.kgpt.tn.charter.com 68.114.160.34
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:12453
X-Tomcat-NG: microsoft.public.windows.server.migration

we had outgrown our old file server, so we have purchased a newer one
with
much more harddrive space.

the old one was running windows 2000, the new one windows 2003. I am
going
to use the old one as a file server at one of our offsite plants, so they
do
not have to go across a VPN to access their files.

I have a mixed domain, we have clients from windows 95, 98, 2000, and XP,
currently have 2 windows 2000 servers (file server, email) and 1 NT 4.0.


I have been looking at the Microsoft file migration wizard, but was
wondering how it would work for me, as I was reading about it looks like
most people were using this to move files from old server to new server,
and then renaming the new server to have the same name as the old server?

will I run into any curves since not all my clients can participate in
active directory?

I was thinking that the migration wizard might at least enable me to move
files over to the new server so that I would only have to re-map drives
on
the windows 98 or 95 PCs, is that correct?



Back to top
Vincent Xu [MSFT]
Guest





Posted: Tue Nov 01, 2005 9:51 am    Post subject: Re: moving data from win 2000 file server to win 2003 file s Reply with quote

Hi Gary,

Maybe I did explain clearly in my previous reply. DFS just a feature which
provide more powserful function. FSMT works fine when moving share folders
to Windows 2003 Standard.

Please refer to :

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


Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security


--------------------
Quote:
From: "gary" <garym_jacksonfurniture_dontspamme_@hotmail.com
References: <uQfo0EL2FHA.3712@TK2MSFTNGP09.phx.gbl
Nkzwk7Q2FHA.3220@TK2MSFTNGXA01.phx.gbl
Subject: Re: moving data from win 2000 file server to win 2003 file server
Date: Fri, 28 Oct 2005 08:31:04 -0400
Lines: 106
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-RFC2646: Format=Flowed; Original
Message-ID: <e5eIBt72FHA.3020@TK2MSFTNGP15.phx.gbl
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: 68-114-160-34.dhcp.kgpt.tn.charter.com 68.114.160.34
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP15.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:12494
X-Tomcat-NG: microsoft.public.windows.server.migration

since I dont have windows 2003 advanced, I cannot run the DFS
consolidation
root wizard (or so it said when I tried). I have standard 2003 server.
so what do I do without that ability?

gary



"Vincent Xu [MSFT]" <v-xuwen@online.microsoft.com> wrote in message
news:Nkzwk7Q2FHA.3220@TK2MSFTNGXA01.phx.gbl...
Hi Gary,

Let me explain something about File Server Migration Tool.

FSMT helps the system administrator easily migrate and consolidate
shared
folders from servers running Windows NT? Server 4.0 or the Windows 2000
family of servers, to a server running Windows Server 2003 or Windows
Storage Server 2003.For example, you can:

" Copy permission, auditing, and ownership information that is
associated
with files and folders.

" Resolve invalid security descriptors on the target files and folders.

" Stop sharing the shared folders on the source file servers after the
copying is finalized.

" Prestage the target file server-for example, by restoring a backup of
the
source file server-and then use the File Server Migration Wizard to
recopy
changed files and share the target folders.

" Specify the DFS root server that hosts DFS consolidation roots that
are
created by the DFS Consolidation Root Wizard. When you select this
setting,
the DFS links that correspond to each copied folder are updated with the
new Universal Naming Convention (UNC) paths of the target folders.

" Specify an existing DFS namespace where you want to add DFS links for
each copied shared folder. You can select this setting even if you do
not
use the DFS Consolidation Root Wizard.

For more information, please refer to

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

Hope it helps.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security


--------------------
From: "gary" <garym_jacksonfurniture_dontspamme_@hotmail.com
Subject: moving data from win 2000 file server to win 2003 file server
Date: Mon, 24 Oct 2005 11:41:36 -0400
Lines: 24
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2180
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
Message-ID: <uQfo0EL2FHA.3712@TK2MSFTNGP09.phx.gbl
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: 68-114-160-34.dhcp.kgpt.tn.charter.com 68.114.160.34
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP09.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:12453
X-Tomcat-NG: microsoft.public.windows.server.migration

we had outgrown our old file server, so we have purchased a newer one
with
much more harddrive space.

the old one was running windows 2000, the new one windows 2003. I am
going
to use the old one as a file server at one of our offsite plants, so
they
do
not have to go across a VPN to access their files.

I have a mixed domain, we have clients from windows 95, 98, 2000, and
XP,
currently have 2 windows 2000 servers (file server, email) and 1 NT
4.0.


I have been looking at the Microsoft file migration wizard, but was
wondering how it would work for me, as I was reading about it looks
like
most people were using this to move files from old server to new
server,
and then renaming the new server to have the same name as the old
server?

will I run into any curves since not all my clients can participate in
active directory?

I was thinking that the migration wizard might at least enable me to
move
files over to the new server so that I would only have to re-map drives
on
the windows 98 or 95 PCs, is that correct?






Back to top
Walt
Guest





Posted: Wed Nov 02, 2005 7:59 am    Post subject: RE: moving data from win 2000 file server to win 2003 file s Reply with quote

I tried to run the Microsoft File server migration wizard but after I enter
the source and destination servers and click continue I receive error the
program can not resolve secuity desciptors or the could not read the amout of
hard drive space or share permissions. Error codes of 9 an others. I have a
Windows 2000 file server with 30 GB of data I am want to migrate to an
existing Windows 2003 server with plenty of space. Anyone else had this same
problem of not getting past the first step?

Thanks.

"gary" wrote:

Quote:
we had outgrown our old file server, so we have purchased a newer one with
much more harddrive space.

the old one was running windows 2000, the new one windows 2003. I am going
to use the old one as a file server at one of our offsite plants, so they do
not have to go across a VPN to access their files.

I have a mixed domain, we have clients from windows 95, 98, 2000, and XP,
currently have 2 windows 2000 servers (file server, email) and 1 NT 4.0.


I have been looking at the Microsoft file migration wizard, but was
wondering how it would work for me, as I was reading about it looks like
most people were using this to move files from old server to new server,
and then renaming the new server to have the same name as the old server?

will I run into any curves since not all my clients can participate in
active directory?

I was thinking that the migration wizard might at least enable me to move
files over to the new server so that I would only have to re-map drives on
the windows 98 or 95 PCs, is that correct?


Back to top
Vincent Xu [MSFT]
Guest





Posted: Thu Nov 03, 2005 9:51 am    Post subject: RE: moving data from win 2000 file server to win 2003 file s Reply with quote

Hi Walt,

Thank you for using Microsoft Newsgroup.

Since we are issue based service, I'd like to suggest you open a new post
to describe your problem to avoid any conflict. Please let us know the
exact error message as well. We'll be glad to be of assistance.

Thanks for understanding.

Best regards,

Vincent Xu
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security


--------------------
Quote:
Thread-Topic: moving data from win 2000 file server to win 2003 file
server
thread-index: AcXfUP7Oa6rhx4cwQSaZjulRx0lMEw==
X-WBNR-Posting-Host: 68.249.203.126
From: "=?Utf-8?B?V2FsdA==?=" <Walt@discussions.microsoft.com
References: <uQfo0EL2FHA.3712@TK2MSFTNGP09.phx.gbl
Subject: RE: moving data from win 2000 file server to win 2003 file server
Date: Tue, 1 Nov 2005 17:59:01 -0800
Lines: 37
Message-ID: <1AA2339F-7EBF-4504-8286-30D3B7A624FF@microsoft.com
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.windows.server.migration
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
Xref: TK2MSFTNGXA01.phx.gbl
microsoft.public.windows.server.migration:12526
X-Tomcat-NG: microsoft.public.windows.server.migration

I tried to run the Microsoft File server migration wizard but after I
enter
the source and destination servers and click continue I receive error the
program can not resolve secuity desciptors or the could not read the
amout of
hard drive space or share permissions. Error codes of 9 an others. I have
a
Windows 2000 file server with 30 GB of data I am want to migrate to an
existing Windows 2003 server with plenty of space. Anyone else had this
same
problem of not getting past the first step?

Thanks.

"gary" wrote:

we had outgrown our old file server, so we have purchased a newer one
with
much more harddrive space.

the old one was running windows 2000, the new one windows 2003. I am
going
to use the old one as a file server at one of our offsite plants, so
they do
not have to go across a VPN to access their files.

I have a mixed domain, we have clients from windows 95, 98, 2000, and
XP,
currently have 2 windows 2000 servers (file server, email) and 1 NT
4.0.


I have been looking at the Microsoft file migration wizard, but was
wondering how it would work for me, as I was reading about it looks
like
most people were using this to move files from old server to new
server,
and then renaming the new server to have the same name as the old
server?

will I run into any curves since not all my clients can participate in
active directory?

I was thinking that the migration wizard might at least enable me to
move
files over to the new server so that I would only have to re-map drives
on
the windows 98 or 95 PCs, is that correct?



Back to top
 
Post new topic   Reply to topic    Windows Server Forum Index -> Migration All times are GMT
Page 1 of 1

 
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum




New Topics Powered by phpBB