Seizure of domain controller roles after old DC has died Troubles....

[Guest markm75]

I'm attempting to use ntsutil and the seize ROLE command..

 

Our old DC,which held all 5 roles.. has died and will not be revived..

 

I was guessing that i just use the ntdsutil utility to seize them..

 

but when i try this.. i get an error stating the orginal owner couldnt

be contacted..

 

How else can I get these roles transfered to this new server if i cant

revive the old one?

 

Thanks in advance

[Guest Lanwench [MVP - Exchange]]

Re: Seizure of domain controller roles after old DC has died Troubles....

 

markm75 <markm75c@msn.com> wrote:

> I'm attempting to use ntsutil and the seize ROLE command..

>

> Our old DC,which held all 5 roles.. has died and will not be revived..

>

> I was guessing that i just use the ntdsutil utility to seize them..

>

> but when i try this.. i get an error stating the orginal owner couldnt

> be contacted..

>

> How else can I get these roles transfered to this new server if i cant

> revive the old one?

>

> Thanks in advance

 

See http://support.microsoft.com/kb/255504 and review your steps.... and if

you still get errors, post the exact text.

[Guest markm75]

Re: Seizure of domain controller roles after old DC has diedTroubles....

 

Re: Seizure of domain controller roles after old DC has diedTroubles....

 

On Dec 1, 2:00 pm, "Lanwench [MVP - Exchange]"

<lanwe...@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote:

> Seehttp://support.microsoft.com/kb/255504and review your steps.... and if

> you still get errors, post the exact text.

 

 

That was the page i was using to do this.. here is what happens:

(PSTDC is the dead server, VSDC01 is the new one)

 

 

fsmo maintenance: seize PDC

Attempting safe transfer of PDC FSMO before seizure.

ldap_modify_sW error 0x34(52 (Unavailable).

Ldap extended error message is 000020AF: SvcErr: DSID-03210511,

problem 5002 (UN

AVAILABLE), data 1722

 

Win32 error returned is 0x20af(The requested FSMO operation failed.

The current

FSMO holder could not be contacted.)

)

Depending on the error code this may indicate a connection,

ldap, or role transfer error.

Transfer of PDC FSMO failed, proceeding with seizure ...

Server "vsdc01" knows about 5 roles

Schema - CN=NTDS Settings,CN=PSTDC,CN=Servers,CN=Default-First-Site-

Name,CN=Site

s,CN=Configuration,DC=pst,DC=local

Domain - CN=NTDS Settings,CN=PSTDC,CN=Servers,CN=Default-First-Site-

Name,CN=Site

s,CN=Configuration,DC=pst,DC=local

PDC - CN=NTDS Settings,CN=VSDC01,CN=Servers,CN=Default-First-Site-

Name,CN=Sites,

CN=Configuration,DC=pst,DC=local

RID - CN=NTDS Settings,CN=PSTDC,CN=Servers,CN=Default-First-Site-

Name,CN=Sites,C

N=Configuration,DC=pst,DC=local

Infrastructure - CN=NTDS Settings,CN=PSTDC,CN=Servers,CN=Default-First-

Site-Name

,CN=Sites,CN=Configuration,DC=pst,DC=local

 

Thanks

[Guest markm75]

Re: Seizure of domain controller roles after old DC has diedTroubles....

 

Re: Seizure of domain controller roles after old DC has diedTroubles....

 

On Dec 2, 8:23 am, markm75 <markm...@msn.com> wrote:

> On Dec 1, 2:00 pm, "Lanwench [MVP - Exchange]"

>

> <lanwe...@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote:

> > Seehttp://support.microsoft.com/kb/255504andreview your steps.... and if

> > you still get errors, post the exact text.

>

> That was the page i was using to do this.. here is what happens:

> (PSTDC is the dead server, VSDC01 is the new one)

>

> fsmo maintenance: seize PDC

> Attempting safe transfer of PDC FSMO before seizure.

> ldap_modify_sW error 0x34(52 (Unavailable).

> Ldap extended error message is 000020AF: SvcErr: DSID-03210511,

> problem 5002 (UN

> AVAILABLE), data 1722

>

> Win32 error returned is 0x20af(The requested FSMO operation failed.

> The current

> FSMO holder could not be contacted.)

> )

> Depending on the error code this may indicate a connection,

> ldap, or role transfer error.

> Transfer of PDC FSMO failed, proceeding with seizure ...

> Server "vsdc01" knows about 5 roles

> Schema - CN=NTDS Settings,CN=PSTDC,CN=Servers,CN=Default-First-Site-

> Name,CN=Site

> s,CN=Configuration,DC=pst,DC=local

> Domain - CN=NTDS Settings,CN=PSTDC,CN=Servers,CN=Default-First-Site-

> Name,CN=Site

> s,CN=Configuration,DC=pst,DC=local

> PDC - CN=NTDS Settings,CN=VSDC01,CN=Servers,CN=Default-First-Site-

> Name,CN=Sites,

> CN=Configuration,DC=pst,DC=local

> RID - CN=NTDS Settings,CN=PSTDC,CN=Servers,CN=Default-First-Site-

> Name,CN=Sites,C

> N=Configuration,DC=pst,DC=local

> Infrastructure - CN=NTDS Settings,CN=PSTDC,CN=Servers,CN=Default-First-

> Site-Name

> ,CN=Sites,CN=Configuration,DC=pst,DC=local

>

> Thanks

 

I should mention that this VSdc01 server was just created (before

trying to seize the roles).. i did a dcpromo on it.. perhaps i need to

do this seizure on my other remaining DC (all of the 5 roles were held

on the dead PSTDC server that i'm trying to seize)..

[Guest Lanwench [MVP - Exchange]]

Re: Seizure of domain controller roles after old DC has died Troubles....

 

markm75 <markm75c@msn.com> wrote:

> On Dec 2, 8:23 am, markm75 <markm...@msn.com> wrote:

>> On Dec 1, 2:00 pm, "Lanwench [MVP - Exchange]"

>>

>> <lanwe...@heybuddy.donotsendme.unsolicitedmailatyahoo.com> wrote:

>>> Seehttp://support.microsoft.com/kb/255504andreview your steps....

>>> and if you still get errors, post the exact text.

>>

>> That was the page i was using to do this.. here is what happens:

>> (PSTDC is the dead server, VSDC01 is the new one)

>>

>> fsmo maintenance: seize PDC

>> Attempting safe transfer of PDC FSMO before seizure.

 

This is normal.....

>> ldap_modify_sW error 0x34(52 (Unavailable).

>> Ldap extended error message is 000020AF: SvcErr: DSID-03210511,

>> problem 5002 (UN

>> AVAILABLE), data 1722

>>

>> Win32 error returned is 0x20af(The requested FSMO operation failed.

>> The current

>> FSMO holder could not be contacted.)

 

Hmmm - I don't remember what the messages usually look like, but I do know

you'll see something indicating failure when it can't find the old server -

it's trying to transfer before it continues with the seize request.

>> )

>> Depending on the error code this may indicate a connection,

>> ldap, or role transfer error.

>> Transfer of PDC FSMO failed, proceeding with seizure ...

 

See...

>

>> Server "vsdc01" knows about 5 roles

>> Schema - CN=NTDS Settings,CN=PSTDC,CN=Servers,CN=Default-First-Site-

>> Name,CN=Site

>> s,CN=Configuration,DC=pst,DC=local

>> Domain - CN=NTDS Settings,CN=PSTDC,CN=Servers,CN=Default-First-Site-

>> Name,CN=Site

>> s,CN=Configuration,DC=pst,DC=local

>> PDC - CN=NTDS Settings,CN=VSDC01,CN=Servers,CN=Default-First-Site-

>> Name,CN=Sites,

>> CN=Configuration,DC=pst,DC=local

>> RID - CN=NTDS Settings,CN=PSTDC,CN=Servers,CN=Default-First-Site-

>> Name,CN=Sites,C

>> N=Configuration,DC=pst,DC=local

>> Infrastructure - CN=NTDS

>> Settings,CN=PSTDC,CN=Servers,CN=Default-First- Site-Name

>> ,CN=Sites,CN=Configuration,DC=pst,DC=local

>>

>> Thanks

>

> I should mention that this VSdc01 server was just created (before

> trying to seize the roles).. i did a dcpromo on it.. perhaps i need to

> do this seizure on my other remaining DC (all of the 5 roles were held

> on the dead PSTDC server that i'm trying to seize)..

 

Well - you could, but are you 100% sure this hasn't worked??

 

You might try posting in microsoft.public.windows.server.active_directory

.....I'm not a guru by any stretch of the imagination.