moving shares, but keeping users' shorcut the same ?

[snufles]

We run a Windows Server 2003 environment (2 DC's) with multiple XP workstations, latest Service Packs.

Users all have a shortcut on their XP workstations that point to server1 for shared folders (\\server1\...).
We need to move the shared folders to server2, but we want to keep the user shorcuts to "\\server1" as is.
We tested with making a CNAME record in the DNS called "shared" and pointing it to the IP of server1...Did a ping and it resolved to the correct IP address (goal was to see if we could path to "\\shared" through windows explorer, but could not." 
Our intention was to move the shares to server2 and put a CNAME record called server1 that would resolve to server2's IP address. But it's obvious that wont work since our little test failed.

How can we do this, simplified. Thanks...

[wbrost]

have you checked into DFS? This is very picky about the configuration but once it is running you can modify paths without changing the users short cuts or paths.

check out the link:
http://technet.microsoft.com/en-us/library/cc738688%28WS.10%29.aspx

 

[snufles]

Yea I've looked into Distributed File System. Just wanted a quick fix for now, plus I'm not sure how DFS would work with a Hard Drive Enclosure; yet. Ultimately that will be the way we go, again just wanted a quick fix so we can hardware upgrade next week. Thanks!

Still researching so if anyone knows a way, or has a idea I can look into please post.

[snufles]

Well after almost two full days of research there are three solutions for me, here they are for anyone with a similar issue...

1) Create alias in WINS server - server1 must be taken offline for this to work

2) Create CNAME record server1 to point to server2's IP address, then reg hack on server2
    HKLM\System\CurrentControlSet\Services\Lanman\Parameters\DisableStrictNameChecking (DWORD = 1)

3) Registry hack again - server1 must be taken offline for this to work
    HKLM\System\CurrentControlSet\Services\Lanman\Parameters\OptionalNames (REG_SZ = server1 name here)
    Do believe you can make it a multiple string value if need be

Haven't tried anyone of these, but I'm sure they will do the trick

[drivenbywhat]

Why not map a drive on their pcs to the new share?