[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.
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.
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?
chocolateyInstall.ps1 script is Powershell, so anything you can do in PowerShell or can call from PowerShell you can do in a Chocolatey package.
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.
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).
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 sayssccm 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"?
@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.
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: ORDChocoThe 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'
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.
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.
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.
setup.exe /s /v/qnfrom the chocolatey package folder on the target server, it works. But
cinst bigfix -s ordchocostill 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)
