sounds like your site links are setup incorrect. You should setup a site link 
for each remote site and only have the hub site and remote site in that site 
link. If you do it this way the remote DC's will only have 1 dc from the hub 
site. Doing it this way will let the KDC control all replication so if a DC 
goes down it will automatically transfer to another DC. 




________________________________
From: Travis Krampy <[EMAIL PROTECTED]>
To: NT System Admin Issues <[email protected]>
Sent: Friday, November 21, 2008 8:32:49 PM
Subject: Re: NTDS Replication Schedule

 
When i remove the bridgehead, now i get all my 
remote sites repliacting to all the DC's in the default site in the NTDS 
connection settings of the remote DC, is this correct?
"mck1012" <[EMAIL PROTECTED]> wrote in message news:[EMAIL PROTECTED]
What I would recommend is to get rid of the bridgehead server and setup  site 
links for each site to your hub site. Let the KDC control all the  replications 
links. Enable change notification on each site link. 

 




________________________________
 From: Travis Krampy  <[EMAIL PROTECTED]>
To: NT System Admin Issues  <[email protected]>
Sent: Wednesday, November 19, 2008  7:53:34 AM
Subject: Re: NTDS  Replication Schedule

 
10 sites, 14 DC's (1 DC in each site, 4 in the  main site), 1000 users, 1 DC 
per site, except for the main site which has  4.  I have one DC as a 
bridgehead, this is the only DC that is handling  all site replication to the 
remote sites
"mck1012" <[EMAIL PROTECTED]>  wrote in message news:[EMAIL PROTECTED]
How  large is your forest? How many sites? how many dc's? how many users? how  
many dc's per site? are you using site links? are any dc's used as a  
bridgehead? 




________________________________
 From: Travis Krampy  <[EMAIL PROTECTED]>
To: NT System Admin Issues  <[email protected]>
Sent: Tuesday, November 18, 2008  9:40:30 PM
Subject: Re:  NTDS Replication Schedule

 
Connection speed varies from DSL to T-1  speeds.  sometimes many changes are 
being made daily (new users,  etc...), but mostly from the main site and 
replicated to the other  sites.
"mck1012" <[EMAIL PROTECTED]>  wrote in message news:[EMAIL PROTECTED]
What is your connection speed at the remote sites. And how often are  changes 
being made. I would look into enabling change notification on the  site links. 
I have over 50 DC's in my forest with about 48 sites and the  convergence time 
is about 2-3 minutes. 




To enable change notification on a site link 
        1. In ADSI Edit, expand the Configuration Container icon and then 
expand CN=Configuration,DC= ForestRootDomainName and CN=Sites.
        2. Expand the CN=Inter-Site Transports container, and  then click CN=IP.
        3. In the details pane, right-click the site link object whose options 
attribute you want to change, and then click Properties.
        4. In the Select a property to view box, click options.
        5. If the Value(s) box displays <not  set>, in the Edit Attribute box, 
type 1 for the value (bit 0=1).
If the Value(s) box contains a value, you must  derive the new value by using a 
Boolean BITWISE-OR calculation of the  existing value and the value that 
enables the replication change you are  making. Then convert that value to an 
integer. Therefore, if a value is  set, convert the integer value to a binary 
value and OR that value with  the value 0001. Then convert the results back to 
an integer and type the  value in the Edit Attribute box.
For example, if the existing decimal value is 4, that value is equal  to 0100 
in the binary system. The value that enables change notification  is 1, or 0001 
in binary. The OR operation combines 0 OR 0 = 0, 0 OR 1 =  1, 1 OR 0 = 1, 1 OR 
1 = 1. Therefore, the following OR calculation  computes the binary value:
0100 (existing value) 
0001 (value that enables change notification) 
0101 (adds enable change notification to the existing setting) 

The binary value 0101 converts to the digital value 5. For  information about 
binary calculations and converting binary values to  digital values, see 
Windows 2000 Server Help.
        6. Click Set and then click OK. 



________________________________
 From: Travis Krampy  <[EMAIL PROTECTED]>
To: NT System Admin Issues  <[email protected]>
Sent: Tuesday, November 18, 2008  8:39:53 PM
Subject: NTDS  Replication Schedule

Hi

I was wondering if anyone had  any advise on setting up NTDS replication 
schedule in ADSS.

I have  a main site, and 10 remote sites.

I have 4 Domain controllers at  the main site, and 1 domain controller at each 
remote site.

I know  that you can set the replication schedule for none, 1x an hour, 2x an  
hour, 3x an hour or 4x an hour.

I was planning on having my local  site replicate to the remote sites 1 time 
per hour and my local site  replicate to the local DC's 4x an hour, but I was 
not sure if this would  generate too much traffic.

Can anyone please  advise?

Thanks

Travis 

~ Finally, powerful endpoint  security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>   ~


      
~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to