2012 R2 Essentials Fails to Integrate with O365

I have an existing client with a Windows 2012 R2 Essential server. I was migrating their email from a GoDaddy POP3/IMAP host over to Office 365. This was going to be my first opportunity to try out the O365 Integration Wizard that comes with the 2012 R2 Essentials dashboard.

image

On May 23rd I set up their Office 365 accounts, setup the DNS records on GoDaddy, and then migrated their email to Office 365, all which went smoothly.

On May 26th I attempted to run the O365 Integration Wizard. After entering the O365 admin account and login info, it errors with this message: “There was an issue configuring the integration. Make sure the computer is connected to the internet and then try again.”

image

I did a lot of web searches, and finally located several posts from people indicating that the error may be related to a corrupt or invalid PCNS.zip file:
https://social.technet.microsoft.com/Forums/en-US/dba06f4f-1011-4de3-946b-2a39718c2cc0/windows-server-2012-essentials-r2-and-office-365-integration?forum=winserveressentials#eb76b50e-6304-48b0-afef-b5fd79978ebf

What’s PCNS? It stands for Microsoft’s Password Change Notification Service which synchronizes user passwords in an enterprise environment.

I confirmed that this was the error by looking at the SharedServiceHost-EmailProvider Config.log file located at C:\Program Data\Microsoft\Windows Server\Logs folder.

The suggested fix was to rename the existing PCNS folder and PCNS.zip file, then download a different PCNS.zip file, and then rerun the wizard. Initially it did not work for me, because I was manually unzipping the corrected PCNS.zip file before running the O365 Wizard. Finally it dawned on me to just download the zip file, and sure enough, the O365 Wizard unzipped it, and we finally had success!

image

Comments

  1. My hero KW. Was stuck on this issue with a WSE 2016 box for hours and your tip about letting the wizard extract the latest PCNS.zip did the trick.

Leave a Reply