<feed xmlns="http://www.w3.org/2005/Atom"><title>instant replication</title><id>https://evotec.xyz/de/tags/instant-replication/index.atom.xml</id><updated>2019-07-21T13:31:06.0000000Z</updated><subtitle>Evotec Main Website</subtitle><link href="https://evotec.xyz/de/tags/instant-replication" /><link href="https://evotec.xyz/de/tags/instant-replication/index.atom.xml" rel="self" type="application/atom+xml" /><entry><title>Instant Replication between Active Directory sites with PowerShell</title><id>https://evotec.xyz/de/blog/active-directory-instant-replication-between-sites-with-powershell</id><link href="https://evotec.xyz/de/blog/active-directory-instant-replication-between-sites-with-powershell" /><updated>2019-07-21T13:31:06.0000000Z</updated><summary>In Active Directory when you change something, it’s replicated to other Domain Controllers regularly. It’s a standard procedure that happens automatically in the background for you. It’s a handy feature because you can have multiple DC’s all over the world and have your users data in sync. You can change almost anything on DC nearest to you and be sure it will be the same value all over the place. But is it always the same? Well, it should be unless it isn’t. Today I was given a new migration from Exchange to Office 365. I started with ADConnect installation and wanted to make sure that UserPrincipalNames have all UPNSuffixes in place.</summary><category term="active directory" /><category term="ad" /><category term="instant replication" /><category term="powershell" /><category term="replication" /></entry></feed>