I get the event id 1083 logged fairly frequently in the system event
logs on a number of my domain controllers, and I believe it is due to
the fact that several groups have gotten out of control with many many
members added to them.

I found these registry entries below which I have been contemplating
adding to my DC's to max out the values for the number of objects and
packet sizes, and to increase the RPC timeout, and to decrease the
replication notification between servers when someone is adding
members to the groups a few at a time. Can anyone make any further
suggestions or comment on the potential impact this might have? I have
tested the values in a lab, and replication works fine, but I don't
have large groups there so I am not sure of the overall impact.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters]
"RPC Replication Timeout"=dword:0000000f
"Replicator Intra Site Packet Size (objects)"=dword:000003e8
"Replicator Intra Site Packet Size (bytes)"=dword:00a00000
"Replicator Inter Site Packet Size (objects)"=dword:000003e8
"Replicator Inter Site Packet Size (bytes)"=dword:00a00000
"Replicator Notify Pause Between DSAs (secs)"=dword:0000001e

TIA!!!

Hi,
I don't think you should change the replication packet sizes without a
precise indication to do so.
Your event id 1083 issue, I think, is unrelated to "packet size problems"
This may help cone down on what the issue is:
http://support.microsoft.com/kb/306091

Regards,

Austin
<cpmf2112@yahoo.com> wrote in message
news:1193348079.075011.320620@50g2000hsm.googlegroups.com...

Quote:

I get the event id 1083 logged fairly frequently in the system event logs on a number of my domain controllers, and I believe it is due to the fact that several groups have gotten out of control with many many members added to them. I found these registry entries below which I have been contemplating adding to my DC's to max out the values for the number of objects and packet sizes, and to increase the RPC timeout, and to decrease the replication notification between servers when someone is adding members to the groups a few at a time. Can anyone make any further suggestions or comment on the potential impact this might have? I have tested the values in a lab, and replication works fine, but I don't have large groups there so I am not sure of the overall impact. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters] "RPC Replication Timeout"=dword:0000000f "Replicator Intra Site Packet Size (objects)"=dword:000003e8 "Replicator Intra Site Packet Size (bytes)"=dword:00a00000 "Replicator Inter Site Packet Size (objects)"=dword:000003e8 "Replicator Inter Site Packet Size (bytes)"=dword:00a00000 "Replicator Notify Pause Between DSAs (secs)"=dword:0000001e TIA!!!

Hi Austin,

Thanks for your reply. I see in the article you mentioned has another
linked article http://support.microsoft.com/kb/214678 that lists one
of the values I mentioned in there ("Replicator notify pause after
modify (secs)") and the suggestion is to set it back to the Windows
2000 default value of 30 seconds instead of the default Windows 2003
value of 3 seconds. The reason I was thinking about the packet sizes
was due to the large number of group members and the fact that I was
not getting any of the other events mentioned there, except for the
12294 one occasionally. I see that changing the in-site timer could
make a difference so I will probably change it over the weekend.

On Oct 25, 6:26 pm, "Austin Osuide" <aus...@nowhere.com> wrote:

Quote:

Hi, I don't think you should change the replication packet sizes without a precise indication to do so. Your event id 1083 issue, I think, is unrelated to "packet size problems" This may help cone down on what the issue is:http://support.microsoft.com/kb/306091 Regards, Austin<cpmf2...@yahoo.com> wrote in message news:1193348079.075011.320620@50g2000hsm.googlegroups.com... I get the event id 1083 logged fairly frequently in the system event logs on a number of my domain controllers, and I believe it is due to the fact that several groups have gotten out of control with many many members added to them. I found these registry entries below which I have been contemplating adding to my DC's to max out the values for the number of objects and packet sizes, and to increase the RPC timeout, and to decrease the replication notification between servers when someone is adding members to the groups a few at a time. Can anyone make any further suggestions or comment on the potential impact this might have? I have tested the values in a lab, and replication works fine, but I don't have large groups there so I am not sure of the overall impact. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters] "RPC Replication Timeout"=dword:0000000f "Replicator Intra Site Packet Size (objects)"=dword:000003e8 "Replicator Intra Site Packet Size (bytes)"=dword:00a00000 "Replicator Inter Site Packet Size (objects)"=dword:000003e8 "Replicator Inter Site Packet Size (bytes)"=dword:00a00000 "Replicator Notify Pause Between DSAs (secs)"=dword:0000001e TIA!!!- Hide quoted text - - Show quoted text -

Good luck.
Let's know if it helps.

Regards,

Austin


<cpmf2112@yahoo.com> wrote in message
news:1193408701.636110.232760@z9g2000hsf.googlegroups.com...

Quote:

Hi Austin, Thanks for your reply. I see in the article you mentioned has another linked article http://support.microsoft.com/kb/214678 that lists one of the values I mentioned in there ("Replicator notify pause after modify (secs)") and the suggestion is to set it back to the Windows 2000 default value of 30 seconds instead of the default Windows 2003 value of 3 seconds. The reason I was thinking about the packet sizes was due to the large number of group members and the fact that I was not getting any of the other events mentioned there, except for the 12294 one occasionally. I see that changing the in-site timer could make a difference so I will probably change it over the weekend. On Oct 25, 6:26 pm, "Austin Osuide" <aus...@nowhere.com> wrote: Hi, I don't think you should change the replication packet sizes without a precise indication to do so. Your event id 1083 issue, I think, is unrelated to "packet size problems" This may help cone down on what the issue is:http://support.microsoft.com/kb/306091 Regards, Austin<cpmf2...@yahoo.com> wrote in message news:1193348079.075011.320620@50g2000hsm.googlegroups.com... I get the event id 1083 logged fairly frequently in the system event logs on a number of my domain controllers, and I believe it is due to the fact that several groups have gotten out of control with many many members added to them. I found these registry entries below which I have been contemplating adding to my DC's to max out the values for the number of objects and packet sizes, and to increase the RPC timeout, and to decrease the replication notification between servers when someone is adding members to the groups a few at a time. Can anyone make any further suggestions or comment on the potential impact this might have? I have tested the values in a lab, and replication works fine, but I don't have large groups there so I am not sure of the overall impact. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters] "RPC Replication Timeout"=dword:0000000f "Replicator Intra Site Packet Size (objects)"=dword:000003e8 "Replicator Intra Site Packet Size (bytes)"=dword:00a00000 "Replicator Inter Site Packet Size (objects)"=dword:000003e8 "Replicator Inter Site Packet Size (bytes)"=dword:00a00000 "Replicator Notify Pause Between DSAs (secs)"=dword:0000001e TIA!!!- Hide quoted text - - Show quoted text -

Well, unfortunately I am still getting the 1083 events being logged on
a regular basis, but everything else appears to be working at this
point. It definitely appears more during normal business hours and
less during the weekend when few people are logged in. I was reading
another article about increasing the replication priority, would this
possibly be helpful or could it be detrimental overall?

I guess I will have to ignore it for now in the absence of a definite
problem, but it is damned annoying.

On Oct 26, 9:53 am, "Austin Osuide" <aus...@nowhere.com> wrote:

Quote:

Good luck. Let's know if it helps. Regards, Austin cpmf2...@yahoo.com> wrote in message news:1193408701.636110.232760@z9g2000hsf.googlegroups.com... Hi Austin, Thanks for your reply. I see in the article you mentioned has another linked articlehttp://support.microsoft.com/kb/214678that lists one of the values I mentioned in there ("Replicator notify pause after modify (secs)") and the suggestion is to set it back to the Windows 2000 default value of 30 seconds instead of the default Windows 2003 value of 3 seconds. The reason I was thinking about the packet sizes was due to the large number of group members and the fact that I was not getting any of the other events mentioned there, except for the 12294 one occasionally. I see that changing the in-site timer could make a difference so I will probably change it over the weekend.