Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
hidemaruki opened this issue Jan 22, 2025 · 0 comments
Open

Comments

@hidemaruki
Copy link

hidemaruki commented Jan 22, 2025

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.

Image Image
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant