ADConnect reinstallation problem

Question

Hi everybody.

Trying to start from scartch, I'd first disabled DirSync with

Set-MsolDirSyncEnabled -EnableDirsync $False

and then uninstalled ADConnect from Add/Remove programs.

My initial setup was with Hash sync and SSO.

Now, when I try to install again, I got an error telling that it's in a pending disabling state. If I check with

(get-msolcompanyinformation).DirectorySynchronizationEnabled

it's in a False state.

But PasswordSynchronizationEnabled is in true state.

At Azure portal, I can see that DirSync is not installed but Hash syn is still enabled, and SSO too. No other related is enabled.
Thanks for your help in advance.

Answer 1

@Administrador Sistemas

Yes, you did look at the wrong object.
It is a known bug at Microsoft.
After waiting for more that 72h it stills got the same problem. By the way - I made a small script that would sent me a msg when the problem was solved. Maybe you can use it to monitor the state.

Connect-MsolService -Credential $MyCredential  
DO  
{  
    $status = (Get-MsolCompanyInformation).directorysynchronizationstatus  
    $status  
    Start-Sleep -s 300  
} while ($status -eq "PendingDisabled")  
$secpasswd = ConvertTo-SecureString "PASSWORD" -AsPlainText -Force  
$cred = New-Object System.Management.Automation.PSCredential ("Loginaccount", $secpasswd)  
Send-MailMessage -SmtpServer 'smtp.office365.com' -Credential $cred -UseSsl -From 'NAME <e-mail>' -To 'NAME <e-mail>' -Subject 'Finished' -Body 'You can start installing again'  

In my case after 72h the problem was not solved. I needed to create a ticked at Microsoft. The problem then was solved within an hour and the script did sent me a mail.
They told me it was a known bug.
I hope this will help you.

Rob

Answer 2

Hi @Administrador Sistemas ,

As directory synchronization isn't activated or deactivated after 72 hrs, follow these steps, and then contact Microsoft Support:

Run below PowerShell cmdlets:

• Connect-MSOLService
• (Get-MSOLCompanyInformation).DirectorySynchronizationStatus

If the output is "PendingEnabled" or "PendingDisabled" after the expected enablement time period has passed, this is a known issue with Exchange Online.
Collect the following information from the Windows PowerShell connection:

• Context ID: To collect the context ID, type the following cmdlet, and then press Enter:
  (Get-MSOLCompanyInformation).objectID
• Service instance: To collect the service instance, type the following cmdlet, and then press Enter:
  (Get-MSOLCompanyInformation).AuthorizedServiceInstances

-----------------------------------------------------------------------------------------------------------

Please do not forget to "Accept the answer" wherever the information provided helps you to help others in the community.