Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
TheCakeIsNaOH
@TheCakeIsNaOH
Currently planned for choco version 1.x
Frank Kintrup
@kintrupf

[DESKTOP] Connecting to remote server DESKTOP failed with the following error message : WinRM cannot process the request. The following error with errorcode 0x8009030e occurred while using Negotiate authentication: A specified logon session does not exist. It may already have been terminated. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting

Can anyone help with this error message while upgrading or installing a package? It crept up some weeks ago but does not occur on every upgrade or install. Nor does it prevent the upgrade or install, it's just an extremely annoying red text output during the upgrade/install process. I tried to google the error number and such, but any solution found there did not help.

Tamar Christina
@Mistuke
Hi, Is there a way to check out why automated validation failed? All the things It said (urls etc) I have manually checked and they seem correct.. referring to https://chocolatey.org/packages/cabal/3.4.0.0-rc5
Kim J. Nordmo
@AdmiringWorm
@Mistuke it may be due to missing ciphers on the server that checks the urls. I know missing ciphers is something that @gep13 has on his TODO list to check.
Tamar Christina
@Mistuke
@AdmiringWorm ah ok, that explains why multiple of my packages are failing :) Cheers, I'll try again later in the week
Burt Harris
@BurtHarris
Cypress Semiconductor has an IDE for developing solutions with their PSOC system on a chip devices called PSocCretaor. Its available for free on the web, but they require you to register and sign-in to download the .exe based installer. For example: https://www.cypress.com/file/514131/download. Can I setup a chocolatey package that will send someone to that download sight so they can register or login to download?
Chris Hall
@situssoft
Hi, can anyone tell me if there us a choco command to pin an application to the start menu in W10?
TheCakeIsNaOH
@TheCakeIsNaOH
@BurtHarris I belive it would be techincally possible, however packages on the chocolatey.org repository should be able to install without human interaction, so I don't think it would be allowed. And if you are wanting to upload it to an internal private repository, you should be able to include the exe inside the package, so there is no need to download the exe during install.
TheCakeIsNaOH
@TheCakeIsNaOH
@situssoft Are you talking about actually pinning or just adding to the start menu in general? For adding to the start menu in general, use Install-ChocolateyShortcut. If you are talking about pinning specifically, then no there is not a chocolatey helper to do that. You would have to find/write the powershell to do that.
Burt Harris
@BurtHarris
@TheCakeIsNaOH Thanks, I understand.
Stu
@kewalaka
hey folks - as an experiment I've created a simple chocolatey server using docker. There was an existing version on Hub but it was not setting permissions for package uploads. Mine comes with Pester tests. More of a learning exercise, but posting in case it is useful - https://github.com/kewalaka/chocolatey-server.
It's Windows & .Net 4, so the container is umm, somewhat a 'heavyweight' :-D https://hub.docker.com/r/kewalaka/chocolatey-server
Gary Ewan Park
@gep13
@kewalaka thanks for sharing!
Kevin Weinrich
@kwein1

Newbie to Chocolatey here. Trying to learn how to use it with DSC.
I'm trying to create a custom package that involves a setup.exe and either a PowerShell script or an import of a registry key to customize the installed software for our site. I have a setup.cmd file that does all that.

I see how to create a package for a .EXE or a .MSI. How do I create a single package for a .CMD file, or how do I combine the setup.exe and regkey/.PS1 invocation into a single Chocolatey package?

TheCakeIsNaOH
@TheCakeIsNaOH
You could run the .cmd from the chocolateyInstall.ps1 script. Alternatively, you could use the Install-ChocolateyInstallPackage helper, then after that call the regkey and .ps1 files.
The chocolateyInstall.ps1 script is Powershell, so anything you can do in PowerShell or can call from PowerShell you can do in a Chocolatey package.
Kevin Weinrich
@kwein1
Hmmm, that sounds doable. I should be able to handle the PowerShell, let me see if I can convince Chocolatey to create the package and refer to all the pieces properly (my very first C. package).
TheCakeIsNaOH
@TheCakeIsNaOH
Not exactly the same thing you want to do, but for example, I have a package where in the chocolateyInstall.ps1 script I extract a zip file, then get the certificate from a driver, check if it is installed, install the certificate if needed, install the correct driver, then remove the extra files.
Kevin Weinrich
@kwein1
Cool. The concept is similar. I'll check out your github. Thanks!
TheCakeIsNaOH
@TheCakeIsNaOH
Also, one small thing on the examples, there are two helpers that are similar: Install-ChocolateyPackage used for download and install of an exe/msi, and Install-ChocolateyInstallPackage which is used for install of an exe/msi that is already downloaded (either included inside the package, or downloaded previously in the script, or available on a network drive).
Kevin Weinrich
@kwein1
I thought my eyes were playing tricks on me the first time I saw "Install-ChocolateyInstallPackage" ;-)
And that's the one I want to use, so good to know.
Paul Broadwith
@pauby
@TheCakeIsNaOH++
The chocolatiest bot this side of the Mississippi
@choco-bot
thecakeisnaoh is on the rise! (Karma: 3)
RocketMan
@RocketM96875137_twitter
Are you supposed to include "choco install" with every program when installing multiple programs? Thanks
TheCakeIsNaOH
@TheCakeIsNaOH
Not required, you can specify multiple in one command: choco install packageA packageB packageC etc
RocketMan
@RocketM96875137_twitter
Thanks
Kevin Weinrich
@kwein1

I now have a custom choco package, 'sccm' that appears to work (I need to test it on the remote server to ensure it works). I have added it to a local, Windows file share choco repository/source named 'ORDChoco'. I think I have those two steps right. This is all on server "A", the local server:
```choco list sccm -verbose -source ORDChoco
Chocolatey v0.10.15
sccm 0.1.0.20210106
Title: | Published: 1/8/2021
Number of Downloads: n/a | Downloads for this version: n/a
Package url
Chocolatey Package Source: n/a
Tags:
Software Site: n/a
Software License: n/a
Description: SCCM client install.

1 packages found.```

For my next two tricks, I need to get DSC to send the package to the remote server, "B". When I specify ChocolateyOptions, Source: ORDChoco, it appears to understand my DSC code, because my DSC push says
sccm not installed. The package was not found with the source(s) listed. Source(s): 'ORDChoco'

But then it fails to find the package (and maybe the Source?). I'm guessing that failure is because the Source is on server A. If that's the case, how do I use DSC to tell server B "Use the \A\store share that server A calls ORDChoco to pull the sccm package from A to B, then install it on B"?

(Sorry for the crappy formatting. I need to figure out the markup rules for Gitter)
rohitrg
@rohitrg
Hi,
I need help in creating packages to install on computers with no internet connectivity. This needs to be an offline installation package.
Paul Broadwith
@pauby

@kwein1 Use the cChocoSource resource of cChoco:

configuration ChocoSource {
    Import-DscResource -ModuleName cChoco

    Node 'localhost' {
        cChocoSource ORDChoco {
            Source = "\\serverA\fileshare"
            Ensure = 'Present'
        }
    }
}

You may need credentials and if that is the case then pass them in under the Ensure option after creating the object.

@rohitrg You will need to add the installer (or payload if it's not an installer) to the package itself. It's generally added either in the tools folder, or if it's many files, by creating a separate folder under the tools folder. See my Gitter package as an example (note you won't find the actual installer on that GitHub site as it's embedded in the package at the creation time automatically - however the code is in there that works with a local installer).
Tunisiano18
@tunisiano187
Hello everyone, Does anyone as a solution to pin package version with the chocolatey's module for puppet in a manifest?
Thank you
Kevin Weinrich
@kwein1

I now have choco working via DSC for packages that are stored in Chocolatey's public repo. And I have the ORDChoco Source set up via DSC. When I log in to the remote server, I can do this:

 choco list -source ORDChoco
Chocolatey v0.10.15
sccm 0.1.0.20210106
1 packages found.

That was created by the following DSCWorkshop-style configuration:

ChocolateyPackages:
  Software:
    Ensure: Present
  Sources:
    Name: ORDChoco
    Ensure: Present
    Source: '\\A\chiz$\software installs and downloads\ChocolateyPackages'
  Features:
    Name: useFipsCompliantChecksums
    Ensure: Present
  Packages:
    - Name: sccm
      Ensure: Present
      ChocolateyOptions:
        Source: ORDChoco

The one thing I still can't do is actually install my custom sccm package from ORDChoco. Am I getting hit with permissions, since I'm doing a DSC push from server A to B, and ORDChoco is on A? Is it because the account (SYSTEM, I guess?) that DSC is using can't access the share on A from B?

Here's the peccant part of my DSC push:

VERBOSE: [B]:                            [[ChocolateyPackage]Chocolatey_sccm::[ChocolateyPackages]ChocolateyPackages] Installing the
following packages:
VERBOSE: [B]:                            [[ChocolateyPackage]Chocolatey_sccm::[ChocolateyPackages]ChocolateyPackages] sccm
VERBOSE: [B]:                            [[ChocolateyPackage]Chocolatey_sccm::[ChocolateyPackages]ChocolateyPackages] By installing you
accept licenses for the packages.
VERBOSE: [B]:                            [[ChocolateyPackage]Chocolatey_sccm::[ChocolateyPackages]ChocolateyPackages] sccm not installed.
 The package was not found with the source(s) listed.
VERBOSE: [B]:                            [[ChocolateyPackage]Chocolatey_sccm::[ChocolateyPackages]ChocolateyPackages]  Source(s):
'\\A\chiz$\software installs and downloads\ChocolateyPackages'
Paul Broadwith
@pauby
@tunisiano187 I'd use an exec for that and maybe an unless or an onlyif if it's not been pinned (run choco pin and parse it) to be idempotent.
1 reply

The one thing I still can't do is actually install my custom sccm package from ORDChoco. Am I getting hit with permissions, since I'm doing a DSC push from server A to B, and ORDChoco is on A? Is it because the account (SYSTEM, I guess?) that DSC is using can't access the share on A from B?

You'll need to make sure B$ (dollar is important) has access to the share.

Kevin Weinrich
@kwein1
@pauby I don't know what B$ is - do you mean the server name followed by a $? As a userid?
Is there a better way to do this - to push the install file from A to B (via DSC somehow), and then install it locally on B via DSC?
Paul Broadwith
@pauby

@pauby I don't know what B$ is - do you mean the server name followed by a $? As a userid?

Yeah, the server name.

Is there a better way to do this - to push the install file from A to B (via DSC somehow), and then install it locally on B via DSC?

You could do it that way, but then you may have to update all of your packages that are using it.

If you want to use file shares with authorisation this is the way it needs to be done unfortunately. This is why we recommend you use a repository manager.

Kevin Weinrich
@kwein1
I was able to get the package install to work after changing the permissions on the Source share, as @pauby indicated - add B$ to NTFS permissions. Works great!
Kevin Weinrich
@kwein1

Now I'm working on my 2nd custom package. This one fails, which is probably due to something I'm not doing right in constructing the package. But when I look for details on precisely WHAT went wrong with the installation, I just get "See the log for details...". The log just says

2021-01-15 15:04:12,065 1316 [ERROR] - ERROR: The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: The operation completed successfully.
2021-01-15 15:04:12,065 1316 [DEBUG] - Built-in PowerShell host called with ['[System.Threading.Thread]::CurrentThread.CurrentCulture = '';[System.Threading.Thread]::CurrentThread.CurrentUICulture = ''; & import-module -name 'C:\ProgramData\chocolatey\helpers\chocolateyInstaller.psm1'; & 'C:\ProgramData\chocolatey\helpers\chocolateyScriptRunner.ps1' -packageScript 'C:\ProgramData\chocolatey\lib\bigfix\tools\chocolateyinstall.ps1' -installArguments '' -packageParameters '''] exited with '-1'.
2021-01-15 15:04:12,065 1316 [DEBUG] - Calling command ['"C:\Windows\System32\shutdown.exe" /a']
2021-01-15 15:04:12,174 1316 [DEBUG] - Command ['"C:\Windows\System32\shutdown.exe" /a'] exited with '1116'

I just don't see what it didn't like. Is there any way to get further debugging info about why it blows up? Or how can I manually walk through the package installation?

Note: In my chocolateyinstall.ps1, I do a "reg import ..." command which IS working. So I'm pretty sure it's the "Install-ChocolateyInstallPackage ..." command that's failing.

Kevin Weinrich
@kwein1
It appears that if I manually do:
setup.exe /s /v/qn
from the chocolatey package folder on the target server, it works. But
cinst bigfix -s ordchoco
still doesn't. How can I see what command line choco is actually using to try to run the setup.exe? (As I understand, it's using my chocolateyinstall.ps1 to call Install-ChocolateyInstallPackage, and the magic happens inside there)
Sathish
@satheeshsoft
Previously created chocolatey package working fine. The same code i used in new package but some changes in install file name and descriptions. The new package created with cpack command but not installing it, install failed. https://github.com/satheeshsoft/Soft-Cleaner-CY can you say what is missing here?
Paul Broadwith
@pauby
@kwein1 Do you get any more info when adding -vd to the choco command line?
5 replies
@satheeshsoft Have you looked at the gist? The error is on this line.
VoomDev
@VoomDev
Is it possible to install choco on mac?
daebenji
@daebenji
would you please stop spamming!