Hi dfseattle,
Pulling it out isn't a big deal, but you'll want to make sure that
everything is off of it. You should also make sure you ahve at least two DCs
in your domain at all times for fault tolerance.
1. Make sure everything is of -- that you have DHCP and DNS elsewhere, that
there are other GCs in the environment.
2. Once you think everything is golden, power it off for a few days just to
be sure. This will give you a good backout path. Do not forget about it.
If it tombstones (60 or 120 days depending on the version of windows) you'll
have a messier problem.
3. Power it back on and make sure it replicates. Use REPLMON from the
support tools to force this and pull a replication report to be sure.
4. Run DCPROMO on the server making sure that you DON'T choose the "last DC
in the domain" option.
5. The server will now be a member server. Now, just pull it out of the
domain by joining it to a work group.
6. Power the server down and validate that the DNS and the windows AD is
clean.
Have fun!
--
Ryan Hanisco
MCSE, MCTS: SQL 2005, Project+
Chicago, IL
Remember: Marking helpful answers helps everyone find the info they need
quickly.
"dsfseattle" wrote:
> Ryan,
>
> Thanks so much. I thought that was the case, but searches on the internet
> keep pointing me to information on pdc and bdc.
>
> Ok, performed steps in the document you attached and it worked just fine.
> I've also moved over other functions you mentioned (e.g. DNS, DHCP, etc.).
> What else would be required to retire this server from the domain?
>
> Thanks, Dave
>
> "Ryan Hanisco" wrote:
>
> > dsfseattle,
> >
> > There isn't a real PDC anymore... this really went with NT 4.0. With
> > 2000/2003all DCs are equal.. its just that some are more equal than others.
> > The FSMO roles are the differentiating factor. Moving the FSMO roles moves
> > the essential services. Other than that, more common services liek DNS and
> > DHCP are moves at they always are...
> >
> > See: http://support.microsoft.com/default.aspx/kb/324801
> > --
> > Ryan Hanisco
> > MCSE, MCTS: SQL 2005, Project+
> > Chicago, IL
> >
> > Remember: Marking helpful answers helps everyone find the info they need
> > quickly.
> >
> >
> > "dsfseattle" wrote:
> >
> > > Originally I started with a Windows 2003 SBS 2003 server. Using the
> > > transition pack I moved to a fully functional Windows 2003 Server
> > > environment.
> > >
> > > I added a new Windows 2003 Server and set it up as a backup domain
> > > controller.
> > >
> > > Now I want to retire the original server. When I look in active directory I
> > > can see that both computers are listed as a domain controller.
> > >
> > > I try and follow instructions I have found to promote the new server to the
> > > primary domain controller, but I cannot follow the directions specified.
> > >
> > > Also, Server Manager is not found on the new server when I go to all
> > > programs, administrative tools. What is happening here?