DFS Namespace

[Andy Simsons]

Using the DFS Management mmc, I created a namespace called DCSfiles and
hosted it on two Win2003 R2 domain controllers - the domain name is DCS. In
DCSfiles I created a folder called IRM and in that folder I created a folder
called Software. To the Software folder I added 3 folder targets - three
separate shared directories on a file server called DFStest. When I map to
\\DCS\DCSfiles\IRM from an XP client only the contents of one of the three
target folder appears under the Software folder. The target folder that
appears varies from one mapping to the next. Any ideas as to why don't all
three target folders appear when mapping to \\DCS\DCSfiles\IRM ?

[DaveMills]

On Wed, 21 Oct 2009 09:21:02 -0700, Andy Simsons

Post by Andy Simsons
Using the DFS Management mmc, I created a namespace called DCSfiles and
hosted it on two Win2003 R2 domain controllers - the domain name is DCS. In
DCSfiles I created a folder called IRM and in that folder I created a folder
called Software. To the Software folder I added 3 folder targets - three
separate shared directories on a file server called DFStest. When I map to
\\DCS\DCSfiles\IRM from an XP client only the contents of one of the three
target folder appears under the Software folder. The target folder that
appears varies from one mapping to the next. Any ideas as to why don't all
three target folders appear when mapping to \\DCS\DCSfiles\IRM ?

Because this is how it is designed to work. DFS name simple provide a way to use
a single DFS name to represent a UNC name. It allows multiple copies (targets)
of the UNC so the clients can be directed to any ONE of the [assumed to be]
identical targets thus providing redundancy and load balancing. It never merges
the target content, that is not the design function.

DFS Names do not in themselves ensure the multiple targets have identical
content. For that you must set up DFS replication or use some other replication
method.

All the gory details are in "How DFS Works"
http://technet.microsoft.com/en-us/library/cc782417(WS.10).aspx

[Andy Simsons]

OK, I think I see what your getting at and thanks for the link to "How DFS
works"
What I'm trying to do is link to a DFS folder three unique and different
folder targets so that when the users map to \\DCS\DCSFiles\IRM that under
the Software folder all three targets will appear:

Domain: DCS
Namespace: DCSFiles
|
+--IRM
| Folder Targets
+--Software ______________
|
| ===> \\DFSTest\Data\Peoplesoft
|
| ===> \\DFSTest\Data\OracleInstalls
|
| ===> \\DFSTest\Data\Quest

The intent is to create a DFS share mapping that will remain constant for
the users. If we have to move say the Quest folder to another server, then
we just need to change the link in DFS without having to remap the users.
How do we go about this?
--
Andy Simsons

Post by DaveMills
On Wed, 21 Oct 2009 09:21:02 -0700, Andy Simsons

Post by Andy Simsons
Using the DFS Management mmc, I created a namespace called DCSfiles and
hosted it on two Win2003 R2 domain controllers - the domain name is DCS. In
DCSfiles I created a folder called IRM and in that folder I created a folder
called Software. To the Software folder I added 3 folder targets - three
separate shared directories on a file server called DFStest. When I map to
\\DCS\DCSfiles\IRM from an XP client only the contents of one of the three
target folder appears under the Software folder. The target folder that
appears varies from one mapping to the next. Any ideas as to why don't all
three target folders appear when mapping to \\DCS\DCSfiles\IRM ?

Because this is how it is designed to work. DFS name simple provide a way to use
a single DFS name to represent a UNC name. It allows multiple copies (targets)
of the UNC so the clients can be directed to any ONE of the [assumed to be]
identical targets thus providing redundancy and load balancing. It never merges
the target content, that is not the design function.
DFS Names do not in themselves ensure the multiple targets have identical
content. For that you must set up DFS replication or use some other replication
method.
All the gory details are in "How DFS Works"
http://technet.microsoft.com/en-us/library/cc782417(WS.10).aspx
--
Dave Mills
There are 10 types of people, those that understand binary and those that don't.
.

[DaveMills]

On Thu, 22 Oct 2009 08:57:02 -0700, Andy Simsons

Post by Andy Simsons
OK, I think I see what your getting at and thanks for the link to "How DFS
works"
What I'm trying to do is link to a DFS folder three unique and different
folder targets so that when the users map to \\DCS\DCSFiles\IRM that under
Domain: DCS
Namespace: DCSFiles
|
+--IRM
| Folder Targets
+--Software ______________
|
| ===> \\DFSTest\Data\Peoplesoft
|
| ===> \\DFSTest\Data\OracleInstalls
|
| ===> \\DFSTest\Data\Quest
The intent is to create a DFS share mapping that will remain constant for
the users. If we have to move say the Quest folder to another server, then
we just need to change the link in DFS without having to remap the users.
How do we go about this?

This is EXACTLY what DFS is for.

1) Create the DFS Root (I think you have done this and called it DCSfiles)
2) Create a folder under the DFS root called IRM, create no links.
3) Create another folder in the DFS console under IRM called Software, again no
links
4) Create another folder in the DFS console under IRM/Software called Quest.
Repeat for Peoplesoft and OracleInstalls
4) Add a link to the Quest folder in the DFS console that targets
\\DFSTest\Data\Quest. Repeat for the other folders.


Now when you open \\DCS\DCSFiles\IRM\Quest the client will say Ah! a DFS link I
need to open \\DFSTest\Data\Quest.

Later you can change the target to \\NewServer\anyshare\Quest

One point though, I would recommend sharing the Quest folder as Quest$ instead
of sharing the Data folder and then linking to \\DFSTest\Quest$. Then you can
move the three target folders to different servers independently of each other
and simply change the target share name. It will still work with Data\Quest etc.
and you can still move the target but I find the simpler target name less
confusing and easier to set different share permissions (if needed). I also add
the "$" so the target is a hidden share and normal users will be unaware of it
so can only connect via DFS (unless they understand how to enumerate hidden
shares, which most do not).

You can also move on later to have say two targets for each folder as replicas.
You may have quest target \\siteAServer\\Quest$ and \\siteBserver\Quest$ and the
client will go to the "nearest" server. Other targets may end up as
\\SiteAServer\PeopleSoft$ and \\SiteCServer\\PeopleSoft$

I have set up my home folders like this, it is a school so I have E:\Data\Home
in which I have shared Year1, Year2 etc. as Year1$ etc.

I have DFS as \\AD\Storage\Home\Year1 pointing to the Year1$. If I run out of
space I can simply move a whole year group to a different server.

My backup software just backs up E:\ it does not know or care about DFS.