In this PowerShell azure tutorial, we will discuss how to fix the error, The term ‘Get-ADSyncScheduler’ is not recognized that I got while trying to check the current state of the synchronization settings for the Azure AD Connect using Azure PowerShell cmdlet.
Table of Contents
The term ‘Get-ADSyncScheduler’ is not recognized
Recently, while trying to check the current state of the sync on-premises Active Directory to Azure Active Directory with Azure AD Connect using the Azure PowerShell cmdlet, I got this error. I was executing the below Azure PowerShell cmdlet.
Get-ADSyncScheduler cmdlet missing
PS C:\WINDOWS\system32> Get-ADSyncScheduler
After, executing the above PowerShell cmdlet, I got the below error. You can see it as below

We got the error The term ‘Get-ADSyncScheduler’ is not recognized as the name of
a cmdlet.
The complete error message was as below
Get-ADSyncScheduler: The term ‘Get-ADSyncScheduler’ 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:1
- Get-ADSyncScheduler
~~~~~~~- CategoryInfo : ObjectNotFound: (Get-ADSyncScheduler:String) [], Comman
dNotFoundException - FullyQualifiedErrorId : CommandNotFoundException
- CategoryInfo : ObjectNotFound: (Get-ADSyncScheduler:String) [], Comman
The term ‘Get-ADSyncScheduler’ is not recognized [Solved]
Well, to fix the error “The term ‘Get-ADSyncScheduler’ is not recognized as the name of
a cmdlet“, We need to follow the below instructions.
- The first step is to navigate to the directory where you have installed your Azure Active Directory Connect. The path will be like C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync.
- Find out the ADSync.psd1 file in the ADSync folder and then open the file in any of the text editors.
- Add a new line for the missing DLL. As this DLL is located under the parent directory, \Bin, make sure to prefix it with another dot: ..\Microsoft.MetadirectoryServices.Scheduler.dll under the RequiredAssemblies.
- You need to do the same changes in the FileList section as well and finally, save the file.
- Close the PowerShell ISE and then relaunch the PowerShell ISE and try running the Get-ADSyncScheduler Azure PowerShell cmdlet again, This time you should able to execute it successfully without any issue.
This is how, you can able to fix the error The term ‘Get-ADSyncScheduler’ is not recognized as the name of a cmdlet by following the above instructions.
Get-ADSyncScheduler
This Azure PowerShell cmdlet can be used to check the current state of the synchronization settings of the Azure Active Directory Connect. Below are a few parameter values that you will get after running the PowerShell cmdlet.
AllowedSyncCycleInterval
This states the synchronization cycles allowed by Azure AD.
CurrentlyEffectiveSyncCycleInterval:
This will show you the current time interval schedule in effect. The default time interval is 30 minutes.
CustomizedSyncCycleInterval
If you want to customize the time interval of the Scheduler, then you can customize and change the default time from 30 minutes to a different time based on your requirement. The customized time value will show here.
NextSyncCyclePolicyType
You can specify this value as either Delta or Initial. If it is Delta then the next run will process only the delta changes or it will do a full import and sync.
NextSyncCycleStartTimeInUTC
It states that when the next time the scheduler will start the next sync cycle.
PurgeRunHistoryInterval
This specifies the duration you should keep the operation logs. The default duration to keep the operation log is 7 days.
SyncCycleEnabled
If the value is true, then it says the import, sync, and export processes is enabled as part of the operation.
MaintenanceEnabled
if the MaintenanceEnabled value is true, it means that the maintenance process is enabled.
StagingModeEnabled
If the StagingModeEnabled is true, then it specifies that the staging mode is enabled.
This all about the Get-ADSyncScheduler Azure PowerShell cmdlet.
How to view Azure AD Connect schedule and force a sync PowerShell
Well, let’s discuss here, How to view Azure AD Connect schedule and force a sync. Follow the below steps to view the Azure AD Connect schedule and force a sync.
Start the PowerShell
- Open the PowerShell ISE using the Run as administrator mode.
Import the ADSync Module
- Run the below Azure PowerShell cmdlet to import the Adsync module.
PS C:\WINDOWS\system32> Import-Module ADSync
Check the current state of the synchronization
- The next step is, you need to run the below Azure PowerShell cmdlet to check the current state of the synchronization settings
PS C:\WINDOWS\system32> Get-ADSyncScheduler
Run the Sync Command (Force a Sync)
Delta Sync
- Run the below Azure PowerShell cmdlet to perform a Delta sync.
PS C:\WINDOWS\system32> Start-ADSyncSyncCycle -PolicyType Delta
Full Sync
- Now, if you want to run a full sync, then you can run the below Azure PowerShell cmdlet
PS C:\WINDOWS\system32> Start-ADSyncSyncCycle -PolicyType Initial
Once, you will run the above Azure PowerShell cmdlet, it will trigger a Initial sync which will sync all the settings. This is How to manually force Sync Azure AD Connect using PowerShell.
You may also like following the below articles
- The specified module ‘ADSync’ was not loaded because no valid module file was found in any module directory error
- How To Create Azure Windows Virtual Machine From A Snapshot PowerShell
- The Specified Module ‘AzureRM’ Was Not Loaded
- The term ‘get-azuresubscription’ is not recognized
- The Term ‘Connect-AzureRmAccount’ is Not Recognized
- The term ‘register-AzureProvider’ is not recognized as the name of a cmdlet
- Microsoft.Azure.WebJobs.Host: Cannot bind parameter ‘name’ to type String
Wrapping Up
Well, in this article, we have discussed the steps to fix the error The term ‘Get-ADSyncScheduler’ is not recognized as the name of a cmdlet, Get-ADSyncScheduler cmdlet missing, Manually Force Sync Azure AD Connect Using PowerShell, How to view Azure AD Connect schedule and force a sync PowerShell and along with this, we also discussed the Get-ADSyncScheduler Azure PowerShell cmdlet. Hope, It will help you to fix your issue as well !!!