Discussion:
DFS after changing hostname
(too old to reply)
Tony
2009-03-09 02:07:06 UTC
Permalink
After changing the hostname of a root target, the metadata in DFS does not
update automatically. So now I have an outdated namespace server point to
the old hostname and several DFS links with outdated folder target inside.
How to fixed this without starting the file sync. all over again?
Isaac Oben [MCITP:EA, MCSE]
2009-03-09 03:21:12 UTC
Permalink
Hello Tony,
To better understand your situation and environment, please give some detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in DFS does not
update automatically. So now I have an outdated namespace server point to
the old hostname and several DFS links with outdated folder target inside.
How to fixed this without starting the file sync. all over again?
Tony
2009-03-09 06:22:01 UTC
Permalink
Ok, my DFS root looks like this right now \\mydomain\PUBLIC and has 6 root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets looks like
this

root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC

Under \mydomain\PUBLIC I have other links with replication setup and running
just fine. Each links also has 6 target. Something looks like this

link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A

For some reason I need to change the hostname host6 to host7. After done
this, root target and link target for host6 still pointing to host6 rather
than host7. So the referral does not work any more when users need to refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give some detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in DFS does not
update automatically. So now I have an outdated namespace server point to
the old hostname and several DFS links with outdated folder target inside.
How to fixed this without starting the file sync. all over again?
Isaac Oben [MCITP:EA, MCSE]
2009-03-09 08:08:36 UTC
Permalink
Tony,
Quick question, when yo say you changed the hostname, did you renamed host6
to host7 or you took host6 out and have host7 with new ip etc. If you
completely took host6 out, then you must forcefully removed it as well from
dfs, make sure it is not found in the root etc. You can do this by running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will just remove
everything regarding host6 from dfs but will not delete any of your data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC and has 6 root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets looks like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication setup and running
just fine. Each links also has 6 target. Something looks like this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7. After done
this, root target and link target for host6 still pointing to host6 rather
than host7. So the referral does not work any more when users need to refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give some detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in DFS does not
update automatically. So now I have an outdated namespace server point to
the old hostname and several DFS links with outdated folder target inside.
How to fixed this without starting the file sync. all over again?
Tony
2009-03-09 08:39:01 UTC
Permalink
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you renamed host6
to host7 or you took host6 out and have host7 with new ip etc. If you
completely took host6 out, then you must forcefully removed it as well from
dfs, make sure it is not found in the root etc. You can do this by running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will just remove
everything regarding host6 from dfs but will not delete any of your data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC and has 6 root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets looks like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication setup and running
just fine. Each links also has 6 target. Something looks like this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7. After done
this, root target and link target for host6 still pointing to host6 rather
than host7. So the referral does not work any more when users need to refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give some detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in DFS does not
update automatically. So now I have an outdated namespace server point to
the old hostname and several DFS links with outdated folder target inside.
How to fixed this without starting the file sync. all over again?
Isaac Oben [MCITP:EA, MCSE]
2009-03-09 09:47:03 UTC
Permalink
Tony,

My suggestions:
On the server side:
Do a net share and delete or unshare all folders pertaining to former host6
that you don't need.
Try doing
dfsutil.exe /unmapftroot /Root:domain.com /Server:host6 /share:public
dfsutil.exe /clean /server:host6 /share:public
and
On the Client side (users machine), I suggest you run dfsutil and flush the
local cached. Or they should reboot or just wait for replication to go
through

dfsutil.exe /PktFlush
dfsutil.exe /PurgeMupCache

Isaac
Post by Tony
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you renamed host6
to host7 or you took host6 out and have host7 with new ip etc. If you
completely took host6 out, then you must forcefully removed it as well from
dfs, make sure it is not found in the root etc. You can do this by running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will just remove
everything regarding host6 from dfs but will not delete any of your data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC and has 6 root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets
looks
like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication setup and running
just fine. Each links also has 6 target. Something looks like this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7. After done
this, root target and link target for host6 still pointing to host6 rather
than host7. So the referral does not work any more when users need to refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give some detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in DFS
does
not
update automatically. So now I have an outdated namespace server
point
to
the old hostname and several DFS links with outdated folder target inside.
How to fixed this without starting the file sync. all over again?
Tony
2009-03-09 10:24:00 UTC
Permalink
Hi Isaac,

I successfully ran the first dfsutil command. The second dfsutil command
returned with the following error

System error 168 has occurred.
Element not found.

Then I try to add host7 as a new root target but failed. The server said
host7 is already a DFS root.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Do a net share and delete or unshare all folders pertaining to former host6
that you don't need.
Try doing
dfsutil.exe /unmapftroot /Root:domain.com /Server:host6 /share:public
dfsutil.exe /clean /server:host6 /share:public
and
On the Client side (users machine), I suggest you run dfsutil and flush the
local cached. Or they should reboot or just wait for replication to go
through
dfsutil.exe /PktFlush
dfsutil.exe /PurgeMupCache
Isaac
Post by Tony
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you renamed host6
to host7 or you took host6 out and have host7 with new ip etc. If you
completely took host6 out, then you must forcefully removed it as well from
dfs, make sure it is not found in the root etc. You can do this by running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will just remove
everything regarding host6 from dfs but will not delete any of your data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC and has 6 root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets
looks
like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication setup and running
just fine. Each links also has 6 target. Something looks like this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7. After done
this, root target and link target for host6 still pointing to host6 rather
than host7. So the referral does not work any more when users need to refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give some detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in DFS
does
not
update automatically. So now I have an outdated namespace server
point
to
the old hostname and several DFS links with outdated folder target inside.
How to fixed this without starting the file sync. all over again?
Mark Parris [ADUG]
2009-03-09 16:36:33 UTC
Permalink
Are you running Windows Server 2000?
--
Mark Parris
MCSE: NT4.0, 2000, 2003
MCITP: EA, SA

Founder: [ADUG] UK Active Directory User Group http://adug.co.uk
Post by Tony
Hi Isaac,
I successfully ran the first dfsutil command. The second dfsutil command
returned with the following error
System error 168 has occurred.
Element not found.
Then I try to add host7 as a new root target but failed. The server said
host7 is already a DFS root.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Do a net share and delete or unshare all folders pertaining to former host6
that you don't need.
Try doing
dfsutil.exe /unmapftroot /Root:domain.com /Server:host6 /share:public
dfsutil.exe /clean /server:host6 /share:public
and
On the Client side (users machine), I suggest you run dfsutil and flush the
local cached. Or they should reboot or just wait for replication to go
through
dfsutil.exe /PktFlush
dfsutil.exe /PurgeMupCache
Isaac
Post by Tony
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you renamed host6
to host7 or you took host6 out and have host7 with new ip etc. If you
completely took host6 out, then you must forcefully removed it as well from
dfs, make sure it is not found in the root etc. You can do this by running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will just remove
everything regarding host6 from dfs but will not delete any of your data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC and has
6
root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets
looks
like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication setup and running
just fine. Each links also has 6 target. Something looks like this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7. After done
this, root target and link target for host6 still pointing to host6 rather
than host7. So the referral does not work any more when users need
to
refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give
some
detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in DFS
does
not
update automatically. So now I have an outdated namespace server
point
to
the old hostname and several DFS links with outdated folder
target
inside.
How to fixed this without starting the file sync. all over again?
Tony
2009-03-09 17:09:01 UTC
Permalink
I am in a mixed environment with W2K and W2K3 server. However, host7 is a
W2K server.
Post by Mark Parris [ADUG]
Are you running Windows Server 2000?
--
Mark Parris
MCSE: NT4.0, 2000, 2003
MCITP: EA, SA
Founder: [ADUG] UK Active Directory User Group http://adug.co.uk
Post by Tony
Hi Isaac,
I successfully ran the first dfsutil command. The second dfsutil command
returned with the following error
System error 168 has occurred.
Element not found.
Then I try to add host7 as a new root target but failed. The server said
host7 is already a DFS root.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Do a net share and delete or unshare all folders pertaining to former host6
that you don't need.
Try doing
dfsutil.exe /unmapftroot /Root:domain.com /Server:host6 /share:public
dfsutil.exe /clean /server:host6 /share:public
and
On the Client side (users machine), I suggest you run dfsutil and flush the
local cached. Or they should reboot or just wait for replication to go
through
dfsutil.exe /PktFlush
dfsutil.exe /PurgeMupCache
Isaac
Post by Tony
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you renamed host6
to host7 or you took host6 out and have host7 with new ip etc. If you
completely took host6 out, then you must forcefully removed it as well from
dfs, make sure it is not found in the root etc. You can do this by running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will just remove
everything regarding host6 from dfs but will not delete any of your data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC and has
6
root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets
looks
like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication setup and
running
just fine. Each links also has 6 target. Something looks like this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7. After done
this, root target and link target for host6 still pointing to host6 rather
than host7. So the referral does not work any more when users need
to
refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give
some
detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in DFS
does
not
update automatically. So now I have an outdated namespace server
point
to
the old hostname and several DFS links with outdated folder
target
inside.
How to fixed this without starting the file sync. all over again?
Isaac Oben [MCITP,MCSE]
2009-03-09 19:22:16 UTC
Permalink
Tony,
The second just indicated that host6 is no longer in the root. you can
forced remove host7 [dfsutil.exe /remftroot /server:host7 /share:public] and
the re add again [dfsutil.exe /addftroot /server:host7 /share:public]
--
Isaac Oben [MCTIP:EA, MCSE]
Post by Tony
Hi Isaac,
I successfully ran the first dfsutil command. The second dfsutil command
returned with the following error
System error 168 has occurred.
Element not found.
Then I try to add host7 as a new root target but failed. The server said
host7 is already a DFS root.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Do a net share and delete or unshare all folders pertaining to former host6
that you don't need.
Try doing
dfsutil.exe /unmapftroot /Root:domain.com /Server:host6 /share:public
dfsutil.exe /clean /server:host6 /share:public
and
On the Client side (users machine), I suggest you run dfsutil and flush the
local cached. Or they should reboot or just wait for replication to go
through
dfsutil.exe /PktFlush
dfsutil.exe /PurgeMupCache
Isaac
Post by Tony
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you renamed host6
to host7 or you took host6 out and have host7 with new ip etc. If you
completely took host6 out, then you must forcefully removed it as well from
dfs, make sure it is not found in the root etc. You can do this by running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will just remove
everything regarding host6 from dfs but will not delete any of your data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC and has
6
root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets
looks
like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication setup and running
just fine. Each links also has 6 target. Something looks like this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7. After done
this, root target and link target for host6 still pointing to host6 rather
than host7. So the referral does not work any more when users need
to
refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give
some
detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in DFS
does
not
update automatically. So now I have an outdated namespace server
point
to
the old hostname and several DFS links with outdated folder
target
inside.
How to fixed this without starting the file sync. all over again?
Tony
2009-03-10 01:07:01 UTC
Permalink
Hi Isaac,

I tried that but failed. It said

System error 183 has occurred.
Cannot create a file when that file already exists.

Which file should I remove before I can execute that command?
Post by Isaac Oben [MCITP,MCSE]
Tony,
The second just indicated that host6 is no longer in the root. you can
forced remove host7 [dfsutil.exe /remftroot /server:host7 /share:public] and
the re add again [dfsutil.exe /addftroot /server:host7 /share:public]
--
Isaac Oben [MCTIP:EA, MCSE]
Post by Tony
Hi Isaac,
I successfully ran the first dfsutil command. The second dfsutil command
returned with the following error
System error 168 has occurred.
Element not found.
Then I try to add host7 as a new root target but failed. The server said
host7 is already a DFS root.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Do a net share and delete or unshare all folders pertaining to former host6
that you don't need.
Try doing
dfsutil.exe /unmapftroot /Root:domain.com /Server:host6 /share:public
dfsutil.exe /clean /server:host6 /share:public
and
On the Client side (users machine), I suggest you run dfsutil and flush the
local cached. Or they should reboot or just wait for replication to go
through
dfsutil.exe /PktFlush
dfsutil.exe /PurgeMupCache
Isaac
Post by Tony
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you renamed host6
to host7 or you took host6 out and have host7 with new ip etc. If you
completely took host6 out, then you must forcefully removed it as well from
dfs, make sure it is not found in the root etc. You can do this by running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will just remove
everything regarding host6 from dfs but will not delete any of your data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC and has
6
root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets
looks
like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication setup and
running
just fine. Each links also has 6 target. Something looks like this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7. After done
this, root target and link target for host6 still pointing to host6 rather
than host7. So the referral does not work any more when users need
to
refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give
some
detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in DFS
does
not
update automatically. So now I have an outdated namespace server
point
to
the old hostname and several DFS links with outdated folder
target
inside.
How to fixed this without starting the file sync. all over again?
Isaac Oben [MCITP:EA, MCSE]
2009-03-10 06:50:43 UTC
Permalink
Tony,
Look through your Root and look for rooot target host7\public and also look
if you see host6\public(I am not sure this is still there) and if you see
any, right click and delete, then restart dfs service and the run command to
attempt to add host7\public to root. Also make sure all the link target for
host6 (if any) and host 7 are unlinked and then you may re link them later.

Isaac
Post by Tony
Hi Isaac,
I tried that but failed. It said
System error 183 has occurred.
Cannot create a file when that file already exists.
Which file should I remove before I can execute that command?
Post by Isaac Oben [MCITP,MCSE]
Tony,
The second just indicated that host6 is no longer in the root. you can
forced remove host7 [dfsutil.exe /remftroot /server:host7 /share:public] and
the re add again [dfsutil.exe /addftroot /server:host7 /share:public]
--
Isaac Oben [MCTIP:EA, MCSE]
Post by Tony
Hi Isaac,
I successfully ran the first dfsutil command. The second dfsutil command
returned with the following error
System error 168 has occurred.
Element not found.
Then I try to add host7 as a new root target but failed. The server said
host7 is already a DFS root.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Do a net share and delete or unshare all folders pertaining to former host6
that you don't need.
Try doing
dfsutil.exe /unmapftroot /Root:domain.com /Server:host6 /share:public
dfsutil.exe /clean /server:host6 /share:public
and
On the Client side (users machine), I suggest you run dfsutil and
flush
the
local cached. Or they should reboot or just wait for replication to go
through
dfsutil.exe /PktFlush
dfsutil.exe /PurgeMupCache
Isaac
Post by Tony
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you
renamed
host6
to host7 or you took host6 out and have host7 with new ip etc. If you
completely took host6 out, then you must forcefully removed it as
well
from
dfs, make sure it is not found in the root etc. You can do this by running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will just remove
everything regarding host6 from dfs but will not delete any of your data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC and has
6
root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets
looks
like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication setup and
running
just fine. Each links also has 6 target. Something looks like this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7.
After
done
this, root target and link target for host6 still pointing to
host6
rather
than host7. So the referral does not work any more when users need
to
refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give
some
detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in DFS
does
not
update automatically. So now I have an outdated namespace server
point
to
the old hostname and several DFS links with outdated folder
target
inside.
How to fixed this without starting the file sync. all over again?
Tony
2009-03-10 08:01:03 UTC
Permalink
I tried to unshare host7\public but it said "the share must be removed from
the DFS before it can be deleted". If I remove the public share, that means
I remove host7 out of the root replica? If I relink everything again will
that trigget the file sync. all over again?
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Look through your Root and look for rooot target host7\public and also look
if you see host6\public(I am not sure this is still there) and if you see
any, right click and delete, then restart dfs service and the run command to
attempt to add host7\public to root. Also make sure all the link target for
host6 (if any) and host 7 are unlinked and then you may re link them later.
Isaac
Post by Tony
Hi Isaac,
I tried that but failed. It said
System error 183 has occurred.
Cannot create a file when that file already exists.
Which file should I remove before I can execute that command?
Post by Isaac Oben [MCITP,MCSE]
Tony,
The second just indicated that host6 is no longer in the root. you can
forced remove host7 [dfsutil.exe /remftroot /server:host7 /share:public] and
the re add again [dfsutil.exe /addftroot /server:host7 /share:public]
--
Isaac Oben [MCTIP:EA, MCSE]
Post by Tony
Hi Isaac,
I successfully ran the first dfsutil command. The second dfsutil command
returned with the following error
System error 168 has occurred.
Element not found.
Then I try to add host7 as a new root target but failed. The server said
host7 is already a DFS root.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Do a net share and delete or unshare all folders pertaining to former host6
that you don't need.
Try doing
dfsutil.exe /unmapftroot /Root:domain.com /Server:host6 /share:public
dfsutil.exe /clean /server:host6 /share:public
and
On the Client side (users machine), I suggest you run dfsutil and
flush
the
local cached. Or they should reboot or just wait for replication to go
through
dfsutil.exe /PktFlush
dfsutil.exe /PurgeMupCache
Isaac
Post by Tony
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you
renamed
host6
to host7 or you took host6 out and have host7 with new ip etc. If you
completely took host6 out, then you must forcefully removed it as
well
from
dfs, make sure it is not found in the root etc. You can do this by
running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will just remove
everything regarding host6 from dfs but will not delete any of your data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC and has
6
root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets
looks
like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication setup and
running
just fine. Each links also has 6 target. Something looks like this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7.
After
done
this, root target and link target for host6 still pointing to
host6
rather
than host7. So the referral does not work any more when users need
to
refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give
some
detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in
DFS
does
not
update automatically. So now I have an outdated namespace
server
point
to
the old hostname and several DFS links with outdated folder
target
inside.
How to fixed this without starting the file sync. all over
again?
Isaac Oben [MCITP:EA, MCSE]
2009-03-10 08:42:36 UTC
Permalink
Tony,
If you remove host7\public it will remove it from the root replica but will
not delete the dfs files and folders. I am not sure what you mean by
triggering the file sync. But when you re add host7\public to the root it
will automatically re copy all the folders in the "public" share. If you
remove it, just remember to stop and restart the dfs service on host7.
Post by Tony
I tried to unshare host7\public but it said "the share must be removed from
the DFS before it can be deleted". If I remove the public share, that means
I remove host7 out of the root replica? If I relink everything again will
that trigget the file sync. all over again?
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Look through your Root and look for rooot target host7\public and also look
if you see host6\public(I am not sure this is still there) and if you see
any, right click and delete, then restart dfs service and the run command to
attempt to add host7\public to root. Also make sure all the link target for
host6 (if any) and host 7 are unlinked and then you may re link them later.
Isaac
Post by Tony
Hi Isaac,
I tried that but failed. It said
System error 183 has occurred.
Cannot create a file when that file already exists.
Which file should I remove before I can execute that command?
Post by Isaac Oben [MCITP,MCSE]
Tony,
The second just indicated that host6 is no longer in the root. you can
forced remove host7 [dfsutil.exe /remftroot /server:host7
/share:public]
and
the re add again [dfsutil.exe /addftroot /server:host7 /share:public]
--
Isaac Oben [MCTIP:EA, MCSE]
Post by Tony
Hi Isaac,
I successfully ran the first dfsutil command. The second dfsutil command
returned with the following error
System error 168 has occurred.
Element not found.
Then I try to add host7 as a new root target but failed. The server said
host7 is already a DFS root.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Do a net share and delete or unshare all folders pertaining to
former
host6
that you don't need.
Try doing
dfsutil.exe /unmapftroot /Root:domain.com /Server:host6
/share:public
dfsutil.exe /clean /server:host6 /share:public
and
On the Client side (users machine), I suggest you run dfsutil and
flush
the
local cached. Or they should reboot or just wait for replication
to
go
through
dfsutil.exe /PktFlush
dfsutil.exe /PurgeMupCache
Isaac
Post by Tony
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you
renamed
host6
to host7 or you took host6 out and have host7 with new ip etc.
If
you
completely took host6 out, then you must forcefully removed it as
well
from
dfs, make sure it is not found in the root etc. You can do this by
running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will
just
remove
everything regarding host6 from dfs but will not delete any of
your
data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC
and
has
6
root
targets say host1 to host6. So \\mydomain\PUBLIC has root targets
looks
like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication
setup
and
running
just fine. Each links also has 6 target. Something looks
like
this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7.
After
done
this, root target and link target for host6 still pointing to
host6
rather
than host7. So the referral does not work any more when users need
to
refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please give
some
detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata in
DFS
does
not
update automatically. So now I have an outdated namespace
server
point
to
the old hostname and several DFS links with outdated folder
target
inside.
How to fixed this without starting the file sync. all over
again?
Tony
2009-03-11 10:29:01 UTC
Permalink
Hi Isaac, thanks for your hints. I get it done finally. Here is the steps
of what I did:

1. use "dfscmd /remove ..." to remove all the links under the DFS tree refer
to host6 or host7
2. use "dfsutil /clean:host7" to clean up host7 as a root replica
3. unshare the DFS root folder (in my case which is public) in host7 to make
sure all DFS links are cleaned up
4. restart DFS service on host7
5. use "dfsutil /reinit:host7" to add host7 as a root replica again
6. use "dfscmd /add ..." to add all the links I removed in step 1 back to
the DFS tree

By this way I can retain all the files in the replication set in host7
without resynchronize everything from scratch. Some simple steps I maybe
missed, but you should know what I mean.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
If you remove host7\public it will remove it from the root replica but will
not delete the dfs files and folders. I am not sure what you mean by
triggering the file sync. But when you re add host7\public to the root it
will automatically re copy all the folders in the "public" share. If you
remove it, just remember to stop and restart the dfs service on host7.
Post by Tony
I tried to unshare host7\public but it said "the share must be removed from
the DFS before it can be deleted". If I remove the public share, that means
I remove host7 out of the root replica? If I relink everything again will
that trigget the file sync. all over again?
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Look through your Root and look for rooot target host7\public and also look
if you see host6\public(I am not sure this is still there) and if you see
any, right click and delete, then restart dfs service and the run command to
attempt to add host7\public to root. Also make sure all the link target for
host6 (if any) and host 7 are unlinked and then you may re link them later.
Isaac
Post by Tony
Hi Isaac,
I tried that but failed. It said
System error 183 has occurred.
Cannot create a file when that file already exists.
Which file should I remove before I can execute that command?
Post by Isaac Oben [MCITP,MCSE]
Tony,
The second just indicated that host6 is no longer in the root. you can
forced remove host7 [dfsutil.exe /remftroot /server:host7
/share:public]
and
the re add again [dfsutil.exe /addftroot /server:host7 /share:public]
--
Isaac Oben [MCTIP:EA, MCSE]
Post by Tony
Hi Isaac,
I successfully ran the first dfsutil command. The second dfsutil command
returned with the following error
System error 168 has occurred.
Element not found.
Then I try to add host7 as a new root target but failed. The server said
host7 is already a DFS root.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Do a net share and delete or unshare all folders pertaining to
former
host6
that you don't need.
Try doing
dfsutil.exe /unmapftroot /Root:domain.com /Server:host6 /share:public
dfsutil.exe /clean /server:host6 /share:public
and
On the Client side (users machine), I suggest you run dfsutil and
flush
the
local cached. Or they should reboot or just wait for replication
to
go
through
dfsutil.exe /PktFlush
dfsutil.exe /PurgeMupCache
Isaac
Post by Tony
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you
renamed
host6
to host7 or you took host6 out and have host7 with new ip etc.
If
you
completely took host6 out, then you must forcefully removed it as
well
from
dfs, make sure it is not found in the root etc. You can do this by
running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will
just
remove
everything regarding host6 from dfs but will not delete any of
your
data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC
and
has
6
root
targets say host1 to host6. So \\mydomain\PUBLIC has root
targets
looks
like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication
setup
and
running
just fine. Each links also has 6 target. Something looks
like
this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7.
After
done
this, root target and link target for host6 still pointing to
host6
rather
than host7. So the referral does not work any more when users
need
to
refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please
give
some
detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the metadata
in
DFS
does
not
update automatically. So now I have an outdated namespace
server
point
to
the old hostname and several DFS links with outdated folder
target
inside.
How to fixed this without starting the file sync. all over
again?
Isaac Oben [MCITP,MCSE]
2009-03-11 13:54:23 UTC
Permalink
Hello Tony,

Good to know you got it going and thanks for sharing your steps,

Isaac
--
Isaac Oben [MCTIP:EA, MCSE]
Post by Tony
Hi Isaac, thanks for your hints. I get it done finally. Here is the steps
1. use "dfscmd /remove ..." to remove all the links under the DFS tree refer
to host6 or host7
2. use "dfsutil /clean:host7" to clean up host7 as a root replica
3. unshare the DFS root folder (in my case which is public) in host7 to make
sure all DFS links are cleaned up
4. restart DFS service on host7
5. use "dfsutil /reinit:host7" to add host7 as a root replica again
6. use "dfscmd /add ..." to add all the links I removed in step 1 back to
the DFS tree
By this way I can retain all the files in the replication set in host7
without resynchronize everything from scratch. Some simple steps I maybe
missed, but you should know what I mean.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
If you remove host7\public it will remove it from the root replica but will
not delete the dfs files and folders. I am not sure what you mean by
triggering the file sync. But when you re add host7\public to the root it
will automatically re copy all the folders in the "public" share. If you
remove it, just remember to stop and restart the dfs service on host7.
Post by Tony
I tried to unshare host7\public but it said "the share must be removed from
the DFS before it can be deleted". If I remove the public share, that means
I remove host7 out of the root replica? If I relink everything again will
that trigget the file sync. all over again?
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Look through your Root and look for rooot target host7\public and
also
look
if you see host6\public(I am not sure this is still there) and if you see
any, right click and delete, then restart dfs service and the run
command
to
attempt to add host7\public to root. Also make sure all the link
target
for
host6 (if any) and host 7 are unlinked and then you may re link them later.
Isaac
Post by Tony
Hi Isaac,
I tried that but failed. It said
System error 183 has occurred.
Cannot create a file when that file already exists.
Which file should I remove before I can execute that command?
Post by Isaac Oben [MCITP,MCSE]
Tony,
The second just indicated that host6 is no longer in the root. you can
forced remove host7 [dfsutil.exe /remftroot /server:host7
/share:public]
and
the re add again [dfsutil.exe /addftroot /server:host7
/share:public]
--
Isaac Oben [MCTIP:EA, MCSE]
Post by Tony
Hi Isaac,
I successfully ran the first dfsutil command. The second dfsutil command
returned with the following error
System error 168 has occurred.
Element not found.
Then I try to add host7 as a new root target but failed. The
server
said
host7 is already a DFS root.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Do a net share and delete or unshare all folders pertaining to
former
host6
that you don't need.
Try doing
dfsutil.exe /unmapftroot /Root:domain.com /Server:host6 /share:public
dfsutil.exe /clean /server:host6 /share:public
and
On the Client side (users machine), I suggest you run dfsutil and
flush
the
local cached. Or they should reboot or just wait for replication
to
go
through
dfsutil.exe /PktFlush
dfsutil.exe /PurgeMupCache
Isaac
Post by Tony
I renamed the server from host6 to host7.
Post by Isaac Oben [MCITP:EA, MCSE]
Tony,
Quick question, when yo say you changed the hostname, did you
renamed
host6
to host7 or you took host6 out and have host7 with new ip etc.
If
you
completely took host6 out, then you must forcefully removed
it
as
well
from
dfs, make sure it is not found in the root etc. You can do
this
by
running
dfsutil at command prompt.
dfsutil.exe /remftroot /server:host6 /share:Public (this will
just
remove
everything regarding host6 from dfs but will not delete any of
your
data)
Post by Tony
Ok, my DFS root looks like this right now \\mydomain\PUBLIC
and
has
6
root
targets say host1 to host6. So \\mydomain\PUBLIC has root
targets
looks
like
this
root: \\mydomain\PUBLIC
root target: \\host1\PUBLIC
root target: \\host2\PUBLIC
root target: \\host3\PUBLIC
root target: \\host4\PUBLIC
root target: \\host5\PUBLIC
root target: \\host6\PUBLIC
Under \mydomain\PUBLIC I have other links with replication
setup
and
running
just fine. Each links also has 6 target. Something looks
like
this
link: \mydomain\PUBLIC\A
target: \\host1\A
target: \\host2\A
target: \\host3\A
target: \\host4\A
target: \\host5\A
target: \\host6\A
For some reason I need to change the hostname host6 to host7.
After
done
this, root target and link target for host6 still pointing to
host6
rather
than host7. So the referral does not work any more when
users
need
to
refer
to the new host.
Post by Isaac Oben [MCITP:EA, MCSE]
Hello Tony,
To better understand your situation and environment, please
give
some
detail
specifics.
Isaac
Post by Tony
After changing the hostname of a root target, the
metadata
in
DFS
does
not
update automatically. So now I have an outdated
namespace
server
point
to
the old hostname and several DFS links with outdated
folder
target
inside.
How to fixed this without starting the file sync. all
over
again?
Continue reading on narkive:
Loading...