Ask a question


How can we help you today?

Ask Question
Manage notifications
Subscribe to this question
Allen Stone

error message recived when attempting to integrate Windows Server 2012 R2 Essentials with Office 365 and DNS warning message

Hello All:


I am hoping that someone can help me fix a couple of problems that I am having with integrating Windows Server 2012 R2 with Office 365 and starting the DNS service on my server. When I look at the DNS section of the server, I get the following warning:

The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server list in the Internet Protocol properties of this computer. This event will be logged every two minutes until AD DS has signaled that the initial synchronization has successfully completed.

When I attempt to do the integration, I get the following message: There was an issue configuring the integration, make sure you are connected to the internet. I am connected to the internet at the time I get this message. Below is a snippet from the OIM file from the windows server logs:

[2868] 200426.233559.2665: General: Initializing...C:\Windows\System32\Essentials\OIMGettingStartedWizard.exe
[7416] 200426.233559.7509: PfBinding: Information: [0] : Adding service dns identity [AESTONE] in proxy endpoint.
[9116] 200426.233559.9540: PfBinding: Information: [0] : Adding service dns identity [AESTONE] in proxy endpoint.
[7420] 200426.233600.0634: PfBinding: Information: [0] : Adding service dns identity [AESTONE] in proxy endpoint.
[5368] 200426.233627.2687: GettingStartedWizard: Start O365 service
[5368] 200426.233627.2999: WssgCommon: Information: [0] : WseEmailSvc is already in the desired state.
[3436] 200426.233629.5814: O365Manager: TResult : Boolean, args : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
[3436] 200426.233629.5814: O365Manager: actualArgs : Microsoft.WindowsServerSolutions.Common.ProviderFramework.OperationInvokeEventArgs`1[System.Boolean]
[6668] 200426.233629.5814: GettingStartedWizard: Stop O365 service
[6668] 200426.233629.7845: GettingStartedWizard: Activate O365 with Error Unexpected returned.
[6668] 200426.233629.7845: GettingStartedWizard: Activate O365 with Error Unexpected returned.
[6668] 200426.233629.7845: GettingStartedWizard: error page exception : O365ConfigurationFault = Unexpected
Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: The request was aborted: Could not create SSL/TLS secure channel.
   at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementCore.ActivateAAD(String adminUserName, String adminPassword)
   at Microsoft.WindowsServerSolutions.O365Integration.O365ManagementProvider.<>c__DisplayClassd9.<InvokeOperationWrapperAsync>b__d8()
   at Microsoft.WindowsServerSolutions.Common.ProviderFramework.ProviderBase`1.InvokeOperation[TResult](String operationName, Func`1 func)
[2868] 200426.233629.8001: GettingStartedWizard: Stop O365 service
[2868] 200426.233642.2090: GettingStartedWizard: RebootOrRestartDashboardIfNecessary with restart flag is False

 

I am hoping that someone can help me fix this problem. I would note that I have preconfigured the router as I was advised to by the document Preconfiguring a Router for Windows Server 2012 R2 Essentials from Microsoft Docs, namely I assigned the server a static IP address, 10.10.10.164, and inserted the subnet 255.255.255.0 and set the default gateway to the 10.10.10.1, I inserted the DNS of my internet provider, 24.92.226.11 and 24.92.226.12. I have access to the internet on the server. I had a Cisco technician configure the router to enable DHCP, forwarded ports 80 and 443 to the server address and was assured that UPnP support was enabled. I believe that I have done everything that I should have done for this to work. Unfortunately, I do received the error above when I attempt to integrate the server with Office 365. I believe that all the required updates have been applied to the server. 

If there is anything else that you need to know please advise. I am hopeful that someone can help me fix this error, thanks in advance for any and all responses, Allen

asked04/27/2020 04:11
359 views
Add Comment
Mariette Knap

The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed. 

It is a timing issue and can be ignored

Reply
Mariette Knap

Stop using those public DNS server IP addresses. It is wrong and on domain joined devices you should only use AD integrated DNS server IP addresses. Change Preferred to 127.0.0.1 and leave the Alternate empty. After that reboot server and try again.

Reply
Last Activity 04/27/2020 11:45

1 Answer(s)

  • Mariette Knap

    We need to 'enable' TLS 1.2 because that I what Office 365 expects since Jan. 2020. I have another WSE 2012 R2 running so I have some screenshots for you to clarify the issue for you and anybody who has this issue.

    Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000a00

[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Internet Settings\WinHttp]
"DefaultSecureProtocols"=dword:00000a00

    The above setting enables TLS 1.1 and 1.2 but disables the unsecure SSL 3.0, 2.0 and TLS 1.0

    Save the above registry entry to 'DefaultSecureProtocols.reg' and merge it to your system and reboot. Or you can download a zipped version here https://server-essentials.com/Portals/0/Download/DefaultSecureProtocols.zip

    answered 04/27/2020 06:54
    Add Comment
Add an Answer