Import-Module ADSync error - could not load a dll or one of its dependencies

Question

Import-Module ADSync error - could not load a dll or one of its dependencies

Betty Stolwyk 70

I get the following error trying to import the ADSYNC module in powershell:

Could not load file or assembly 'file:///C:\Program Files\Microsoft Azure AD Sync\Bin*Microsoft.Azure.ActiveDirectory.Synchronization.ProvisioningWebServiceAdapter.dll*' or one of its dependencies. An attempt was made to load a program with an incorrect format.

I have verified that the above mentioned dll does indeed exist in the specified folder.

I cannot figure out how to update/reload the powershell module. It does not exist in the PSGallery repository. I suppose it was magically loaded when I installed the ADConnect software. I believe I had loaded and worked with the module with no problems at one time.

This is on a Windows 2019 Server VM, release 1809.

Powershell version 5.1.17763.3770

import-module adsync -Verbose

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\ClientConfiguration.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\Microsoft.Azure.ActiveDirectory.ADSyncManagement.Client.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\Microsoft.Azure.ActiveDirectory.ADSyncManagement.Contract.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\Microsoft.Online.Coexistence.Provision.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\Microsoft.Online.Coexistence.Schema.Ex.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\Microsoft.Online.Coexistence.Security.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\Microsoft.Online.DirSync.Common.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\Microsoft.Online.DirSync.ResAgent.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\Microsoft.Online.DirSync.Resources.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync\UiUtils.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\Microsoft.Azure.ActiveDirectory.Synchronization.Framework.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\Microsoft.Azure.ActiveDirectory.Synchronization.ProvisioningWebServiceAdapter.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\Microsoft.CredentialManagement.OnPremisesPasswordReset.Library.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\Microsoft.CredentialManagement.OnPremisesPasswordReset.Shared.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\Microsoft.IdentityModel.Clients.ActiveDirectory.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\Microsoft.Online.Deployment.Client.Framework.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\Microsoft.Online.PasswordSynchronization.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\Microsoft.Online.PasswordSynchronization.Rpc.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\Microsoft.ServiceBus.dll'.

VERBOSE: Loading 'Assembly' from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\OnPremisesPasswordReset.Security.Cryptography.dll'.

VERBOSE: Loading module from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\adsync\adsync.psd1'.

import-module : Could not load file or assembly 'file:///C:\Program Files\Microsoft Azure AD Sync\Bin\Microsoft.Azure.ActiveDirectory.Synchronization.ProvisioningWebServiceAdapter.dll' or one of its dependencies. An attempt was made to load a program with an incorrect format.

JimmySalian-2011 42,491 Reputation points

2023-03-30T05:23:10.8966667+00:00

Hi,

Can you run the PowerShell with administrator mode and also check the file properties sometimes if you download or extracted it gets blocked, my Antivirus did this and had to put an exception, check the PS version is updated, .Net version is updated also check the event logs.

Hope this helps.

JS

==
Mike Sawin 0 Reputation points

2023-03-30T17:56:17.36+00:00
I have this exact same issue. Same .dll, same Server 2019 version, same Powershell version, and get the exact same error.

AAD Connect was working seamlessly for us for months, and then one day i tried to manually start a sync with the PowerShell command:

Start-ADSyncSyncCycle -PolicyType Delta

which produces this error:

Start-ADSyncSyncCycle : The term 'Start-ADSyncSyncCycle' 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 + Start-ADSyncSyncCycle -PolicyType Delta + ~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Start-ADSyncSyncCycle:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException

Trying to look up a solution to that error led me to try and re-import the ADSync module, which gives me your same error you are experiencing.

AAD Connect still runs automatically without issue, and sync still go through, but not being able to manually initiate a sync is a pain when making changes and wanting to verify they have gone through.

I have tried backing up and deleting the offending .dll and running the AD Connect installer in repair mode hoping that would re-install the .dll, but no luck.

Hopefully someone out there will provide some guidance for us!
Sandeep G-MSFT 20,906 Reputation points Microsoft Employee Moderator

2023-04-03T04:51:39.5333333+00:00

@Betty Stolwyk Is the issue happening only for PowerShell?

Is AD connect tool working fine in terms of syncing objects to Azure AD?

What is the version of Windows 2019 you are using?
Betty Stolwyk 70 Reputation points

2023-04-05T00:08:34.3466667+00:00

@Sandeep - The AD Connect sync tool is working just fine. The problem is only in Powershell. I mentioned the Windows 2019 was release 1809. Is there a different version identifier you are asking about?
@Mike Swain appears to have the exact same problem. I am trying the Import-module ADSYNC because running any ADSync module command, such as 'Get-AdSyncConnector' gives the following error: > get-adsyncconnector get-adsyncconnector : The 'get-adsyncconnector' command was found in the module 'ADSync', but the module could not be loaded. For more information, run 'Import-Module ADSync'. But running the 'import-module ADSync' gets the error mentioned in my original post. Many of the dll's load, but it burps on '\Microsoft.Azure.ActiveDirectory.Synchronization.ProvisioningWebServiceAdapter.dll' It appears to be an issue with that specific dll, as though the ADSync module is somehow corrupted. But I do not see a way to install a different/newer/uncorrupted ADSync module since it is magically installed when AD Connect is installed. @Mike Swain tried reinstalling AD Connect itself, but that did not help.
Betty Stolwyk 70 Reputation points

2023-04-05T00:34:06.1666667+00:00

@JimmySalian-2011
In answer to your questions: I am running as administrator. There is no downloading or extracting involved. The files are individual dll's on the local machine. The machine has .NET 3.5 and 4.7 I'm not sure what you mean by the latest Powershell. I have version 5.1 which is compatible with the ADSync module. No Event Viewer errors except the .dll error mentioned in the original post.
Sandeep G-MSFT 20,906 Reputation points Microsoft Employee Moderator

2023-04-05T02:25:34.03+00:00

@Betty Stolwyk Let's try to work on this issue offline. Please send us an email on azcommunity [at] microsoft [dot] com with Sub - Attn: Sandeg and following details in the email body: Link to this thread/post We can connect offline and discuss further on this.
Betty Stolwyk 70 Reputation points

2023-04-11T23:11:11.21+00:00
@Mike Sawin does my solution below fix your issue?
Mike Sawin 0 Reputation points

2023-04-12T13:16:13.5533333+00:00

@Betty Stolwyk Unfortunately that did not work for me. I didn't check what version of PowerShellGet I was on before i ran the update, but after installing the new one i confirmed i was on 2.2.5. Still got the same error. Tried following the same process to update my ExchangeOnlineManagement module, successfully updated from 3.0.0 to 3.1.0, but no luck there either, still the same issue.

Accepted answer

4 additional answers

Your answer

JimmySalian-2011 42,491 Reputation points

2023-03-30T05:23:10.8966667+00:00

Hi,

Can you run the PowerShell with administrator mode and also check the file properties sometimes if you download or extracted it gets blocked, my Antivirus did this and had to put an exception, check the PS version is updated, .Net version is updated also check the event logs.

Hope this helps.

JS

==
Mike Sawin 0 Reputation points

2023-03-30T17:56:17.36+00:00

I have this exact same issue. Same .dll, same Server 2019 version, same Powershell version, and get the exact same error.

AAD Connect was working seamlessly for us for months, and then one day i tried to manually start a sync with the PowerShell command:

Start-ADSyncSyncCycle -PolicyType Delta

which produces this error:

Start-ADSyncSyncCycle : The term 'Start-ADSyncSyncCycle' 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 + Start-ADSyncSyncCycle -PolicyType Delta + ~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : ObjectNotFound: (Start-ADSyncSyncCycle:String) [], CommandNotFoundException + FullyQualifiedErrorId : CommandNotFoundException

Trying to look up a solution to that error led me to try and re-import the ADSync module, which gives me your same error you are experiencing.

AAD Connect still runs automatically without issue, and sync still go through, but not being able to manually initiate a sync is a pain when making changes and wanting to verify they have gone through.

I have tried backing up and deleting the offending .dll and running the AD Connect installer in repair mode hoping that would re-install the .dll, but no luck.

Hopefully someone out there will provide some guidance for us!
Sandeep G-MSFT 20,906 Reputation points Microsoft Employee Moderator

2023-04-03T04:51:39.5333333+00:00

@Betty Stolwyk Is the issue happening only for PowerShell?

Is AD connect tool working fine in terms of syncing objects to Azure AD?

What is the version of Windows 2019 you are using?
Betty Stolwyk 70 Reputation points

2023-04-05T00:08:34.3466667+00:00

@Sandeep - The AD Connect sync tool is working just fine. The problem is only in Powershell. I mentioned the Windows 2019 was release 1809. Is there a different version identifier you are asking about?
@Mike Swain appears to have the exact same problem. I am trying the Import-module ADSYNC because running any ADSync module command, such as 'Get-AdSyncConnector' gives the following error: > get-adsyncconnector get-adsyncconnector : The 'get-adsyncconnector' command was found in the module 'ADSync', but the module could not be loaded. For more information, run 'Import-Module ADSync'. But running the 'import-module ADSync' gets the error mentioned in my original post. Many of the dll's load, but it burps on '\Microsoft.Azure.ActiveDirectory.Synchronization.ProvisioningWebServiceAdapter.dll' It appears to be an issue with that specific dll, as though the ADSync module is somehow corrupted. But I do not see a way to install a different/newer/uncorrupted ADSync module since it is magically installed when AD Connect is installed. @Mike Swain tried reinstalling AD Connect itself, but that did not help.
Betty Stolwyk 70 Reputation points

2023-04-05T00:34:06.1666667+00:00

@JimmySalian-2011
In answer to your questions: I am running as administrator. There is no downloading or extracting involved. The files are individual dll's on the local machine. The machine has .NET 3.5 and 4.7 I'm not sure what you mean by the latest Powershell. I have version 5.1 which is compatible with the ADSync module. No Event Viewer errors except the .dll error mentioned in the original post.
Sandeep G-MSFT 20,906 Reputation points Microsoft Employee Moderator

2023-04-05T02:25:34.03+00:00

@Betty Stolwyk Let's try to work on this issue offline. Please send us an email on azcommunity [at] microsoft [dot] com with Sub - Attn: Sandeg and following details in the email body: Link to this thread/post We can connect offline and discuss further on this.
Betty Stolwyk 70 Reputation points

2023-04-11T23:11:11.21+00:00

@Mike Sawin does my solution below fix your issue?
Mike Sawin 0 Reputation points

2023-04-12T13:16:13.5533333+00:00

@Betty Stolwyk Unfortunately that did not work for me. I didn't check what version of PowerShellGet I was on before i ran the update, but after installing the new one i confirmed i was on 2.2.5. Still got the same error. Tried following the same process to update my ExchangeOnlineManagement module, successfully updated from 3.0.0 to 3.1.0, but no luck there either, still the same issue.

Answer 1

@Betty Stolwyk

I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this! Since the Microsoft Q&A community has a policy that "[The question author cannot accept their own answer. They can only accept answers by others] (https://docs.microsoft.com/en-us/answers/support/accepted-answers#why-only-one-accepted-answer)", I'll repost your solution in case you'd like to "[Accept] (https://docs.microsoft.com/en-us/answers/support/accepted-answers#accepted-answer-in-a-question-thread)" the answer.

You updated the PowerShellGet module. The machine that ADConnect was installed on still had PowerShellGet 1.0.0.1. The updated version was 2.2.5. You also installed the ExchangeOnlineManagement powershell module. Here is the PowerShellGet update command you ran: Install-Module PowerShellGet -Force -AllowClobber An import-module executes successfully now.

Please "Accept the answer" if the information helped you. This will help us and others in the community as well.

Matt Reid 25 Reputation points

2023-06-05T11:49:40.0466667+00:00

I had a similar issue where the "Start-ADSyncSyncCycle -PolicyType Delta" command would work in elevated PowerShell, but would not work from a script. It baffled me as it has no issues on two other DCs that had AD Connect installed. This DC was a fresh install (imported settings from another DC as well) and what worked for me was updating PowerShellGet to 2.2.5 AND rebooting the DC. TBH it may have just needed a reboot to begin with, but this is the path I followed. Thanks for the help.

Answer 2

Ryan Shoemaker 15

For anyone else running into this, I found the issue to be when running the (x86) version of powershell is not compatible with the ADSync module. Check your shortcuts that you're using to open powershell. You can use the command:

[Environment]::Is64BitProcess

to check if you're running a 64 bit version of Powershell. If it returns false, ADSync commands won't work.

User's image

I hope this helps!

Answer 3

Hello there,

Do you have the Connector installed?

Usually, by installing the connector, all prerequisites get installed as well.

Install Azure Active Directory Connect
Import the ADSync PowerShell module
Run the Start-AdSyncSchedule cmdlet with reads a domain controller’s password hashes and syncs with Azure AD.

You have to run or invoke that on the same machine where the Azure AD - Connector is installed.

https://docs.microsoft.com/en-us/azure/active-directory/hybrid/how-to-connect-sync-feature-scheduler

Hope this resolves your Query !!

--If the reply is helpful, please Upvote and Accept it as an answer–

Answer 4

So, it's working now. I updated the PowerShellGet module and I think that's what did it. the machine that ADConnect was installed on still had PowerShellGet 1.0.0.1. The updated version was 2.2.5. I can't say for sure that is what fixed things because I also installed the ExchangeOnlineManagement powershell module, but I don't see what that would have to do with the ADConnect module. Anyway here is the PowerShellGet update command I ran: Install-Module PowerShellGet -Force -AllowClobber An import-module executes successfully now: Import-Module -Name adsync -verbose VERBOSE: Loading module from path 'C:\Program Files\Microsoft Azure AD Sync\Bin\adsync\adsync.psd1'.

VERBOSE: Importing cmdlet 'Add-ADSyncAADServiceAccount'.
VERBOSE: Importing cmdlet 'Add-ADSyncADDSConnectorAccount'.
VERBOSE: Importing cmdlet 'Add-ADSyncAttributeFlowMapping'.
VERBOSE: Importing cmdlet 'Add-ADSyncConnector'.
VERBOSE: Importing cmdlet 'Add-ADSyncConnectorAnchorConstructionSettings'.
VERBOSE: Importing cmdlet 'Add-ADSyncConnectorAttributeInclusion'.
VERBOSE: Importing cmdlet 'Add-ADSyncConnectorHierarchyProvisioningMapping'.
VERBOSE: Importing cmdlet 'Add-ADSyncConnectorObjectInclusion'.
VERBOSE: Importing cmdlet 'Add-ADSyncGlobalSettingsParameter'.
VERBOSE: Importing cmdlet 'Add-ADSyncJoinConditionGroup'.
VERBOSE: Importing cmdlet 'Add-ADSyncRule'.
VERBOSE: Importing cmdlet 'Add-ADSyncRunProfile'.
VERBOSE: Importing cmdlet 'Add-ADSyncRunStep'.
VERBOSE: Importing cmdlet 'Add-ADSyncScopeConditionGroup'.
VERBOSE: Importing cmdlet 'Add-AgentToResourceGroup'.
VERBOSE: Importing cmdlet 'Clear-ADSyncRuleAudit'.
VERBOSE: Importing cmdlet 'Disable-ADSyncConnectorPartition'.
VERBOSE: Importing cmdlet 'Disable-ADSyncConnectorPartitionHierarchy'.
VERBOSE: Importing cmdlet 'Disable-ADSyncExportDeletionThreshold'.
VERBOSE: Importing cmdlet 'Enable-ADSyncConnectorPartition'.
VERBOSE: Importing cmdlet 'Enable-ADSyncConnectorPartitionHierarchy'.
VERBOSE: Importing cmdlet 'Enable-ADSyncExportDeletionThreshold'.
VERBOSE: Importing cmdlet 'Get-ADSyncAADCompanyFeature'.
VERBOSE: Importing cmdlet 'Get-ADSyncAADPasswordResetConfiguration'.
VERBOSE: Importing cmdlet 'Get-ADSyncAADPasswordSyncConfiguration'.
VERBOSE: Importing cmdlet 'Get-ADSyncADConnectorSchemaDsml'.
VERBOSE: Importing cmdlet 'Get-ADSyncAutoUpgrade'.
VERBOSE: Importing cmdlet 'Get-ADSyncConnector'.
VERBOSE: Importing cmdlet 'Get-ADSyncConnectorHierarchyProvisioningDNComponent'.
VERBOSE: Importing cmdlet 'Get-ADSyncConnectorHierarchyProvisioningMapping'.
VERBOSE: Importing cmdlet 'Get-ADSyncConnectorHierarchyProvisioningObjectClass'.
VERBOSE: Importing cmdlet 'Get-ADSyncConnectorParameter'.
VERBOSE: Importing cmdlet 'Get-ADSyncConnectorPartition'.
VERBOSE: Importing cmdlet 'Get-ADSyncConnectorPartitionHierarchy'.
VERBOSE: Importing cmdlet 'Get-ADSyncConnectorRunStatus'.
VERBOSE: Importing cmdlet 'Get-ADSyncConnectorStatistics'.
VERBOSE: Importing cmdlet 'Get-ADSyncConnectorTypes'.
VERBOSE: Importing cmdlet 'Get-ADSyncCSGroupStatistics'.
VERBOSE: Importing cmdlet 'Get-ADSyncCSGroupSummary'.
VERBOSE: Importing cmdlet 'Get-ADSyncCSObject'.
VERBOSE: Importing cmdlet 'Get-ADSyncCSObjectLog'.
VERBOSE: Importing cmdlet 'Get-ADSyncCSObjectReferences'.
VERBOSE: Importing cmdlet 'Get-ADSyncDatabaseConfiguration'.
VERBOSE: Importing cmdlet 'Get-ADSyncDomainReachabilityStatus'.
VERBOSE: Importing cmdlet 'Get-ADSyncExportDeletionThreshold'.
VERBOSE: Importing cmdlet 'Get-ADSyncGlobalSettings'.
VERBOSE: Importing cmdlet 'Get-ADSyncGlobalSettingsParameter'.
VERBOSE: Importing cmdlet 'Get-ADSyncMVObject'.
VERBOSE: Importing cmdlet 'Get-ADSyncPartitionPasswordSyncState'.
VERBOSE: Importing cmdlet 'Get-ADSyncRule'.
VERBOSE: Importing cmdlet 'Get-ADSyncRuleAudit'.
VERBOSE: Importing cmdlet 'Get-ADSyncRunProfileResult'.
VERBOSE: Importing cmdlet 'Get-ADSyncRunStepResult'.
VERBOSE: Importing cmdlet 'Get-ADSyncScheduler'.
VERBOSE: Importing cmdlet 'Get-ADSyncSchedulerConnectorOverride'.
VERBOSE: Importing cmdlet 'Get-ADSyncSchema'.
VERBOSE: Importing cmdlet 'Get-ADSyncServerConfiguration'.
VERBOSE: Importing cmdlet 'Invoke-ADSyncCSObjectPasswordHashSync'.
VERBOSE: Importing cmdlet 'Invoke-ADSyncGarbageCollection'.
VERBOSE: Importing cmdlet 'Invoke-ADSyncRunProfile'.
VERBOSE: Importing cmdlet 'Invoke-ADSyncSpecificObjectRunProfile'.
VERBOSE: Importing cmdlet 'New-ADSyncConnector'.
VERBOSE: Importing cmdlet 'New-ADSyncJoinCondition'.
VERBOSE: Importing cmdlet 'New-ADSyncRule'.
VERBOSE: Importing cmdlet 'New-ADSyncRunProfile'.
VERBOSE: Importing cmdlet 'New-ADSyncScopeCondition'.
VERBOSE: Importing cmdlet 'Register-Agent'.
VERBOSE: Importing cmdlet 'Remove-ADSyncAADPasswordResetConfiguration'.
VERBOSE: Importing cmdlet 'Remove-ADSyncAADPasswordSyncConfiguration'.
VERBOSE: Importing cmdlet 'Remove-ADSyncAADServiceAccount'.
VERBOSE: Importing cmdlet 'Remove-ADSyncAttributeFlowMapping'.
VERBOSE: Importing cmdlet 'Remove-ADSyncConnector'.
VERBOSE: Importing cmdlet 'Remove-ADSyncConnectorAnchorConstructionSettings'.
VERBOSE: Importing cmdlet 'Remove-ADSyncConnectorAttributeInclusion'.
VERBOSE: Importing cmdlet 'Remove-ADSyncConnectorHierarchyProvisioningMapping'.
VERBOSE: Importing cmdlet 'Remove-ADSyncConnectorObjectInclusion'.
VERBOSE: Importing cmdlet 'Remove-ADSyncCSObject'.
VERBOSE: Importing cmdlet 'Remove-ADSyncGlobalSettingsParameter'.
VERBOSE: Importing cmdlet 'Remove-ADSyncJoinConditionGroup'.
VERBOSE: Importing cmdlet 'Remove-ADSyncRule'.
VERBOSE: Importing cmdlet 'Remove-ADSyncRunProfile'.
VERBOSE: Importing cmdlet 'Remove-ADSyncRunStep'.
VERBOSE: Importing cmdlet 'Remove-ADSyncScopeConditionGroup'.
VERBOSE: Importing cmdlet 'Search-ADSyncDirectoryObjects'.
VERBOSE: Importing cmdlet 'Set-ADSyncAADCompanyFeature'.
VERBOSE: Importing cmdlet 'Set-ADSyncAADPasswordResetConfiguration'.
VERBOSE: Importing cmdlet 'Set-ADSyncAADPasswordSyncConfiguration'.
VERBOSE: Importing cmdlet 'Set-ADSyncAADPasswordSyncState'.
VERBOSE: Importing cmdlet 'Set-ADSyncAutoUpgrade'.
VERBOSE: Importing cmdlet 'Set-ADSyncConnectorOrder'.
VERBOSE: Importing cmdlet 'Set-ADSyncConnectorParameter'.
VERBOSE: Importing cmdlet 'Set-ADSyncDirSyncConfiguration'.
VERBOSE: Importing cmdlet 'Set-ADSyncGlobalSettings'.
VERBOSE: Importing cmdlet 'Set-ADSyncScheduler'.
VERBOSE: Importing cmdlet 'Set-ADSyncSchedulerConnectorOverride'.
VERBOSE: Importing cmdlet 'Set-ADSyncSchema'.
VERBOSE: Importing cmdlet 'Set-ADSyncServerConfiguration'.
VERBOSE: Importing cmdlet 'Set-MIISADMAConfiguration'.
VERBOSE: Importing cmdlet 'Start-ADSyncAADPasswordResetEndpoint'.
VERBOSE: Importing cmdlet 'Start-ADSyncPurgeRunHistory'.
VERBOSE: Importing cmdlet 'Start-ADSyncSyncCycle'.
VERBOSE: Importing cmdlet 'Stop-ADSyncAADPasswordResetEndpoint'.
VERBOSE: Importing cmdlet 'Stop-ADSyncRunProfile'.
VERBOSE: Importing cmdlet 'Stop-ADSyncSyncCycle'.
VERBOSE: Importing cmdlet 'Sync-ADSyncCSObject'.
VERBOSE: Importing cmdlet 'Test-ADSyncADDSConnectivity'.
VERBOSE: Importing cmdlet 'Test-AdSyncAzureServiceConnectivity'.
VERBOSE: Importing cmdlet 'Test-ADSyncGetDirectoryReplicationChanges'.
VERBOSE: Importing cmdlet 'Test-AdSyncUserHasPermissions'.
VERBOSE: Importing cmdlet 'Update-ADSyncAADPasswordResetClientVersion'.
VERBOSE: Importing cmdlet 'Update-ADSyncAADPasswordResetConfiguration'.
VERBOSE: Importing cmdlet 'Update-ADSyncConnectorOrder'.
VERBOSE: Importing cmdlet 'Update-ADSyncConnectorPartitions'.
VERBOSE: Importing cmdlet 'Update-ADSyncConnectorSchema'.
VERBOSE: Importing cmdlet 'Update-ADSyncDirectoryObject'.
VERBOSE: Importing cmdlet 'Update-ADSyncDRSCertificates'.
VERBOSE: Importing cmdlet 'Update-ADSyncServicePrincipalCertificate'.

Answer 5

Deleted

This answer has been deleted due to a violation of our Code of Conduct. The answer was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Comments have been turned off. Learn more

Share via

Import-Module ADSync error - could not load a dll or one of its dependencies

4 additional answers

Your answer