Introduction of the Intune Device Troubleshooter


If you follow my blog, you know that there are two things I really like: helping people with their problems, and automating or simplifying processes. In this blog, I want to introduce you to my new tool, the Intune Device Troubleshooter. This is a PowerShell UI application that will help you to check the status of your devices, as well as support you to trigger remediation scripts to fix issues add-hock on single devices. It also provides you intelligent recommendations what you should check at a single device to determine and possible issue. So let’s get started and look at the features of the tool.

The features of the Intune Device Troubleshooter

Device Overview

The Intune Device Troubleshooter provides you with a great overview of a lot of data around a single device that you wouldn’t be able to get all of them through the MEM interface. The data is prepared and gives you a very clear view of the status of the device. If you double click on the IDs of the devices, it will open up the MEM console or Azure AD directly, where you can make changes as well.

Trigger Action

You can perform actions directly through the tool, such as syncing the device or restarting it.

Recommendations

All the data that is accessible for thisdevice is intelligently analysed and suggestions are made to quickly see what might be wrong with the device so that you can check or fix it. This speeds up your troubleshooting process and prevents you from missing anything. If you have any further ideas for checks, please let me know so that I can include them.

Remediation Scrips trigger

This is a feature that can really help you with the solving of errors. In the MEM Console, you can only assign remediation scripts to a group but you can’t trigger it on an individual device. That’s exactly what I did with the Intune Troubleshooter. If you want to run an action on a single device, you can trigger the script and I’ll create a group in the background (if it doesn’t already exist) with the name “MDM-Remediation-Trigger-{ScriptName}” which you can of course change, and add the device to it. So the remediation action will be performed on the device quite timely.

How can you get the Tool

  • Make sure that the Powershell SDK is installed on your system. If not install the SKD using the following command:
Install-Module Microsoft.Graph -Scope CurrentUser

Note

If you get the following error on your system when executing the Intune Device Troubleshooter:

You have to unblock the dll’s. Navigate for this to the libaries folder and click Unblock in the properties on each dll’s. 

It may be that you need to restart your PowerShell session to get the error message gone

Conclusion

I hope you like the Intune Device Troubleshooter and I was able to simplify your troubleshooting workflow with it. Of course, I’m very happy about your feedback and your ideas for further development. I’m also happy for anyone who shares the tool with others on Twitter or other networks. Have fun with it 🙂

Stay healthy, Cheers
Jannik

7 thoughts on “Introduction of the Intune Device Troubleshooter

  1. Hello Jannik, how are you today?
    Your post is amazing! Congrats!
    But i have issue… I’m check the pre-requisite on my pc and i have all…
    The issue is after running powershell script and after sig-in on my environment a new window opens and cannot connect on any device =(
    You can help me?
    Thansk!!!

    Like

    • Hi Jannik
      I do before it connects to the tenant and after. Very lengthy errors.

      The property ‘source’ cannot be found on this object. Verify that the property exists and can be set.
      At C:\Temp\Scripts\Intune-Device-Troubleshooter-main\modules\uiHandler.psm1:297 char:5
      + $WPFImgHome.source = Get-DecodeBase64Image -ImageBase64 $iconHome
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo : InvalidOperation: (:) [], RuntimeException
      + FullyQualifiedErrorId : PropertyNotFound

      The property ‘source’ cannot be found on this object. Verify that the property exists and can be set.
      At C:\Temp\Scripts\Intune-Device-Troubleshooter-main\modules\uiHandler.psm1:298 char:5
      + $WPFImgButtonLogIn.source = Get-DecodeBase64Image -ImageBase64 $i …
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo : InvalidOperation: (:) [], RuntimeException
      + FullyQualifiedErrorId : PropertyNotFound

      some after it connects

      The property ‘Width’ cannot be found on this object. Verify that the property exists and can be set.
      At C:\Temp\Scripts\Intune-Device-Troubleshooter-main\modules\utility.psm1:162 char:3
      + $WPFImgButtonLogIn.Width=”35″
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo : InvalidOperation: (:) [], RuntimeException
      + FullyQualifiedErrorId : PropertyNotFound

      The property ‘Height’ cannot be found on this object. Verify that the property exists and can be set.
      At C:\Temp\Scripts\Intune-Device-Troubleshooter-main\modules\utility.psm1:163 char:3
      + $WPFImgButtonLogIn.Height=”35″
      + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
      + CategoryInfo : InvalidOperation: (:) [], RuntimeException
      + FullyQualifiedErrorId : PropertyNotFound

      Like

  2. PS C:\Users\ed.hixon\Downloads\DT> .\Start-DeviceTroubleshooter.ps1
    The property ‘source’ cannot be found on this object. Verify that the property exists and can be set.
    At C:\Users\ed.hixon\Downloads\DT\modules\uiHandler.psm1:297 char:5
    + $WPFImgHome.source = Get-DecodeBase64Image -ImageBase64 $iconHome
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertyNotFound

    The property ‘source’ cannot be found on this object. Verify that the property exists and can be set.
    At C:\Users\ed.hixon\Downloads\DT\modules\uiHandler.psm1:298 char:5
    + $WPFImgButtonLogIn.source = Get-DecodeBase64Image -ImageBase64 $i …
    + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertyNotFound

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s