Intune – Oops… an error occurred! (Windows desktop management)

Just a quick one today, with the surge of BYOD and IT organisations having to look at ways of securing company data a lot are turning to Microsoft Intune.  I have been doing some testing with Intune and Windows 10 desktop.  All in all the management offered by Intune isn’t bad, that not to say there is room for improvement.   However that’s not what this post is about.  This post is about this lovely error you get when trying to access the Company Portal from the Intune desktop client.

Intune Oops... an error occurred!

I had the Microsoft technical staff trying to help me sort this one out but after a lot of testing with a bunch of VMs I found the issue.  If you follow the guidelines on Intune you are instructed to install Windows 10, Azure Active Directory join it, workplace join and finally install the Intune Client.  Well that isn’t quite correct.  The order I found that worked is:

  • Install Windows 10
  • If you want/need to join the PC to AAD you can either do this during the install or afterwards.
  • Install the Intune client (either by GPO, manually or connecting to https://manage.microsoft.com and login with a Intune licenses user and follow the prompts to install)

What’s missing….that darn Workplace join.  If you do this it will break the client and you’ll not be able to access the Intune Company Portal website.  I did find un-enrolling the PC from Workplace Join didn’t help the cause, re-install was by far the quickest solution.

So moral of this story, don’t use work place join on a Windows 10 desktop PC if you are using Intune to manage it.

The downside of this is that the PC’s don’t report correctly in Intune admin console, at the time of writing this blog I’ve been told my the Intune support guys this is correct.

Intune dashboard

It also confuses the console as to what device is actually connected…good eh!

Intune PC information

Things are evolving at a massive rate in Microsoft Intune so I expect this not to be the case for very long.

Leave a Reply

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