Re: Running DCPROMO issues
Tech-Archive recommends: Speed Up your PC by fixing your registry
Pat,
Like Paul said: if this is the only domain in the forest and you want to
get rid of it (the domain and the forest) then you might want to simply
dcpromo /forceremoval and be done with it. However, let's try a couple of
things. But, before we get going we might need some more information. Here
are my questions:
1) is there a DNS Server in this domain? How many are there?
2) in the IP Configuration, to what DNS Server(s) do DC2 and DC3 point?
3) if you want to learn about how to do a metadata cleanup this might be a
good time. Using ntdsutil you might want to clean up any references to DC1.
This will help.
4) is the a Global Catalog Server in this Domain? If yes, which DC(s)?
5) which DCs hold which of the five FSMO roles? If DC1 holds any of them
you will have to use ntdsutil to seize it/them to another DC.
Basically, you would want to make sure that at least one of the remaining
DCs is also a DNS Server and a Global Catalog Server. You also want to make
sure that all five of the FSMO Roles are held by an existing DC. Once you
clean all this up you can run dcpromo on DC2 to remove it ( make sure that
before you do this you change the IP Configuration so that it is not
pointing to itself in DNS - in other words, that it points only to DC3).
When it comes time to dcpromo DC3 you would just make sure the check the
"This is the last Domain Controller in the Domain", or whatever the text is.
Have you created any Application Partitions?
Now, I realize that this might be overkill for you. If you really just want
to be done with it, try the /forceremoval switch that Paul mentioned. If
you want a little practice - and have the time - then play with it for the
experience.
--
Cary W. Shultz
Roanoke, VA 24012
"Pat" <Pat@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:8061077C-2990-4892-9ECB-A2E811D7C3EF@xxxxxxxxxxxxxxxx
>I have a development AD that was used awhile back but is no longer needed
>it
> consisted of 3 domain controllers
>
> DC1,DC2 and DC3 which was also used as a development server.
>
> DC1 DIED
> DC2 IS NO LONGER NEEDED
> DC3 I NEED STILL FOR DEVELOPMENT APPLICATION
>
> I tried to demote DC2 but it said it needed to talk to DC1 which is dead
> I powered down DC2 and tried to demote DC3 and it wanted to talk to DC1
> and
> DC2
>
> I basically don't care what happens to the Development Domain, my goal is
> that I want to keep only DC3 as a development server but no longer want it
> to
> be a DC in this domain, I want to get rid of the role of DC and want to
> add
> it to our Main corporate domain.
>
> Is there a way to drop this role and get around the issues I am
> encountering?
>
> Thanks
>
> Pat
>
>
.
Relevant Pages
- Re: Running DCPROMO issues
... I have 1 server left that is running no other dc's ... > 1) is there a DNS Server in this domain? ... > sure that all five of the FSMO Roles are held by an existing DC. ... > pointing to itself in DNS - in other words, that it points only to DC3). ... (microsoft.public.windows.server.active_directory) - Re: Running DCPROMO issues
... Not sure what you mean by 'Application Server'. ... >> dcpromo /forceremoval and be done with it. ... >> sure that all five of the FSMO Roles are held by an existing DC. ... >> pointing to itself in DNS - in other words, that it points only to DC3). ... (microsoft.public.windows.server.active_directory) - Re: Upgrading to SBS2003 - realistic to do ourselves?
... Hi Pat... ... the same LAN as your exisitng server though, server name and domain needs to ... Personally I would quote the other way round...clean install takes longer ... >I guess I don't know how geeky I am (I'm an engineer - does that count as ... (microsoft.public.backoffice.smallbiz2000) - Re: [git head] Should X86_PAT really default to yes?
... The artifacts also appear when I log out from KDE (i.e. without exiting the ... server), and I also get the messages when logging out and logging in again. ... The artifacts may not be a PAT issue directly, but it is a clear regression ... (Linux-Kernel) - Event ID 10016 DCOM and Event ID 4 Kerberos errors
... On Monday we had to install a new DC at a remote site. ... used the option to promote the remote DC by using the backup. ... The kerberos client received a KRB_AP_ERR_MODIFIED error from the server ... Is there any way that promoting DC3 from a backup has messed anything up? ... (microsoft.public.win2000.general) |
|