Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » NTDS Repliction event 1863
NTDS Repliction event 1863 [message #377214] Tue, 26 January 2010 02:22 Go to next message
Jason Huang  is currently offline Jason Huang  Taiwan
Messages: 60
Registered: September 2009
Member
Hi,

Due to the NTDS Replication event 1863, I went trough all my 3DCs to find:

HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Repli cator latency
error interval

However, I can't find that registry in any of my DCs to change the tombstone
lifetime.
How do I fix this problem?
Thanks for help.


Jason
Re: NTDS Repliction event 1863 [message #377269 is a reply to message #377214] Tue, 26 January 2010 04:23 Go to previous messageGo to next message
meiweb  is currently offline meiweb  Germany
Messages: 2225
Registered: September 2009
Senior Member
Hello Jason,

Does this also belong to your previous posting "New DC problem with event
log NTDS Replication error 1864"? By default this key dones't exist. What
exactly are you trying to achive? Wich Microsoft article are you using?

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


> Hi,
>
> Due to the NTDS Replication event 1863, I went trough all my 3DCs to
> find:
>
> HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Repli cator
> latency error interval
>
> However, I can't find that registry in any of my DCs to change the
> tombstone
> lifetime.
> How do I fix this problem?
> Thanks for help.
> Jason
>
Re: NTDS Repliction event 1863 [message #377346 is a reply to message #377214] Tue, 26 January 2010 06:26 Go to previous messageGo to next message
pbbergs  is currently offline pbbergs  United States
Messages: 1024
Registered: July 2009
Senior Member
The tombstone lifetime isn't stored in the registry, but in the ntds.dit
file (Which is Active Directory). Once you have objects that have become
tombstoned, you can't change the lifetime to reanimate these, however you
can modify it for future tombstone control though.

See the link below on how to extend the lifetime:
http://www.petri.co.il/changing_the_tombstone_lifetime_windo ws_ad.htm

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Jason Huang" <JasonHuang8888@hotmail.com> wrote in message
news:OT28OkmnKHA.1544@TK2MSFTNGP02.phx.gbl...
> Hi,
>
> Due to the NTDS Replication event 1863, I went trough all my 3DCs to find:
>
> HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Repli cator latency
> error interval
>
> However, I can't find that registry in any of my DCs to change the
> tombstone lifetime.
> How do I fix this problem?
> Thanks for help.
>
>
> Jason
>
>
>
>
Re: NTDS Repliction event 1863 [message #378037 is a reply to message #377269] Tue, 26 January 2010 21:02 Go to previous messageGo to next message
Jason Huang  is currently offline Jason Huang  Taiwan
Messages: 60
Registered: September 2009
Member
Yes.
2 zone dc ( root dc MIS and 1 newly promoted dc Sun) and one childzone dc
V00s( promoted 5 years ago).
Is it possible not to demote the V00s and still let the synchronizations
working normal?
If the newly promoted dc is working correctly, will it have the DNS service
and all the records from the root dc?
Thanks for help.


Jason


"Meinolf Weber [MVP-DS]" <meiweb@(nospam)gmx.de>
???????:6cb2911dcd188cc6c99746e6ef7@msnews.microsoft.com...
> Hello Jason,
>
> Does this also belong to your previous posting "New DC problem with event
> log NTDS Replication error 1864"? By default this key dones't exist. What
> exactly are you trying to achive? Wich Microsoft article are you using?
>
> 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
>
>> Hi,
>>
>> Due to the NTDS Replication event 1863, I went trough all my 3DCs to
>> find:
>>
>> HKLM\System\CurrentControlSet\Services\NTDS\Parameters\Repli cator
>> latency error interval
>>
>> However, I can't find that registry in any of my DCs to change the
>> tombstone
>> lifetime.
>> How do I fix this problem?
>> Thanks for help.
>> Jason
>>
>
>
Re: NTDS Repliction event 1863 [message #378074 is a reply to message #378037] Tue, 26 January 2010 22:10 Go to previous messageGo to next message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Jason Huang" <JasonHuang8888@hotmail.com> wrote in message
news:%23hcUHWwnKHA.5524@TK2MSFTNGP05.phx.gbl...
> Yes.
> 2 zone dc ( root dc MIS and 1 newly promoted dc Sun) and one childzone dc
> V00s( promoted 5 years ago).
> Is it possible not to demote the V00s and still let the synchronizations
> working normal?
> If the newly promoted dc is working correctly, will it have the DNS
> service and all the records from the root dc?
> Thanks for help.
>
>
> Jason

if V00s is having problems and is already past the tombstone, there is
really no way to save it.

If the new DC is in a child domain, and the forest root DC DNS zone's scope
is set to Forest-wide, then yes, it should populate automatically. However,
in this scenario, if the forest root domain DC's zone's scope is set to
domain-wide only, none of the child DCs DNS servers will see the zone.

Ace
Re: NTDS Repliction event 1863 [message #378095 is a reply to message #378074] Tue, 26 January 2010 23:25 Go to previous messageGo to next message
Jason Huang  is currently offline Jason Huang  Taiwan
Messages: 60
Registered: September 2009
Member
Thanks.
The V00s is the DC for the child zone V00Domain, and it's working as the
file server for a particular department.
If demote the V00s, I'm afraid that all file sharings for client's will be
disconnected.


>> Yes.
>> 2 zone dc ( root dc MIS and 1 newly promoted dc Sun) and one childzone dc
>> V00s( promoted 5 years ago).
>> Is it possible not to demote the V00s and still let the synchronizations
>> working normal?
>> If the newly promoted dc is working correctly, will it have the DNS
>> service and all the records from the root dc?
>> Thanks for help.
>>
>>
>> Jason
>
> if V00s is having problems and is already past the tombstone, there is
> really no way to save it.
>
> If the new DC is in a child domain, and the forest root DC DNS zone's
> scope is set to Forest-wide, then yes, it should populate automatically.
> However, in this scenario, if the forest root domain DC's zone's scope is
> set to domain-wide only, none of the child DCs DNS servers will see the
> zone.
>
> Ace
>
>
>
Re: NTDS Repliction event 1863 [message #378204 is a reply to message #378095] Wed, 27 January 2010 06:15 Go to previous messageGo to next message
pbbergs  is currently offline pbbergs  United States
Messages: 1024
Registered: July 2009
Senior Member
If it is the only dc in the domain you will lose all security and it would
have to be rebuilt. If there is more than one dc in the domain then you can
demote and promote and not lose the security defined.

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4
Microsoft's Thrive IT Pro of the Month - June 2009

http://www.pbbergs.com

Please no e-mails, any questions should be posted in the NewsGroup This
posting is provided "AS IS" with no warranties, and confers no rights.

"Jason Huang" <JasonHuang8888@hotmail.com> wrote in message
news:%232sV%23lxnKHA.1548@TK2MSFTNGP06.phx.gbl...
> Thanks.
> The V00s is the DC for the child zone V00Domain, and it's working as the
> file server for a particular department.
> If demote the V00s, I'm afraid that all file sharings for client's will be
> disconnected.
>
>
>>> Yes.
>>> 2 zone dc ( root dc MIS and 1 newly promoted dc Sun) and one childzone
>>> dc V00s( promoted 5 years ago).
>>> Is it possible not to demote the V00s and still let the synchronizations
>>> working normal?
>>> If the newly promoted dc is working correctly, will it have the DNS
>>> service and all the records from the root dc?
>>> Thanks for help.
>>>
>>>
>>> Jason
>>
>> if V00s is having problems and is already past the tombstone, there is
>> really no way to save it.
>>
>> If the new DC is in a child domain, and the forest root DC DNS zone's
>> scope is set to Forest-wide, then yes, it should populate automatically.
>> However, in this scenario, if the forest root domain DC's zone's scope is
>> set to domain-wide only, none of the child DCs DNS servers will see the
>> zone.
>>
>> Ace
>>
>>
>>
>
>
Re: NTDS Repliction event 1863 [message #378273 is a reply to message #378204] Wed, 27 January 2010 08:26 Go to previous message
aceman  is currently offline aceman  United States
Messages: 5816
Registered: July 2009
Senior Member
"Paul Bergson [MVP-DS]" <pbbergs@no_spammsn.com> wrote in message
news:OgA%23DL1nKHA.5508@TK2MSFTNGP02.phx.gbl...
> If it is the only dc in the domain you will lose all security and it would
> have to be rebuilt. If there is more than one dc in the domain then you
> can demote and promote and not lose the security defined.
>

I'm thinking the same thing. I believe I replied to one of Jason's other
threads indicating that he NEEDS an additional DC in that child domain for
more than one reason, besides fault tolerance for the domain, to also move
the IM role off of the GC to the other DC.

I think with all of the problems Jason is having, it may be easier at this
juncture for him to contact Microsoft PSS for a small fee to let them fix it
and sort it out for him so he get his infrastructure up and running properly
again.They will take as much time as needed for the small fee, whether a
couple of hours or a few days, no longer how long it takes.

Ace
Previous Topic:changing user group membership, IAS policies
Next Topic:AD name public vs private battle
Goto Forum:
  


Current Time: Wed Jan 17 04:14:05 MST 2018

Total time taken to generate the page: 0.03338 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software