Official repo of Modern Driver Management from MSEndpointMgr.com
Home Page: https://www.msendpointmgr.com
License: MIT License
For implementation instructions, please go to https://www.msendpointmgr.com/modern-driver-management
How do I specify where to download the drivers so it does not delete them all when the TS completes? I want to precache the drivers locally so the next task sequence (user initiated) runs it and they're already downloaded to a specific location. IE C:\Drivers
This might be an easy one to change in the code.
It's kind of annoying that the details pane doesn't receive focus after having selected the Package Type and the Deployment State. Every time I use this tab, I set those two parameters and I start scrolling through the results, only to see the values of the Deployment State being scrolled up or down. Set it back to the desired choice, hit tab, sigh, and carry on. No big deal.
But if it's easy enough to change this, than maybe you could? :)
I was trying the latest version of the Invoke-CMApplyDriverPackage.ps1 and was trying it in debug mode and the script seemed to do a false positive on a package that doesnt have the SKU in its description.
At this moment i've tried to do a write-host $DriverPackageInputArray " hello" under the line with the comment "# Attempt to match for each SystemSKU item based on computer data input"
Here's what i've got in the first place :
807c 8079 hello
80fd 8125 hello <-
When i've seen this i came back to look at the package matching with "8125" and it was just like that : "Hewlett-Packard ProBook 650 G2 Notebook PC Windows 10 x64 Drivers (Models included:80fd,8125)"
But WHY did it match with 8549? Believe me or not, but i've just edited the text by removing the last two characters of the description and writing it back by hand. It solved my problem. I've had 4 other packages with this problem. Now they all seem good and my detection works with the new script.
So its a solved ISSUE, but its good to know.
Hi,
I'm not able to use the UseDriverFallback switch with Invoke-CMApplyDriverPackage.ps1 v4.0.5 because when come to invoke Confirm-FallbackDriverPackage function, it expect to get the $WebService object even if (as I understand) we do not have this object anymore available if we use the AdminService...
Although, I think it shloud be interesting that you log some informations about the exception message on the catch block. Something like that:
catch [System.Exception] {
Write-CMLogEntry -Value "[ApplyDriverPackage]: - Error Message:
Write-CMLogEntry -Value "[ApplyDriverPackage]: - Error in Line: $($.InvocationInfo.Line)" -Severity 3
Write-CMLogEntry -Value "[ApplyDriverPackage]: - Error in Line Number:
Write-CMLogEntry -Value "[ApplyDriverPackage]: - Error Item Name: $($.Exception.ItemName)" -Severity 3
Write-CMLogEntry -Value "[ApplyDriverPackage]: Apply Driver Package process failed, please refer to previous error or warning messages" -Severity 3
# Main try-catch block was triggered, this should cause the script to fail with exit code 1
exit 1
}
Regards,
Flo313
When running the script using -Whatif, the script does not create log entries, so tracking what's happening is difficult as all that's shown in the PowerShel console is
What if: Performing the operation "Output to File" on target "C:\WINDOWS\Temp\ApplyDriverPackage.log". over and over.
I'd suggest adding -WhatIf:$false to the Write-CMLogEntry function:
Current:
ModernDriverManagement/Invoke-CMApplyDriverPackage.ps1
Lines 358 to 361 in f029903
# Add value to log file
try {
Out-File -InputObject $LogText -Append -NoClobber -Encoding Default -FilePath $LogFilePath -ErrorAction Stop -WhatIf:$false
}Hello.
Are there any documentation for implementing 4.01 with support for Windows 10 2004 ?
Hi,
Could you add support for 20H2 build? (19042.xxx)
I get an os version not supported error :)
Regards,
gor3t3x
Two problems:
Surface GO driver doesn't apply during task sequence. It has version 0 in MECM and the comments refer to other Surface models.
Surface GO 2 model missing in catalog, only GO and GO LTE is there.
can anyone please help me out with this? this is in -debug mode
[ApplyDriverPackage]: Apply Driver Package process initiated ApplyDriverPackage 8/4/2020 1:33:58 PM 9672 (0x25C8)
I am trying to have some SoftPaqs on a bare metal deployment. I am unable to get them to install. What do I need to put in the TS to get these to run.
Currently testing the 4.0.2 script out with MECM 2006 through the CMG. Using the script internally I have no issues but I have a client on the internet that is returning its AdminServiceType as Internal and therefore cannot download the driver package.
Going through the script and looking at how it is determined I see what is going on. I see that the script gets all the active MPs with this line
$ActiveMPCandidates = Get-WmiObject -Namespace "root\ccm\LocationServices" -Class "SMS_ActiveMPCandidate"
and then counts both the Internal and External mps with the next two lines
$ActiveMPInternalCandidatesCount = ($ActiveMPCandidates | Where-Object { $PSItem.Type -like "Assigned" } | Measure-Object).Count
$ActiveMPExternalCandidatesCount = ($ActiveMPCandidates | Where-Object { $PSItem.Type -like "Internet" } | Measure-Object).Count
On the client I'm working with, I get counts for both Internal and External. The scripts appears to default to "Internal" if the "$ActiveMPInternalCandidatesCount" is not 0.
switch ($ActiveMPInternalCandidatesCount) { 0 { if ($ActiveMPExternalCandidatesCount -ge 1) { $Script:AdminServiceEndpointType = "External" } else { Write-CMLogEntry -Value " - Unable to determine AdminService endpoint type, bailing out" -Severity 3 $ErrorRecord = New-TerminatingErrorRecord -Message ([string]::Empty) $PSCmdlet.ThrowTerminatingError($ErrorRecord) } } default { $Script:AdminServiceEndpointType = "Internal" } }
The client appears to function, I can install applications, CBs run, etc. Is it possible I have something configured incorrectly on my client or is this a possible expected behavior for a client?
Hi there,
get with v4.0.2 in ApplyDriverPackage.log this error message:
[DriverPackageDownload]: Starting driver package download phase ApplyDriverPackage 28.08.2020 12:18:03 412 (0x019C)
- Attempting to download content files for matched driver package: Drivers - Dell Latitude 5510 - Windows 10 x64 ApplyDriverPackage 28.08.2020 12:18:03 412 (0x019C)
- Setting task sequence variable OSDDownloadDownloadPackages to: SER000D6 ApplyDriverPackage 28.08.2020 12:18:03 412 (0x019C)
- Setting task sequence variable OSDDownloadDestinationLocationType to: Custom ApplyDriverPackage 28.08.2020 12:18:03 412 (0x019C)
- Setting task sequence variable OSDDownloadDestinationVariable to: OSDDriverPackage ApplyDriverPackage 28.08.2020 12:18:03 412 (0x019C)
- Setting task sequence variable OSDDownloadDestinationPath to: %_SMSTSMDataPath%\DriverPackage ApplyDriverPackage 28.08.2020 12:18:03 412 (0x019C)
- Starting package content download process (WinPE), this might take some time ApplyDriverPackage 28.08.2020 12:18:03 412 (0x019C)
- Failed to download package content with PackageID 'SER000D6'. Return code was: -2147221246 ApplyDriverPackage 28.08.2020 12:18:03 412 (0x019C)
- An error occurred while attempting to download package content. Error message: The argument is null or empty. Provide an argument that is not null or empty, and then try the command again. ApplyDriverPackage 28.08.2020 12:18:03 412 (0x019C)
[ApplyDriverPackage]: Apply Driver Package process failed, please refer to previous error or warning messages ApplyDriverPackage 28.08.2020 12:18:03 412 (0x019C)
Package SER000D6 is valide.
Any help here ?
You using $DriverPackageCompressedContent but above that the variable is $DriverPackageCompressedFile. You might of forgot to combine location and zip file into one variable to be used.
i am running invoke-cmapplydriverpackage.ps1 4.0.2
invoke-cmapplydriverpackage.ps1 -PreCache -Endpoint "pri02.xxx.net" -TargetOSVersion "2004"
the applydriverpackage.log all looks successful it reads the service account name from the TS variable but it failed to apply driver package process failed, please refer to previous error or warning. i am not seeing any errors in the log so i am not sure what is failing.
Hello,
Using Driver automation Tool 6.4.9 and version 4.0.5 of the script, 7zip archive doesn'T work properly. When I create the package in either uncompress or zip, the computer install fine and no issue. If I use 7zip compression, it then does error during the dism and once booted, a lot of driver missing. I tried with various computer and all consistent result.
For my current exemple, I have uncompress driver of 3.3gig, zip of 2gig and 7z of 1.3gig. When unzipping, all of them are 3.3gig thus I'm unsure where's the problem, either the .exe of 7zip not unzipping properly or at the right place? The script does say a dism error occured:
- An error occurred while installing drivers. Continuing with warning code: 2. See DISM.log for more details
dism.log
The Dell 5410 drivers download finds the correct .CAB file, but then attempts to download that .CAB file using a URL of an older file and fails the download process.
Not sure what the issue is here but the drivers seem to download but never actually installs. There are no errors but the drivers clearly do not install as it would take more than 1 second to install them ;)
[DriverPackageDownload]: Starting driver package download phase ApplyDriverPackage 24/09/2020 15:39:38 2416 (0x0970)
- Attempting to download content files for matched driver package: Drivers - HP ProDesk 600 G3 Base Model Small Form Factor PC - Windows 10 1909 x64 ApplyDriverPackage 24/09/2020 15:39:38 2416 (0x0970)
- Setting task sequence variable OSDDownloadDownloadPackages to: HQ100389 ApplyDriverPackage 24/09/2020 15:39:38 2416 (0x0970)
- Setting task sequence variable OSDDownloadDestinationLocationType to: Custom ApplyDriverPackage 24/09/2020 15:39:38 2416 (0x0970)
- Setting task sequence variable OSDDownloadDestinationVariable to: OSDDriverPackage ApplyDriverPackage 24/09/2020 15:39:38 2416 (0x0970)
- Setting task sequence variable OSDDownloadDestinationPath to: %_SMSTSMDataPath%\DriverPackage ApplyDriverPackage 24/09/2020 15:39:38 2416 (0x0970)
- Starting package content download process (FullOS), this might take some time ApplyDriverPackage 24/09/2020 15:39:38 2416 (0x0970)
- Successfully downloaded package content with PackageID: HQ100389 ApplyDriverPackage 24/09/2020 15:39:47 2416 (0x0970)
- Driver package content files was successfully downloaded to: C:\_SMSTaskSequence\DriverPackage\HQ100389 ApplyDriverPackage 24/09/2020 15:39:47 2416 (0x0970)
[DriverPackageDownload]: Completed driver package download phase ApplyDriverPackage 24/09/2020 15:39:47 2416 (0x0970)
[DriverPackageInstall]: Starting driver package install phase ApplyDriverPackage 24/09/2020 15:39:47 2416 (0x0970)
- Downloaded driver package content contains a compressed archive with driver content ApplyDriverPackage 24/09/2020 15:39:47 2416 (0x0970)
- Attempting to decompress 7-Zip driver package content file: DriverPackage.exe ApplyDriverPackage 24/09/2020 15:39:47 2416 (0x0970)
- Decompression destination: C:\_SMSTaskSequence\DriverPackage\HQ100389 ApplyDriverPackage 24/09/2020 15:39:47 2416 (0x0970)
- Successfully decompressed 7-Zip driver package content file ApplyDriverPackage 24/09/2020 15:40:28 2416 (0x0970)
- Driver package content downloaded successfully, attempting to apply drivers using pnputil.exe located in: C:\_SMSTaskSequence\DriverPackage\HQ100389 ApplyDriverPackage 24/09/2020 15:40:28 2416 (0x0970)
- Successfully installed drivers ApplyDriverPackage 24/09/2020 15:40:37 2416 (0x0970)
[DriverPackageInstall]: Completed driver package install phase ApplyDriverPackage 24/09/2020 15:40:37 2416 (0x0970)
- Setting task sequence variable OSDDownloadDownloadPackages to a blank value ApplyDriverPackage 24/09/2020 15:40:37 2416 (0x0970)
- Setting task sequence variable OSDDownloadDestinationLocationType to a blank value ApplyDriverPackage 24/09/2020 15:40:37 2416 (0x0970)
- Setting task sequence variable OSDDownloadDestinationVariable to a blank value ApplyDriverPackage 24/09/2020 15:40:37 2416 (0x0970)
- Setting task sequence variable OSDDownloadDestinationPath to a blank value ApplyDriverPackage 24/09/2020 15:40:37 2416 (0x0970)
[ApplyDriverPackage]: Completed Apply Driver Package process ApplyDriverPackage 24/09/2020 15:40:37 2416 (0x0970)
The download seems awfully quick but it's via the LAN and the package is only 400MB or so. I have run the pnputil code manually and it works just fine, it just doesn't seem to run via the TS. No Install-drivers.txt file is generated so I think the Invoke-Executable step is failing but I notice you don't write to the logfile in the Catch statement, you just use Write-Warning.
That's not much use when running it via a TS :)
Hello,
I found out a problem with Surface Driver. The problem is both on the script invoke-cmapplydriverpackage.ps1 and in the driver automation tool.
The problem is when there's a sku that is empty or space, it get parsed as an empty string and not removed. Thus, when running "Confirm-SystemSku", the -match job pull a match when the string is empty.
Exemple I have, surface pro 6 drivers pack for windows 10. The systemSku, when doing copy/paste, we don't have any empty char:
(Models included:Surface_Pro_6_1796_Consumer, Surface_Pro_6_1796_Commercial)
We can see on the picture a line break, maybe it's just because of number of char.
But, in the code, running in debug for a suface pro 4, the sku will match. During the "Confirm-SystemSku" function, $DriverPackageInputArray = "Surface_Pro_6_1796_Consumer", "", "Surface_Pro_6_1796_Commercial"
As we can see, there's a "" value.
Here's a screenshot of what going on while processing ""
Currently, we can see we're at line 1669, which is after the match. We can see below the value of $SystemSkuItem is Empty and $computerData.SystemSku = "surface_pro_4", thus, it shouldn't be a match.
What's needed is skipping null, and the correction to line 1667 is
if ($ComputerData.SystemSKU -match $SystemSKUItem -and $SystemSKUItem -ne "") {
tested and working for me
Any idea why this might be happening? this is the PWSH transcript
IPU scenario w/
webservice 1.8.0
Invoke-CMApplyDriverPackage.ps1 3.0.5
Windows PowerShell transcript start
Start time: 20200622145751
Username: xxxx\SYSTEM
RunAs User: xxxx\SYSTEM
Configuration Name:
Machine: xxxxxx (Microsoft Windows NT 10.0.17763.0)
Host Application: C:\WINDOWS\system32\windowspowershell\v1.0\powershell.exe -NoProfile -NonInteractive -ExecutionPolicy Bypass -Command & 'C:\WINDOWS\ccmcache\k\Invoke-CMApplyDriverPackage.ps1' -URI http://XXXXXX-XXXX/ConfigMgrWebService/ConfigMgr.asmx -SecretKey xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -Filter Driver -DeploymentType OSUpgrade -TargetOSVersion 18363 ; exit (
Process ID: 11960
PSVersion: 5.1.17763.1007
PSEdition: Desktop
PSCompatibleVersions: 1.0, 2.0, 3.0, 4.0, 5.0, 5.1.17763.1007
BuildVersion: 10.0.17763.1007
CLRVersion: 4.0.30319.42000
WSManStackVersion: 3.0
PSRemotingProtocolVersion: 2.3
SerializationVersion: 1.1.0.1
Command start time: 20200622145751
PS>& 'C:\WINDOWS\ccmcache\k\Invoke-CMApplyDriverPackage.ps1' -URI http://XXXXXX-XXXX/ConfigMgrWebService/ConfigMgr.asmx -SecretKey xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx -Filter Driver -DeploymentType OSUpgrade -TargetOSVersion 18363 ; exit (
Command start time: 20200622145757
**PS>TerminatingError(Confirm-OSName): "Cannot validate argument on parameter 'DriverPackageInput'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again."
TerminatingError(Confirm-DriverPackage): "Cannot validate argument on parameter 'DriverPackageInput'. The argument is null or empty. Provide an argument that is not null or empty, and then try the command again."**
Windows PowerShell transcript end
End time: 20200622145757
here is the apply driver log
[ApplyDriverPackage]: Apply Driver Package process initiated ApplyDriverPackage 6/22/2020 2:57:52 PM 11960 (0x2EB8)
Hi
I'm trying to setup MDM on our MCEM 2002 environment. I was able to download and create the driver packages with the Driver Automation tool but the part for the task sequence does not work. I'm using version 4.0.1 of the Invoke-CMApplyDriverPackage.ps1 script. I was able to setup the AdminService on our MCEM and it is working correctly. I was also able to configure a read-only user and I added the credentials in the task sequence.
When the "Apply driver package" step runs, the script is able to connect to the admin service and filter the correct driver package but then it suddenly stops with exit code 1 and without decent logging what went wrong. Any suggestions what could be wrong? The package with the drivers is distributed to the DP.
Kind regards
Niels
Hello,
This is in fact 2 issue. When you create package with DAT, let's say HP Drivers, if they already existe, the comments are happened. Because of that, it does stuff like Models included: 3834,3835,3836 3834,3835,3836 3834,3835,3836) each time it ran. Because of that, the (2nd issue) make the script crash and not found matching models since it try to add a double keys.
In function "Confirm-systemsku" at this section:
# Attempt to match for each SystemSKU item based on computer data input
foreach ($SystemSKUItem in $DriverPackageInputArray) {
if ($ComputerData.SystemSKU -match $SystemSKUItem) {
# Add key value pair with match success
$SystemSKUTable.Add($SystemSKUItem, $true)
# Set custom object property with SystemSKU value that was matched on the detection result object
$SystemSKUDetectionResult.SystemSKUValue = $SystemSKUItem
}
else {
# Add key value pair with match failure
$SystemSKUTable.Add($SystemSKUItem, $false)
}
}
I would add a try catch on each (or check if it's already in the table) like:
foreach ($SystemSKUItem in ($DriverPackageInput -split $SystemSKUDelimiter))
{
if ($ComputerData.SystemSKU -match $SystemSKUItem)
{
# Add key value pair with match success
try
{
$SystemSKUTable.Add($SystemSKUItem, $true)
# Set custom object property with SystemSKU value that was matched on the detection result object
$SystemSKUDetectionResult.SystemSKUValue = $SystemSKUItem
}
catch
{
}
}
else
{
# Add key value pair with match failure
try
{
$SystemSKUTable.Add($SystemSKUItem, $false)
}
catch
{
}
}
}
This morning i did a switch from 2.2.1 to 3.0.9 and the first machine build crashed on detection, because there were a Windows 7 package in the detection list. The $DriverPackageDetails.OSName variable was NULL and the Confirm-OSName function just crashed. Cancelling the whole detection and returning an EVIL "1" exit code. I've rolled back to 2.2.1....
By looking at the code, i've realised that Windows 7 have been completely removed from the detection methods since version 3.0.0.
I know its the end of support for Windows 7, but many Governments are paying for the ESU and still managing it. Its sadly still "actual".
So i've looked at the code and changed the line 1059 :
if ($DriverPackageItem.PackageName -match "^.*Windows.*(?<OSName>(10)).*") {
to
if ($DriverPackageItem.PackageName -match "^.*Windows.*(?<OSName>(10|7)).*") {
After that, the trouble was with the build detection, so i've added this under line 614
"6.1.*" {
$OSName = "Windows 7"
switch (([System.Version]$InputObject).Build) {
"7601" {
$OSVersion = "7601"
}
}
}
I've havent put it in production yet, i'm asking if there is any other issues expected.
Hi,
We're seeing these errors in the ApplyDriverPackage.log file when running builds..
We also notice that the Package download takes about 1.5 hours to complete..
We've only just upgraded to use the new Invoke-CMApplyDriverPackage.ps1 script and the AdminService and I'm wondering if the 2 errors above are related to a misconfiguration of the AdminService?
Does anyone have any idea what might be causing this issue?
Many thanks
Running on a W2K12R2 server with Powershell 5.1:
Import-Module : Mixed mode assembly is built against version 'v2.0.50727' of the runtime and cannot be loaded in the 4.0 runtime without additional configuration information.
At line:162 char:1
+ Import-Module -Name BitsTransfer -Verbose
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [Import-Module], FileLoadException
+ FullyQualifiedErrorId : FormatXmlUpdateException,Microsoft.PowerShell.Commands.ImportModuleCommand
Hello,
I have a very weird issue with HP driver package. I'm still on 3.0.4 (website didn't say there was a new version, just found it on github), thus, using the webservice. With Dell drivers, no problem.
What happen is it start enumarating drivers, then suddenly stop saying an error occur, but there's no error. It used to work well and I can't find what changed that broke it. I added a debug in the try catch to get the error, here's the output:
- Retrieved a total of '94' driver packages from web service matching operational mode: Production ApplyDriverPackage 2020-07-15 11:48:37 2052 (0x0804)
- Attempting to detect OS Image data from task sequence with PackageID: PR1009F1 ApplyDriverPackage 2020-07-15 11:48:37 2052 (0x0804)
- Multiple OS Image objects detected and OSImageTSVariableName was not specified. Selecting the first OS Image object from web service call ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Target operating system name detected as: Windows 10 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Target operating system architecture detected as: x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Target operating system build version detected as: 10.0.18362.900 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Target operating system translated version detected as: 1903 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[WebService]: Completed ConfigMgr WebService phase ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage]: Starting driver package matching phase ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Filtering driver package results to detected computer manufacturer: Hewlett-Packard ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Count of driver packages after filter processing: 67 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Filtering driver package results to only include packages that have details added to the description field ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Count of driver packages after filter processing: 67 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR10098B]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard Elite x2 1013 G3 Tablet - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100970]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard Elite x2 1013 G3 Tablet - Windows 10 1909 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR10098C]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard Elite x2 G4 Tablet with Keyboard - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100971]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard Elite x2 G4 Tablet with Keyboard - Windows 10 1909 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A12]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 820 G1 Notebook PC - Windows 10 1709 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A6C]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 820 G1 Notebook PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A14]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 820 G3 Notebook PC - Windows 10 1709 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A27]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 820 G3 Notebook PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A15]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 820 G4 Notebook PC - Windows 10 1709 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A28]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 820 G4 Notebook PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A16]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 830 G5 Notebook PC - Windows 10 1709 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A29]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 830 G5 Notebook PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A17]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 830 G6 Notebook PC - Windows 10 1709 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A2A]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 830 G6 Notebook PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A18]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 840 G5 Notebook PC - Windows 10 1709 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A2B]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 840 G5 Notebook PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A19]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 840 G6 Notebook PC - Windows 10 1709 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A2C]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook 840 G6 Notebook PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A1A]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook Revolve 810 G3 Tablet - Windows 10 1709 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A67]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook Revolve 810 G3 Tablet - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A1B]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook x360 1030 G2 Base Model - Windows 10 1709 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A1C]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook x360 1030 G3 Notebook PC - Windows 10 1709 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR10092E]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteBook x360 1040 G6 Notebook PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR10086E]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 35W G3 Desktop Mini PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR10086F]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 35W G4 Desktop Mini PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100870]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 95W G4 Desktop Mini PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100929]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G1 Base Model Small Form Factor PC - Windows 10 1809 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100871]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G1 Base Model Ultra-slim PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100872]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G1 Desktop Mini PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100926]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G1 SFF PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR10091D]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G1 TWR PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A0B]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G2 Small Form Factor PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100995]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G3 Small Form Factor PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Matched SystemSKU: 8299 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Matched operating system name: Windows 10 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Matched operating system architecture: x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
- Matched operating system version: 1903 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100995]: Driver package was created on: 05/04/2020 13:47:51 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100995]: Match found between driver package and computer for 4/4 checks, adding to list for post-processing of matched driver packages ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100996]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G3 Tower PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR10097C]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G3 Tower PC - Windows 10 1909 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100997]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G4 Small Form Factor PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR10097D]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G4 Small Form Factor PC - Windows 10 1909 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100998]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G5 Desktop Mini PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR10097E]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G5 Desktop Mini PC - Windows 10 1909 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100999]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G5 Small Form Factor PC - Windows 10 1903 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR10097F]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteDesk 800 G5 Small Form Factor PC - Windows 10 1909 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR10094C]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard EliteOne 800 G1 All-in-One PC - Windows 10 1809 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A1D]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard ProBook 640 G1 Notebook PC - Windows 10 1709 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[DriverPackage:PR100A6D]: Processing driver package with 4 detection methods: Drivers - Hewlett-Packard ProBook 640 G1 Notebook PC - Windows 10 1809 x64 ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
[ApplyDriverPackage]: Apply Driver Package process failed, please refer to previous error or warning messages ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
Exception calling "Add" with "2" argument(s): "Item has already been added. Key in dictionary: '2102' Key being added: '2102'" ApplyDriverPackage 2020-07-15 11:48:39 2052 (0x0804)
The exception calling... is the debug I added.
This is the list of driver package I have for HP. Note that everything worked well about a month ago and I only worked on adding Dell Drivers, thus why I'm really bothered on why now it's stop working...
Drivers - Hewlett-Packard EliteBook 820 G1 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 1.00 A 1 PR100A6C 2020-07-15 08:29:00
Drivers - Hewlett-Packard Elite x2 1013 G3 Tablet - Windows 10 1903 x64 0 Hewlett-Packard 9.00 A 1 PR10098B 2020-05-04 13:20:00
Drivers - Hewlett-Packard Elite x2 1013 G3 Tablet - Windows 10 1909 x64 0 Hewlett-Packard 9.00 A 1 PR100970 2020-05-04 10:05:00
Drivers - Hewlett-Packard Elite x2 G4 Tablet with Keyboard - Windows 10 1903 x64 0 Hewlett-Packard 5.00 A 1 PR10098C 2020-05-04 13:23:00
Drivers - Hewlett-Packard Elite x2 G4 Tablet with Keyboard - Windows 10 1909 x64 0 Hewlett-Packard 5.00 A 1 PR100971 2020-05-04 10:17:00
Drivers - Hewlett-Packard EliteBook 820 G1 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 1.00 A 1 PR100A12 2020-06-22 09:07:00
Drivers - Hewlett-Packard EliteBook 820 G3 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 13.0 A 1 PR100A14 2020-06-22 09:13:00
Drivers - Hewlett-Packard EliteBook 820 G3 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 17.0 A 1 PR100A27 2020-06-23 08:14:00
Drivers - Hewlett-Packard EliteBook 820 G4 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 11.0 A 1 PR100A15 2020-06-22 09:22:00
Drivers - Hewlett-Packard EliteBook 820 G4 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 15.0 A 1 PR100A28 2020-06-23 08:20:00
Drivers - Hewlett-Packard EliteBook 830 G5 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 4.00 A 1 PR100A16 2020-06-22 09:29:00
Drivers - Hewlett-Packard EliteBook 830 G5 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 10.0 A 1 PR100A29 2020-06-23 08:26:00
Drivers - Hewlett-Packard EliteBook 830 G6 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 2.00 A 1 PR100A17 2020-06-22 09:36:00
Drivers - Hewlett-Packard EliteBook 830 G6 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 3.00 A 1 PR100A2A 2020-06-23 08:33:00
Drivers - Hewlett-Packard EliteBook 840 G5 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 4.00 A 1 PR100A18 2020-06-22 09:42:00
Drivers - Hewlett-Packard EliteBook 840 G5 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 10.0 A 1 PR100A2B 2020-06-23 08:39:00
Drivers - Hewlett-Packard EliteBook 840 G6 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 2.00 A 1 PR100A19 2020-06-22 09:50:00
Drivers - Hewlett-Packard EliteBook 840 G6 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 3.00 A 1 PR100A2C 2020-06-23 08:46:00
Drivers - Hewlett-Packard EliteBook Revolve 810 G3 Tablet - Windows 10 1709 x64 0 Hewlett-Packard 6.00 A 1 PR100A1A 2020-06-22 09:56:00
Drivers - Hewlett-Packard EliteBook Revolve 810 G3 Tablet - Windows 10 1903 x64 0 Hewlett-Packard 7.00 A 1 PR100A67 2020-07-14 11:43:00
Drivers - Hewlett-Packard EliteBook x360 1030 G2 Base Model - Windows 10 1709 x64 0 Hewlett-Packard 15.0 A 1 PR100A1B 2020-06-22 10:04:00
Drivers - Hewlett-Packard EliteBook x360 1030 G3 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 3.00 A 1 PR100A1C 2020-06-22 10:13:00
Drivers - Hewlett-Packard EliteBook x360 1040 G6 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 4.00 A 1 PR10092E 2020-03-18 08:47:00
Drivers - Hewlett-Packard EliteDesk 800 35W G3 Desktop Mini PC - Windows 10 1903 x64 0 Hewlett-Packard 17.0 A 1 PR10086E 2019-12-06 14:45:00
Drivers - Hewlett-Packard EliteDesk 800 35W G4 Desktop Mini PC - Windows 10 1903 x64 0 Hewlett-Packard 8.00 A 2 PR10086F 2019-12-06 14:51:00
Drivers - Hewlett-Packard EliteDesk 800 95W G4 Desktop Mini PC - Windows 10 1903 x64 0 Hewlett-Packard 8.00 A 2 PR100870 2019-12-06 14:58:00
Drivers - Hewlett-Packard EliteDesk 800 G1 Base Model Small Form Factor PC - Windows 10 1809 x64 0 Hewlett-Packard 1.00 A 1 PR100929 2020-03-16 13:45:00
Drivers - Hewlett-Packard EliteDesk 800 G1 Base Model Ultra-slim PC - Windows 10 1903 x64 0 Hewlett-Packard 2.00 A 1 PR100871 2019-12-06 15:05:00
Drivers - Hewlett-Packard EliteDesk 800 G1 Desktop Mini PC - Windows 10 1903 x64 0 Hewlett-Packard 2.00 A 1 PR100872 2019-12-06 15:12:00
Drivers - Hewlett-Packard EliteDesk 800 G1 SFF PC - Windows 10 1903 x64 0 Hewlett-Packard 2.00 A 1 PR100926 2020-03-13 10:52:00
Drivers - Hewlett-Packard EliteDesk 800 G1 TWR PC - Windows 10 1903 x64 0 Hewlett-Packard 2.00 A 1 PR10091D 2020-03-06 11:45:00
Drivers - Hewlett-Packard EliteDesk 800 G2 Small Form Factor PC - Windows 10 1903 x64 0 Hewlett-Packard 13.0 A 1 PR100A0B 2020-06-18 09:22:00
Drivers - Hewlett-Packard EliteDesk 800 G3 Small Form Factor PC - Windows 10 1903 x64 0 Hewlett-Packard 18.0 A 1 PR100995 2020-05-04 13:47:00
Drivers - Hewlett-Packard EliteDesk 800 G3 Tower PC - Windows 10 1903 x64 0 Hewlett-Packard 18.0 A 1 PR100996 2020-05-04 13:50:00
Drivers - Hewlett-Packard EliteDesk 800 G3 Tower PC - Windows 10 1909 x64 0 Hewlett-Packard 18.0 A 1 PR10097C 2020-05-04 11:36:00
Drivers - Hewlett-Packard EliteDesk 800 G4 Small Form Factor PC - Windows 10 1903 x64 0 Hewlett-Packard 11.0 A 1 PR100997 2020-05-04 13:51:00
Drivers - Hewlett-Packard EliteDesk 800 G4 Small Form Factor PC - Windows 10 1909 x64 0 Hewlett-Packard 11.0 A 1 PR10097D 2020-05-04 11:40:00
Drivers - Hewlett-Packard EliteDesk 800 G5 Desktop Mini PC - Windows 10 1903 x64 0 Hewlett-Packard 4.00 A 1 PR100998 2020-05-04 13:53:00
Drivers - Hewlett-Packard EliteDesk 800 G5 Desktop Mini PC - Windows 10 1909 x64 0 Hewlett-Packard 4.00 A 1 PR10097E 2020-05-04 11:43:00
Drivers - Hewlett-Packard EliteDesk 800 G5 Small Form Factor PC - Windows 10 1903 x64 0 Hewlett-Packard 4.00 A 1 PR100999 2020-05-04 13:55:00
Drivers - Hewlett-Packard EliteDesk 800 G5 Small Form Factor PC - Windows 10 1909 x64 0 Hewlett-Packard 4.00 A 1 PR10097F 2020-05-04 11:48:00
Drivers - Hewlett-Packard EliteOne 800 G1 All-in-One PC - Windows 10 1809 x64 0 Hewlett-Packard 1.00 A 1 PR10094C 2020-04-09 09:38:00
Drivers - Hewlett-Packard ProBook 640 G1 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 1.00 A 1 PR100A1D 2020-06-22 10:19:00
Drivers - Hewlett-Packard ProBook 640 G1 Notebook PC - Windows 10 1809 x64 0 Hewlett-Packard 1.00 A 1 PR100A6D 2020-07-15 08:48:00
Drivers - Hewlett-Packard ProBook 640 G1 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 2.00 A 1 PR100A2D 2020-06-23 08:51:00
Drivers - Hewlett-Packard ProBook 640 G2 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 14.0 A 1 PR100879 2019-12-06 15:56:00
Drivers - Hewlett-Packard ProBook 640 G3 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 10.0 A 1 PR100A1F 2020-06-22 10:34:00
Drivers - Hewlett-Packard ProBook 640 G3 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 13.0 A 1 PR10087A 2019-12-06 16:03:00
Drivers - Hewlett-Packard ProBook 640 G4 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 4.00 A 1 PR100A20 2020-06-22 10:45:00
Drivers - Hewlett-Packard ProBook 640 G4 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 10.0 A 1 PR10087B 2019-12-06 16:09:00
Drivers - Hewlett-Packard ProBook 640 G5 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 4.00 A 1 PR10099C 2020-05-04 14:03:00
Drivers - Hewlett-Packard ProBook 640 G5 Notebook PC - Windows 10 1909 x64 0 Hewlett-Packard 4.00 A 1 PR100983 2020-05-04 12:21:00
Drivers - Hewlett-Packard ProBook 650 G1 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 1.00 A 1 PR100A21 2020-06-22 10:51:00
Drivers - Hewlett-Packard ProBook 650 G1 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 2.00 A 1 PR100A2E 2020-06-23 08:56:00
Drivers - Hewlett-Packard ProBook 650 G2 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 11.0 A 1 PR100A22 2020-06-22 10:57:00
Drivers - Hewlett-Packard ProBook 650 G2 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 14.0 A 1 PR10087D 2019-12-06 16:20:00
Drivers - Hewlett-Packard ProBook 650 G3 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 10.0 A 1 PR100A23 2020-06-22 11:07:00
Drivers - Hewlett-Packard ProBook 650 G3 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 13.0 A 1 PR10087E 2019-12-06 16:26:00
Drivers - Hewlett-Packard ProBook 650 G4 Notebook PC - Windows 10 1709 x64 0 Hewlett-Packard 4.00 A 1 PR100A24 2020-06-22 11:14:00
Drivers - Hewlett-Packard ProBook 650 G4 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 10.0 A 1 PR100880 2019-12-06 16:38:00
Drivers - Hewlett-Packard ProBook 650 G5 Notebook PC - Windows 10 1903 x64 0 Hewlett-Packard 4.00 A 1 PR10099F 2020-05-04 14:12:00
Drivers - Hewlett-Packard ProBook 650 G5 Notebook PC - Windows 10 1909 x64 0 Hewlett-Packard 4.00 A 1 PR100989 2020-05-04 13:01:00
Drivers - Hewlett-Packard Z4 G4 Workstation - Windows 10 1709 x64 0 Hewlett-Packard 4.2019 G 2 PR100A25 2020-06-22 11:19:00
Drivers - Hewlett-Packard Z4 G4 Workstation - Windows 10 1809 x64 0 Hewlett-Packard 2.00 A 1 PR100A6B 2020-07-15 08:25:00
Drivers - Hewlett-Packard Z4 G4 Workstation - Windows 10 1903 x64 0 Hewlett-Packard 2.00 A 1 PR100A68 2020-07-14 14:16:00
Drivers - Hewlett-Packard Z440 Workstation - Windows 10 1903 x64 0 Hewlett-Packard 5.2018 J 1 PR10092D 2020-03-17 10:54:00
Drivers - Hewlett-Packard ZBook 15 G2 Mobile Workstation - Windows 10 1709 x64 0 Hewlett-Packard 6.00 A 1 PR100A26 2020-06-22 11:26:00
Thunderbolt Dock 120W G2 x64 0 Hewlett-Packard PR1009C4 2020-05-19 10:01:00
Thank you!
I have looked everywhere but cannot find an answer.
Basically, I want to run a task sequence (once every 6 months) on all my machines just to update the drivers.
Do I use DriverUpdate deployment type as described here https://msendpointmgr.com/modern-driver-management/#deployment-types-and-scenarios.
If yes, does anyone have any instructions on what type of Task Sequence I have to use? is it going to be a "custom task sequence"
I dont seem to be able to enter the site server and the site code during the installation process.
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?
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 "[email protected]" -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?
I have more info from the logfile I hope someone can help me with his:
The remote AdminService endpoint certificate is invalid according to the validation procedure. Error message: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.
Will attempt to set the current session to ignore self-signed certificates and retry AdminService endpoint connection
Failed to retrieve available package items from AdminService endpoint. Error message: The remote server returned an error: (401) Unauthorized.
The account I use to connect has Read-Only Analyst rights
When I start a browser under my own credentials I am able to browse to the AdminService webpage, but when I start a browser under the AdminService account I get a HTTP ERROR 401. What could this be?
When I make the account Full Administrator I still cant browse to the AdminService Webpage. It keeps giving me a HTTP ERROR 401.
When I use the debuf mode to test I see the AdminService log add entries stating that the WMI query went succesful, but it is nor returning any packages eventhough I have 1 Standard Pkg with drivers for model Latitude 5300
When running the -DriverUpdate within the OS, there is a log file created called "Install-Drivers.txt" in the CCM/Logs/SMSTS directory. When the TS completes, the .txt file is deleted instead of merged into CCM/Logs. Simply making this a .log instead of .txt on line 2062 resolves this issue.
As always, thanks for everything you guys do!
I just recently started using the AdminService version of this solution. Everything is working well! However, it does appear that if I try to use -UseDriverFallback (fallback packages exist for each manufacturer), the script fails even when a matching driver package is found. Upon checking the script, it looks like the Confirm-FallbackDriverPackage function is looking for $WebService as part of its parameters. Though, I can see that $FallbackDriverPackages is using Get-AdminServiceItem. Unless I'm seeing things incorrectly (maybe?), it looks like a little additional cleanup of the old web service might be needed for -UseDriverFallback functionality? If I don't use -UseDriverFallback, everything works perfectly.
Example when a matching driver is found, but it fails
` - Retrieved a total of '3' driver packages from AdminService matching operational mode: Production ApplyDriverPackage 12/17/2020 9:37:16 PM 512 (0x0200)
First of all, I love this solution! Thanks for a great job!
This is not an "issue" as such, but for your information BIOS updates using the Modern BIOS Management solution for Lenovo ThinkCentre machines is not working... Lenovo ThinkCentre machines need a full shutdown before the BIOS update is started.
With earlier scripts, I have devised myself, after the execution of the BIOS update exe file, I always executed a shutdown.exe -s -t 10. The next step in my Task Sequence would be Restart computer with a 60 sec. timer on it, When the BIOS update script then rebooted the computer using the shutdown command, the BIOS update would start and finish successfully. The Restart Computer step would recognize the shutdown command as if the Restart now button had been pressed so the task sequence would successfully reinitialize.
Just a thought, so that you maybe could facilitate this in the Invoke-LenovoBIOSUpdate.ps1 script.
Regards
Holger
The error log told me to reach out to you.
ApplyDriverPackage.log
This occurred with new admin service script. I am testing with the legacy and will report back on that result.
With Windows 10 1909, I have noticed that for some reason unknown to me, the drivers for the Nvidia display adapter do install, but then ARENT USED. The device continues to use the previous driver version.
Any ideas why this could be taking place?
Using version 3.0.5 by the way.
-URI "http://serverConfigMgrWebService/ConfigMgr.asmx" -SecretKey "secret" -Filter "Drivers" -DeploymentType "DriverUpdate" -TargetOSVersion 18363
The problem does not occur for other devices. Just the Nvidia drivers. I do see, in the install-drivers.txt file that the drivers are all being installed successfully... the device just doesn't switch to the latest version.
The UI seems to reporting that it is downloading a Dell driver package rather than a package from Microsoft. After the extraction is done an empty folder is created under the directory where the driver packs are stored:
This is not necessarily a problem, but just a simple improvement to make in a future version.
In Install-DriverPackageContent there is logic to expand compressed driver archives. The .zip version includes code to remove the compressed .zip file after expansion. This is not included in the 7-zip self-extract .exe version and probably should be. Or the logic can be moved to after the switch -wildcard for non .wim extension files.
Earlier with the ConfigMgr WebService, we didn't have to manually set the -TargetOSVerson parameter on the TS step.
But after moving over to the AdminService, looks like -TargetOSVerson is mandatory.
This means we have to manually adjust the TS Step every time we move over to a new version of Windows.
Is this a limitation of the AdminService, because we didn't have to specify the Windows version with the ConfigMgr WebService?
OR could this be possibly fixed in a future release?
Instructions indicate to set the Do not display this value checkbox in the Set Dynamic Variables step for each MSMUserName and MDMPassword variable but this results in the strings being scrambled before it is even obfuscated in log file, resulting in a 401 Unauthorised error because the credentials are wrong.
I had to uncheck Do not display this value for respective variables to get script to use them correctly.
Hello
I wanted to give a big thank you for the previous tool as we’ve been using it heavily for onsite OSD driver deployments
I wanted to ask if there is is any way to leverage pre caching functionality similar to how task sequences download content first before running the task sequence/install package? As the current solution requires the script to run first and download drivers while it installs. We are upgrading drivers with 80% vpn users however there is no way for us to download content for the particular device first before running the task sequence. If the driver update package runs and installs a network drivers, the system is disconnects and the task sequence fails and all drivers after the network adaptor fail. Has anyone brought this up yet being most of our work force is WFH or vpn?
Also, is there anyway to force only the network driver to update last so the task sequence does not fail or interrupt the user?
How do I go about fixing an issue where it cannot find OS Name or Version. Was working but had to test a new image but went back to the old image and now this.
Performing the operation "Remove Directory" on target "\SRV-010\cmsources$\OSD\DRVSRC\Lenovo".
Cannot convert value "20H2" to type "System.Int32". Error: "Input string was not in a correct format."
At line:17837 char:5
... $OSBuild = $WindowsBuildHashTable.Item([int]$OSVersion)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Should be an easy fix 👍 Using 6.5.0.
Surface Laptop 3 is applying the wrong drivers (Surface Laptop 2) and it has missing drivers post build.
Since Driver Automation Tool doesn´t support Fujitsu Drivers, but the script does how do i create Fujitsu Driver Packages in SCCM so the script will work in the task sequence?
Is there an instruction or something?
Thank you.
Plese delete this as the problem I am having seems to only be on one model.
Looks like this repo and https://github.com/MSEndpointMgr/ConfigMgr/tree/master/Operating%20System%20Deployment/Drivers should be one and the same.
Slightly disconcerting that they have different content. :)
Hi,
When I run the tool to download en import the drivers for Dell system I get an error on some system types.
It says that it can't download the driver and when I go to the link manually I also get a 404 error that the directory doesn't exist.
Is this an issue within the driver tool or is it an issue that Dell has to fix?
I noticed that there is a problem with the URL reported in the Driver Management tool:
URL https://downloads.dell.com/FOLDER06520426M/1/5511-win10-A01-275V1.CAB FOLDER06605773M/1/5511-win10-A02-TKP8D.CAB
If you look closely there is a Space after .CAB and then it is another FOLDER06605773M/1/5511-win10-A02-TKP8D.CAB.
If I remove everything after the Space the URL works and I can download the source
The part behind the space is the correct path to the NEW cab file. the first path is to an OLDER CAB file
Looks like the name change is resulting in all the old Hewlett Packard packages as not recognised.
I found the problem and the solution. The problem is caused by the following line not being present in the script. Add this line fixes it.
[parameter(Mandatory = $true, ParameterSetName = "DriverUpdate")]
Having the section look like this resolves the issue updating drivers from within an existing OS.
[parameter(Mandatory = $true, ParameterSetName = "BareMetal", HelpMessage = "Define the value that will be used as the target operating system version e.g. '2004'.")]
[parameter(Mandatory = $true, ParameterSetName = "DriverUpdate")]
[parameter(Mandatory = $true, ParameterSetName = "OSUpgrade")]
[parameter(Mandatory = $true, ParameterSetName = "PreCache")]
[parameter(Mandatory = $true, ParameterSetName = "Debug")]
[parameter(Mandatory = $false, ParameterSetName = "XMLPackage")]
[ValidateNotNullOrEmpty()]
[ValidateSet("2004", "1909", "1903", "1809", "1803", "1709", "1703", "1607")]
[string]$TargetOSVersion,
Was this intended?
If the Apply Operating System Image steps are in a child task sequence, then the script will return the error:
Call to ConfigMgr WebService returned empty OS Image data. Error message at line :
I am receiving the following error message when running a DebugMode or BareMetal. Https is enabled in my environment (binding IIS Cert for https is exist) and AdminService appears to be working fine:
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
Django
The Web framework for perfectionists with deadlines.
Laravel
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
Microsoft
Open source projects and samples from Microsoft.
Google
Google ❤️ Open Source for everyone.
Alibaba
Alibaba Open Source for everyone
D3
Data-Driven Documents codes.
Tencent
China tencent open source team.