Open rubenwelle opened 3 years ago
Facing the same issue. IDK if you ever solved it.
Hi yes I did, but I am not sure how I resolved it.. This is the command I use now: -BareMetal -Endpoint "Server.FQDN.com" -TargetOSVersion "2004"
On Tue, Dec 7, 2021 at 3:45 AM ThomasFaherty @.***> wrote:
Facing the same issue. IDK if you ever solved it.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MSEndpointMgr/ConfigMgr/issues/297#issuecomment-987516773, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASFLOM445ZNLRPMMTP3OC2TUPVYL5ANCNFSM4VAY3HCA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
That's the same that I have. The only thing I can think is that it's not accepting the MDMUser and MDMPassword variables or something.
Can you test if your AdminService is working properly for your SCCM environment?
On Tue, Dec 7, 2021 at 9:29 PM ThomasFaherty @.***> wrote:
That's the same that I have. The only thing I can think is that it's not accepting the MDMUser and MDMPassword variables or something.
— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/MSEndpointMgr/ConfigMgr/issues/297#issuecomment-988242396, or unsubscribe https://github.com/notifications/unsubscribe-auth/ASFLOM2SKDXDLFVIIWCJTYDUPZVCFANCNFSM4VAY3HCA . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
Made a little more progress I think?
I took out the -TargetOSVersion from the -DriverUpdate command. Seems like it's not supported but now I am getting
Join-Path : Cannot bind argument to parameter 'Path' because it is an empty string.
It wants to write to the ApplyDriverPackage log but the above error is stopping it.
I want to apply drivers within the task sequence and I use the following command line: -DriverUpdate -Endpoint "server.domain.com"
I get the following error: Parameter set cannot be resolved using the specified named parameters
When I use the Debugmode I have the same issue. What is the problem?
Some additional info maybe.
I only want to use the driver automation tool for adding drivers to a Windows Image during the task sequence. I would like the script to be as versatile as possible so not adding the TargetOSVersion hence why I want to use DriverUpdate.
I followed the guidelines on Installing the Driver Management Software Step 1, Step 2 and Step 4. I found some command to test the Powershell script and I used the following command: .\Invoke-CMApplyDriverPackage.ps1 -DebugMode -DriverUpdate -Endpoint "server..domain.com" -UserName "MDM-AS-Account@domain.com" -Password "the password we set for the AD account"
But this also gives me the error: Parameter set cannot be resolved using the specified named parameters
We are also using ConfigMgr - StandardPkg and not a Driver package
Maybe I am not understanding how to set it up properly?