As you may already know, Microsoft has released some time ago a new tool – AAD Connect for Azure Active Directory Connect – to manage on premises Active Directory with Office 365 and Azure Active Directory tenants.
This tool is intended to replace the existing Directory Synchronization (DirSync) tool for Office 365 in a few weeks (see the end of this post http://blogs.technet.com/b/ad/archive/2014/12/15/azure-ad-connect-one-simple-fast-lightweight-tool-to-connect-active-directory-and-azure-active-directory.aspx).
Apart of this replacement, it provides ability to synchronize multiple AD Forest, and additional automatic configuration (see for more details about the tool http://blogs.technet.com/b/ad/archive/2014/12/15/azure-ad-connect-one-simple-fast-lightweight-tool-to-connect-active-directory-and-azure-active-directory.aspx)
But this is not the objective of this post. With DirSync it was simple to force the synchronization between the local AD and Azure AD using a PowerShell command (Start-OnlineCoexistenceSync with the –FullSync if you wanted to run a full synchro).
But with AAD Connect, this PowerShell command does not exist anymore.
Ok, so how can you manually start a synchronization with AADConnect?
Simple, open a command prompt with the run as adminitrator.
Then reach the C:\Program Files\Microsoft Azure AD Sync\Bin directory and run the DirectorySyncClientCmd.exe file. And if you want to run a full synchronization, just add the initial parameter (which looks like DirectorySyncClientCmd.exe initial)
And there is no need to open the MIIS console to see the progress as the progress will be shown in the command prompt 
