AD Sync between two Sites

scottalanmiller

Network connectivity is a big factor. How fast is it, how reliable is it.

gjacobse

@LAH3385 I guess a better question for you is: How did you know, or realized, AD replication has stop working?

Created User on one side of AD,.. checked the other side, User was NOT there.

Dashrender

@LAH3385 said:

@LAH3385 I guess a better question for you is: How did you know, or realized, AD replication has stop working?

Created User on one side of AD,.. checked the other side, User was NOT there.

long distance replication can take over 15 mins to happen.

Dashrender

@coliver said:

You may want to look into the repadmin command. This will give you an insight into how the replication is working. I think it can even output log files associated with AD replication.

reposted

here are some additional notes
https://technet.microsoft.com/en-us/library/cc794749(v=ws.10).aspx?f=255&MSPPError=-2147217396

gjacobse

@Dashrender said:

@gjacobse said:

@LAH3385 said:

@LAH3385 I guess a better question for you is: How did you know, or realized, AD replication has stop working?

Created User on one side of AD,.. checked the other side, User was NOT there.

long distance replication can take over 15 mins to happen.

I expected as much.

It's been a hour now.

Dashrender

@gjacobse said:

@Dashrender said:

@gjacobse said:

@LAH3385 said:

@LAH3385 I guess a better question for you is: How did you know, or realized, AD replication has stop working?

Created User on one side of AD,.. checked the other side, User was NOT there.

long distance replication can take over 15 mins to happen.

I expected as much.

It's been a hour now.

what does repadmin tell you?

gjacobse

C:\Windows\system32>repadmin /showrepl

Repadmin: running command /showrepl against full DC localhost
DomainName \Srvr-DC3
DSA Options: IS_GC
Site Options: (none)
DSA object GUID: 1a460929-6e4c-4fc3-8377-5ef3b92b422d
DSA invocationID: d85ce1be-42cb-423c-9187-1135bcf58f94

==== INBOUND NEIGHBORS ======================================

DC=Domain Name,DC=com
    Default-First-Site-Name\Srvr-DC2 via RPC
        DSA object GUID: xxxxxxx-xxxx-xxxx-xxxx-f589d72ba337
        Last attempt @ 2016-02-24 10:03:26 was successful.

CN=Configuration,DC=Domain Name,DC=com
    Default-First-Site-Name\Srvr-DC2 via RPC
        DSA object GUID: xxxxxxx-xxxx-xxxx-xxxx-f589d72ba337
        Last attempt @ 2016-02-24 10:03:26 was successful.

CN=Schema,CN=Configuration,DC=Domain Name,DC=com
    Default-First-Site-Name\Srvr-DC2 via RPC
        DSA object GUID: xxxxxxx-xxxx-xxxx-xxxx-f589d72ba337
        Last attempt @ 2016-02-24 10:03:27 was successful.

DC=DomainDnsZones,DC=Domain Name,DC=com
    Default-First-Site-Name\Srvr-DC2 via RPC
        DSA object GUID: xxxxxxx-xxxx-xxxx-xxxx-f589d72ba337
        Last attempt @ 2016-02-24 10:03:27 was successful.

DC=ForestDnsZones,DC=Domain Name,DC=com
    Default-First-Site-Name\Srvr-DC2 via RPC
        DSA object GUID: xxxxxxx-xxxx-xxxx-xxxx-f589d72ba337
        Last attempt @ 2016-02-24 10:03:27 was successful.

looking to force replication now.

coliver

I think it is

repadmin /replicate DC1 DC2 dc=domain,dc=com

Dashrender

Everything looks good - I've heard of replication taking up to 4 hours before.

gjacobse

It just occurred to me... does it matter which end this is performed from?

thedalton

@gjacobse you may want to check your site link replication schedule. The default is 180 minutes. You can drop it down to 15 minutes

gjacobse

@coliver said:

repadmin /replicate DC1 DC2 dc=domain,dc=com

So I have have limited success.. but success was made. I the user I created on the other end,.. is now on the local AD.

I'll look at this more,.. but think it's otherwise solved.

Solved AD Sync between two Sites