As of yesterday, Intune now lets us deploy MSI files to (auto) enrolled devices!*
This is another nice step forward into making this product more mature, hopefully in the future we’ll be able to use Intune auto enrollment to manage anything, anywhere, anytime. Until now, managing roaming laptops with Intune was basically useless if you wanted to deploy any type of software outside of the Windows Store.
Some gotcha’s with this improvement:
you need a full deployment of SCCM (2012 R2 SP1 CU1)
If you’re using System Center Configuration Manager 2012 and have integrated it with Intune or are planning to pilot Windows 10, this is the time to update your hierarchy!
I’ve been stumped and irritated several times by the flimsy integration between SCCM and Intune, seems I wasn’t the only one. Both products have such a huge potential! With the service pack that was just released, this seems to be changing, read all about it in this blogpost by Microsoft’s Brad Anderson.
And for the techies, this article has a list of all the new features.
When you’re using both ADFS and Intune, you may want to save your users the annoying redirect after they type in their UPN when they access ADFS secured resources.
I personally like simplicity, so to build a fast and effective method for logging in to the Intune Portal (could be used for other things too) I did the following: Continue reading ADFS SmartLink for the Intune Portal→
If you hit error 0x80cf401b or 0x80cf0438 when attempting to install the Windows Intune client, disable your proxy or use a network that is not proxied.
In addition, after the Intune Client had been installed, I ran into several other errors that you might also run into. Always check for log files in c:\program files\microsoft\onlinemanagement\logs