chocolatey-community/chocolatey-packages

(totalcommander) No Start Menu entries when deploying via Intune

strausmann opened this issue · 4 comments

strausmann commented

Chocolatey Version

2.2.2

Chocolatey License

Business

Package Version

11.2.0

Current Behaviour

After the installation there is no start menu entry, neither globally nor for the user himself.

Expected Behaviour

After a successful installation, a start menu entry for Total Commander must be found.

Steps To Reproduce

We install Total Commander for a few users via Microsoft Intune. We use IntuneWin for this.

The PowerShell script ChocoInstall.ps1 can be found in the Gist linked under Chocolatey Log. This is integrated into the IntuneWin file and serves us in this form as a standard package when we run a Chocolatey installation via Intune.

In the Gist you will also find the ChocoInstall.log, which shows a complete output of the ChocoInstall.ps1.

Environment

- Operating System: Microsoft Windows NT 10.0.22631.0
- PowerShell Version: 7.4.1
- Shell: PowerShell 7

Chocolatey Log

https://gist.github.com/strausmann/e792262af9dc434aef2664405251ad41

Anything else?

No response

pauby commented

This isn't an issue with the package.

I've just installed Totalcommander here on a Windows Server 2019 virtual machine I was working on and it created the Start Menu entries as expected.

image

Not all software can be deployed via Intune (with or without Chocolatey CLI). That's a limitation of the platform.

As far as the package, I can't see anything for us to do here.

pauby commented

As you are a licensed customer, my suggestion is you reach out to Chocolatey Support as they may be able to help you with the deployment via Intune. To do that, run choco support from the command line.

Note that packages on the Chocolatey Community Repository, including the ones in this repository, are not supported.

github-actions commented

Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue will be closed in 14 days if it continues to be inactive.

Please do not add a comment to circumvent automatic closure unless you plan to help move it forward.
Doing this may lead to the issue being closed immediately instead.

github-actions commented

Dear contributor,

As this issue seems to have been inactive for quite some time now, I've automatically closed it.
If you feel this is a valid issue, please feel free to re-open the issue if/when a pull request
has been added.
Thank you for your contribution.