Open claudiaMCR opened 4 years ago
i think you shouldn´t use the BareMetal parameter. For normal installations i use this: -URI "http://FQND/ConfigMgrWebService/ConfigMgr.asmx" -SecretKey "verysecretkey" -Filter "Drivers"
I think you can use BareMetal parameter only if you use AdminService and Version 4 of MDM
Hello,
if i try this via powershell on some installed client i get this result:
PS C:\temp> .\NEU_Invoke-CMApplyDriverPackage.ps1 -URI "http://xxxx/ConfigMgrWebService/ConfigMgr.asmx" -SecretKey "xxxx" -Filter "Drivers" WARNUNG: Unable to construct Microsoft.SMS.TSEnvironment object Es ist nicht möglich, eine Methode für einen Ausdruck aufzurufen, der den NULL hat. In C:\temp\NEU_Invoke-CMApplyDriverPackage.ps1:257 Zeichen:5
+ CategoryInfo : InvalidOperation: (:) [], RuntimeException
+ FullyQualifiedErrorId : InvokeMethodOnNull
Join-Path : Das Argument kann nicht an den Parameter "Path" gebunden werden, da es NULL ist. In C:\temp\NEU_Invoke-CMApplyDriverPackage.ps1:279 Zeichen:34
+ CategoryInfo : InvalidData: (:) [Join-Path], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
WARNUNG: Unable to append log entry to ApplyDriverPackage.log file. Error message at line 304: Das Argument kann nicht an den Parameter "FilePath" geb unden werden, da es NULL ist. Join-Path : Das Argument kann nicht an den Parameter "Path" gebunden werden, da es NULL ist. In C:\temp\NEU_Invoke-CMApplyDriverPackage.ps1:279 Zeichen:34
+ CategoryInfo : InvalidData: (:) [Join-Path], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
WARNUNG: Unable to append log entry to ApplyDriverPackage.log file. Error message at line 304: Das Argument kann nicht an den Parameter "FilePath" geb unden werden, da es NULL ist. Join-Path : Das Argument kann nicht an den Parameter "Path" gebunden werden, da es NULL ist. In C:\temp\NEU_Invoke-CMApplyDriverPackage.ps1:279 Zeichen:34
+ CategoryInfo : InvalidData: (:) [Join-Path], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.JoinPathCommand
WARNUNG: Unable to append log entry to ApplyDriverPackage.log file. Error message at line 304: Das Argument kann nicht an den Parameter "FilePath" geb unden werden, da es NULL ist. Write-CMLogEntry : Das Argument kann nicht an den Parameter "Path" gebunden werden, da es NULL ist. In C:\temp\NEU_Invoke-CMApplyDriverPackage.ps1:1822 Zeichen:3
+ CategoryInfo : InvalidData: (:) [Write-CMLogEntry], ParameterBindingValidationException
+ FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Write-CMLogEntry
or these error: PS C:\temp> .\Invoke-CMApplyDriverPackage.ps1 -URI "http://xxxx/ConfigMgrWebService/ConfigMgr.asmx" -SecretKey "xxxx" -Filter "Drivers" C:\temp\Invoke-CMApplyDriverPackage.ps1 : Der Parametersatz kann mit den angegebenen benannten Parametern nicht aufgelöst werden.
Cant upload the ps1-files as zip here. But i also try the new version -> same issue: https://github.com/MSEndpointMgr/ModernDriverManagement/commit/753e58dadd8e8b2ab93ef39deb10304167b65289 I want to test it local before i deploy it via tasksequenz.
you can use the invoke script in "normal" running windows. The script create TS variables and need the TS environment for that:
WARNUNG: Unable to construct Microsoft.SMS.TSEnvironment object
hello,
ApplyDriverPackage.log
<![LOG[[ApplyDriverPackage]: Apply Driver Package process initiated]LOG]!>
Hello,
i want to setup "MSEndpointMgr-Drivermanagement" for SCCM and not able to install driver packages via tasksequenz. Im able to download and import driver packs to my sccm server. The pack i want to test is deployed and i use the Invoke-CMApplyDriverPackage.ps1 version 3.0.5. Inside the tasksequenz i use the command: -URI "http://xxxxx/ConfigMgrWebService/ConfigMgr.asmx" -SecretKey "xxxx" -Filter "Drivers" -DeploymentType BareMetal
The Error is still the same:
The task sequence execution engine failed executing the action (Driver Automation Tool - MSEndpointMgr) in the group (Auto Apply Drivers) with the error code 1 Action output: ... CMApplyDriverPackage.ps1 range 0-114092 Downloaded file from http://xxxxxx:80/SMS_DP_SMSPKG$/HRO007B6/sccm?/Invoke-CMApplyDriverPackage.ps1 to C:_SMSTaskSequence\Packages\HRO007B6\Invoke-CMApplyDriverPackage.ps1 VerifyContentHash: Hash algorithm is 32780 Content successfully downloaded at C:_SMSTaskSequence\Packages\HRO007B6. Resolved source to 'C:_SMSTaskSequence\Packages\HRO007B6' Working dir 'C:_SMSTaskSequence\Packages\HRO007B6' Command line for extension .exe is "%1"%* Set command line: Run PowerShell Script PowerShell command line is NOT shown in the log ('OSDLogPowerShellParameters' is NOT set to 'True') Executing command line: Run PowerShell Script with options (0, 4) Process completed with exit code 1 PowerShell command line returned code 1 ReleaseSource() for C:_SMSTaskSequence\Packages\HRO007B6. reference count 1 for the source C:_SMSTaskSequence\Packages\HRO007B6 before releasing Released the resolved source C:_SMSTaskSequence\Packages\HRO007B6 C. The operating system reported error 1: Incorrect function.
Has anyone some idea how to fix this.
If i run the powershell script local i get these error:
Logfile: <![LOG[[ApplyDriverPackage]: Apply Driver Package process initiated]LOG]!>