The Package Name is Fixed as "IntunePackage.intunewin" in IntuneWin32App

[hidemaruki]

Hi,

Background

I'm considering registering Win32 applications to Intune using the IntuneWin32App available at this URL.
I have confirmed that I can register Win32 applications and upload Intune package files, but the following issue has occurred.

Issue

After registering a Win32 application, when viewing the application's properties in the Intune management center, the "App Package File" is fixed as "IntunePackage.intunewin" instead of the uploaded Intune package file name (or the name is overwritten).

Note: When registering a Win32 application manually using the Intune management center, the Intune package file name is the actual file name.

Request

I would like to request a modification so that the name of the Intune package file uploaded when registering a Win32 application using the "Add-IntuneWin32App" function matches the actual file name, if you can.

Investigation Results (1)

I'm using the "Add-IntuneWin32App" function to register applications to Intune. We have reviewed the Add-IntuneWin32App.ps1 file and identified the following sections that may be relevant to this issue.

• Line 294: $IntuneWinXMLMetaData = Get-IntuneWin32AppMetaData -FilePath $FilePath -ErrorAction Stop

  • This line reads the information of the Intune package file. When executing the "Get-IntuneWin32AppMetaData" function manually, I confirmed that the value of $IntuneWinXMLMetaData.ApplicationInfo.FileName is always "IntunePackage.intunewin".

• Line 445: "FileName" = $IntuneWinXMLMetaData.ApplicationInfo.FileName

  • This line appears to specify the Intune package file name for the registered application. As mentioned above, $IntuneWinXMLMetaData.ApplicationInfo.FileName is "IntunePackage.intunewin".

• Lines 545-553:

  $Win32AppFileBody = [ordered]@{
      "@odata.type" = "#microsoft.graph.mobileAppContentFile"
      #"name" = $IntuneWinXMLMetaData.ApplicationInfo.FileName
      "name" = [System.IO.Path]::GetFileName($FilePath)
      "size" = [int64]$IntuneWinXMLMetaData.ApplicationInfo.UnencryptedContentSize
      "sizeEncrypted" = (Get-Item -Path $IntuneWinFilePath).Length
      "manifest" = $null
      "isDependency" = $false
  }

  • This section appears to be just before the file upload process. It does not seem to change the name of the Intune package file (the actual file name is specified).

Investigation Results (2)

After registering the application using the "Add-IntuneWin32App" function, I tried re-uploading the Intune package file using the "Update-IntuneWin32AppPackageFile" function, but there was no change.

Screen Image

Below is the package file name after registering the Win32 application, as seen in the Intune management center when viewing the application's overview and editing screen.

[hidemaruki]

After checking the process of uploading a Win32 app, I confirmed that even when performed from the Intune admin center, the file name is temporarily set to "IntunePackage.intunewin".

However, since the PATCH method is used to reconfigure the file name and other settings, I confirmed that it is possible to change only the file name of the Win32 app by creating a JSON that rewrites only the file name and executing it.

Specifically, the steps are as follows:

Can the original module be modified based on the following steps?

[Steps]
#1 Run the following command to grant read and write permissions to the application and connect to the Graph API.

Connect-MgGraph -Scopes "DeviceManagementApps.ReadWrite.All"

#2 Run the following command to set the file name in the JSON request. Note: The sample uses "test.intunewin", so please change it to an appropriate name.

$requestBody = @"
{"@odata.type" : "#microsoft.graph.win32LobApp","fileName" : "test.intunewin"}
"@

#3 Run the following command to specify the application ID of the target Win32 app and change it to the file name set in step 2.

$url = "/beta/deviceAppManagement/mobileApps/"
Invoke-MgGraphRequest -Method PATCH -Uri $url -ContentType "application/json" -OutputType PSObject -Body $requestBody

[obuolinis]

I have also analyzed this specific issue and tested some things, you can find the thread HERE

I tested your proposed solution - while my Graph request completes successfully the intunewin name doesn't get changed. Are you sure it's possible to rename an already uploaded file? Or perhaps you could clarify at what stage the request has to be triggered?

[hidemaruki]

Thank you for your comment. In my environment, I have confirmed that by using the source code below with the parts in red changed, I can rename the intunwin file later.

$requestBody = @"
{"@odata.type":"#microsoft.graph.win32LobApp","fileName":"ExampleApp.intunewin"}
"@

$Geturl = "beta/deviceAppManagement/mobileApps/?`$filter=(isof('Microsoft.graph.win32LobApp'))"
#(Invoke-MgGraphRequest -Method GET -Uri $url -OutputType PSObject).Value | Select id,displayname,filename
$Win32App = (Invoke-MgGraphRequest -Method GET -Uri $Geturl -OutputType PSObject).Value | Where-Object { $_.displayname -eq 'ExampleApp' }
$url = "beta/deviceAppManagement/mobileApps/" + $Win32App.id

Invoke-MgGraphRequest -Method PATCH -Uri $url -ContentType "application/json" -OutputType PSObject -Body $requestBody

[obuolinis]

I've just found time to give it a proper test and bloody hell, it worked indeed! Thumbs up @hidemaruki

With that in mind, to integrate it in Add-IntuneWin32App.ps1 you need to add one more PATCH request just after this line here:

IntuneWin32App/Public/Add-IntuneWin32App.ps1

Line 633 in 21b0c09

$Win32AppFileCommitBodyRequest = Invoke-IntuneGraphRequest -APIVersion "Beta" -Resource "mobileApps/$($Win32MobileAppRequest.id)" -Method "PATCH" -Body ($Win32AppFileCommitBody | ConvertTo-Json)

The code could look like this:

$Win32AppFileRenameBody = [ordered]@{
    "@odata.type" = "#microsoft.graph.win32LobApp"
    "fileName" = [System.IO.Path]::GetFileName($FilePath)
}
$Win32AppFileRenameBodyRequest = Invoke-IntuneGraphRequest -APIVersion "Beta" -Resource "mobileApps/$($Win32MobileAppRequest.id)" -Method "PATCH" -Body ($Win32AppFileRenameBody | ConvertTo-Json)

Or, if doing it properly:

Set up a new variable right after this line

IntuneWin32App/Public/Add-IntuneWin32App.ps1

Line 541 in 21b0c09

$IntuneWinFilePath = Expand-IntuneWin32AppCompressedFile -FilePath $FilePath -FileName $IntuneWinXMLMetaData.ApplicationInfo.FileName -FolderName "Expand"

$IntuneWinFileName = [System.IO.Path]::GetFileName($FilePath)

Then the PATCH request block:

# Rename intunewin file to match the original file name
Write-Verbose -Message "Renaming intunewin file to: $IntuneWinFileName"
$Win32AppFileRenameBody = [ordered]@{
    "@odata.type" = "#microsoft.graph.win32LobApp"
    "fileName"    = $IntuneWinFileName
}
$Win32AppFileRenameBodyRequest = Invoke-IntuneGraphRequest -APIVersion "Beta" -Resource "mobileApps/$($Win32MobileAppRequest.id)" -Method "PATCH" -Body ($Win32AppFileRenameBody | ConvertTo-Json)