Remove an old BDC

I use to have two DC's but one eventually bit the dust. We decided not to
replace the down PC. What is the best way to remove the old DC from AD. I see
several errors in Event Viewer regarding replication among other things
regarding the old DC.
The DC in a Win2003.

Hello DaveH,

If the DC never comes back follow this way, also make sure the existing one
is also DNS server for the domain machines:
http://support.microsoft.com/kb/555846/en-us

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I use to have two DC's but one eventually bit the dust. We decided not
> to
> replace the down PC. What is the best way to remove the old DC from
> AD. I see
> several errors in Event Viewer regarding replication among other
> things
> regarding the old DC.
> The DC in a Win2003

Howdie!

On 30.03.2010 14:55, DaveH wrote:
> I use to have two DC's but one eventually bit the dust. We decided not to
> replace the down PC. What is the best way to remove the old DC from AD. I see
> several errors in Event Viewer regarding replication among other things
> regarding the old DC.
> The DC in a Win2003.
>

Plan on creating a new DC. Really. What if the other DC bites the dust,
too. How's your domain going to work after that? Recovering on different
hardware isn't as easy. A 1DC-Domain is a no-go. You'll need to DCs.

Other than that, you'll have to create a metadata cleanup Meinolf
already sent you a link about. Note that you might remove references in
AD Sites and Services and in DNS (old static records) manually.

Cheers,
Florian

Do you know of any issues if I was to replace the old server (upgrade it) to
Win08?
What actually happened was the old server was a SBS server and we purchased
a new Win03 server. Shortly after we got the Win03 server online the SBS
server started, well let’s just say Microsoft never intended a SBS server to
have another DC sitting on the same network. So it’s been dormant this whole
time.
I do understand the importance of having another DC available.

My options would be to:
Upgrade the old SBS server to Win08
Upgrade Win03 server to Win08 and move the 03 License to SBS server.

I’d like to get your thoughts on this.

Dave






"Florian Frommherz [MVP]" wrote:

> Howdie!
>
> On 30.03.2010 14:55, DaveH wrote:
> > I use to have two DC's but one eventually bit the dust. We decided not to
> > replace the down PC. What is the best way to remove the old DC from AD. I see
> > several errors in Event Viewer regarding replication among other things
> > regarding the old DC.
> > The DC in a Win2003.
> >
>
> Plan on creating a new DC. Really. What if the other DC bites the dust,
> too. How's your domain going to work after that? Recovering on different
> hardware isn't as easy. A 1DC-Domain is a no-go. You'll need to DCs.
>
> Other than that, you'll have to create a metadata cleanup Meinolf
> already sent you a link about. Note that you might remove references in
> AD Sites and Services and in DNS (old static records) manually.
>
> Cheers,
> Florian
> .
>

"DaveH" <> wrote

> ...let's just say Microsoft never intended a SBS server to
> have another DC sitting on the same network.


Huh? This is simply not true.

What version of SBS?

Did you run dcdiag against the old domain prior to making any
changes?

Did you remember to use ADPrep to update the schema to 2003 on the
SBS DC before tossing the new DC into the mix?

Did you attempt to improperly have the new DC seize the FMSO roles
from the SBS DC?

If you shut the new server down, what does the old DC do?

Regards,

Len Agoado

"DaveH" <> wrote

> ...let's just say Microsoft never intended a SBS server to
> have another DC sitting on the same network.


Huh? This is simply not true.

What version of SBS?

Did you run dcdiag against the old domain prior to making any
changes?

Did you remember to use ADPrep to update the schema to 2003 on the
SBS DC before tossing the new DC into the mix?

Did you attempt to improperly have the new DC seize the FSMO roles
from the SBS DC?

If you shut the new server down, what does the old DC do?

Regards,

Len Agoado

DaveH wrote:
> Do you know of any issues if I was to replace the old server (upgrade
> it) to Win08?
> What actually happened was the old server was a SBS server and we
> purchased a new Win03 server. Shortly after we got the Win03 server
> online the SBS server started, well let's just say Microsoft never
> intended a SBS server to have another DC sitting on the same network.
> So it's been dormant this whole time.
> I do understand the importance of having another DC available.
>
> My options would be to:
> Upgrade the old SBS server to Win08
No. SBS won't "in place upgrade" to Server 2008

> Upgrade Win03 server to Win08 and move the 03 License to SBS server.
No, SBS licenses are SBS no Server Licenses. Neither the Server license or
the Client (CALs) licenses transfer.

>
> I'd like to get your thoughts on this.

You may bring up a second server (of any version 2003 or later) promote to
being a Domain Controller (after upgrading the schema), allow your Active
Directory data to transfer, and then decommishin the SBS server. You can
then go forth with a standard Windows Server Active Directory enviroment.

However, SBS includes Exchange. If you are using it then you'd need to
factor in migrating the SBS Exchange enviroment to a Standard Exchange
enviroment. Sharepoint, ISA, and user data likewise needs consideration.
But none of your licenses are re-usable. There used to be a product called
Transistion Pack, but that has been discontinued.



>
> Dave
>
>
>
>
>
>
> "Florian Frommherz [MVP]" wrote:
>
>> Howdie!
>>
>> On 30.03.2010 14:55, DaveH wrote:
>>> I use to have two DC's but one eventually bit the dust. We decided
>>> not to replace the down PC. What is the best way to remove the old
>>> DC from AD. I see several errors in Event Viewer regarding
>>> replication among other things regarding the old DC.
>>> The DC in a Win2003.
>>>
>>
>> Plan on creating a new DC. Really. What if the other DC bites the
>> dust, too. How's your domain going to work after that? Recovering on
>> different hardware isn't as easy. A 1DC-Domain is a no-go. You'll
>> need to DCs.
>>
>> Other than that, you'll have to create a metadata cleanup Meinolf
>> already sent you a link about. Note that you might remove references
>> in AD Sites and Services and in DNS (old static records) manually.
>>
>> Cheers,
>> Florian
>> .

--
/kj

Hello DaveH,

Except SBS versions support an inplace upgrade to Windows server 2008.

There is no problem with additional DC/DNS/GC added to a SBS domain, only
the FSMO roles MUST be on the SBS machine.

You cannot upgrade SBS 2003 to Windows server 2008.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Do you know of any issues if I was to replace the old server (upgrade
> it) to
> Win08?
> What actually happened was the old server was a SBS server and we
> purchased
> a new Win03 server. Shortly after we got the Win03 server online the
> SBS
> server started, well let's just say Microsoft never intended a SBS
> server to
> have another DC sitting on the same network. So it's been dormant this
> whole
> time.
> I do understand the importance of having another DC available.
> My options would be to:
> Upgrade the old SBS server to Win08
> Upgrade Win03 server to Win08 and move the 03 License to SBS server.
> I'd like to get your thoughts on this.
>
> Dave
>
> "Florian Frommherz [MVP]" wrote:
>
>> Howdie!
>>
>> On 30.03.2010 14:55, DaveH wrote:
>>
>>> I use to have two DC's but one eventually bit the dust. We decided
>>> not to
>>> replace the down PC. What is the best way to remove the old DC from
>>> AD. I see
>>> several errors in Event Viewer regarding replication among other
>>> things
>>> regarding the old DC.
>>> The DC in a Win2003.
>> Plan on creating a new DC. Really. What if the other DC bites the
>> dust, too. How's your domain going to work after that? Recovering on
>> different hardware isn't as easy. A 1DC-Domain is a no-go. You'll
>> need to DCs.
>>
>> Other than that, you'll have to create a metadata cleanup Meinolf
>> already sent you a link about. Note that you might remove references
>> in AD Sites and Services and in DNS (old static records) manually.
>>
>> Cheers,
>> Florian
>>

Add another voice to seriously reconsider replacing the crashed DC. If
the last remaining one goes, you are up the proverbial creek without a
paddle and a leaking boat.

Follow Meinolf's advice on removing the DC from the domain.


Regards,
Hank Arnold
Microsoft MVP
Windows Server - Directory Services
http://it.toolbox.com/blogs/personal-pc-assistant/

On 3/30/2010 8:55 AM, DaveH wrote:
> I use to have two DC's but one eventually bit the dust. We decided not to
> replace the down PC. What is the best way to remove the old DC from AD. I see
> several errors in Event Viewer regarding replication among other things
> regarding the old DC.
> The DC in a Win2003.
>