| Author |
Message |
Bryan L
Guest
|
 Posted:
Mon Jul 25, 2005 4:51 pm Post subject:
Oops - didn't remove DFS Links for server before retiring it |
|
|
I implemented a domain DFS as a means to migrate shares from one file server
to another, as preparation for rebuilding the original server from scratch.
I first migrated all my clients to use DFS paths when accessing the shares
on the original server. I then enabled one-way replication from the
original server to a "new" server to create a replica, but I continued to
provide DFS referrals only to the original server. During off-hours, I
verified that the replica on the new server was complete, and then enabled
referrals to the new server and disabled referrals to the old server. I
then took the old server offline permanently.
The new file server now hosting those shares has errors in the event log
because it's still trying to establish replication with the old server
that's no longer there. I see now that I should have removed all references
to the old server from my DFS configuration before taking the server
offline; instead I merely disabled referrals to the server. Then about a
week ago, I deleted the DFS links to the old server from my DFS
configuration. The errors on the new file server remain, and I want to
clean those up.
I've read this article
(http://www.microsoft.com/windows2000/techinfo/administration/fileandprint/dfsbp.asp)
but it's still not clear exactly what I should do to clean this up. It
gives in structions on what to do if the now-missing/nonexistent server was
a root target, but mine was not; it was simply the target of links.
A few more points of information:
- The old server was running 2000 Server and was a member server only.
- Before taking the 2000 Server box offline, there were no additional root
targets; the only DFS root resided on my only DC.
- The old server was reinstalled with a clean install of Server 2003 SP1,
with a different computer name but the same static IP.
- The reinstalled server now has a gigabit NIC in it and is using it
exclusively. It was installed just after the clean install of Server 2003.
The onboard 10/100 NIC has been disabled.
- The reinstalled server is now a DC and is hosting an additional root
target. - The file server that took over hosting of the shares is working
fine, but is still logging event 13508 for the old 2000 Server box.
How can I get the new file server to stop looking to replicate with the
nonexistent old server? I haven't found much in the way of clear,
straightforward guidance on using DFSutil.
Any help or comments appreciated.
Thanks in advance,
Bryan |
|
| Back to top |
|
 |
Paul Williams [MVP]
Guest
|
| Posted:
Wed Jul 27, 2005 12:51 pm Post subject:
Re: Oops - didn't remove DFS Links for server before retirin |
|
|
| Quote: | How can I get the new file server to stop looking to replicate with the
nonexistent old server?
|
There's some objects in Active Directory that you need to remove.
If you haven't already, install the Windows support tools.
-- Load ASDSIEdit.msc and expand the domain naming context container.
-- Expand the sub-containers until you reach your server.
-- Expand your server and there will be an NTFRS Subscriptions container
(class nTFRSSubscriptions). If there is only one child object
(nTFRSSubscriber) (other than SYSVOL) you can delete it the
nTFRSSubscriptions object. If you have several child objects, or this is a
DC and there's also therefore a SYSVOL replica set, you must only delete the
nTFRSSubscriber object that represents the root in question.
-- Next you need to drill down to the CN=System, CN=File Replication Service
container.
-- Delete the nTFRSMember object that represents this computer (you can
further clarify which member object is related to which computer by the
frsComputerReference attribute)
Start with that. There's probably some registry entries as well, but I'm
not in front of a server to get those. We'll come back to those once you've
done this.
Also, please bear with the above description. I'm doing this from memory
and haven't been able to verify that each object is in the exact place I've
said. You may have to expand one or two more containers. The types are
correct though.
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net |
|
| Back to top |
|
|
David Gibbons
Guest
|
| Posted:
Wed Jul 27, 2005 8:51 pm Post subject:
Re: Oops - didn't remove DFS Links for server before retirin |
|
|
How do you go about translating the GUID of the server to the "DNS Name" of
the server? In my DFS all I see are GUID numbers. No DNS names.
Thanks
David.
"Paul Williams [MVP]" <ptw2001@hotmail.com> wrote in message
news:ulY9UVpkFHA.1440@TK2MSFTNGP14.phx.gbl...
| Quote: | How can I get the new file server to stop looking to replicate with the
nonexistent old server?
There's some objects in Active Directory that you need to remove.
If you haven't already, install the Windows support tools.
-- Load ASDSIEdit.msc and expand the domain naming context container.
-- Expand the sub-containers until you reach your server.
-- Expand your server and there will be an NTFRS Subscriptions container
(class nTFRSSubscriptions). If there is only one child object
(nTFRSSubscriber) (other than SYSVOL) you can delete it the
nTFRSSubscriptions object. If you have several child objects, or this is
a
DC and there's also therefore a SYSVOL replica set, you must only delete
the
nTFRSSubscriber object that represents the root in question.
-- Next you need to drill down to the CN=System, CN=File Replication
Service
container.
-- Delete the nTFRSMember object that represents this computer (you can
further clarify which member object is related to which computer by the
frsComputerReference attribute)
Start with that. There's probably some registry entries as well, but I'm
not in front of a server to get those. We'll come back to those once
you've
done this.
Also, please bear with the above description. I'm doing this from memory
and haven't been able to verify that each object is in the exact place
I've
said. You may have to expand one or two more containers. The types are
correct though.
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net
|
|
|
| Back to top |
|
|
David Gibbons
Guest
|
| Posted:
Wed Jul 27, 2005 8:51 pm Post subject:
Re: Oops - didn't remove DFS Links for server before retirin |
|
|
Nevermind, I found it... Looks like I have to go to the server itself and
get the guid then go to the DFS and look.
"David Gibbons" <FreRange@nospam.postalias> wrote in message
news:e5HydgtkFHA.3260@TK2MSFTNGP10.phx.gbl...
| Quote: | How do you go about translating the GUID of the server to the "DNS Name"
of
the server? In my DFS all I see are GUID numbers. No DNS names.
Thanks
David.
"Paul Williams [MVP]" <ptw2001@hotmail.com> wrote in message
news:ulY9UVpkFHA.1440@TK2MSFTNGP14.phx.gbl...
How can I get the new file server to stop looking to replicate with
the
nonexistent old server?
There's some objects in Active Directory that you need to remove.
If you haven't already, install the Windows support tools.
-- Load ASDSIEdit.msc and expand the domain naming context container.
-- Expand the sub-containers until you reach your server.
-- Expand your server and there will be an NTFRS Subscriptions container
(class nTFRSSubscriptions). If there is only one child object
(nTFRSSubscriber) (other than SYSVOL) you can delete it the
nTFRSSubscriptions object. If you have several child objects, or this
is
a
DC and there's also therefore a SYSVOL replica set, you must only delete
the
nTFRSSubscriber object that represents the root in question.
-- Next you need to drill down to the CN=System, CN=File Replication
Service
container.
-- Delete the nTFRSMember object that represents this computer (you can
further clarify which member object is related to which computer by the
frsComputerReference attribute)
Start with that. There's probably some registry entries as well, but
I'm
not in front of a server to get those. We'll come back to those once
you've
done this.
Also, please bear with the above description. I'm doing this from
memory
and haven't been able to verify that each object is in the exact place
I've
said. You may have to expand one or two more containers. The types are
correct though.
--
Paul Williams
Microsoft MVP - Windows Server - Directory Services
http://www.msresource.net | http://forums.msresource.net
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in