DFS question - this sounds like a Microsoft exam question!
Environ: Server 2008 domain with site in Houston and site in Phoenix. All on the same LAN.
I need a namespace for my office 2013 install files. The namespace will consist of a shared folder in Hou and a shared folder in PHX. I'm thinking my namespace will be something like \\office2013 and in that namespace will be target folders of \\houserver\share and \\phxserver\share.
Now, IF I copy my office 2013 install files into that namespace, will it also copy to the two target folders?
Am I thinking of this correctly?
Thanks
Cliff
I need a namespace for my office 2013 install files. The namespace will consist of a shared folder in Hou and a shared folder in PHX. I'm thinking my namespace will be something like \\office2013 and in that namespace will be target folders of \\houserver\share and \\phxserver\share.
Now, IF I copy my office 2013 install files into that namespace, will it also copy to the two target folders?
Am I thinking of this correctly?
Thanks
Cliff
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I think that's my issue at present....HOW it's being used.
The ROLE DFS is not installed. We are relying on the DFS and DFR that gets installed when the server is promoted to a DC, so, basically, our DFS shares are on our DC and we manage it from the DC.
I have always seen DFS on a file server, ROLE installed, and not on a DC, per se.
Also, the way we are using it, users in Houston sometimes hit name spaces that have targets in PHX. I mean why pull stuff across the P2P when you could have it stored locally? It just seems like we are "misusing" DFS in a way, or at least not using it like we should.
Make sense?
The ROLE DFS is not installed. We are relying on the DFS and DFR that gets installed when the server is promoted to a DC, so, basically, our DFS shares are on our DC and we manage it from the DC.
I have always seen DFS on a file server, ROLE installed, and not on a DC, per se.
Also, the way we are using it, users in Houston sometimes hit name spaces that have targets in PHX. I mean why pull stuff across the P2P when you could have it stored locally? It just seems like we are "misusing" DFS in a way, or at least not using it like we should.
Make sense?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I'm onsite and this organization keeps telling me that they use DFS but the roles aren't installed on the file servers.
DFS is on the DCs because its replicating sysvol and netlogon folders.
What they are doing is loading the DFS snapin on local PCs and creating a single namespace and then mapping that name space to a UNC path. So there's a namespace named \\domain.local\corpshare and under there are shortcuts pointing to file shares on servers all over the domain. So, while I guess it works for name spaces, it doesn't seem like DFS to me.
I thought DFS was more creating a name space, pointing that to several target folders and storing info in the name space and seeing it replicate to the target folders. It seems we are not doing that at all since every name space points to a single network share. I mean what's the point in that? If Im in Hou hitting a name space pointed to a target in Phoenix, I'm having to pull that data across our P2P. It seems that a "real" DFS share with replication and site awareness would be the preferred solution.
Am I crazy?