You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not sure about this, but it appears that this package is unable to be imported because it fails some kind of validation. Here is a export of the test console.
Checking if Chocolatey repository is configured: OK
Checking if SCCM module is imported: OK
Connecting to SCCM site: Succesfully connected
Checking SCCM Folder 'TST:\Application\Chocolatey' OK
Checking Chocolatey installer: OK
Preparing icon: couldn't prepare icon, using default one:
\\SCCM01\sources\Choco\Icons\chocolatey.ico
Please update icon manually using SCCM console
Adding 7zip.install to SCCM Applications
WARNING: The maximum size of an icon is 250px X 250px.
New-CMApplication : Validation of input parameters failed. Cannot continue.
At C:\Users\TESTUSER\Documents\WindowsPowerShell\Modules\SCCMChoco.psm1:315 char:18
+ $CMapp = New-CMApplication @CMAppParams
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidArgument: (Microsoft.Confi...licationCommand:NewApplicationCommand) [New-CMApplication], InvalidOperationException
+ FullyQualifiedErrorId : ValidationFailed,Microsoft.ConfigurationManagement.Cmdlets.AppMan.Commands.NewApplicationCommand
Adding deployment type
Add-CMScriptDeploymentType : No object corresponds to the specified parameters.
At C:\Users\TESTUSER\Documents\WindowsPowerShell\Modules\SCCMChoco.psm1:341 char:23
+ ... $CMDeplType = Add-CMScriptDeploymentType @CMAppDeplParams | Out-N ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : ObjectNotFound: (Microsoft.Confi...mentTypeCommand:AddScriptDeploymentTypeCommand) [Add-CMScriptDeploymentType], ItemNotFoundExcept
ion
+ FullyQualifiedErrorId : ItemNotFound,Microsoft.ConfigurationManagement.Cmdlets.AppMan.Commands.AddScriptDeploymentTypeCommand
Adding dependencies
New-CMDeploymentTypeDependencyGroup : Cannot bind argument to parameter 'InputObject' because it is null.
At C:\Users\TESTUSER\Documents\WindowsPowerShell\Modules\SCCMChoco.psm1:346 char:91
+ ... oymentTypeDependencyGroup -GroupName "Choco" -InputObject $CMDeplType
+ ~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [New-CMDeploymentTypeDependencyGroup], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.ConfigurationManagement.Cmdlets.AppMan.Commands.NewDeploymentTypeDependenc
yGroupCommand
Add-CMDeploymentTypeDependency : Cannot bind argument to parameter 'InputObject' because it is null.
At C:\Users\TESTUSER\Documents\WindowsPowerShell\Modules\SCCMChoco.psm1:348 char:26
+ -InputObject $CMDepGroup -IsAutoInstall $true | Out-Null
+ ~~~~~~~~~~~
+ CategoryInfo : InvalidData: (:) [Add-CMDeploymentTypeDependency], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.ConfigurationManagement.Cmdlets.AppMan.Commands.AddDeploymentTypeDependenc
yCommand
Moving object
Move-CMObject : Cannot bind argument to parameter 'InputObject' because it is null.
At C:\Users\TESTUSER\Documents\WindowsPowerShell\Modules\SCCMChoco.psm1:351 char:62
+ Move-CMObject -FolderPath $CMFolderPath -InputObject $CMapp
+ ~~~~~~
+ CategoryInfo : InvalidData: (:) [Move-CMObject], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.ConfigurationManagement.Cmdlets.Common.Folder.Commands.MoveObjectCommand
Getting Device Collection: Ok
Starting Deployment
WARNING: The cmdlet 'Start-CMApplicationDeployment' has been deprecated and may be removed in a future release. The cmdlet 'New-CMApplicationDeployment' may be use
d as a replacement.
Failed
The text was updated successfully, but these errors were encountered:
Package URL - https://chocolatey.org/packages/7zip
Not sure about this, but it appears that this package is unable to be imported because it fails some kind of validation. Here is a export of the test console.
The text was updated successfully, but these errors were encountered: