Intune Win32 App Troubleshooting Client Side Process Flow

0
Intune Win32 App Troubleshooting

In my previous post part 1, we the created Intune Win32 app and deployed as “available” for users. In this post, we will Deep dive intune client-side events. Intune Win32 app troubleshooting details are explained in this post.

Do you see any similarities between the Intune Win32 app troubleshooting and SCCM troubleshooting? If so, that is not coincident 🙂 Intune Win32 app code is very similar to SCCM application model. Hence in many scenarios, you will see many similarities.

[Related TopicIntune Win32 App Deployment using Modern Management]

Intune Win32 Application – Client-Side Events

I tried to explain you the Intune Win32 app deployment process flow. You need to understand the process flow to perform Intune Win32 app troubleshooting.

intune win32 application workflowUser Requested legacy apps

We initiated the application installation from the company portal. Once initiated the application will start downloading and install. Intune Win32 App Troubleshooting starts with the deployments checks or Intune troubleshooting as Anoop explained in his post.

Intune Management Extension

The Intune management extension is the client-side component to manage the MDM Win 32 application deployment. Below are the 3 Intune Management Extension Agent working folders. We will go through the purpose of these folders in detail.

[Related TopicIntune Win32 App Deployment using Modern Management]

  • Incoming
  • Staging
  • Staged

Intune Win32 App Troubleshooting

Logs – Intune Win32 App Troubleshooting

For troubleshooting Intune client-side events, you can refer below 3 logs

  • IntuneManagementExtension.log : Tracks the Intune Management extension component events
  • AgentExecuter : Track any PowerShell execution events
  • ClientHealth.log :  Track client-health related events

Intune Win32 App Troubleshooting

Detection Rules Evaluation – Intune Win32 App Troubleshooting

Detection rules are again used in SCCM application model deployments, and Intune win32 uses the similar detection rules 🙂

  • Detection rules processed
  • WMI query used to detect the application installation status.
[Win32App] ProcessDetectionRules starts
query: select * from Win32_Product where IdentifyingNumber='{AC76BA86-7AD7-1033-7B44-AC0F074E4100}' or IdentifyingNumber='AC76BA86-7AD7-1033-7B44-AC0F074E4100'
[Win32App] Checked ProductCode {AC76BA86-7AD7-1033-7B44-AC0F074E4100}, Cannot find, applicationDetected: False
[Win32App] Completed detectionManager SideCarProductCodeDetectionManager, applicationDetectedByCurrentRule: False

Intune Win32 App Troubleshooting

Check Applicability – Intune Win32 App Troubleshooting

Once app “Detection rule” evaluation complete then next step is “Check Applicability“. Checks performed against the rules we configured before.

[Win32App] applicationRequirementMetadata RequiredOSArchitecture: 2, client Is64BitOperatingSystem: True, applicability: Applicable.
[Win32App] applicationRequirementMetadata expected version: 10.0.14393, client version: 10.0.17763, applicability: Applicable.
[Win32App] applicationRequirementMetadata RequiredFreespace: 250.00, availableFreeSpaceInMB: 10,925.00 on Drive C:\, applicability: Applicable
[Win32App] applicationRequirementMetadata RequiredTotalPhysicalMemory: 250.00, totalPhysicalMemoryInMB: 1,024.00, applicability: Applicable.

Intune Win32 App Troubleshooting

After “Check applicability” completes then next stage is to process Content Download

Content Download – Intune Win32 App Troubleshooting

You can see Package Content is missing in the cache hence content started to download.

[Related TopicIntune Win32 App Deployment using Modern Management]

Content cache miss for app id 86995d21-f2ed-4e2c-a88e-1ef5f65d02e3,start downloading...

The Intune CDN URL used to download the file if you suspect any download issue due to network proxy. You can copy the URL and paste download in your browser to troubleshoot.

https://swdc01.manage.microsoft.com/5d3c257f-df2e-4885-b9b3-01dd9713d655/
081e6fbd-2594-44f6-9f5b-f3532d7652da/ad87f066-4d0e-4d05-b495-73ad17490b12.intunewin.bin

Content is download initially to folder “Incoming”

The encrypted file downloads first to folder “Incoming”. This is a temporary download folder for further processing. The extension of the file will be in bin format.

“Incoming” folder to “Staging folder”

The download file moves from “Incoming” folder to “Staging folder”. In Staging Folder, the downloaded file will be in Zip format.

C:\Program Files (x86)\Microsoft Intune Management Extension\Content\
Staging\86995d21-f2ed-4e2c-a88e-1ef5f65_1\86995d21-f2ed-4e2c-a88e-1ef5f65_1.zip

Hash verification and Decryption

Hash value checked to ensure downloaded content is consistent. Decryption starts after hash verification.
[Win32App] Starts verifying encrypted hash
[Win32App] hmac validation is pass.
[Win32App] file hash validation pass, starts decrypting
[Win32App] Decryption is done successfully.
[Win32App] CDN mode, content is decrypted.

Unzipping Stage

In this stage downloaded package in zip format gets uncompressed. Content gets extracted from “Staging” folder to “Staged” folder.

Unzipping file on session 2 from C:\Program Files (x86)\Microsoft Intune
Management Extension\Content\Staging\86995d21-f2ed-4e2c-a88e-1ef5f65d02e3_1
\86995d21-f2ed-4e2c-a88e-1ef5f65d02e3_1.zip to C:\Program Files (x86)\
Microsoft Intune Management Extension\Content\Staged\86995d21-f2ed-4e2c-a88e-1ef5f65d02e3_1

Clean up Staging content

Once unzip completes then temporary content in the staging folder removed.

Cleaning up staging content C:\Program Files (x86)\Microsoft Intune Management Extension\Content\Staging\86995d21-f2ed-4e2c-a88e-1ef5f65d02e3_1

Started application installation

This stage is the installation stage. So you can jump to this stage if you have no issues with content download etc. Intune Win32 App Troubleshooting.

  • The installation directory is set
  • Launched the Intune application installation in machine context.
  • While troubleshooting, you can make a note of the process id to track.
  • The Installation process is completed.
[Win32App] SetCurrentDirectory: C:\Program Files (x86)\Microsoft Intune Management Extension\Content\Staged\86995d21-f2ed-4e2c-a88e-1ef5f65d02e3_1
[Win32App] Launch Win32AppInstaller in machine session
[Win32App] lastWin32Error 0 after CreateProcess
[Win32App] Create installer process successfully.
[Win32App] process id = 6256
[Win32App] Installer process timeout milliseconds: 3600000.
[Win32App] Installation is done, collecting result

Detection Rules after Application Installation

Post application installation, Intune client evaluate application detection rules in the computer. In our example detection Logic is MSI product code. WMI query is used to detect the MSI product code.

[Related TopicIntune Win32 App Deployment using Modern Management]

query: select * from Win32_Product where IdentifyingNumber='{AC76BA86-7AD7-1033-7B44-AC0F074E4100}' or IdentifyingNumber='AC76BA86-7AD7-1033-7B44-AC0F074E4100'
[Win32App] Checked ProductCode {AC76BA86-7AD7-1033-7B44-AC0F074E4100}, Found it. 
sideCarProductCodeDetectionMetadata.ProductVersionOperator is 0 applicationDetected: True
[Win32App] detectionManager SideCarProductCodeDetectionManager got applicationDetectedByCurrentRule: True as system

Compliance State Message

State messages processed as shown below. These state messages are being delivered to back to Intune as part of Intune Win32 App Troubleshooting.

Intune Win32 App Troubleshooting

The compliance information sent from Windows 10 client to Intune cloud. As seen below you can see state message results posted by the client to Intune cloud service. After this, you can see the application installation status from intune console.

Successfully get the token
Add Token with length 1654 into WebRequest
Add MdmDeviceCertificate F70D046494CEF0F625365320CDC47DE8E635865B into WebRequest
SendWebRequest, client-request-id: d98c8975-3c54-4d0c-ad79-582cecb2f927, Method: PUT
Current proxy is https://fef.msuc01.manage.microsoft.com/SideCar/StatelessSideCarGatewayService/SideCarGatewaySessions('04d64f55-0c99-4cb8-bd09-d7e71dfdefcf')%3Fapi-version=1.1
Sending network request...
[Win32App] Results are successfully sent.
[Win32App] Got result with session id 04d64f55-0c99-4cb8-bd09-d7e71dfdefcf. RequestContentType: Acknowledge

After successful application installation, Toast message displayed to the user.

End User Experience of Intune Win32 App Deployment

Microsoft Intune Software Distribution is successfully completed.

Intune Win32 App Troubleshooting

Resource:

Intune Troubleshooting – https://www.anoopcnair.com/configuration-profile-settings-view/

Intune Standalone – Win32 app management (Public Preview) – https://docs.microsoft.com/en-us/intune/apps-win32-app-management

LEAVE A REPLY

Please enter your comment!
Please enter your name here

This site uses Akismet to reduce spam. Learn how your comment data is processed.