Windows Shares on Windows 2003 Server

Posted on 2011-10-14
Last Modified: 2013-11-05
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
Question by:novice1980
    LVL 5

    Expert Comment

    This is a good tool that is easy to use and will get the job done.

    Free but harder option
    LVL 3

    Expert Comment

    -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

    Author Comment

    I dont need a paid solution
    LVL 5

    Expert Comment

    You get a 30 day free trial : )

    Author Comment

    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.
    LVL 27

    Expert Comment

    LVL 69

    Expert Comment

    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
    xcopy commands in video,or.r_gc.r_pw.,cf.osb&fp=b7e5bb913cb3de15&biw=1412&bih=718
    Switches That You Can Use with Xcopy and Xcopy32 Commands
    That should cover it for you including KenMcF comment
    LVL 43

    Expert Comment

    by:Steve Knight
    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.

        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!


    Author Comment

    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
    LVL 43

    Accepted Solution

    Yes, sure.  Now I'm on a PC is somewhat easier :-)

    Have migrated many servers using these methods in different ways and orders depending upon what is required.  Main problems run into is you find an old legacy app. is running on a Win 2000 domain controller which is also a CA, file server etc. or the like. but various things rely on the server name being kept the same.... you know the sort of thing!

    ANyway here goes... this is the documentation I used recently to cover what we planned doing for the client.  You will need out of this if responding to an old servername :

    Disable Strict Name Checking
    Set SPN's
    Set CNAME alias in DNS

    Responding to another server name

    Alias CNAME in DNS for old server name "oldserver" for instance pointing to "newserver.domain.local"

    Needs amendments to servers:

    If you have an existing Windows 2008 R2 file server and would like to add an alternate name or alias for file share access, an SMB alias needs to be created.

    In previous version of Windows 2000 and 2003, a registry setting was all that was required in order to enable SMB aliasing, see Microsoft KB281308, but this only works with SMB 1.0 and not SMB 2.0. Computers that run Windows Server 2008, Windows Server 2008 R2, Windows Vista, and Windows 7 support both SMB 1.0 and SMB 2.0. Windows includes an SMB client component (Client for Microsoft Windows) and an SMB server component (File and Printer Sharing for Microsoft Windows). By default, SMB 2.0 is the file sharing protocol that is used when both client and server support it. For more information on SMB 2.0 click here.

    To add a SMB alias in Windows 2008 R2 which supports SMB 2.0, do as follows:
    1. Add a CNAME record in your DNS pointing at the primary server name, e.g. fileserver.mydomain.local CNAME server1.mydomain.local.

    2. Open the Registry Editor (regedit) on the server and browse to: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters

    3. Add a new REG_DWORD 32bit entry using the edit menu.
    Value name: DisableStrictNameChecking
    Data type : REG_DWORD
    Radix : Decimal
    Value : 1

    4. Exit the registry editor then reboot your server.

    5. Once the server reboots you need to add a Service Principal Name (SPN) as follows:
    a. Open the command prompt.
    b. Type: setspn -a host/fileserver server 1 (where 'server1' is the primary name of your server and 'fileserver' is the alternate name)
    b. Type: setspn -a host/fileserver.mydomain.local server1 (where fileserver.mydomain.local is the fully qualified domain name alias and server1 is the primary name of your server)
    setspn -a host/<NEW_CNAME_Server> <NetBIOS_Name_Server>
    setspn -a host/<NEW_CNAME_FQDN_Server> <NetBIOS_Name_Server>
    Your new SMB 2.0 alias should now be configured. Browse to \\your-new-alias to confirm.


    MS etc. documents on this subject which I used when doing this a little while ago:

    Disable Strict Name Checking and setting SPN

    More of the same:

    Disabling loopback checking (shouldn’t be relevant as is from server back to itself)


    LVL 43

    Expert Comment

    by:Steve Knight
    though if you can possiby use DFS aswell you will stop yourself any future migration headaches.


    Author Comment

    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
    LVL 43

    Expert Comment

    by:Steve Knight
    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

    Featured Post

    6 Surprising Benefits of Threat Intelligence

    All sorts of threat intelligence is available on the web. Intelligence you can learn from, and use to anticipate and prepare for future attacks.

    Join & Write a Comment

    Join Greg Farro and Ethan Banks from Packet Pushers ( and Greg Ross from Paessler ( for a discussion about smart network …
    If you're not part of the solution, you're part of the problem.   Tips on how to secure IoT devices, even the dumbest ones, so they can't be used as part of a DDoS botnet.  Use PRTG Network Monitor as one of the building blocks, to detect unusual…
    This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…
    After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

    731 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    16 Experts available now in Live!

    Get 1:1 Help Now