{"id":16451,"date":"2016-06-01T10:00:28","date_gmt":"2016-06-01T08:00:28","guid":{"rendered":"http:\/\/nolabnoparty.com\/en\/?p=16451"},"modified":"2016-08-01T08:39:00","modified_gmt":"2016-08-01T06:39:00","slug":"office-365-upgrade-dirsync-azure-ad-connect","status":"publish","type":"post","link":"https:\/\/nolabnoparty.com\/en\/office-365-upgrade-dirsync-azure-ad-connect\/","title":{"rendered":"Office 365: upgrade DirSync to Azure AD Connect"},"content":{"rendered":"<p><img decoding=\"async\" class=\"aligncenter wp-image-16879 size-full\" title=\"upgdirsynctoadconnect01\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect01.jpg\" alt=\"upgdirsynctoadconnect01\" width=\"602\" height=\"202\" \/><\/p>\n<p>Azure AD connect is the solution used to connect the\u00a0on-premises directory with Azure AD\u00a0and it replaces the tools\u00a0<strong>DirSync<\/strong> and <strong>Azure AD Sync<\/strong>\u00a0now deprecated.<\/p>\n<p>The synchronization tools offered for <strong>single forest<\/strong>\u00a0(DirSync) and for <strong>multi-forest<\/strong>\u00a0(Azure AD Sync) have been\u00a0replaced by\u00a0Azure AD Connect, the new solution\u00a0that offers new functionality, feature enhancements and support for new scenarios. The old tools\u00a0will reach\u00a0<strong>end of support<\/strong> on April 13, 2017.<!--more--><\/p>\n<p>If you are running <strong>DirSync with\u00a0a recent OS<\/strong> and less than 50.000 objects, the\u00a0<strong>In-place upgrade<\/strong>\u00a0is the procedure recommended for most customers.\u00a0In other scenarios where the<strong>\u00a0DirSync configuration is moved<\/strong> to a new server running Azure AD Connect,\u00a0<strong>Parallel deployment<\/strong>\u00a0should be used instead.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16880 size-large\" title=\"upgdirsynctoadconnect02\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect02-600x273.jpg\" alt=\"upgdirsynctoadconnect02\" width=\"600\" height=\"273\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Prerequisites<\/h2>\n<p>On-premises servers and environment must meet\u00a0the following prerequisites:<\/p>\n<ul>\n<li>If password synchronization feature is being used, the Azure AD Connect server must be on Windows Server 2008 R2 SP1 or later.<\/li>\n<li>.NET Framework 4.5.1 or later and Microsoft PowerShell 3.0 or later must be installed.<\/li>\n<li>The servers where AD FS or Web Application Proxy will be installed must be Windows Server 2012 R2 or later.<\/li>\n<li>An Azure subscription.\u00a0With a paid Office 365 license you can also get into the Azure portal from the Office 365 portal.<\/li>\n<\/ul>\n<p>&nbsp;<\/p>\n<h2>In-place upgrade<\/h2>\n<p>If you have an existing DirSync server already running, an in-place upgrade is recommended.<\/p>\n<p>Download from Microsoft website\u00a0<a href=\"http:\/\/go.microsoft.com\/fwlink\/?LinkId=615771\" target=\"_blank\" rel=\"noopener\">Azure AD Connect<\/a> and run the installer. Accept the EULA then click <strong>Continue<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16881 size-large\" title=\"upgdirsynctoadconnect03\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect03-600x423.jpg\" alt=\"upgdirsynctoadconnect03\" width=\"600\" height=\"423\" \/><\/p>\n<p>The system starts analyzing\u00a0previously installed DirSync configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16882 size-large\" title=\"upgdirsynctoadconnect04\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect04-600x423.jpg\" alt=\"upgdirsynctoadconnect04\" width=\"600\" height=\"423\" \/><\/p>\n<p>Click <strong>Next<\/strong> to proceed with upgrade.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16883 size-large\" title=\"upgdirsynctoadconnect05\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect05-600x423.jpg\" alt=\"upgdirsynctoadconnect05\" width=\"600\" height=\"423\" \/><\/p>\n<p>The process installs required components and the application.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16884 size-large\" title=\"upgdirsynctoadconnect06\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect06-600x423.jpg\" alt=\"upgdirsynctoadconnect06\" width=\"600\" height=\"423\" \/><\/p>\n<p>Enter the Azure AD <strong>Admin password<\/strong> and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16885 size-large\" title=\"upgdirsynctoadconnect07\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect07-600x423.jpg\" alt=\"upgdirsynctoadconnect07\" width=\"600\" height=\"423\" \/><\/p>\n<p>The entered credentials are being verified.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16886 size-large\" title=\"upgdirsynctoadconnect08\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect08-600x423.jpg\" alt=\"upgdirsynctoadconnect08\" width=\"600\" height=\"423\" \/><\/p>\n<p>Enter now the <strong>AD Enterprise Administrator<\/strong> credentials for the current forest and click <strong>Next<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16889 size-large\" title=\"upgdirsynctoadconnect09\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect09-600x423.jpg\" alt=\"upgdirsynctoadconnect09\" width=\"600\" height=\"423\" \/><\/p>\n<p>Enable <strong>Start the synchronization process when configuration completes<\/strong>\u00a0option then click <strong>Upgrade<\/strong> button to proceed.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16890 size-large\" title=\"upgdirsynctoadconnect10\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect10-600x423.jpg\" alt=\"upgdirsynctoadconnect10\" width=\"600\" height=\"423\" \/><\/p>\n<p><strong>DirSync is uninstalled<\/strong> from the system keeping previous configuration.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16891 size-large\" title=\"upgdirsynctoadconnect11\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect11-600x423.jpg\" alt=\"upgdirsynctoadconnect11\" width=\"600\" height=\"423\" \/><\/p>\n<p>Application is installed applying <strong>previous configuration<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16892 size-large\" title=\"upgdirsynctoadconnect12\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect12-600x423.jpg\" alt=\"upgdirsynctoadconnect12\" width=\"600\" height=\"423\" \/><\/p>\n<p>When the upgrade process completes, click <strong>Exit<\/strong> to exit the wizard.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16897 size-large\" title=\"upgdirsynctoadconnect13\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect13-600x423.jpg\" alt=\"upgdirsynctoadconnect13\" width=\"600\" height=\"423\" \/><\/p>\n<p>Login the Office 365 portal and under <strong>DirSync Status<\/strong> check the <strong>Last directory sync<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16898 size-large\" title=\"upgdirsynctoadconnect14\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect14-600x322.jpg\" alt=\"upgdirsynctoadconnect14\" width=\"600\" height=\"322\" \/><\/p>\n<p>&nbsp;<\/p>\n<h4>Change the configuration and advanced\u00a0features<\/h4>\n<p>Run the Azure AD Connect from Desktop's icon to <strong>modify the configuration<\/strong>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16899 size-large\" title=\"upgdirsynctoadconnect15\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect15-600x423.jpg\" alt=\"upgdirsynctoadconnect15\" width=\"600\" height=\"423\" \/><\/p>\n<p>Details of the <strong>synchronization status <\/strong>and<strong> advanced configuration<\/strong> can be accessed\u00a0running the <strong>miisclient.exe<\/strong> tool locatd in <em>C:\\Program Files\\Microsoft Azure AD Sync\\UIShell<\/em>.<\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16905 size-large\" title=\"upgdirsynctoadconnect16\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect16-600x469.jpg\" alt=\"upgdirsynctoadconnect16\" width=\"600\" height=\"469\" \/><\/p>\n<p>&nbsp;<\/p>\n<h2>Force synchronization using PowerShell<\/h2>\n<p>The synchronization between on-premises directory and Azure AD can be forced\u00a0using <strong>PowerShell commands<\/strong>.<\/p>\n<p>Open Windows PowerShell and run the command:<\/p>\n<p><span style=\"color: #0000ff;\">PS: C:\\&gt; Import-Module adsync<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16906 size-large\" title=\"upgdirsynctoadconnect17\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect17-600x107.jpg\" alt=\"upgdirsynctoadconnect17\" width=\"600\" height=\"107\" \/><\/p>\n<p>Check the <strong>current sync schedule<\/strong> with the command:<\/p>\n<p><span style=\"color: #0000ff;\">PS: C:\\&gt; Get-ADSyncScheduler<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16907 size-large\" title=\"upgdirsynctoadconnect18\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect18-600x249.jpg\" alt=\"upgdirsynctoadconnect18\" width=\"600\" height=\"249\" \/><\/p>\n<p>To perform the synchronization you can use two commands:<\/p>\n<ul>\n<li><strong>Full sync<\/strong>: \u00a0 \u00a0Start-ADSyncSyncCycle -PolicyType Initial<\/li>\n<li><strong>Delta sync<\/strong>: Start-ADSyncSyncCycle -PolicyType Delta<\/li>\n<\/ul>\n<p><span style=\"color: #0000ff;\">PS: C:\\&gt; Start-ADSyncSyncCycle -PolicyType Initial<\/span><\/p>\n<p><img decoding=\"async\" class=\"aligncenter wp-image-16908 size-large\" title=\"upgdirsynctoadconnect19\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/2016\/06\/upgdirsynctoadconnect19-600x261.jpg\" alt=\"upgdirsynctoadconnect19\" width=\"600\" height=\"261\" \/><\/p>\n<p>Completed the upgrade procedure, the system is now able to synchronize\u00a0the\u00a0on-premises directory with Azure AD.<\/p>\n<p><img decoding=\"async\" src=\"https:\/\/nolabnoparty.com\/wp-content\/uploads\/images\/firma.jpg\" alt=\"firma\" title=\"\"><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Azure AD connect is the solution used to connect the\u00a0on-premises directory with Azure AD\u00a0and it replaces the tools\u00a0DirSync and Azure AD Sync\u00a0now deprecated. The synchronization tools offered for single forest\u00a0(DirSync) and for multi-forest\u00a0(Azure AD Sync) have been\u00a0replaced by\u00a0Azure AD Connect, the new solution\u00a0that offers new functionality, feature enhancements and support for new scenarios. The old tools\u00a0will reach\u00a0end of support on April 13, 2017.<\/p>\n","protected":false},"author":3,"featured_media":16879,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"rop_custom_images_group":[],"rop_custom_messages_group":[],"rop_publish_now":"initial","rop_publish_now_accounts":{"facebook_2879994398731222_17841400390232720":"","mastodon_115463926174894442_115463926174894442":"","linkedin_93tdZWzMZc_93tdZWzMZc":"","bluesky_did:plc:tkabz5kl2rukzdwtuongv3kz_did:plc:tkabz5kl2rukzdwtuongv3kz":""},"rop_publish_now_history":[],"rop_publish_now_status":"pending","footnotes":""},"categories":[1065,1721],"tags":[1683,1682,1577,1402],"class_list":["post-16451","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-microsoft-en","category-office365-en","tag-ad-connect","tag-azure","tag-dirsync","tag-sso-en","has_thumb"],"_links":{"self":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/16451","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/comments?post=16451"}],"version-history":[{"count":0,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/posts\/16451\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media\/16879"}],"wp:attachment":[{"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/media?parent=16451"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/categories?post=16451"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nolabnoparty.com\/en\/wp-json\/wp\/v2\/tags?post=16451"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}