File Server Migration

  • Thread starter Thread starter Arsenal2003
  • Start date Start date
A

Arsenal2003

Guest
We want to migrate our old file server to a new server running 2003 R2. The
main objective is to keep all mapped drives/printers and UNC paths the same
as the old path from the client perspective. All the current mappings have
been made manually not via a login script. I tested the File Server
Migration Toolkit in a lab. While the data and permissions migrated
flawlessly, sometimes the mapped drives did not resolve on the client side.

Do we have to use DFS to accomplish the above objectives? Has anyone else
had a similar scenario? Too eventually I will have another server to perform
the same task on. Any thoughts would be appreciated.
 
Re: File Server Migration


"Arsenal2003" <Arsenal2003@newsgroup.nospam> wrote in message
news:%23CO$eP8rIHA.5068@TK2MSFTNGP02.phx.gbl...
> We want to migrate our old file server to a new server running 2003 R2.
> The main objective is to keep all mapped drives/printers and UNC paths the
> same as the old path from the client perspective. All the current mappings
> have been made manually not via a login script. I tested the File Server
> Migration Toolkit in a lab. While the data and permissions migrated
> flawlessly, sometimes the mapped drives did not resolve on the client
> side.
>
> Do we have to use DFS to accomplish the above objectives? Has anyone else
> had a similar scenario? Too eventually I will have another server to
> perform the same task on. Any thoughts would be appreciated.


Export this key from the registry the path
hklm/system/currentcontrolset/services/lanmanserver/shares
to a file and import it on the new server.
 
RE: File Server Migration

Hi,

Thanks for posting here.

From your description, I understand you concern how to keep consistency of
all UNC paths, mapped drivers/printers after migrating files to the new
serve with Windows server 2003 R2 by using FSMT. If I misunderstood, please
let me know.

DFS can make end-users easily access files without being aware of where
these files really reside. However, based on the situation you want to keep
consistency of mapped drivers and UNC paths, I suggest performing the
following steps. Here, I listed two methods for your reference:

<1> Rename the new file serve as old server

After migrating files and folders and ensuring everything works fine on the
new server, we can remove the old server and rename the new serve as old
server. Then, update A record on DNS according to the current IP address of
new file serve.

After doing this, clients can still use the old UNC path to access mapped
drives, etc.

<2>Create Alias record on DNS for the new file server

We can remove old server and create a Alias record for the new file server,
so that the end-users will not be aware of file serve changing.

How to create a DNS Alias record, please refer to:

Creating a DNS Alias Record
http://support.microsoft.com/kb/168322/en-us

Also, please have a look at the following KB article to avoid access error
caused by alias record access.

Connecting to SMB share on a Windows 2000-based computer or a Windows
Server 2003-based computer may not work with an alias name
http://support.microsoft.com/default.aspx?scid=kb;EN-US;281308

If anything is unclear, please post back.

Have a nice day!


Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center

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.


--------------------
--->From: "Arsenal2003" <Arsenal2003@newsgroup.nospam>
--->Subject: File Server Migration
--->Date: Tue, 6 May 2008 14:56:59 -0700
--->Lines: 12
--->X-Priority: 3
--->X-MSMail-Priority: Normal
--->X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
--->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
--->X-RFC2646: Format=Flowed; Original
--->Message-ID: <#CO$eP8rIHA.5068@TK2MSFTNGP02.phx.gbl>
--->Newsgroups: microsoft.public.windows.server.general
--->NNTP-Posting-Host: 66-193-206-2.static.twtelecom.net 66.193.206.2
--->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
--->Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.general:37832
--->X-Tomcat-NG: microsoft.public.windows.server.general
--->
--->We want to migrate our old file server to a new server running 2003 R2.
The
--->main objective is to keep all mapped drives/printers and UNC paths the
same
--->as the old path from the client perspective. All the current mappings
have
--->been made manually not via a login script. I tested the File Server
--->Migration Toolkit in a lab. While the data and permissions migrated
--->flawlessly, sometimes the mapped drives did not resolve on the client
side.
--->
--->Do we have to use DFS to accomplish the above objectives? Has anyone
else
--->had a similar scenario? Too eventually I will have another server to
perform
--->the same task on. Any thoughts would be appreciated.
--->
--->
--->
 
Re: File Server Migration

Thank you for the excellent information. I will look into these options.

Seems like I can still use the File Server Migration Toolkit to migrate the
information over to the new server, correct? It seems like this will be
easier than restoring a backup of the files on the new server.


"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
news:hW$2WUCsIHA.1788@TK2MSFTNGHUB02.phx.gbl...
> Hi,
>
> Thanks for posting here.
>
> From your description, I understand you concern how to keep consistency of
> all UNC paths, mapped drivers/printers after migrating files to the new
> serve with Windows server 2003 R2 by using FSMT. If I misunderstood,
> please
> let me know.
>
> DFS can make end-users easily access files without being aware of where
> these files really reside. However, based on the situation you want to
> keep
> consistency of mapped drivers and UNC paths, I suggest performing the
> following steps. Here, I listed two methods for your reference:
>
> <1> Rename the new file serve as old server
>
> After migrating files and folders and ensuring everything works fine on
> the
> new server, we can remove the old server and rename the new serve as old
> server. Then, update A record on DNS according to the current IP address
> of
> new file serve.
>
> After doing this, clients can still use the old UNC path to access mapped
> drives, etc.
>
> <2>Create Alias record on DNS for the new file server
>
> We can remove old server and create a Alias record for the new file
> server,
> so that the end-users will not be aware of file serve changing.
>
> How to create a DNS Alias record, please refer to:
>
> Creating a DNS Alias Record
> http://support.microsoft.com/kb/168322/en-us
>
> Also, please have a look at the following KB article to avoid access error
> caused by alias record access.
>
> Connecting to SMB share on a Windows 2000-based computer or a Windows
> Server 2003-based computer may not work with an alias name
> http://support.microsoft.com/default.aspx?scid=kb;EN-US;281308
>
> If anything is unclear, please post back.
>
> Have a nice day!
>
>
> Sincerely
> Morgan Che
> Microsoft Online Support
> Microsoft Global Technical Support Center
>
> 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.
>
>
> --------------------
> --->From: "Arsenal2003" <Arsenal2003@newsgroup.nospam>
> --->Subject: File Server Migration
> --->Date: Tue, 6 May 2008 14:56:59 -0700
> --->Lines: 12
> --->X-Priority: 3
> --->X-MSMail-Priority: Normal
> --->X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
> --->X-RFC2646: Format=Flowed; Original
> --->Message-ID: <#CO$eP8rIHA.5068@TK2MSFTNGP02.phx.gbl>
> --->Newsgroups: microsoft.public.windows.server.general
> --->NNTP-Posting-Host: 66-193-206-2.static.twtelecom.net 66.193.206.2
> --->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
> --->Xref: TK2MSFTNGHUB02.phx.gbl
> microsoft.public.windows.server.general:37832
> --->X-Tomcat-NG: microsoft.public.windows.server.general
> --->
> --->We want to migrate our old file server to a new server running 2003
> R2.
> The
> --->main objective is to keep all mapped drives/printers and UNC paths the
> same
> --->as the old path from the client perspective. All the current mappings
> have
> --->been made manually not via a login script. I tested the File Server
> --->Migration Toolkit in a lab. While the data and permissions migrated
> --->flawlessly, sometimes the mapped drives did not resolve on the client
> side.
> --->
> --->Do we have to use DFS to accomplish the above objectives? Has anyone
> else
> --->had a similar scenario? Too eventually I will have another server to
> perform
> --->the same task on. Any thoughts would be appreciated.
> --->
> --->
> --->
>
 
Re: File Server Migration

No need to reply. I answered my own question. Thanks again Morgan che.


"Arsenal2003" <Arsenal2003@newsgroup.nospam> wrote in message
news:Okp2j5EsIHA.1236@TK2MSFTNGP02.phx.gbl...
> Thank you for the excellent information. I will look into these options.
>
> Seems like I can still use the File Server Migration Toolkit to migrate
> the information over to the new server, correct? It seems like this will
> be easier than restoring a backup of the files on the new server.
>
>
> "Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
> news:hW$2WUCsIHA.1788@TK2MSFTNGHUB02.phx.gbl...
>> Hi,
>>
>> Thanks for posting here.
>>
>> From your description, I understand you concern how to keep consistency
>> of
>> all UNC paths, mapped drivers/printers after migrating files to the new
>> serve with Windows server 2003 R2 by using FSMT. If I misunderstood,
>> please
>> let me know.
>>
>> DFS can make end-users easily access files without being aware of where
>> these files really reside. However, based on the situation you want to
>> keep
>> consistency of mapped drivers and UNC paths, I suggest performing the
>> following steps. Here, I listed two methods for your reference:
>>
>> <1> Rename the new file serve as old server
>>
>> After migrating files and folders and ensuring everything works fine on
>> the
>> new server, we can remove the old server and rename the new serve as old
>> server. Then, update A record on DNS according to the current IP address
>> of
>> new file serve.
>>
>> After doing this, clients can still use the old UNC path to access mapped
>> drives, etc.
>>
>> <2>Create Alias record on DNS for the new file server
>>
>> We can remove old server and create a Alias record for the new file
>> server,
>> so that the end-users will not be aware of file serve changing.
>>
>> How to create a DNS Alias record, please refer to:
>>
>> Creating a DNS Alias Record
>> http://support.microsoft.com/kb/168322/en-us
>>
>> Also, please have a look at the following KB article to avoid access
>> error
>> caused by alias record access.
>>
>> Connecting to SMB share on a Windows 2000-based computer or a Windows
>> Server 2003-based computer may not work with an alias name
>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;281308
>>
>> If anything is unclear, please post back.
>>
>> Have a nice day!
>>
>>
>> Sincerely
>> Morgan Che
>> Microsoft Online Support
>> Microsoft Global Technical Support Center
>>
>> 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.
>>
>>
>> --------------------
>> --->From: "Arsenal2003" <Arsenal2003@newsgroup.nospam>
>> --->Subject: File Server Migration
>> --->Date: Tue, 6 May 2008 14:56:59 -0700
>> --->Lines: 12
>> --->X-Priority: 3
>> --->X-MSMail-Priority: Normal
>> --->X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
>> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
>> --->X-RFC2646: Format=Flowed; Original
>> --->Message-ID: <#CO$eP8rIHA.5068@TK2MSFTNGP02.phx.gbl>
>> --->Newsgroups: microsoft.public.windows.server.general
>> --->NNTP-Posting-Host: 66-193-206-2.static.twtelecom.net 66.193.206.2
>> --->Path:
>> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
>> --->Xref: TK2MSFTNGHUB02.phx.gbl
>> microsoft.public.windows.server.general:37832
>> --->X-Tomcat-NG: microsoft.public.windows.server.general
>> --->
>> --->We want to migrate our old file server to a new server running 2003
>> R2.
>> The
>> --->main objective is to keep all mapped drives/printers and UNC paths
>> the
>> same
>> --->as the old path from the client perspective. All the current mappings
>> have
>> --->been made manually not via a login script. I tested the File Server
>> --->Migration Toolkit in a lab. While the data and permissions migrated
>> --->flawlessly, sometimes the mapped drives did not resolve on the client
>> side.
>> --->
>> --->Do we have to use DFS to accomplish the above objectives? Has anyone
>> else
>> --->had a similar scenario? Too eventually I will have another server to
>> perform
>> --->the same task on. Any thoughts would be appreciated.
>> --->
>> --->
>> --->
>>

>
>
 
Re: File Server Migration


Hi,

How are you?

I am writing to see if you have any update about this post. If you
encounter any break/fix issue, please feel free to let me know.

Have a good day!
Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center

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.


--------------------
--->From: "Arsenal2003" <Arsenal2003@newsgroup.nospam>
--->References: <#CO$eP8rIHA.5068@TK2MSFTNGP02.phx.gbl>
<hW$2WUCsIHA.1788@TK2MSFTNGHUB02.phx.gbl>
<Okp2j5EsIHA.1236@TK2MSFTNGP02.phx.gbl>
--->Subject: Re: File Server Migration
--->Date: Wed, 7 May 2008 09:44:24 -0700
--->Lines: 126
--->X-Priority: 3
--->X-MSMail-Priority: Normal
--->X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
--->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
--->X-RFC2646: Format=Flowed; Response
--->Message-ID: <#A2VfFGsIHA.5580@TK2MSFTNGP04.phx.gbl>
--->Newsgroups: microsoft.public.windows.server.general
--->NNTP-Posting-Host: 66-193-206-2.static.twtelecom.net 66.193.206.2
--->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
--->Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.general:37889
--->X-Tomcat-NG: microsoft.public.windows.server.general
--->
--->No need to reply. I answered my own question. Thanks again Morgan che.
--->
--->
--->"Arsenal2003" <Arsenal2003@newsgroup.nospam> wrote in message
--->news:Okp2j5EsIHA.1236@TK2MSFTNGP02.phx.gbl...
--->> Thank you for the excellent information. I will look into these
options.
--->>
--->> Seems like I can still use the File Server Migration Toolkit to
migrate
--->> the information over to the new server, correct? It seems like this
will
--->> be easier than restoring a backup of the files on the new server.
--->>
--->>
--->> "Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
--->> news:hW$2WUCsIHA.1788@TK2MSFTNGHUB02.phx.gbl...
--->>> Hi,
--->>>
--->>> Thanks for posting here.
--->>>
--->>> From your description, I understand you concern how to keep
consistency
--->>> of
--->>> all UNC paths, mapped drivers/printers after migrating files to the
new
--->>> serve with Windows server 2003 R2 by using FSMT. If I misunderstood,
--->>> please
--->>> let me know.
--->>>
--->>> DFS can make end-users easily access files without being aware of
where
--->>> these files really reside. However, based on the situation you want
to
--->>> keep
--->>> consistency of mapped drivers and UNC paths, I suggest performing the
--->>> following steps. Here, I listed two methods for your reference:
--->>>
--->>> <1> Rename the new file serve as old server
--->>>
--->>> After migrating files and folders and ensuring everything works fine
on
--->>> the
--->>> new server, we can remove the old server and rename the new serve as
old
--->>> server. Then, update A record on DNS according to the current IP
address
--->>> of
--->>> new file serve.
--->>>
--->>> After doing this, clients can still use the old UNC path to access
mapped
--->>> drives, etc.
--->>>
--->>> <2>Create Alias record on DNS for the new file server
--->>>
--->>> We can remove old server and create a Alias record for the new file
--->>> server,
--->>> so that the end-users will not be aware of file serve changing.
--->>>
--->>> How to create a DNS Alias record, please refer to:
--->>>
--->>> Creating a DNS Alias Record
--->>> http://support.microsoft.com/kb/168322/en-us
--->>>
--->>> Also, please have a look at the following KB article to avoid access
--->>> error
--->>> caused by alias record access.
--->>>
--->>> Connecting to SMB share on a Windows 2000-based computer or a Windows
--->>> Server 2003-based computer may not work with an alias name
--->>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;281308
--->>>
--->>> If anything is unclear, please post back.
--->>>
--->>> Have a nice day!
--->>>
--->>>
--->>> Sincerely
--->>> Morgan Che
--->>> Microsoft Online Support
--->>> Microsoft Global Technical Support Center
--->>>
--->>> 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.
--->>>
--->>>
--->>> --------------------
--->>> --->From: "Arsenal2003" <Arsenal2003@newsgroup.nospam>
--->>> --->Subject: File Server Migration
--->>> --->Date: Tue, 6 May 2008 14:56:59 -0700
--->>> --->Lines: 12
--->>> --->X-Priority: 3
--->>> --->X-MSMail-Priority: Normal
--->>> --->X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
--->>> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
--->>> --->X-RFC2646: Format=Flowed; Original
--->>> --->Message-ID: <#CO$eP8rIHA.5068@TK2MSFTNGP02.phx.gbl>
--->>> --->Newsgroups: microsoft.public.windows.server.general
--->>> --->NNTP-Posting-Host: 66-193-206-2.static.twtelecom.net 66.193.206.2
--->>> --->Path:
--->>> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
--->>> --->Xref: TK2MSFTNGHUB02.phx.gbl
--->>> microsoft.public.windows.server.general:37832
--->>> --->X-Tomcat-NG: microsoft.public.windows.server.general
--->>> --->
--->>> --->We want to migrate our old file server to a new server running
2003
--->>> R2.
--->>> The
--->>> --->main objective is to keep all mapped drives/printers and UNC
paths
--->>> the
--->>> same
--->>> --->as the old path from the client perspective. All the current
mappings
--->>> have
--->>> --->been made manually not via a login script. I tested the File
Server
--->>> --->Migration Toolkit in a lab. While the data and permissions
migrated
--->>> --->flawlessly, sometimes the mapped drives did not resolve on the
client
--->>> side.
--->>> --->
--->>> --->Do we have to use DFS to accomplish the above objectives? Has
anyone
--->>> else
--->>> --->had a similar scenario? Too eventually I will have another
server to
--->>> perform
--->>> --->the same task on. Any thoughts would be appreciated.
--->>> --->
--->>> --->
--->>> --->
--->>>
--->>
--->>
--->
--->
--->
 
Re: File Server Migration

Migration went as advertised. I used FSMT (without DFS), renamed the server
and verified the DNS A record reflected the correct IP.

Thanks again.


"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
news:O88eDR%23sIHA.1784@TK2MSFTNGHUB02.phx.gbl...
>
> Hi,
>
> How are you?
>
> I am writing to see if you have any update about this post. If you
> encounter any break/fix issue, please feel free to let me know.
>
> Have a good day!
> Sincerely
> Morgan Che
> Microsoft Online Support
> Microsoft Global Technical Support Center
>
> 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.
>
>
> --------------------
> --->From: "Arsenal2003" <Arsenal2003@newsgroup.nospam>
> --->References: <#CO$eP8rIHA.5068@TK2MSFTNGP02.phx.gbl>
> <hW$2WUCsIHA.1788@TK2MSFTNGHUB02.phx.gbl>
> <Okp2j5EsIHA.1236@TK2MSFTNGP02.phx.gbl>
> --->Subject: Re: File Server Migration
> --->Date: Wed, 7 May 2008 09:44:24 -0700
> --->Lines: 126
> --->X-Priority: 3
> --->X-MSMail-Priority: Normal
> --->X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
> --->X-RFC2646: Format=Flowed; Response
> --->Message-ID: <#A2VfFGsIHA.5580@TK2MSFTNGP04.phx.gbl>
> --->Newsgroups: microsoft.public.windows.server.general
> --->NNTP-Posting-Host: 66-193-206-2.static.twtelecom.net 66.193.206.2
> --->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
> --->Xref: TK2MSFTNGHUB02.phx.gbl
> microsoft.public.windows.server.general:37889
> --->X-Tomcat-NG: microsoft.public.windows.server.general
> --->
> --->No need to reply. I answered my own question. Thanks again Morgan che.
> --->
> --->
> --->"Arsenal2003" <Arsenal2003@newsgroup.nospam> wrote in message
> --->news:Okp2j5EsIHA.1236@TK2MSFTNGP02.phx.gbl...
> --->> Thank you for the excellent information. I will look into these
> options.
> --->>
> --->> Seems like I can still use the File Server Migration Toolkit to
> migrate
> --->> the information over to the new server, correct? It seems like this
> will
> --->> be easier than restoring a backup of the files on the new server.
> --->>
> --->>
> --->> "Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
> --->> news:hW$2WUCsIHA.1788@TK2MSFTNGHUB02.phx.gbl...
> --->>> Hi,
> --->>>
> --->>> Thanks for posting here.
> --->>>
> --->>> From your description, I understand you concern how to keep
> consistency
> --->>> of
> --->>> all UNC paths, mapped drivers/printers after migrating files to the
> new
> --->>> serve with Windows server 2003 R2 by using FSMT. If I
> misunderstood,
> --->>> please
> --->>> let me know.
> --->>>
> --->>> DFS can make end-users easily access files without being aware of
> where
> --->>> these files really reside. However, based on the situation you want
> to
> --->>> keep
> --->>> consistency of mapped drivers and UNC paths, I suggest performing
> the
> --->>> following steps. Here, I listed two methods for your reference:
> --->>>
> --->>> <1> Rename the new file serve as old server
> --->>>
> --->>> After migrating files and folders and ensuring everything works
> fine
> on
> --->>> the
> --->>> new server, we can remove the old server and rename the new serve
> as
> old
> --->>> server. Then, update A record on DNS according to the current IP
> address
> --->>> of
> --->>> new file serve.
> --->>>
> --->>> After doing this, clients can still use the old UNC path to access
> mapped
> --->>> drives, etc.
> --->>>
> --->>> <2>Create Alias record on DNS for the new file server
> --->>>
> --->>> We can remove old server and create a Alias record for the new file
> --->>> server,
> --->>> so that the end-users will not be aware of file serve changing.
> --->>>
> --->>> How to create a DNS Alias record, please refer to:
> --->>>
> --->>> Creating a DNS Alias Record
> --->>> http://support.microsoft.com/kb/168322/en-us
> --->>>
> --->>> Also, please have a look at the following KB article to avoid
> access
> --->>> error
> --->>> caused by alias record access.
> --->>>
> --->>> Connecting to SMB share on a Windows 2000-based computer or a
> Windows
> --->>> Server 2003-based computer may not work with an alias name
> --->>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;281308
> --->>>
> --->>> If anything is unclear, please post back.
> --->>>
> --->>> Have a nice day!
> --->>>
> --->>>
> --->>> Sincerely
> --->>> Morgan Che
> --->>> Microsoft Online Support
> --->>> Microsoft Global Technical Support Center
> --->>>
> --->>> 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.
> --->>>
> --->>>
> --->>> --------------------
> --->>> --->From: "Arsenal2003" <Arsenal2003@newsgroup.nospam>
> --->>> --->Subject: File Server Migration
> --->>> --->Date: Tue, 6 May 2008 14:56:59 -0700
> --->>> --->Lines: 12
> --->>> --->X-Priority: 3
> --->>> --->X-MSMail-Priority: Normal
> --->>> --->X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
> --->>> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
> --->>> --->X-RFC2646: Format=Flowed; Original
> --->>> --->Message-ID: <#CO$eP8rIHA.5068@TK2MSFTNGP02.phx.gbl>
> --->>> --->Newsgroups: microsoft.public.windows.server.general
> --->>> --->NNTP-Posting-Host: 66-193-206-2.static.twtelecom.net
> 66.193.206.2
> --->>> --->Path:
> --->>> TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
> --->>> --->Xref: TK2MSFTNGHUB02.phx.gbl
> --->>> microsoft.public.windows.server.general:37832
> --->>> --->X-Tomcat-NG: microsoft.public.windows.server.general
> --->>> --->
> --->>> --->We want to migrate our old file server to a new server running
> 2003
> --->>> R2.
> --->>> The
> --->>> --->main objective is to keep all mapped drives/printers and UNC
> paths
> --->>> the
> --->>> same
> --->>> --->as the old path from the client perspective. All the current
> mappings
> --->>> have
> --->>> --->been made manually not via a login script. I tested the File
> Server
> --->>> --->Migration Toolkit in a lab. While the data and permissions
> migrated
> --->>> --->flawlessly, sometimes the mapped drives did not resolve on the
> client
> --->>> side.
> --->>> --->
> --->>> --->Do we have to use DFS to accomplish the above objectives? Has
> anyone
> --->>> else
> --->>> --->had a similar scenario? Too eventually I will have another
> server to
> --->>> perform
> --->>> --->the same task on. Any thoughts would be appreciated.
> --->>> --->
> --->>> --->
> --->>> --->
> --->>>
> --->>
> --->>
> --->
> --->
> --->
>
 
Re: File Server Migration

Hi,

Thanks for the reply.

If you need further assitance or solve this issue, please let me know!

Sincerely
Morgan Che
Microsoft Online Support
Microsoft Global Technical Support Center

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.


--------------------
--->From: "Arsenal2003" <Arsenal2003@newsgroup.nospam>
--->References: <#CO$eP8rIHA.5068@TK2MSFTNGP02.phx.gbl>
<hW$2WUCsIHA.1788@TK2MSFTNGHUB02.phx.gbl>
<Okp2j5EsIHA.1236@TK2MSFTNGP02.phx.gbl>
<#A2VfFGsIHA.5580@TK2MSFTNGP04.phx.gbl>
<O88eDR#sIHA.1784@TK2MSFTNGHUB02.phx.gbl>
--->Subject: Re: File Server Migration
--->Date: Wed, 14 May 2008 13:32:09 -0700
--->Lines: 209
--->X-Priority: 3
--->X-MSMail-Priority: Normal
--->X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
--->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
--->X-RFC2646: Format=Flowed; Original
--->Message-ID: <O4b9WFgtIHA.1220@TK2MSFTNGP04.phx.gbl>
--->Newsgroups: microsoft.public.windows.server.general
--->NNTP-Posting-Host: 66-193-206-2.static.twtelecom.net 66.193.206.2
--->Path: TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
--->Xref: TK2MSFTNGHUB02.phx.gbl
microsoft.public.windows.server.general:38314
--->X-Tomcat-NG: microsoft.public.windows.server.general
--->
--->Migration went as advertised. I used FSMT (without DFS), renamed the
server
--->and verified the DNS A record reflected the correct IP.
--->
--->Thanks again.
--->
--->
--->"Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in message
--->news:O88eDR%23sIHA.1784@TK2MSFTNGHUB02.phx.gbl...
--->>
--->> Hi,
--->>
--->> How are you?
--->>
--->> I am writing to see if you have any update about this post. If you
--->> encounter any break/fix issue, please feel free to let me know.
--->>
--->> Have a good day!
--->> Sincerely
--->> Morgan Che
--->> Microsoft Online Support
--->> Microsoft Global Technical Support Center
--->>
--->> 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.
--->>
--->>
--->> --------------------
--->> --->From: "Arsenal2003" <Arsenal2003@newsgroup.nospam>
--->> --->References: <#CO$eP8rIHA.5068@TK2MSFTNGP02.phx.gbl>
--->> <hW$2WUCsIHA.1788@TK2MSFTNGHUB02.phx.gbl>
--->> <Okp2j5EsIHA.1236@TK2MSFTNGP02.phx.gbl>
--->> --->Subject: Re: File Server Migration
--->> --->Date: Wed, 7 May 2008 09:44:24 -0700
--->> --->Lines: 126
--->> --->X-Priority: 3
--->> --->X-MSMail-Priority: Normal
--->> --->X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
--->> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
--->> --->X-RFC2646: Format=Flowed; Response
--->> --->Message-ID: <#A2VfFGsIHA.5580@TK2MSFTNGP04.phx.gbl>
--->> --->Newsgroups: microsoft.public.windows.server.general
--->> --->NNTP-Posting-Host: 66-193-206-2.static.twtelecom.net 66.193.206.2
--->> --->Path:
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP04.phx.gbl
--->> --->Xref: TK2MSFTNGHUB02.phx.gbl
--->> microsoft.public.windows.server.general:37889
--->> --->X-Tomcat-NG: microsoft.public.windows.server.general
--->> --->
--->> --->No need to reply. I answered my own question. Thanks again Morgan
che.
--->> --->
--->> --->
--->> --->"Arsenal2003" <Arsenal2003@newsgroup.nospam> wrote in message
--->> --->news:Okp2j5EsIHA.1236@TK2MSFTNGP02.phx.gbl...
--->> --->> Thank you for the excellent information. I will look into these
--->> options.
--->> --->>
--->> --->> Seems like I can still use the File Server Migration Toolkit to
--->> migrate
--->> --->> the information over to the new server, correct? It seems like
this
--->> will
--->> --->> be easier than restoring a backup of the files on the new
server.
--->> --->>
--->> --->>
--->> --->> "Morgan che(MSFT)" <v-morche@online.microsoft.com> wrote in
message
--->> --->> news:hW$2WUCsIHA.1788@TK2MSFTNGHUB02.phx.gbl...
--->> --->>> Hi,
--->> --->>>
--->> --->>> Thanks for posting here.
--->> --->>>
--->> --->>> From your description, I understand you concern how to keep
--->> consistency
--->> --->>> of
--->> --->>> all UNC paths, mapped drivers/printers after migrating files
to the
--->> new
--->> --->>> serve with Windows server 2003 R2 by using FSMT. If I
--->> misunderstood,
--->> --->>> please
--->> --->>> let me know.
--->> --->>>
--->> --->>> DFS can make end-users easily access files without being aware
of
--->> where
--->> --->>> these files really reside. However, based on the situation you
want
--->> to
--->> --->>> keep
--->> --->>> consistency of mapped drivers and UNC paths, I suggest
performing
--->> the
--->> --->>> following steps. Here, I listed two methods for your reference:
--->> --->>>
--->> --->>> <1> Rename the new file serve as old server
--->> --->>>
--->> --->>> After migrating files and folders and ensuring everything
works
--->> fine
--->> on
--->> --->>> the
--->> --->>> new server, we can remove the old server and rename the new
serve
--->> as
--->> old
--->> --->>> server. Then, update A record on DNS according to the current
IP
--->> address
--->> --->>> of
--->> --->>> new file serve.
--->> --->>>
--->> --->>> After doing this, clients can still use the old UNC path to
access
--->> mapped
--->> --->>> drives, etc.
--->> --->>>
--->> --->>> <2>Create Alias record on DNS for the new file server
--->> --->>>
--->> --->>> We can remove old server and create a Alias record for the new
file
--->> --->>> server,
--->> --->>> so that the end-users will not be aware of file serve changing.
--->> --->>>
--->> --->>> How to create a DNS Alias record, please refer to:
--->> --->>>
--->> --->>> Creating a DNS Alias Record
--->> --->>> http://support.microsoft.com/kb/168322/en-us
--->> --->>>
--->> --->>> Also, please have a look at the following KB article to avoid
--->> access
--->> --->>> error
--->> --->>> caused by alias record access.
--->> --->>>
--->> --->>> Connecting to SMB share on a Windows 2000-based computer or a
--->> Windows
--->> --->>> Server 2003-based computer may not work with an alias name
--->> --->>> http://support.microsoft.com/default.aspx?scid=kb;EN-US;281308
--->> --->>>
--->> --->>> If anything is unclear, please post back.
--->> --->>>
--->> --->>> Have a nice day!
--->> --->>>
--->> --->>>
--->> --->>> Sincerely
--->> --->>> Morgan Che
--->> --->>> Microsoft Online Support
--->> --->>> Microsoft Global Technical Support Center
--->> --->>>
--->> --->>> 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.
--->> --->>>
--->> --->>>
--->> --->>> --------------------
--->> --->>> --->From: "Arsenal2003" <Arsenal2003@newsgroup.nospam>
--->> --->>> --->Subject: File Server Migration
--->> --->>> --->Date: Tue, 6 May 2008 14:56:59 -0700
--->> --->>> --->Lines: 12
--->> --->>> --->X-Priority: 3
--->> --->>> --->X-MSMail-Priority: Normal
--->> --->>> --->X-Newsreader: Microsoft Outlook Express 6.00.3790.3959
--->> --->>> --->X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.4133
--->> --->>> --->X-RFC2646: Format=Flowed; Original
--->> --->>> --->Message-ID: <#CO$eP8rIHA.5068@TK2MSFTNGP02.phx.gbl>
--->> --->>> --->Newsgroups: microsoft.public.windows.server.general
--->> --->>> --->NNTP-Posting-Host: 66-193-206-2.static.twtelecom.net
--->> 66.193.206.2
--->> --->>> --->Path:
--->> --->>>
TK2MSFTNGHUB02.phx.gbl!TK2MSFTNGP01.phx.gbl!TK2MSFTNGP02.phx.gbl
--->> --->>> --->Xref: TK2MSFTNGHUB02.phx.gbl
--->> --->>> microsoft.public.windows.server.general:37832
--->> --->>> --->X-Tomcat-NG: microsoft.public.windows.server.general
--->> --->>> --->
--->> --->>> --->We want to migrate our old file server to a new server
running
--->> 2003
--->> --->>> R2.
--->> --->>> The
--->> --->>> --->main objective is to keep all mapped drives/printers and
UNC
--->> paths
--->> --->>> the
--->> --->>> same
--->> --->>> --->as the old path from the client perspective. All the
current
--->> mappings
--->> --->>> have
--->> --->>> --->been made manually not via a login script. I tested the
File
--->> Server
--->> --->>> --->Migration Toolkit in a lab. While the data and permissions
--->> migrated
--->> --->>> --->flawlessly, sometimes the mapped drives did not resolve on
the
--->> client
--->> --->>> side.
--->> --->>> --->
--->> --->>> --->Do we have to use DFS to accomplish the above objectives?
Has
--->> anyone
--->> --->>> else
--->> --->>> --->had a similar scenario? Too eventually I will have another
--->> server to
--->> --->>> perform
--->> --->>> --->the same task on. Any thoughts would be appreciated.
--->> --->>> --->
--->> --->>> --->
--->> --->>> --->
--->> --->>>
--->> --->>
--->> --->>
--->> --->
--->> --->
--->> --->
--->>
--->
--->
--->
 
Back
Top