Single domain controller failing

[John B. Dykes]

So we got bitten... or are in the process of it.

We are migrating from an enterprise-wide hodge podge of NT Domains to an AD
Forest (Root Domain at the top, one child domain for each geographical
location). The plan was to do the migration with single Windows 2000 domain
controllers and once the old NT domains were put to bed, we'd reuse those
machines as secondary domain controllers in each domain.

Unfortunately, one of our single domain controllers is beginning to die -
disk errors. We can't add users, or computers - people can't even change
their passwords.
We can't even add a new server to the domain to run a DC
Promo...

Any thoughts on getting a new DC before this one dies?

Thanks...

jbd
Denver.

 

[Mark Renoden [MSFT]]

Hi John

Got a backup? If not, can you take one? If not, you're running out of
options and it might be worth engaging a data recovery expert.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Paul McGuire]

You should beable to take a system state backup. then try doing a restore
to a offline server with the same name and IP. then after the restore
connect to the network and take down the failing server. Worth a TRY

HTH

Paul McGuire

Hi John

Got a backup? If not, can you take one? If not, you're running out of
options and it might be worth engaging a data recovery expert.

Kind regards
--
Mark Renoden [MSFT]
Windows Platform Support Team
Email: (e-mail address removed)

Please note you'll need to strip ".online" from my email address to email
me; I'll post a response back to the group.

This posting is provided "AS IS" with no warranties, and confers no rights.

So we got bitten... or are in the process of it.

We are migrating from an enterprise-wide hodge podge of NT Domains to an
AD
Forest (Root Domain at the top, one child domain for each geographical
location). The plan was to do the migration with single Windows 2000
domain
controllers and once the old NT domains were put to bed, we'd reuse those
machines as secondary domain controllers in each domain.

Unfortunately, one of our single domain controllers is beginning to die -
disk errors. We can't add users, or computers - people can't even change
their passwords.
We can't even add a new server to the domain to run a DC
Promo...

Any thoughts on getting a new DC before this one dies?

Thanks...

jbd
Denver.

 

[Enkidu]

So we got bitten... or are in the process of it.

We are migrating from an enterprise-wide hodge podge of NT Domains to an AD
Forest (Root Domain at the top, one child domain for each geographical
location). The plan was to do the migration with single Windows 2000 domain
controllers and once the old NT domains were put to bed, we'd reuse those
machines as secondary domain controllers in each domain.

Unfortunately, one of our single domain controllers is beginning to die -
disk errors. We can't add users, or computers - people can't even change
their passwords.
We can't even add a new server to the domain to run a DC
Promo...

Any thoughts on getting a new DC before this one dies?

Have you thought of hiring one? Sure you'd have problems getting it
out of AD afterwards, but it should get you over the hump.

Cheers,

Cliff

{MVP Directory Services}

 

[Enkidu]

Have you thought of hiring one? Sure you'd have problems getting it
out of AD afterwards, but it should get you over the hump.

Please ignore my post. I didn't read the OP carefully enough.

Cheers,

Cliff

{MVP Directory Services}