R
redheart27@rediffmail.com
Guest
I have a fundamental question that is not directly answered anywhere,
hence I seek your help. I wish to understand the idea behind the
design. My intention is to learn.
This is how I (as a newbie) would expect DFS to be designed. (Assume a
Domain environment)
A DFS service runs on the DC/member servers. The namespace and other
configuration is replicated among these servers. The service will
listen to requests from clients and answer them by looking up its
data.
(a) As per the MS implementation, an empty physical directory
structure is created to represent the namespace. Why was this unusual
data representation chosen?
(b) Why does Active Directory(AD) duplicate the information of the DFS
root? In fact, why does AD get involved at all, except perhaps, to
provide the information for clients to locate the DFS servers?
Please help. Thanks.
hence I seek your help. I wish to understand the idea behind the
design. My intention is to learn.
This is how I (as a newbie) would expect DFS to be designed. (Assume a
Domain environment)
A DFS service runs on the DC/member servers. The namespace and other
configuration is replicated among these servers. The service will
listen to requests from clients and answer them by looking up its
data.
(a) As per the MS implementation, an empty physical directory
structure is created to represent the namespace. Why was this unusual
data representation chosen?
(b) Why does Active Directory(AD) duplicate the information of the DFS
root? In fact, why does AD get involved at all, except perhaps, to
provide the information for clients to locate the DFS servers?
Please help. Thanks.