DFS Windows 2003 domain

Hi Experts,

We are planning to implement DFS in a Windows 2003 domain and forest. The DCs are running 2003 R2 and our file server is a Windows 2008 R2 server. We were planning to implement at the domain level and have roots on the 2008 file server. This is a single site network but file shares are greater than 2TB on VMFS which is why we want to use DFS to make shares transparent to users.

Is there a better way to implement DFS? WIll running file shares on a 2008 R2 server in a 2003 domain have any issues?

Who is Participating?
kevinhsiehConnect With a Mentor Commented:
There are DFS namespaces (DFS-N), which should be hosted by your domain controllers. This relates to the pathing that users see to files, such as \\domain.local\dfs\departments\payroll\folder1.

DFS replication, (DFS-R) is about replicating files among various servers. While I always recommend DFS-N, even for tiny environments due to the advantages of UNC paths staying the same while physical file servers change, DFS-R requires a good understanding of what it does and how it can really hurt you because there is no distributed file locking, and different copies of the same file can get modified at the same time on different servers causing changes to be lost.
Since you are using domain based DFS, you actually are installing the DFS namespace on your Windows 2003 R2 domain controllers. You will then create links to your file server(s). Make sure that you setup the namespace on at least two domain controllers for redundancy.
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

On your Windows 2008 server you can setup a replication group for redundancy purposes.

Create a Replication Group-applies to 2008 and 2008 r2

abhijitm00Author Commented:
So I would go about creating the Namespace on the Windows 2008 File server or WIndows 2003 DC? I was under the assumption that if I create the namespace on the File Server then it will automatically generate the namespace under the 2003 DC? Many thanks
Your assumption about the namespace is incorrect. You need to create it on a domain controller.
abhijitm00Author Commented:
Hi kevinhsieh, thanks for your patience. On my Windows 2003 R2 DC I have the following data:

Domain: abc.com
Host Server: Windows 2008 R2 file server
Share name: program
Root name: program

Will I be having a new root name for each share that I create on the 2008 File Server?
I suggest 1 root, and then put everything under that.

domain: abc.com
root name: DFS
Root Share: \\abc.com\DFS (dc.abc.com\DFS)
      |_______ Program1 -> \\server1\apps$\program1
      |_______ Program2 -> \\server1\apps2$\program2
   Users -> \\server1\users$

I am using hidden $shares so they will not show up for clients browsing the file servers. It encourages them to just look at the DFS
abhijitm00Author Commented:
Hi Kevinhsieh, thanks for the response. I was able to implement the basic setup as you mentioned above but all my shares which are 2TB in size are shared from only one file server and when I try to browse to Programs I see only the content in Program1 and not Program2 i.e. Programs does not allow me to see combined data from Program1 and Program2 and I only see content from the first folder in the link. Do you know what I could look at to fix this? Thanks
Did you create a second folder and links for Program2 in DFS?
abhijitm00Author Commented:
Yes I created a folder target called as Program2 under the share called as Programs
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.

All Courses

From novice to tech pro — start learning today.