ConfigMgr Windows Intune connector stops working with error 0x8013150c

intuneconnector-error-00For some reason my Windows Intune connector stopped working correctly recently. While testing I was able to enroll devices to Configuration Manager / Windows Intune but the devices never showed up in the Configuration Manager console.

Same behavior was for newly applications deployed to the collection with all the Windows Intune enabled users. The deployed application did not became available in the Company Portal after logging on.

After some troubleshooting I noticed that for some reason the Connector was not able to reach the Windows Intune service and logged the following errors in the dmpdownloader.log files.

ERROR: GetServiceAddresses – LSU cannot be reached: System.TimeoutException: The request channel timed out while waiting for a reply after 00:04:47.5937516.

Failed to call SaveAccountInfo. error = Unknown error 0x8013150C

intuneconnector-error-01

Restarting the component or the server did not resolve the timeout and the SaveAccountInfo error. The fix / workaround was removing the Windows Intune Connector site role and reinstalling it again. After this action, all enrolled devices became visable in the Configuration Manager 2012 R2 Console and the newly deployed applications became available in the Company Portal.

Be sure to redistribute the deployed applications to the manage.microsoft.com Windows Intune Distribution Point. Redistributing an Application can be done as follows:

  1. Open the Properties of the Application
  2. Go to the Content Locations tab
  3. Select the \\manage.microsoft.com distribution point
  4. Click on Redistribute.

Now that the Windows Intune connector is up and running again I will be looking at the next blog in the Managing Android via ConfigMrg and Windows Intune blog series. (as promised)

I will also have al look why this issue occurred and report back if I know the reason.

Comments

Total
0
Shares
Leave a Reply

Your email address will not be published. Required fields are marked *

Previous Post

ConfigMgrBlog.com, the figures of 2013

Next Post

A quick ConfigMgr 2012 R2 installation tip from Wally Mead

Related Posts
Total
0
Share