tabs-not-spaces / intune-app-deploy

A fast, reliable way to package your win32 applications and deploy them to Intune from any source - including SCCM!

intune-app-deploy's Issues

AADSTS50011 Error

when I try to use the publish task I get the AADSTS50011 error
"The reply URL specified in the request does not match the reply URLs configured for the application"

extend Registry detection

How can i extend the registry detection?
registry:
registryKeyPath: "HKLM:/SOFTWARE/WOW6432Node/Microsoft/Windows/CurrentVersion/Uninstall/{AC76BA86-7AD7-1031-7B44-AC0F074E4100}"
registryDetectionType: "version"
valueName: "DisplayVersion"
detectionType: "version"
operator: "equals"
detectionValue: "20.012.20043"
check32BitRegOn64System: true

it ignores the values others than in your example.

unpack function expects subfolders in compressed folder

Due to my own small test packages all being set up the same way, the solution hasn't accounted for the fact that some packages won't be inside a root folder within the compressed file.

Should be a simple fix - just analyze the compressed media before unpacking and validate what should be there and pass off to the rest of the build workflow.

[Feature Request] YAML - Support all settings available in Graph JSON

This is a great start against automating packaging and deployment of Win32 packages but:

• A lot of settings available for Win32 in GUI and JSON is missing.
  • The ability to run scripts for detection and requerements
  • Return codes
  • Icon
  • etc.

Will take a look when I got time, If I can add this I'll share the code.

• Maybe we simply could reuse JSON from Graph after a Win32 has been manuallyc reated? As an option at least.

Support for Executable Installers

Hi,

I was reading through some of the code and I don't believe I saw support for non MSI installers. Would it be difficult implement this support? And would the YAML file have to be modified to accommodate a non MSI file?

I'm willing to try and help with this, but this project exceeds my current understanding of many of these matters.

commitFileFailed

I tried publishing the sample app to my tenant and got this error

Aborting with exception: System.Management.Automation.RuntimeException: File upload state is not success: commitFileFailed

above that I see
WARNING: The term 'C:\Program Files (x86)\Microsoft SDKs\Azure\AzCopy\AzCopy.exe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the spelling of the
name, or if a path was included, verify that the path is correct and try again.

And inn Intune > client apps : the SampleApp exists, but states "Your app is not ready yet. Check back again soon."

Is it possible I'm missing a prerequisite?

Insert app display version into Intune

In the current version the script doesn't yet add the display version to the app body. I'll create a pull request in order to add display version to app body.

Add a way for silent authentication using client secrets

I'd like to be able to start a publishing workflow without always having to enter my credentials. Therefore a client secret could be set up in the Azure app if a custom app is used. I'll send a pull request with my idea how to do that.

Unable to Publish

When i want to publish a package, the error says

"Get-MsalToken" not known as a Cmdlet.

Do i need to install anything else? Module MSonline is installed.