Easiest way to move from UNC to DFS?

We have a really large file server w/UNC shares on it.  What is the easiest way to setup DFS w/out disrupton to our users?  I was thinking about install DFS on the files server and set it up there but not sure what the best practice is.  We also use login scrips w/UNC paths.  What do you do after DFS is setup to fix the login scripts?  What does a new path look like?  Sorry. I realize DFS has been around forever but we are just not thinking about moving to it.
LVL 1
pclark6127Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

BrandonGalderisiCommented:
DFS stands for distributed file system.  So you can "HOST" all of your shares on one server, but the files are elsewhere.

So you create a DFS share on your server.  When you add new shared folders, you give them a path and a location.

So if you want the MyShare folder on the MyServer Server to point to \\ABC\DEF, the end result would be that by typing in \\MyServer\MyShare the user would see the files and folders in the \\abc\def folder.

You would simply change the login script to point the existing drive letter to the DFS share that tool the place of the old share.
0
pclark6127Author Commented:
So, if I install the DFS software and setup the pointers in the DFS root I can do this w/out affecting my users and then when I am ready just change the login scripts to point to the new DFS shares?  I don't have to worry about share permissions or anythinng like that do I?   Thanks....
0
BrandonGalderisiCommented:
I "BELIEVE" that the share permissions are all still handled by the target servers.  So not changing the share permissions is the right thing to do.  I just don't recall whether you need to setup permissions within the DFS.

Regardless, the "cutover" should be as simple as changing your login script to point to the DFS reference instead of the actual share.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
AmericomCommented:
NTFS permission still control by the server itself. The only time you would worry about permission is when you do DFS replication that is replicate the same share to a different servers, then the permission will replicate to the other server.

Also, you could use DFS namespace to address share instead of servername. For example, a regular share you have on a server is \\ServeName\Users\ can be accessed by \\DomainName\Users where "Users" is the sharename. This way if you ever move the share from old server to a new server, no need to update your script or shortcuts. With site design and replication, you can have the same data on different servers in different location with the same UNC path and name.
0
pclark6127Author Commented:
I am going to accept Brandons answer as it's specifically fits what I am looking for.  Thanks to the other contributor for the added info.

0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Legacy OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.