dcpromo /forceremoval

Good afternoon!

I think that I know this, but I want to check....

If I use dcpromo /forceremoval to remove a dying DC and then clean things up
(via the metadata cleanup and ntdsutil) and things have run nicely and
cleanly for two months or more can I introduce - temporarily - a workstation
or server that has the same computer name (actually, same FQDN) of the
machine on which I performed a dcpromo /forceremoval?

Here is why I ask:

Had an older DC that continued to fail (hardware). Finally, client
purchased replacement. Could not run dcpromo on failing server so used
dcpromo /forceremoval. After that, cleaned up everything with our friend,
ntdsutil. Environment is running nicely and cleaning since then.

Let's say that the servername was DAFFY. In addition to being a DC/GC it
was also the main file server (where the users "My Documents" were
redirected, among other things).

One of the lingering affects (no...not that...oh, lingering affects...not
lingering objects) was that the usesrs of MS Access now have a multitude of
choices when they synchronize - they click on the little drop down and
choose the replica (do not worry what I mean here...not really the point).
Client wants this cleaned up as half the entries point to
\\DAFFY\blah\blah\blah\file.mdb and the like. Essentially we need to remove
all replicas that reference DAFFY.

According to some MS Access MVPs the only way to do that is to recreate the
old directory structure and to then remove the replicas via normal methods
(whatever that means...not an MS Access person).

Thanks,

Cary

Don
Wed Mar 26 12:58:11 PDT 2008

It sounds like you are looking for a temporary solution. If that is the
case, create a host record in dns to point DAFFY (is that really a server
name!!) to the IP address if the new location. Then
\\DAFFY\blah\blah\blah\file.mdb will become
\\NewServerName\blah\blah\blah\file.mdb and your access guys can do what
they need to do. You can then leave the entry or delete it as you like.
Deleting it would be cleaner if your sure its no longer needed.

--
Hope it helps!

dw

----------------------------------------------
Don Wilwol
www.atthedatacenter.com



"Cary W. Shultz" <cshultz@n0spam.outsourceitcorp.com> wrote in message
news:ePN2Hr3jIHA.3400@TK2MSFTNGP03.phx.gbl...
> Good afternoon!
>
> I think that I know this, but I want to check....
>
> If I use dcpromo /forceremoval to remove a dying DC and then clean things
> up (via the metadata cleanup and ntdsutil) and things have run nicely and
> cleanly for two months or more can I introduce - temporarily - a
> workstation or server that has the same computer name (actually, same
> FQDN) of the machine on which I performed a dcpromo /forceremoval?
>
> Here is why I ask:
>
> Had an older DC that continued to fail (hardware). Finally, client
> purchased replacement. Could not run dcpromo on failing server so used
> dcpromo /forceremoval. After that, cleaned up everything with our friend,
> ntdsutil. Environment is running nicely and cleaning since then.
>
> Let's say that the servername was DAFFY. In addition to being a DC/GC it
> was also the main file server (where the users "My Documents" were
> redirected, among other things).
>
> One of the lingering affects (no...not that...oh, lingering affects...not
> lingering objects) was that the usesrs of MS Access now have a multitude
> of choices when they synchronize - they click on the little drop down and
> choose the replica (do not worry what I mean here...not really the point).
> Client wants this cleaned up as half the entries point to
> \\DAFFY\blah\blah\blah\file.mdb and the like. Essentially we need to
> remove all replicas that reference DAFFY.
>
> According to some MS Access MVPs the only way to do that is to recreate
> the old directory structure and to then remove the replicas via normal
> methods (whatever that means...not an MS Access person).
>
> Thanks,
>
> Cary
>

MikeMcClymont
Thu Mar 27 06:21:02 PDT 2008

It would seem that if AD is not reporting any problems with not being able to
find DAFFY, and you need to bring up a server with the name DAFFY for a short
period of time, there should be no issues.
--
Mike McClymont


"Cary W. Shultz" wrote:

> Good afternoon!
>
> I think that I know this, but I want to check....
>
> If I use dcpromo /forceremoval to remove a dying DC and then clean things up
> (via the metadata cleanup and ntdsutil) and things have run nicely and
> cleanly for two months or more can I introduce - temporarily - a workstation
> or server that has the same computer name (actually, same FQDN) of the
> machine on which I performed a dcpromo /forceremoval?
>
> Here is why I ask:
>
> Had an older DC that continued to fail (hardware). Finally, client
> purchased replacement. Could not run dcpromo on failing server so used
> dcpromo /forceremoval. After that, cleaned up everything with our friend,
> ntdsutil. Environment is running nicely and cleaning since then.
>
> Let's say that the servername was DAFFY. In addition to being a DC/GC it
> was also the main file server (where the users "My Documents" were
> redirected, among other things).
>
> One of the lingering affects (no...not that...oh, lingering affects...not
> lingering objects) was that the usesrs of MS Access now have a multitude of
> choices when they synchronize - they click on the little drop down and
> choose the replica (do not worry what I mean here...not really the point).
> Client wants this cleaned up as half the entries point to
> \\DAFFY\blah\blah\blah\file.mdb and the like. Essentially we need to remove
> all replicas that reference DAFFY.
>
> According to some MS Access MVPs the only way to do that is to recreate the
> old directory structure and to then remove the replicas via normal methods
> (whatever that means...not an MS Access person).
>
> Thanks,
>
> Cary
>
>
>