{"id":1588,"date":"2022-05-13T07:00:00","date_gmt":"2022-05-13T05:00:00","guid":{"rendered":"https:\/\/scloud.work\/?p=1588"},"modified":"2023-08-17T12:54:45","modified_gmt":"2023-08-17T10:54:45","slug":"custom-detection-script-intune-win32","status":"publish","type":"post","link":"https:\/\/scloud.work\/custom-detection-script-intune-win32\/","title":{"rendered":"Custom Detection Script f\u00fcr Intune (win32 Apps)"},"content":{"rendered":"\n

There are still many applications that cannot be installed via MSI or a simple installation routine. This is where the win32 app comes into play in Intune (Microsoft Endpoint Manager). In Intune, this allows us to deal with routines and processes in a script and then check the installation with another script (custom detection script) or predefined detection rules (MSI, EXE, file or registry key).<\/p>\n\n\n\n

In the past few years, I have accumulated a few different variations of detection scripts, which I am trying to collect here.<\/p>\n\n\n\n

\n
Script Collection @GitHub<\/a><\/div>\n<\/div>\n\n\n\n

<\/p>\n\n\n\n

Use the button above to find my current collection of custom detection scripts for Intune win32 apps. It is important that you only use one of the blocks for your detection rule. If you want to know how a win32 app is structured in general and how I handle it, you can find it here (my take on win32 apps - Intune<\/a>) one of my past blog posts.<\/p>\n\n\n\n

You can currently find the following detection rules in my GitHub repository:<\/p>\n\n\n\n