Server 2012 R2 Essentials Archives

Unable to set up Office 365 integration on Windows Server 2012 R2 Essentials

By David | September 8, 2016 | Comments 0 Comment

I’ve previously came across a problem with integrating the Windows Server Essentials 2012 Dashboard with Office 365. I’m posting the problem and solution here as it has helped some other users on a few forums.

Problem:

When running the Office 365 integration wizard in the Windows Server 2012 R2 Essentials dashboard the wizard runs for a very long time, and returns the following error:

“An unknown error occurred. Make sure that the computer is connected to the internet, and the try again. If you continue to to experience, restart the server and then try again”

My Solution:

After checking through the log files (C:\ProgramData\Microsoft\Windows Server\Logs\SharedServiceHost-EmailProviderServiceConfig.log) I found the following:

Microsoft.WindowsServerSolutions.O365Integration.O365ConfigureException: The remote server returned an error: (404) Not Found. —> System.Net.WebException: The remote server returned an error: (404) Not Found.
at System.Net.WebClient.DownloadFile(Uri address, String fileName)
at Microsoft.WindowsServerSolutions.O365Integration.SharePointManagementUtils.InstallCSOM()

I resolved the error by installing the ‘SharePoint Server 2013 Client Components SDK‘ which contains the CSOM modules. See here:

http://www.microsoft.com/en-gb/download/details.aspx?id=35585

Once this had been installed the Integration wizard worked correctly.

Hope that this helps.

Using the Connector with a PC that is already domain joined, to add it into the Essentials Dashboard – Server 2012 R2 Essentials

By David | July 12, 2016 | Comments 0 Comment

I recently came across a problem whereby a number of PCs had been manually added to a domain within a Server 2012 R2 Essentials environment. The customer wanted to be able to connect to the computer remotely via Remote Web Workplace. Therefore the connector needed to be installed.

When you try and install the connector on a PC that is already joined to the domain you get an error saying that a duplicate name already exists on the network (yes, the PC you’re on!).

To resolve the error you need to add a registry key/hack on the client machine which bypasses the domain join section of the wizard. See below:

reg add “HKLM\SOFTWARE\Microsoft\Windows Server\ClientDeployment” /v SkipDomainJoin /t REG_DWORD /d 1

Original Article were the solution was posted:
https://social.technet.microsoft.com/Forums/windowsserver/en-US/603bf59c-4b1f-4fa1-817e-8d0a6bbf236f/how-to-join-a-client-pc-to-ws2012e-r2-thats-already-a-member-of-another-enterprise-domain-using-the?forum=winserveressentials