Password replication across AD sites

active-directorypassword

We are going to be adding a few new Domain Controllers into our school environment to have authentication closer to the end user. I've read about creating the site links and setting the replication intervals there, but I was just trying to get some clarification on how passwords work.

If all DCs are set to replicate from the main DC at SITEA, and someone at SITEB needs a password reset, do I need to reset their password from the DC at SITEB? Or will resetting the password on the DC at SITEA automatically push it down to the other DCs, or does it have to wait for the next tick of the replication interval?

Best Answer

The password is replicated to the domain controller with the PDC Emulator role immediately, at the next replication interval to all other domain controllers.

Additionally, if a logon fails, the authentication is attempted at the the PDC Emulator role domain controller, so you should not need to be too concerned about the effects of delayed replication for password changes.

Related Solutions

Ssh – How to automate SSH login with password

Don't use a password. Generate a passphrase-less SSH key and push it to your VM.

If you already have an SSH key, you can skip this step… Just hit Enter for the key and both passphrases:

$ ssh-keygen -t rsa -b 2048
Generating public/private rsa key pair.
Enter file in which to save the key (/home/username/.ssh/id_rsa):
Enter passphrase (empty for no passphrase):
Enter same passphrase again:
Your identification has been saved in /home/username/.ssh/id_rsa.
Your public key has been saved in /home/username/.ssh/id_rsa.pub.

Copy your keys to the target server:

$ ssh-copy-id id@server
id@server's password:

Now try logging into the machine, with ssh 'id@server', and check-in:

.ssh/authorized_keys

Note: If you don't have .ssh dir and authorized_keys file, you need to create it first

to make sure we haven’t added extra keys that you weren’t expecting.

Finally, check to log in…

$ ssh id@server

id@server:~$

You may also want to look into using ssh-agent if you want to try keeping your keys protected with a passphrase.

Active Directory Replication across Sites slow or not working

We have set the DEFAULTIPSITELINK to 15 minutes for the replication time.

Local DCs replicate instantly... across different sites, it depends on this replication time.

Change this to 15minutes, create a new users, it will replicate instantly across local DCs, wait 15 minutes, it will replicate across different sites.

Best Answer

Related Solutions

Ssh – How to automate SSH login with password

Active Directory Replication across Sites slow or not working

Related Topic