DFS after changing hostname

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?

Hello Tony,
To better understand your situation and environment, please give some detail
specifics.
Isaac

"Tony" <> wrote in message
news:05462462-4567-48AA-BD9A-...
> 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?

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.

"Isaac Oben [MCITP:EA, MCSE]" wrote:

>
> Hello Tony,
> To better understand your situation and environment, please give some detail
> specifics.
> Isaac
>
> "Tony" <> wrote in message
> news:05462462-4567-48AA-BD9A-...
> > 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,
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)


"Tony" <> wrote in message
news:EFAD226E-A603-41C2-B3AC-...
> 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.
>
> "Isaac Oben [MCITP:EA, MCSE]" wrote:
>
>>
>> Hello Tony,
>> To better understand your situation and environment, please give some
>> detail
>> specifics.
>> Isaac
>>
>> "Tony" <> wrote in message
>> news:05462462-4567-48AA-BD9A-...
>> > 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?
>>
>>
>>

I renamed the server from host6 to host7.

"Isaac Oben [MCITP:EA, MCSE]" wrote:

> 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)
>
>
> "Tony" <> wrote in message
> news:EFAD226E-A603-41C2-B3AC-...
> > 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.
> >
> > "Isaac Oben [MCITP:EA, MCSE]" wrote:
> >
> >>
> >> Hello Tony,
> >> To better understand your situation and environment, please give some
> >> detail
> >> specifics.
> >> Isaac
> >>
> >> "Tony" <> wrote in message
> >> news:05462462-4567-48AA-BD9A-...
> >> > 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,

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 /shareublic
dfsutil.exe /clean /server:host6 /shareublic
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

"Tony" <> wrote in message
news:40A6A053-EFE4-4430-AB72-...
>I renamed the server from host6 to host7.
>
> "Isaac Oben [MCITP:EA, MCSE]" wrote:
>
>> 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)
>>
>>
>> "Tony" <> wrote in message
>> news:EFAD226E-A603-41C2-B3AC-...
>> > 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.
>> >
>> > "Isaac Oben [MCITP:EA, MCSE]" wrote:
>> >
>> >>
>> >> Hello Tony,
>> >> To better understand your situation and environment, please give some
>> >> detail
>> >> specifics.
>> >> Isaac
>> >>
>> >> "Tony" <> wrote in message
>> >> news:05462462-4567-48AA-BD9A-...
>> >> > 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?
>> >>
>> >>
>> >>
>>
>>
>>

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.

"Isaac Oben [MCITP:EA, MCSE]" wrote:

> 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 /shareublic
> dfsutil.exe /clean /server:host6 /shareublic
> 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
>
> "Tony" <> wrote in message
> news:40A6A053-EFE4-4430-AB72-...
> >I renamed the server from host6 to host7.
> >
> > "Isaac Oben [MCITP:EA, MCSE]" wrote:
> >
> >> 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)
> >>
> >>
> >> "Tony" <> wrote in message
> >> news:EFAD226E-A603-41C2-B3AC-...
> >> > 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.
> >> >
> >> > "Isaac Oben [MCITP:EA, MCSE]" wrote:
> >> >
> >> >>
> >> >> Hello Tony,
> >> >> To better understand your situation and environment, please give some
> >> >> detail
> >> >> specifics.
> >> >> Isaac
> >> >>
> >> >> "Tony" <> wrote in message
> >> >> news:05462462-4567-48AA-BD9A-...
> >> >> > 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?
> >> >>
> >> >>
> >> >>
> >>
> >>
> >>
>
>
>

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

"Tony" <> wrote in message
news:305F2366-4742-4065-AA07-...
> 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.
>
> "Isaac Oben [MCITP:EA, MCSE]" wrote:
>
>> 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 /shareublic
>> dfsutil.exe /clean /server:host6 /shareublic
>> 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
>>
>> "Tony" <> wrote in message
>> news:40A6A053-EFE4-4430-AB72-...
>> >I renamed the server from host6 to host7.
>> >
>> > "Isaac Oben [MCITP:EA, MCSE]" wrote:
>> >
>> >> 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)
>> >>
>> >>
>> >> "Tony" <> wrote in message
>> >> news:EFAD226E-A603-41C2-B3AC-...
>> >> > 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.
>> >> >
>> >> > "Isaac Oben [MCITP:EA, MCSE]" wrote:
>> >> >
>> >> >>
>> >> >> Hello Tony,
>> >> >> To better understand your situation and environment, please give
>> >> >> some
>> >> >> detail
>> >> >> specifics.
>> >> >> Isaac
>> >> >>
>> >> >> "Tony" <> wrote in message
>> >> >> news:05462462-4567-48AA-BD9A-...
>> >> >> > 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?
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>

I am in a mixed environment with W2K and W2K3 server. However, host7 is a
W2K server.

"Mark Parris [ADUG]" wrote:

> 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
>
> "Tony" <> wrote in message
> news:305F2366-4742-4065-AA07-...
> > 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.
> >
> > "Isaac Oben [MCITP:EA, MCSE]" wrote:
> >
> >> 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 /shareublic
> >> dfsutil.exe /clean /server:host6 /shareublic
> >> 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
> >>
> >> "Tony" <> wrote in message
> >> news:40A6A053-EFE4-4430-AB72-...
> >> >I renamed the server from host6 to host7.
> >> >
> >> > "Isaac Oben [MCITP:EA, MCSE]" wrote:
> >> >
> >> >> 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)
> >> >>
> >> >>
> >> >> "Tony" <> wrote in message
> >> >> news:EFAD226E-A603-41C2-B3AC-...
> >> >> > 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.
> >> >> >
> >> >> > "Isaac Oben [MCITP:EA, MCSE]" wrote:
> >> >> >
> >> >> >>
> >> >> >> Hello Tony,
> >> >> >> To better understand your situation and environment, please give
> >> >> >> some
> >> >> >> detail
> >> >> >> specifics.
> >> >> >> Isaac
> >> >> >>
> >> >> >> "Tony" <> wrote in message
> >> >> >> news:05462462-4567-48AA-BD9A-...
> >> >> >> > 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,
The second just indicated that host6 is no longer in the root. you can
forced remove host7 [dfsutil.exe /remftroot /server:host7 /shareublic] and
the re add again [dfsutil.exe /addftroot /server:host7 /shareublic]

--
Isaac Oben [MCTIP:EA, MCSE]

"Tony" <> wrote in message
news:305F2366-4742-4065-AA07-...
> 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.
>
> "Isaac Oben [MCITP:EA, MCSE]" wrote:
>
>> 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 /shareublic
>> dfsutil.exe /clean /server:host6 /shareublic
>> 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
>>
>> "Tony" <> wrote in message
>> news:40A6A053-EFE4-4430-AB72-...
>> >I renamed the server from host6 to host7.
>> >
>> > "Isaac Oben [MCITP:EA, MCSE]" wrote:
>> >
>> >> 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)
>> >>
>> >>
>> >> "Tony" <> wrote in message
>> >> news:EFAD226E-A603-41C2-B3AC-...
>> >> > 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.
>> >> >
>> >> > "Isaac Oben [MCITP:EA, MCSE]" wrote:
>> >> >
>> >> >>
>> >> >> Hello Tony,
>> >> >> To better understand your situation and environment, please give
>> >> >> some
>> >> >> detail
>> >> >> specifics.
>> >> >> Isaac
>> >> >>
>> >> >> "Tony" <> wrote in message
>> >> >> news:05462462-4567-48AA-BD9A-...
>> >> >> > 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?
>> >> >>
>> >> >>
>> >> >>
>> >>
>> >>
>> >>
>>
>>
>>