issing Start-OnlineCoexistenceSync when running DirSync via Powershell: Recently working on an environment, I noticed that the Start-OnlineCoexistenceSync is missing when trying to re-sync the Active Directory with Office 365 via PowerShell. This was very helpful when we need to sync the changes manually to Office 365. You’ll also notice that DirSyncConfigShell.psc1 is no longer present in its default location of C:\Program Files\Windows Azure Active Directory Sync. This is due to the change version of the Directory Sync Tool currently running on your Computer. To know more about the Directory Sync tool revision history, click here.
When you try to run command to sync the changes, you get the following error message:
PS C:\> Start-OnlineCoexistenceSync
The term ‘Start-OnlineCoexistenceSync’ is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:28
+ start-onlinecoexistencesync <<<<
+ CategoryInfo : ObjectNotFound: (start-onlinecoexistencesync:String) [], CommandNotFoundException
+ FullyQualifiedErrorId : CommandNotFoundException
PS C:\>
In order to manually sync the directory changes, follow the following steps:
Open PowerShell
Type: Set-ExecutionPolicy Unrestricted and hit return.
Type: Import-Module DirSync and hit return.
Type: Start-OnlineCoexistenceSync and hit return.
Now that you have successfully forced the Directory Sync with Office 365 for changes. You may now want to check what’s synced and if it at all worked.
Open the MIIS Client: “C:\Program Files\Windows Azure Active Directory Sync\SYNCBUS\Synchronization Service\UIShell\miisclient.exe”
On the main screen that opens by default, you’ll see what all has been synced, and its detailed result. There are different section to this page. Clicking on any of the underlined item will show its details. If for any reason it doesn’t open the default screen (shown above), you can open it by clicking the Operations button on the top left side of the screen.
To know more about Directory Synchronization, click here.
Please do not forget to share your feedback, or ask us a question by clicking here.
Latest posts by Rishi Chaudhary (see all)
- ShadowCopy Backup after renaming VSSADMIN.EXE - October 5, 2016
- No Network Connection after Windows 10 Upgrade – Fixed - August 25, 2015
- Windows 10 System Tray Notification Issue - August 7, 2015
Sadly this doesn’t work on our freshly installed Windows 2012 R2 Server with Azure, since MS has removed the DirSync module. There is an “ADSync” module, but it doesn’t contain the Start-OnlineCoexistenceSync method.
ohhh wow, this took a while to figure out why this command was not working. In your instructions above in bold there is a typo. You have “Start-OnlineCoexistanceSync” notice the “a”. The command should be “Start-OnlineCoexistenceSync” with an “e”.
I have no idea why running this in powershell made my users show up in 0365. For some reason, just using miisclient.exe was not working.
Thanks for the update Matt, we have made the required changes