novice1980
asked on
Windows Shares on Windows 2003 Server
I am currently working on a project where i need to migrate several Windows 2003 servers to Windows 2008 servers. The problem which i am having at the moment is few of the Windows 2003 Servers are working as an application servers and few of them got File shares in them as most people normally access these shares.
I need to know is there any way that i can migrate these file shares without any issues.
Secondly what will be the Migration steps
I need to know is there any way that i can migrate these file shares without any issues.
Secondly what will be the Migration steps
-Run FastCopy application (free) to copy from source to destination file server -- make sure you checkmark ACL
-during a scheduled downtime, turn on "Server" service on old file server
-Run FastCopy application (free) to copy from source to destination file server for a Delta copy -- make sure you checkmark ACL
-Reshare the shares on the new file server with SAME share names
-Rename the old server's hostname to for example: "FileServerOLD"
-Rename the new server's hostname to the same name as the old server had
-during a scheduled downtime, turn on "Server" service on old file server
-Run FastCopy application (free) to copy from source to destination file server for a Delta copy -- make sure you checkmark ACL
-Reshare the shares on the new file server with SAME share names
-Rename the old server's hostname to for example: "FileServerOLD"
-Rename the new server's hostname to the same name as the old server had
ASKER
I dont need a paid solution
You get a 30 day free trial : )
ASKER
My environment will not allow me to use third party software's so i need to find a solution which i can perform this task by giving solutions from Microsoft.
Take a look at Robocopy or the file server migration toolkit.
http://blogs.technet.com/b/josebda/archive/2009/06/30/microsoft-file-server-migration-toolkit-1-2-available-as-a-free-download.aspx
http://technet.microsoft.com/en-us/library/cc733145(WS.10).aspx
http://blogs.technet.com/b/josebda/archive/2009/06/30/microsoft-file-server-migration-toolkit-1-2-available-as-a-free-download.aspx
http://technet.microsoft.com/en-us/library/cc733145(WS.10).aspx
XCOPY should work on 2003 fine
Copy files and/or directory trees to another folder. XCOPY is similar to the COPY command except that it has additional switches to specify both the source and destination in detail.
NOTE: Xcopy is now deprecated under Vista and Windows 2008 - use Robocopy instead
http://ss64.com/nt/xcopy.html
xcopy commands in video
http://www.google.com.au/search?sourceid=navclient&aq=1&oq=Xcopy&hl=en-GB&ie=UTF-8&rlz=1T4GGLL_enAU394AU394&q=xcopy+commands#q=xcopy+commands&hl=en&rlz=1T4GGLL_enAU394AU394&prmd=imvns&source=lnms&tbm=vid&ei=DqubTtbHDaWriAfjpOisAg&sa=X&oi=mode_link&ct=mode&cd=4&ved=0CBEQ_AUoAw&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=b7e5bb913cb3de15&biw=1412&bih=718
Switches That You Can Use with Xcopy and Xcopy32 Commands
http://support.microsoft.com/kb/289483
http://www.computerhope.com/xcopyhlp.htm
That should cover it for you including KenMcF comment
Copy files and/or directory trees to another folder. XCOPY is similar to the COPY command except that it has additional switches to specify both the source and destination in detail.
NOTE: Xcopy is now deprecated under Vista and Windows 2008 - use Robocopy instead
http://ss64.com/nt/xcopy.html
xcopy commands in video
http://www.google.com.au/search?sourceid=navclient&aq=1&oq=Xcopy&hl=en-GB&ie=UTF-8&rlz=1T4GGLL_enAU394AU394&q=xcopy+commands#q=xcopy+commands&hl=en&rlz=1T4GGLL_enAU394AU394&prmd=imvns&source=lnms&tbm=vid&ei=DqubTtbHDaWriAfjpOisAg&sa=X&oi=mode_link&ct=mode&cd=4&ved=0CBEQ_AUoAw&bav=on.2,or.r_gc.r_pw.,cf.osb&fp=b7e5bb913cb3de15&biw=1412&bih=718
Switches That You Can Use with Xcopy and Xcopy32 Commands
http://support.microsoft.com/kb/289483
http://www.computerhope.com/xcopyhlp.htm
That should cover it for you including KenMcF comment
ok. copying the data is relatively easy as I'm sure you know, as is setting up new ahares.
What can be an issue of course is the people with shortcutsp, unc links, drives mapped to the servers old name.
Aside from changing these your options are:
1. New server replaces old one
Bring 2008 server in temp name
precopy data, permissions
create shares
Rename old server
recopy changed data
rename new 2008 server with old name.
2. New server with diffeereent name responds to old name too
Now if you want to poimt several old servers to one new one with the same old name you can do that.... Though not ideal...:
new 2008 server 'newserver'
old server 'old1' 'old2'
move data etc.
Rename old1 and old2 servers to different name
create alias (cname) record in dns pointing old1 and old2 to newserver
need to use setspn to set service principal name on newserver to accept \\old1 and \\old1.domain.local as names too and also a registry key to turn off 'strictnamechecking'.
I can give you links on MS documents etc. On those but too difficult from phone!
3. newserver - tell users to repoint to it....
If you are going to do this and arent already us,ing dfs then create a dfs name space and link all your shares under there. you could do that BEFORE your migration for instance to get people to change, i.e.
\\domain.local\dfs
share1 - points to \\oldserver\share1
ahare2 - points to \\oldserver2\share2
then you can either use entry for each link to \\newserver\share1 etc. And the users will still be able to access it through the dfs path.
Anyway written far too much on phone, give us some feedback on what direction you need to take if you want more....
Oh yeah.... Option 4, get someone in to help you implement option 1-3 if needed!
Steve
What can be an issue of course is the people with shortcutsp, unc links, drives mapped to the servers old name.
Aside from changing these your options are:
1. New server replaces old one
Bring 2008 server in temp name
precopy data, permissions
create shares
Rename old server
recopy changed data
rename new 2008 server with old name.
2. New server with diffeereent name responds to old name too
Now if you want to poimt several old servers to one new one with the same old name you can do that.... Though not ideal...:
new 2008 server 'newserver'
old server 'old1' 'old2'
move data etc.
Rename old1 and old2 servers to different name
create alias (cname) record in dns pointing old1 and old2 to newserver
need to use setspn to set service principal name on newserver to accept \\old1 and \\old1.domain.local as names too and also a registry key to turn off 'strictnamechecking'.
I can give you links on MS documents etc. On those but too difficult from phone!
3. newserver - tell users to repoint to it....
If you are going to do this and arent already us,ing dfs then create a dfs name space and link all your shares under there. you could do that BEFORE your migration for instance to get people to change, i.e.
\\domain.local\dfs
share1 - points to \\oldserver\share1
ahare2 - points to \\oldserver2\share2
then you can either use entry for each link to \\newserver\share1 etc. And the users will still be able to access it through the dfs path.
Anyway written far too much on phone, give us some feedback on what direction you need to take if you want more....
Oh yeah.... Option 4, get someone in to help you implement option 1-3 if needed!
Steve
ASKER
Thanks dragon-it for your comments. I really appreciate that. My project has been put into pending stage for 2 weeks. But i will do the testing this weekend by following your comments and hope everything works fine for me
Is it possible that you can provide me with the links of microsoft documents if possible.
Thanks again
Is it possible that you can provide me with the links of microsoft documents if possible.
Thanks again
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
though if you can possiby use DFS aswell you will stop yourself any future migration headaches.
Steve
Steve
ASKER
Thanks dragon-it for your time and helping me out with this problem. I tried it on my testing enviornment and it works for me.
I will give it a go for my production environment after 2 weeks.
In addition thanks everyone for your time and replying with solutions
I will give it a go for my production environment after 2 weeks.
In addition thanks everyone for your time and replying with solutions
no problem, glad to help. is tried and tested methods so should be ok but shout if any issues with related q and will try and help
Free but harder option http://www.microsoft.com/download/en/details.aspx?DisplayLang=en&id=10268