System Information and Self Service Tool

In this blog I would like to introduce you to my new System Information Tool. The System Information Tool is a software that displays various system information, such as the serial number, IP address, username and logged-in user, and many more. It also provides functions for troubleshooting and analysing problems with Intune Management and Intune Management Extension. In addition, custom scripts for self-service support can be added and provided to them user. The tool is thus a useful resource for users who need quick access to system information and assistance in troubleshooting problems.

Where can I find the System Information Tool?

You can find the tool and all sources in my GitHub repository.

How can I install the tool?

In this repository there is a “Install-SystemInformationTool.ps1” script to install the tool on the device. Once the installation is done you can find the tool in the Start menu. You can use this also to package the application as Win32 app to distribute via Intune. If you don’t want to install the tool you can also use the “Start-SystemInformationTool.ps1″to execute the application.

Introduction of the System Information Tool

Which Features has the System Information Tool?

Informarion View

This view provides you an overview of different system attributes like Hostname, IPs, SerialNr., Ram and many more. You can also include here more informations for you needs.

Intune and support actions

This feature provides you different actions to troubleshoot and fix the Intune management extension.

Trigger device action

You can include your custom script and self service actions on an realy easy way to this tool.

To add self service actions you have to place the Powershell script in the script folder and add to the “_actions.json” the action name and the script name.

5 thoughts on “System Information and Self Service Tool

  1. Hallo Jannik,
    Thanks for this amazing script.
    I want package the application as Win32 app to distribute via Intune. Which install behavior should I take (System or User). Which Detection Rule would be the best? Is it possible to change the Install Folder to ProgramData?
    Bernhard

    Like

    • Hey Bernhard, you should use user as install behavior.
      You can also change the path to ProgramData.

      It is planned that I publish a Youtube Video how to create a win32 app latest mid of next week.
      Here I can use this as example how to create a intunewin file from this app.

      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