Issue with Detection Methods in SCCM Apps during Win32 App Creation

[geri-wolf]

Hi Ben,

First off, I want to express my appreciation for the tool – it's been incredibly useful and simplifies a lot of workflows. Thank you for your efforts in creating and maintaining it!

However, I've encountered an issue when creating packages for apps from SCCM that don't use a Script Detection Method. The MethodBody.xml file is successfully created and contains the correct information.

The process continues until "Getting deployment type details..." where it throws the following error:

'There was an error getting the local detection methods for deployment type 'F:\MigTool\DetectionMethods**\MethodBody.xml' from the XML.'

Subsequently, the script proceeds and fails at "Creating Win32 app JSON body" with the message:

It seems like the script is unable to handle cases where a different detection method other than script is defined. I’d appreciate any guidance or recommendations you could offer to resolve this.

Thank you in advance for your help, and again, great work on the tool!

Best regards, Gerald

[theoldsport]

I ran into this issue too, resolved by running in PowerShell 7

[cosmickatamari]

Having the same issue with PowerShell 7.4.1 and 7.5 both running as administrator.
Using Migration Tool 3.0.5

---

Creating Win32 app JSON body...

Working on application 'WinSCP 6.3.5'...
Found the .intunewin file at 'C:\Win32AppMigrationTool\Win32Apps\WinSCP 6.3.5\WinSCP - Windows Installer (_.msi file)\WinSCP-6.3.5.intunewin'
Function: Get-IntuneWinInfo was called
Creating Win32 app body for the deployment type 'WinSCP - Windows Installer (*.msi file)' for app 'WinSCP 6.3.5'
No detection method found for 'WinSCP 6.3.5'
Function: New-Win32appFramework was called
Processing JSON body for 'WinSCP 6.3.5'
InvalidOperation: C:\Users\x\Documents\PowerShell\Modules\Win32AppMigrationTool\3.0.5\Private\New-IntuneFramework.ps1:280
Line |
280 | if ($jsonObject.Contains("rules") -and $jsonObject["rules"][0 …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| You cannot call a method on a null-valued expression.
JSON body created
'{"@odata.type":"#microsoft.graph.win32LobApp","displayName":"WinSCP 6.3.5","description":"WinSCP is a free and open-source SSH File Transfer Protocol, File Transfer Protocol, WebDAV, Amazon S3, and secure copy protocol client for Microsoft Windows. Its main function is secure file transfer between a local computer and a remote server. Beyond this, WinSCP offers basic file manager and file synchronization functionality. For secure transfers, it uses the Secure Shell protocol and supports the SCP protocol in addition to SFTP.\n\nIf you have any issues with this program or installation, please contact your TSP or email .","publisher":"Martin Prikryl","displayVersion":"6.3.5","informationUrl":"https://winscp.net/eng/docs/guides#tasks","privacyInformationUrl":"https://winscp.net/eng/docs/privacy","notes":"Created by the Win32App Migration Tool","installExperience":{"@odata.type":"microsoft.graph.win32LobAppInstallExperience","runAsAccount":"System"},"largeIcon":"Base64IcondDataPresentButOmittedFromOutputDuetoSize","fileName":"IntunePackage.intunewin","setupFilePath":"WinSCP-6.3.5.msi","installCommandLine":"msiexec /i "WinSCP-6.3.5.msi" /q","uninstallCommandLine":"msiexec /x {819533C9-2894-4224-A2A8-763058A9351C} /q","minimumSupportedWindowsRelease":"Windows10_21H2","applicableArchitectures":"x64,x86","returnCodes":[{"returnCode":0,"type":"success"},{"returnCode":1707,"type":"success"},{"returnCode":3010,"type":"softReboot"},{"returnCode":1641,"type":"hardReboot"},{"returnCode":1618,"type":"retry"}],"rules":[]}'

Writing JSON body to 'C:\Win32AppMigrationTool\Win32Apps\WinSCP 6.3.5\WinSCP - Windows Installer (.msi file)\Win32appBody.json'
Successfully wrote JSON body to 'C:\Win32AppMigrationTool\Win32Apps\WinSCP 6.3.5\WinSCP - Windows Installer (.msi file)\Win32appBody.json'
We have a JSON body for the Win32 app

---

Creating Win32 app in Intune...

Building Uri for Graph request. Method: 'Post', Uri: 'https://graph.microsoft.com/beta/deviceAppManagement/mobileApps'
POST https://graph.microsoft.com/beta/deviceAppManagement/mobileApps
HTTP/2.0 400 Bad Request
Vary: Accept-Encoding
Strict-Transport-Security: max-age=31536000
request-id: fa22422a-8396-4fe9-a0b9-8a5680d0ec71
client-request-id: d7e4d952-ef70-46a5-a7dc-4cbaea22607f
x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"South Central US","Slice":"E","Ring":"5","ScaleUnit":"000","RoleInstance":"SA2PEPF00006C62"}}
Date: Mon, 03 Mar 2025 20:05:08 GMT
Content-Type: application/json

{"error":{"code":"BadRequest","message":"{\r\n "_version": 3,\r\n "Message": "The Win32LobApp must have at least one detection rule specified. - Operation ID (for customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: d7e4d952-ef70-46a5-a7dc-4cbaea22607f - Url: https://fef.msua01.manage.microsoft.com/AppLifecycle_2502/StatelessAppMetadataFEService/deviceAppManagement/mobileApps?api-version=5024-12-04\",\r\n "CustomApiErrorPhrase": "",\r\n "RetryAfter": null,\r\n "ErrorSourceService": "",\r\n "HttpHeaders": "{}"\r\n}","innerError":{"date":"2025-03-03T20:05:08","request-id":"fa22422a-8396-4fe9-a0b9-8a5680d0ec71","client-request-id":""}}}
Invoke-MgGraphRequest: C:\Users\x\Documents\PowerShell\Modules\Win32AppMigrationTool\3.0.5\Private\Invoke-MgGraphRequestCustom.ps1:78
Line |
78 | … aphResult = Invoke-MgGraphRequest -Uri $GraphUri -Method $Method -Bod …
| ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| POST https://graph.microsoft.com/beta/deviceAppManagement/mobileApps HTTP/2.0 400 Bad Request Vary:
| Accept-Encoding Strict-Transport-Security: max-age=31536000 request-id: fa22422a-8396-4fe9-a0b9-8a5680d0ec71
| client-request-id: d7e4d952-ef70-46a5-a7dc-4cbaea22607f x-ms-ags-diagnostic: {"ServerInfo":{"DataCenter":"South
| Central US","Slice":"E","Ring":"5","ScaleUnit":"000","RoleInstance":"SA2PEPF00006C62"}} Date: Mon, 03 Mar 2025
| 20:05:08 GMT Content-Type: application/json {"error":{"code":"BadRequest","message":"{\r\n "_version":
| 3,\r\n "Message": "The Win32LobApp must have at least one detection rule specified. - Operation ID (for
| customer support): 00000000-0000-0000-0000-000000000000 - Activity ID: -
| Url:
| https://fef.msua01.manage.microsoft.com/AppLifecycle_2502/StatelessAppMetadataFEService/deviceAppManagement/mobileApps?api-version=5024-12-04\",\r\n "CustomApiErrorPhrase": "",\r\n "RetryAfter": null,\r\n "ErrorSourceService": "",\r\n "HttpHeaders": "{}"\r\n}","innerError":{"date":"2025-03-03T20:05:08","request-id":"fa22422a-8396-4fe9-a0b9-8a5680d0ec71","client-request-id":""}}}

[byteben]

are you able to share MethodBody xml and the JSON here?

[cosmickatamari]

are you able to share MethodBody xml and the JSON here?

Here is the JSON file
Win32appBody.json

The MethodBody XML in "C:\Win32AppMigrationTool\DetectionMethods" does not generate.

[QMUL-JayHay]

@cosmickatamari You said yours was an MSI detection method? I've noticed issues here as well. Planning to take a look in the next week or so. My first guess might be handling of curly brackets, but we'll see.

[QMUL-JayHay]

Hi, @byteben - Just wondering if you picked up Microst adding Convert-CMApplication cmdlet. It saves adding a lot of the XML handling and might help with simplifying detection method logic. Are you accepting merge requests etc.? Happy to contribute (it'll be my first contribution to an open-source project :D )

Cheers,
J

[crujonescheated]

@QMUL-JayHay Were you able to figure it out? I'm having this same issue and I've been unsuccessfully throwing everything at it.

[DanielZ0815]

I also had an issue that the detection method was not properly read when there is just one registry detection method.
I fixed it myself by modifying Get-DeploymentTypeInfo.ps1:

Changed
$localDetectionMethods = Get-DetectionMethod -LogId $LogId -XMLObject $detectionTypeMethodBody
to
$localDetectionMethods = @()
$localDetectionMethods += Get-DetectionMethod -LogId $LogId -XMLObject $detectionTypeMethodBody

With that change, it is ensured that the return of the Get-DetectionMethod function is added to a list and the count method is properly working. Obviously lists returned from the Get-DetectionMethod function are somehow automatically converted into single objects if there is just one member...
Hope this helps

[QMUL-JayHay]

Sorry for the delay. One consideration is that detection methods in Intune suffer from a dearth of operator options in InTune compared to SCCM. e.g. String Comparison only has equal / not equal, not startswith, endswith etc. I'm finding that changing my detection methods is resolving the issue. It will be a tricky problem to automate translation from all possible SCCM detection methods in the tool, as it will not always capture the intention of the original in InTune until they make it more expressive. Not sure why MS have missed this out. Not a great situation, as we have 00's of apps to migrate (although many will migrate just fine, to be fair).

[cjr145]

Same experience here. There's value here for sure - thanks for this app! If my source application in Intune has a detection script, this process works well. However, if it has an MSI product code only, the detection .JSON is not created. If I add additional detection rules based on presence of a file to my MSI product code detection rule, the JSON is created but fails with an int64 error (noted elsewhere in the bugs reported here) . I tried to trim down the JSON to only an MSI rule manually, then run the script again but it keeps generating the bad JSON. It seems it's not supported to run the Intune app creation only.