K2000 Prevent certain drivers being injected
Hi All,
Currently we use Kace to install windows on a machine, inject drives and install ssoftware.
Ive noticed that for our Dell Latitude e7240 laptops, the windows 8.1 display driver in kace causes lots of bsods (atleast 5 a day).
I can uninstall the display driver and get windows to search and install from winupdate and have no issues there after (after running ccleaner to clean the registry up after uninstallation of said drivers).
Is there a way to have kace exclude the gfx drivers while still deploying all other drivers??
Thanks
Currently we use Kace to install windows on a machine, inject drives and install ssoftware.
Ive noticed that for our Dell Latitude e7240 laptops, the windows 8.1 display driver in kace causes lots of bsods (atleast 5 a day).
I can uninstall the display driver and get windows to search and install from winupdate and have no issues there after (after running ccleaner to clean the registry up after uninstallation of said drivers).
Is there a way to have kace exclude the gfx drivers while still deploying all other drivers??
Thanks
0 Comments
[ + ] Show comments
Answers (1)
Please log in to answer
Posted by:
genfoch01
9 years ago
My assumption is that this is a sysprepped image, you have the driver feed package for the E7240 Windows 8.1 x64 installed, and the image has the use driver feed for sysprepped image checked.
I noticed there is a new release of the driver cab (as of 7/31/2014 version A02) so I'd first uninstall and reinstall the driver feed package to ensure you have the latest drivers. If that does not solve the issue, I'd mount the \\k2\drivers_postinstall share and go into dell\windows_8\e7240 and remove the driver in question. if you have an updated driver you could place it in this location as well. then test your deployment.
I'd also check the \\k2\drivers\windows_8_x64 to see if there is any conflicting drivers in it. In fact if you find anything in this location i'd back it up to a remote site, delete everything from \\k2\drivers\windows_8_x64 and then recache the windows 8 (x64) drivers to clean it up.
I noticed there is a new release of the driver cab (as of 7/31/2014 version A02) so I'd first uninstall and reinstall the driver feed package to ensure you have the latest drivers. If that does not solve the issue, I'd mount the \\k2\drivers_postinstall share and go into dell\windows_8\e7240 and remove the driver in question. if you have an updated driver you could place it in this location as well. then test your deployment.
I'd also check the \\k2\drivers\windows_8_x64 to see if there is any conflicting drivers in it. In fact if you find anything in this location i'd back it up to a remote site, delete everything from \\k2\drivers\windows_8_x64 and then recache the windows 8 (x64) drivers to clean it up.
\\k2\drivers\windows_8_x64
Comments:
-
Unfortunately it isnt. Its from the scripted build using the install.wim from the windows dvd, and then postinstall injection of drivers. I will try removing the driver, after removing and recaching the drivers.
Thanks :) - david.pegler 9 years ago-
The scripted install will also use the \\k2\drivers_postinstall\dell\windows_8\e7240 drivers to inject into the image. so I would still uninstall/reinstall the driver package and remove anything in \\k2\drivers\windows_8_x64
then recache the test the deployment. - genfoch01 9 years ago-
Will do, thanks :) - david.pegler 9 years ago
