Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations derfloh on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
moving a share, want the same path, don't want dfs...
- Thread starter age
- Start date
snootalope
IS-IT--Management
Gee.. I was going to say folder redirection, but now that I look at how Group Policy handles it, I don't think it's possible without using DFS or changing the names of the servers of course..
snoots
"tis better to remain silent and be thought of as a fool..
then open your mouth and remove all doubt" Mark Twain
"I should of been a doctor.." Me
snoots
"tis better to remain silent and be thought of as a fool..
then open your mouth and remove all doubt" Mark Twain
"I should of been a doctor.." Me
GenesisCraigM
MIS
The thing to remember is that that's what DFS is FOR. If you don't want to use DFS, you are waiving your right to move shares without having to change the UNC path. That's sort of the point of having DFS.
You can't reasonably expect to be able to move a share to an entirely new server without having to change where the clients are connecting without either using DFS or alternatively, naming the new server the same as the old server. With DFS, you will still have to change where the clients connect, but only once. From then on, you have the advantage of the DFS namespace. You really should use this as an opportunity to set up DFS. You will be happy you did it the next 5 times you have to migrate a file server.
ADDITIONALLY, you should be VERY CAREFUL with Microsoft Office applications if the UNC paths change.
Microsoft Office's "Recent Document List" on every FILE menu will, RANDOMLY sometimes bind to the UNC path or the DRIVE LETTER path. There is no rhyme or reason to this behavior in Microsoft Office and no pattern to it. SO:
If the UNC path IS going to change, you REALLY NEED to make sure the files on the old server are NO LONGER SHARED. Because Microsoft Office applications will indeed accidentally try to connect to it when someone uses their recent file list in Office. If the old files are still shared, and users are using Microsoft office's recently opened files list, half your users will be using the old files, and half will be using the new files, and then the nightmares, screaming, and anger begin.
Good luck.
Craig J Matthews
System Administrator, Genesis Group
craigm@genesisgroup.com
You can't reasonably expect to be able to move a share to an entirely new server without having to change where the clients are connecting without either using DFS or alternatively, naming the new server the same as the old server. With DFS, you will still have to change where the clients connect, but only once. From then on, you have the advantage of the DFS namespace. You really should use this as an opportunity to set up DFS. You will be happy you did it the next 5 times you have to migrate a file server.
ADDITIONALLY, you should be VERY CAREFUL with Microsoft Office applications if the UNC paths change.
Microsoft Office's "Recent Document List" on every FILE menu will, RANDOMLY sometimes bind to the UNC path or the DRIVE LETTER path. There is no rhyme or reason to this behavior in Microsoft Office and no pattern to it. SO:
If the UNC path IS going to change, you REALLY NEED to make sure the files on the old server are NO LONGER SHARED. Because Microsoft Office applications will indeed accidentally try to connect to it when someone uses their recent file list in Office. If the old files are still shared, and users are using Microsoft office's recently opened files list, half your users will be using the old files, and half will be using the new files, and then the nightmares, screaming, and anger begin.
Good luck.
Craig J Matthews
System Administrator, Genesis Group
craigm@genesisgroup.com
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question