Azure AD connect failed

Démo TEST 0 Points de réputation
2024-09-25T14:23:52.3266667+00:00

Error at the end of Azure AD connect installation

In log file I can read those lines ! Anybody can help please?

[14:11:35.363] [ 9] [INFO ] MSAL: False MSAL 4.36.0.0 MSAL.Desktop 4.7.2 Windows Server 2019 Standard [09/25 12:11:35.36 - 4aa3c589-c114-45e0-a339-e944967c4b68] [Region discovery] Azure region was not configured or could not be discovered. Not using a regional authority.

[14:11:35.372] [ 9] [INFO ] MSAL: False MSAL 4.36.0.0 MSAL.Desktop 4.7.2 Windows Server 2019 Standard [09/25 12:11:35.37] Found 0 cache accounts and 0 broker accounts

[14:11:35.373] [ 9] [INFO ] MSAL: False MSAL 4.36.0.0 MSAL.Desktop 4.7.2 Windows Server 2019 Standard [09/25 12:11:35.37] Returning 0 accounts

Thanks
Fred

Windows Server 2019
Windows Server 2019
Système d’exploitation de serveur Microsoft qui prend en charge la gestion au niveau de l’entreprise mise à jour pour le stockage de données.
20 questions
{count} votes

1 réponse

Trier par : Le plus utile
  1. Nouroudine Mohamed KORABOU 0 Points de réputation
    2024-10-24T15:47:27.48+00:00

    Hi,

    Possible causes

    1. Missing or corrupted Azure AD Connect PowerShell module: The Azure AD Connect module, which includes the Get-ADSyncConnector command, might not be installed correctly or corrupted.
    2. Incorrect PowerShell execution context : If you try to run Azure AD Connect commands from a PowerShell session that hasn't loaded the correct module, commands such as Get-ADSyncConnector won't be recognized.
    3. Insufficient permissions : The user account running the Sync Rule Editor or PowerShell might not have the necessary rights to interact with the sync connectors.

    Solutions

    1. Verify that the Azure AD Connect module is loaded

    Make sure that the Azure AD Connect module is loaded in your PowerShell session before running any commands specific to that module. To do this, you can use the following commands:

    Import-Module ADSync

    Then check if the module has been loaded:

    Get-Module -Name ADSync

    If the module is missing, reinstall Azure AD Connect to restore the module.

    2. Run the command from the dedicated PowerShell console

    You must run these commands in a PowerShell session that is open as an administrator on the server where Azure AD Connect is installed. Try the following steps:

    1. Open PowerShell as an administrator.
    2. Manually import the module:

    Import-Module "C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync"

    1. Run the command to see the available connectors:

    Get-ADSyncConnector

    If this works, then the problem is with the Sync Rule Editor environment. You may need to reinstall Azure AD Connect or restart the sync service.

    3. Repair or reinstall Azure AD Connect

    If the ADSync module  is missing or corrupted, a repair or reinstallation of Azure AD Connect could resolve the issue.

    • Repair : Try running the repair from the Control Panel or by downloading the latest Azure AD Connect installer and choosing the repair option.
    • Reinstall: If the repair fails, uninstall and reinstall Azure AD Connect, and then check if the Get-ADSyncConnector command  works correctly after installation.

    4. Check execution permissions

    Make sure that the account you're using to run the orders has sufficient permissions. They must be an on-premises administrator and have rights to Azure AD Connect services.

    5. Additional error logs

    Check the Azure AD Connect logs in the Event Viewer > Applications and Services Logs > Microsoft > AAD), for any additional errors related to PowerShell modules or synchronization.

     

    Hopping it helps!

    Possible causes

    1. Missing or corrupted Azure AD Connect PowerShell module: The Azure AD Connect module, which includes the Get-ADSyncConnector command, might not be installed correctly or corrupted.
    2. Incorrect PowerShell execution context : If you try to run Azure AD Connect commands from a PowerShell session that hasn't loaded the correct module, commands such as Get-ADSyncConnector won't be recognized.
    3. Insufficient permissions : The user account running the Sync Rule Editor or PowerShell might not have the necessary rights to interact with the sync connectors.

    Solutions

    1. Verify that the Azure AD Connect module is loaded

    Make sure that the Azure AD Connect module is loaded in your PowerShell session before running any commands specific to that module. To do this, you can use the following commands:

    Import-Module ADSync

    Then check if the module has been loaded:

    Get-Module -Name ADSync

    If the module is missing, reinstall Azure AD Connect to restore the module.

    2. Run the command from the dedicated PowerShell console

    You must run these commands in a PowerShell session that is open as an administrator on the server where Azure AD Connect is installed. Try the following steps:

    1. Open PowerShell as an administrator.
    2. Manually import the module:

    Import-Module "C:\Program Files\Microsoft Azure AD Sync\Bin\ADSync"

    1. Run the command to see the available connectors:

    Get-ADSyncConnector

    If this works, then the problem is with the Sync Rule Editor environment. You may need to reinstall Azure AD Connect or restart the sync service.

    3. Repair or reinstall Azure AD Connect

    If the ADSync module  is missing or corrupted, a repair or reinstallation of Azure AD Connect could resolve the issue.

    • Repair : Try running the repair from the Control Panel or by downloading the latest Azure AD Connect installer and choosing the repair option.
    • Reinstall: If the repair fails, uninstall and reinstall Azure AD Connect, and then check if the Get-ADSyncConnector command  works correctly after installation.

    4. Check execution permissions

    Make sure that the account you're using to run the orders has sufficient permissions. They must be an on-premises administrator and have rights to Azure AD Connect services.

    5. Additional error logs

    Check the Azure AD Connect logs in the Event Viewer > Applications and Services Logs > Microsoft > AAD), for any additional errors related to PowerShell modules or synchronization.

     

    0 commentaires Aucun commentaire

Votre réponse

Les réponses peuvent être marquées comme réponses acceptées par l’auteur de la question, ce qui aide les utilisateurs à savoir que la réponse a résolu le problème de l’auteur.