Moving Domain Based DFS from member server to DC's
Hello,
We currently have a domain based DFS namespace hosted on our file server. We want to move it to our DC's instead. Now the actual Namespace root is called \\domain\public and there are no links listed under it as the namespace was created using an existing share. I want to try to avoid having to create a new link called Public under that one and have it shown as \\slgreen.prv\Public\Publi
We currently have a domain based DFS namespace hosted on our file server. We want to move it to our DC's instead. Now the actual Namespace root is called \\domain\public and there are no links listed under it as the namespace was created using an existing share. I want to try to avoid having to create a new link called Public under that one and have it shown as \\slgreen.prv\Public\Publi
What version of DFS are you running? Is it 2000, 2003 or 2008? It will make a difference on how you will go about moving it.
ASKER
It is on a 2003 R2 server and I'm moving it to a 2008 R2 server.
Add the new server to the DFS replication group to get the data replicated.
one you have that done, you would alter the DFS management and add the new server as a target while removing the other server.
i.e. \domain\public you have a list of targets. or alias links?
one you have that done, you would alter the DFS management and add the new server as a target while removing the other server.
i.e. \domain\public you have a list of targets. or alias links?
ASKER
The problem is that i want keep the data where it is. I just want the DC's to hold the Namespace links. There are no links as the Root was created on the member server using the existing share Public. So we map the the users to that DFS share.
Are the files going to stay at their current location or are you going to move them to the DC's?
You can see from our DFS implementation that we have a Domain DFS. I renamed ours to "\\dfs.com\group" I created links to all the folders on the 3 file servers we have, but yours can be different.
You would add the DC's as namespace servers to the existing DFS.
dfs.jpg
You can see from our DFS implementation that we have a Domain DFS. I renamed ours to "\\dfs.com\group" I created links to all the folders on the 3 file servers we have, but yours can be different.
You would add the DC's as namespace servers to the existing DFS.
dfs.jpg
ASKER
Tripyre,
We currently have our Main file shares done that way. This was created before anyone knew what they were doing. So that under the Namespace tab there are NO folders. See attached.
Clipboard01.jpg
We currently have our Main file shares done that way. This was created before anyone knew what they were doing. So that under the Namespace tab there are NO folders. See attached.
Clipboard01.jpg
What do you mean?
You can define multiple root shares i.e.
\\domain\share
\\domain\share2
It all depends on your setup.
Some prefer to have
\\domain\primary\
and then have each share defined individually.
I do not get the significance you are trying to address. Do you want all the domain shares listed under a single \\domain\listofallshares\ setup?
Just to be clear the DFS is controlled by the DC's and is then redirected to the servers holding the shares. you can confirm this by running \\dcserver1\share and you will end up on the same share you would if you were using \\domain\share.
You can define multiple root shares i.e.
\\domain\share
\\domain\share2
It all depends on your setup.
Some prefer to have
\\domain\primary\
and then have each share defined individually.
I do not get the significance you are trying to address. Do you want all the domain shares listed under a single \\domain\listofallshares\ setup?
Just to be clear the DFS is controlled by the DC's and is then redirected to the servers holding the shares. you can confirm this by running \\dcserver1\share and you will end up on the same share you would if you were using \\domain\share.
ASKER
I apologize for the long break.
@arnold
Yes. We want to have \\domain\Public hosted on our DC's. SO, if I add the DC's to available Namespace servers the folder Public will be created under c:\dfsroots\public right? But if people get redirected to that server they will see nothing in it because the original DFS root was set on the File server that hosted the shared folder. I can add a folder that points to the Public folder but then the share would be \\domain\Public\Public. I wanted to see if i could avoid that.
@arnold
Yes. We want to have \\domain\Public hosted on our DC's. SO, if I add the DC's to available Namespace servers the folder Public will be created under c:\dfsroots\public right? But if people get redirected to that server they will see nothing in it because the original DFS root was set on the File server that hosted the shared folder. I can add a folder that points to the Public folder but then the share would be \\domain\Public\Public. I wanted to see if i could avoid that.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
We are not replicating data yet. We don't want our DC's hosting data either. With that said, you have confirmed my route. I will be setting up a new DFS namespace called All Public with links to different Public folders (we currently have 2 subsidiary companies with their own public folders). Thank you for all the help.