The driverfeed has been updated in 3.4 and now includes this workaround automatically when deploying scripted installs, so you can remove any previous tasks you had assigned. However, the process is not automatic for images, so you can still use the tasks provided here.

If you are deploying Windows XP, you might still want to use the driverfeed workaround with scripted installs as well. The latest version of the tasks now looks at the drivers that are copied over to the workstation and identifies all the directories that have an .inf. These directory paths are then inserted into your XP answer file (scripted install or image). If you have an image, they are also injected into the XP registry “DevicePath” entry. This means that many drivers are installed during the PnP process and ready for you before post installs start running. The drivers that are not picked up should be during the postinstall task to run dpinst. It is possible that some drivers will need a reboot, and even with this method, some drivers will not install at all.


The drivers_postinstall path has also been changed in 3.4, please refer to the KB Article 1142:
K2000 3.4 Drivers Postinstallation Structure
http://www.kace.com/support/kb/index.php?action=artikel&cat=54&id=1142&artlang=en

Refer to KB 1128 if using non-dell systems and would like to setup the correct path:
K2000 Setting up Driver Feed with non-Dell Systems in 3.4
http://www.kace.com/support/kb/index.php?action=artikel&cat=54&id=1128&artlang=en

In 3.4, the drivers_postinstall share has a directory named feed_tools that contains a vbscript named Get_Manufacturer_Model_OS.vbs. You can run this script on the machine in question to get the Manufacturer, Model, and OS of that machine. You can also choose to run the new version of model_report.exe to get the 3.3 or 3.4 path needed for your machine.

Note: Many have asked about the combo drivers and how to use them in 3.4. Here are the paths used in 3.4 for these drivers, however, you will HAVE to use the driverfeed workaround tasks even in scripted installs for the combo drivers to work.
\dell\Operating_system(arch)\combo\Desktop
\dell\Operating_system(arch)\combo\Notebook


Download driverfeed tasks - http://downloads.kace.com/support/downloads/k2000/tasks/driver_feed_tasks-3.4.zip

After downloading the file, unzip the contents and you will be presented with:

README – general information
model_report.zip – x86 and x64 version of the script to run on the machine, either in Windows or KBE.
driver_feed_mid_task.zip – This file gets uploaded as an application midlevel task, with the command line: “call driver_feed_mid_task.bat”
install_drivers.exe – Gets uploaded as an application postinstall task to be used with XP images.

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hey Corey,

I'm really liking the progress with the Driver Feed. Many thanks to you and Kent for your work on this.

I tried out the drivercab_downloader imported in v.3 of the driver_feed_tasks packages in order to test it against a new Latitude E6320, but am getting an error on the mid level task Drivers - Copy x64 Feed Files to Workstation.

I get the following error:

Line 42 (File Y:\applications\78\driverfeed_x64.exe")"
Error: Variable used without being declared

Any ideas on what this may be? This also happens on other Dell laptops that previously worked with an earlier version of the driver feed tasks.

Thanks!
Answered 07/13/2011 by: asanchez
Orange Senior Belt

Please log in to comment
0
When I run the DriverCAB downloader I get the following error: Error: 2003 Can't connect to MySQL server on 'IP address' (10060). I have enabled the Allow Offboard Database Access option and rebooted the server. I am trying to get drivers for Dell Optiplex 990 (Win7 x64), which is not available through the driver feed. Thanks!
Answered 07/13/2011 by: sburkey2
Second Degree Blue Belt

Please log in to comment
0
Are you sure there is data that correlates to an OS on this drive? That is the only way I'm able to duplicate your issue.
Answered 07/13/2011 by: cserrins
Red Belt

Please log in to comment
0
asanchez helped me to troubleshoot the x64 version, turns out that when I added some additional checking on the drive letter, I left out some variable declarations, that should teach me to require all variables be declared in the future :)

sburkey2 found that their firewall was blocking the port necessary to access MySQL, which is port 3306
I sent him a link to this article to see if he could get excel to connect to it: http://helpdeskgeek.com/office-tips/excel-to-mysql/
Answered 07/13/2011 by: cserrins
Red Belt

Please log in to comment
0
I am getting an error when trying to use the tool for the first time. I have tried two different drivers, the e6320 and the 390, and I am getting the same error on both. I am getting the following:

Line 6497 (File "C:\Users\administrator\AppData\Local\Temp\12\drivercab_downloader.exe"):

Error: Subscript used with non-Array variable

Any idea what might be causing this?

Thanks.
Answered 07/18/2011 by: sfreitag
Yellow Belt

Please log in to comment
0
Please disregard my earlier post, I thought I had installed the driver patch a few days ago, but I hadn't. After doing this, the downloads are completing successfully.

Thanks.
Answered 07/18/2011 by: sfreitag
Yellow Belt

Please log in to comment
0
I can't seem to get this to work for either system images or scripted installs using Windows 7. I have a few different test machines, but the two I am currently working on are the Latitude 2100 and the 2110, both of which are supposed to have offical support by the KACE appliance.

I have the packages downloaded, and I've recached the drivers, but the install never happens. I tested this by doing a scripted install on the 2100 (which took ages), and then captured a sysprep'd image of it, and then deployed it to the 2110. Neither of them had any drivers installed except what was available already.

My other post-install tasks work fine (scripted installs: all programs, system images: installing the KBOX software, deleting unattend.xml) so I'm at a loss as to why the drivers aren't installing at all.
Answered 07/18/2011 by: aggybong
Senior Yellow Belt

Please log in to comment
0
Does anyone know how to apply the driver patch to an eval install of the K2000? The manual update option is not available under settings & maintenance/appliance maintenance.

Thanks
Answered 07/31/2011 by: Reppy2009
Yellow Belt

Please log in to comment
0
Reppy, get with your sales guy, or get into the trial patch and tell them this issue. Patches can not be applied to a trial. However, if you do want to try this, you can follow the instructions for the RSA by adding a drivers_postinstall directory to the petemp share. Then use the drivercab_downloader to download some cabs. You won't be able to test what is currently in the feed, but this should get you started.

Corey
Answered 08/01/2011 by: cserrins
Red Belt

Please log in to comment
0
I have been using the v.2 driver_feed_tasks scripts for a while, and they have been working great. I recently updated to the newest version of driver_feed_tasks to allow us to use RSAs, but now the driverfeed_x86.exe script is not working correctly when deploying from both the K2000 and the RSAs. After the Windows 7 setup finishes, it launches driverfeed_x86.exe, and that pops an error message saying "There is an error in that no data is being found that correlates to an OS." This is using the same scripted installation that worked fine with v.2. I just deleted the old post install tasks, imported the new ones, and added the new ones to the scripted installation. I have also tried re-downloading the drivers using the new drivercab_downloader, but the error still pops up. Is there anything I can do to get this working properly? These scripts have been very useful to us, since we got a lot of new Optiplex 790s and Latitude E5420s that need to be deployed at our remote sites.
Answered 08/10/2011 by: felegaspi
Yellow Belt

Please log in to comment
0
I am also having issues with the downloader. It seems to grab newer drivers, but when I tell it to get older drivers (GX620), it seems to error out without downloading anything. Anyone else experiencing this?
Answered 08/11/2011 by: mnaylor@wooster.edu
Senior Yellow Belt

Please log in to comment
0
Dell has changed the location of these files, I just noticed this the other day. They are now on google docs and you have to sign in, so trying to work around that.
Answered 08/11/2011 by: cserrins
Red Belt

Please log in to comment
0
It did not seem that I had to login...just ended up being a strange path.

D620 took me here (eventually) https://docs.google.com/uc?export=download&confirm=no_antivirus&id=0B0eQ3eQtDlyHNzk3NDc3ZjItMGU5Mi00NjljLTk5OWItNzg2Mzk5Zjc3MTIx&authkey=CJC6vsYJ

Turns out this is the "XP Notebook Combo Driver CAB"

Any chance that you could make your app reference an already downloaded cab file?

*EDIT*
In fact, if you can tell us where the downloaded file is put and is named (I see the cabdownload folder), it can be downloaded by hand.
Answered 08/12/2011 by: mnaylor@wooster.edu
Senior Yellow Belt

Please log in to comment
0
A new version of the drivercab_downloader script has been uploaded (v.58) to account for the movement of the combo pack cab files by Dell.
Looking into possibly adding the ability to select a .cab file that has been manually downloaded. However, the issue becomes getting the right model from the .cab
Answered 08/16/2011 by: cserrins
Red Belt

Please log in to comment
0
I am using a Windows 7 32 bit machine. I downloaded the Run_drivercab_downloader.exe. I enter the drive mapping information, choose New Dell Models not yet listed, then select E5520 and windows xp or E5420 and Windows 7. It will go through the Download stage, then starts the extraction stage and as it gets to the end i get Line 6498 error. Any suggestions????
Answered 08/18/2011 by: jbigman3122
Senior Yellow Belt

Please log in to comment
0
Hello Corey,
I followed your instruction to update the driver patch and import the tasks but it does not work for me.

I use the driver feed tool in K2000 to download the drivers for Dell Prec T3500 because this model is not listed in Driver Downloader. I see the drivers are downloaded "\\K2000Box\drivers_postinstall\windows_7_x64\feed\dell\t3500"

"Drivers - Copy x64 feed files to workstation" is added in mid-postinstallation task of scripted installation and I see the "driverfeed_x64.exe" is called
before the system is rebooted the first time.

When the PC is running in Post Install Task, I browse to "C:\kace\" folder and don't see "Drivers" folder.

if I copy the drivers to "C:\Kace\Drivers" and run the "install_drivers.exe" manually on the pc. It installs the missing drivers and replaces the drivers installed by Windows 7.

Could you advice me how to fix this issue?

thanks
Cody
Answered 08/18/2011 by: CodyNguyen
Yellow Belt

Please log in to comment
0
Corey -

I am working through this procedure for the first time starting today. Two quick questions for you:

1) When the drivercab_downloader script downloads drivers for new models (not available in the driver feed), I notice that it puts everything it downloads into the "drivers_postinstall" share. Are the network drivers not needed in the "drivers" shares, similar to how the network drivers for everything downloaded via the feed are still left in the "drivers" share?

2) For computer models that are not available in the feed or via the drivercab_downloader script (but still has an available CAB file on the Dell technet site), am I in compliance with this workaround if I

- Download and extract the CAB file manually
- Copy only the network drivers folder into the "drivers" share
- Copy everything else into the "drivers_postinstall" share
- Recache the drivers

Thanks

Bill Ward
Answered 08/18/2011 by: btw256
Yellow Belt

Please log in to comment
0
I dont know if this would be a Culprit or not, but was able to get the tool to work on an XP machine just not a Windows 7.
Answered 08/19/2011 by: jbigman3122
Senior Yellow Belt

Please log in to comment
0
So ignore all my previous posts. I just figured out my problem was my machine still had me mapped to the Post install folder. I ran a net use command and it showed up not being assigned to a driver letter, but i went ahead and deleted the connection and it worked.
Answered 08/19/2011 by: jbigman3122
Senior Yellow Belt

Please log in to comment
0
Cody,

After the machine restarts from the mid-level tasks, can you boot immediately into KBE again and check the C:\Kace directory for the drivers. In Windows 7, typically the post install tasks are all run prior to getting to the desktop, so technically, the c:\kace directory shouldn't even be there anymore.
Answered 08/24/2011 by: cserrins
Red Belt

Please log in to comment
0
Guys this tool is working great for my optiplex 790 deployment, thanks for the hardwork on the workaround. I have one minor annoyance that I assume is related to the workaround

- when using the workaround, as the driver for video is detected a bit later in the process than if the drivers were incorporated as standard during the install, my build starts up with all hardware perfectly installed including video, however the default 'windows 7 basic' theme has no fancy aero effects enabled. I can enable it all by re-running the experience index thing, however it is a 'post deploy check' that I would rather automate. Anybody else run into this?
Answered 09/01/2011 by: dogfish182
Orange Belt

Please log in to comment
0
Hi,

i've tried the driver feed on a E5520 x64 win7..
i see the drivers beeing (i think) copied, but when the install is ready i still have exclemation marks and unknown devices..

i did have the install feed to workstation task in place..
do i have an additional step to perform?
i don't see an c:\kace\drivers on the local disk of the machine
what i do see is the custom folder with the dell e5520 drivers in the postinstall share..

thanks in advance!!

Tom
Answered 09/06/2011 by: syseng99
Yellow Belt

Please log in to comment
0
syseng99,

Make sure the drivers are in \\k2ip\drivers_postinstall\windows_7_x64\custom\dell\e5520

This is where the script will be looking for them based on what you've told me.

I can understand a driver or two missing. c:\KACE\drivers (or the new c:\KACE\drivers_postinstall) get cleaned up by kcleanup after all postinstallation tasks run. To check if they are there, reboot to kbe immediately after the first reboot of the SI.

Make sure you have the install drivers to workstation postinstall task assigned o this SI.

Corey
Answered 09/06/2011 by: cserrins
Red Belt

Please log in to comment
0
@cserrins

The drivers are where they should be.
i see when doing a scripted install the xcopy, copying over all the correct drivers..

but when the scripted install is ready, no drivers have been applied.

when i say a driver or two are missing, i mean still missing, before using the workaround and now same amount.
all drivers are just the windows 7 default drivers it usses..
no dell drivers.
so looks like it doesn't do the next task.. (install the feed to the computer)

thx!!
Answered 09/07/2011 by: syseng99
Yellow Belt

Please log in to comment
0
Greetings -- Have the driver cabs been moved again? I am getting "cannot find archive" errors when running the latest version of the drivercabdownloader. When I checked, it's going to
http://downloads.kace.com/support/downloads/drivers/dell_combo_packs/Win7-Desktop-1.0.zip. However, if I go there manually, it says the file cannot be found. If someone has this file already, maybe I can simply populate the drivers_postinstall and recache to get it working.[/align] [/align]P.S. I tried the previous version to make sure and it doesn't work.[/align] [/align]Any assistance would be appreciated.[/align] [/align] [/align]Thanks![/align]
Answered 09/08/2011 by: hwt
Yellow Belt

Please log in to comment
0
when I try and download these feeds I am getting a strange outcome. It says sucsessful, but the progress bar is at the begining of the bar and doesn't actually make it to the end (see image). Then the 7-zip app runs and errors out saying it cannot find the archive.

Answered 09/13/2011 by: pedter
Orange Belt

Please log in to comment
0
Just wanted to say thank you for this method. Working great so far, saving a lot of driver frustrations!
Answered 09/14/2011 by: funkstar
Senior Yellow Belt

Please log in to comment
0
hwt and pedter,

Yes, they moved the .cabs again [:(] I have this fixed in the next version, but there are numerous other changes as well that I am still working on. A new release is imminent, stay tuned [8D]
Answered 09/15/2011 by: cserrins
Red Belt

Please log in to comment
0
I downloaded the .62 version and after installing the download started normally, made it almost all the way through and then errord with a expected file size error. this is repeatable for me.
Answered 09/16/2011 by: pedter
Orange Belt

Please log in to comment
0
This usually means that it is not downloading correctly, or a network glitch happened, and couldn't finish the download. In the next version I think I'll add a link to manually download it from that point and then bring the user to the place to manually select the file.

What model/os are you trying to download?

Corey
Answered 09/16/2011 by: cserrins
Red Belt

Please log in to comment
0
i tried all 4 of the options. but am specifically looking for the legacy notebook xp/7 drivers. (d series)

can i get the download links so i can grab the firls while you fix the application?
Answered 09/19/2011 by: pedter
Orange Belt

Please log in to comment
0
pedter,

The latest version .62 should be able to download the combo packs now. I just tried it and had success.

Corey
Answered 09/19/2011 by: cserrins
Red Belt

Please log in to comment
0
I'm getting an error "The downloaded file is not the proper size. Try again?" when downloading the legacy xp desktop drivers. I just downloaded the newest version of the app.
Answered 09/20/2011 by: RodCarbon
Yellow Belt

Please log in to comment
0
RodCarbon,

Yes, that was an issue, that is now fixed in v.6.3. So sorry about that, a syntax error that worked for the Dell cab downloads, but not for the combo packs.

Thank you all for your support and patience as I not only correct bugs that occur, but bugs that come up from new features that are being added.
Answered 09/21/2011 by: cserrins
Red Belt

Please log in to comment
0
**NOTE**

The K2000 driver feed has been updated. To use it you should be currently doing what the first post mentions with the driverfeed_tasks.

If you run drivercab_downloader at this point, any "custom" drivers you had downloaded previously will be deleted. This is OK, because you can now download them from the feed. The tasks will work as usual. But, if you copied your own stuff there, you should copy them out first.

In a few hours the drivercab_downloader will have an empty list :(

However, when dell releases a new model and has drivers, you can simply run it again and it will show up in the list until KACE releases it in the feed.

Please let us know of any issues.
Answered 09/23/2011 by: cserrins
Red Belt

Please log in to comment
0
Thank you very much for this fix/workaround. It works wonders with our Dell E series laptops. I am waiting to try it with one of our Alienware machines but even for the lappy's it's an awesome fix! Thank you
Answered 11/14/2011 by: pg_mandelbug
Senior Yellow Belt

Please log in to comment
0
Hi

We have some Alienware Aurora-R3 machines that I would like to use this method for.
I have followed the instructions in the first post and have run the model_report.exe file on the specified machine, this produced a path of \\{KACE-IP}\drivers_postinstall\{Windows-Version}\custom\Unknown\Aurora-R3

I have placed the drivers from the Alienware install CD into this directory, both as just a list of 'R' directories and also with the 'R' directories sub divided into the relevant criteria, i.e. Audio,Video etc.

Neither of these methods have worked, it seems to just completely ignore the install tasks.
Could you offer any advice/assistance on this.

Thanks
Answered 11/15/2011 by: PG_t4ttyt3ddy
Senior Yellow Belt

Please log in to comment
0
I am trying to do an installation on an optiplex 780 and receive an error on the driver mid-level post install tast after installing the driver feed update:

Line 2624 (File "Y:\applications\32\driver_feed_mid_task.exe"): Error: Subscript used with non-Array variable.
Answered 11/18/2011 by: Fatty_McBiggin
Yellow Belt

Please log in to comment
0
PG_t4ttyt3ddy,

Are the R files just .exe's? If so, they need to be expanded out to the drivers, you can extract them using 7-zip, winrar or winzip.
Answered 11/21/2011 by: cserrins
Red Belt

Please log in to comment
0
Fatty_McBiggen,

Does the 780 directory exist for you?
Are you using the latest tasks from the first post?
Answered 11/21/2011 by: cserrins
Red Belt

Please log in to comment
0
ORIGINAL: cserrins

PG_t4ttyt3ddy,

Are the R files just .exe's? If so, they need to be expanded out to the drivers, you can extract them using 7-zip, winrar or winzip.




HI

I have tried just .exe, unpacked .exe into a seperate Rxxxxxx folder per device driver and also packing the unpacked items back up into .zip files.

The task just seems exit without doing anything.

Thanks
Answered 11/21/2011 by: PG_t4ttyt3ddy
Senior Yellow Belt

Please log in to comment
0
I know have this working for all drivers but NVidia.

I had to place mine in the path
\\{K2-IP}\drivers_postinstall\windows_7_x64\feed\Unknown\Aurora-R3

Without the \feed\ part it doesn't even look for drivers.

Thanks for your assistance this workaround is an amazing help.

Has anyone else has success pushing out the NVidia Video Drivers with this workaround?
Answered 11/22/2011 by: PG_t4ttyt3ddy
Senior Yellow Belt

Please log in to comment
0
is there a change to make a t1500 cab ?
Answered 11/23/2011 by: petrybosch
Senior Yellow Belt

Please log in to comment
0
This works 100% percent for a Dell Latitude E6520 with windows 7 X86 32-bit. I do get the attached error, but i just click "ok" and everything seems to load fine.

thanks for you help on this!
Answered 11/29/2011 by: heidcinti
Senior Yellow Belt

Please log in to comment
0
heidcinti,

Are you using the latest tasks that I uploaded yesterday?
If so, please pm me your phone number, we can webex and get that resolved. No reason to click extra buttons ;)

Corey
Answered 11/29/2011 by: cserrins
Red Belt

Please log in to comment
0
This works 100% percent for a Dell Latitude 13 with windows 7 X86 32-bit.
Answered 12/01/2011 by: jestes1013
Orange Belt

Please log in to comment
0
I am seeing the same error message:

Line 2624 (File "Y:\applications\32\driver_feed_mid_task.exe"): Error: Subscript used with non-Array variable.

The drivercabdownloader says that the drivers have been downloaded to \\ikbox\drivers_postinstall..., but they are not there when I check. I manually copied them to the path given in the message and recached. However, I still get the non-Array error above. Do I need to do the "workaround" for the workaround that is mentioned (manually copying/moving the drivers to the feed folder? I am using the latest versions of the feed tasks and cab downloader.


Thanks!
Answered 12/02/2011 by: hwt
Yellow Belt

Please log in to comment
0
hwt, did you try the latest tasks? The last update I did should have resolved that issue.

Corey
Answered 12/13/2011 by: cserrins
Red Belt

Please log in to comment
0
I am still receiving the Line 2624 (File "Y:\applications\32\driver_feed_mid_task.exe"): Error: Subscript used with non-Array variable after the update only on the 64 bit script.
Answered 12/16/2011 by: jestes1013
Orange Belt

Please log in to comment
0
I'm probably doing something super dumb.
I get this error during the mid level x64 task

No Driver directory found
10

After I hit ok it appears to install the drivers ok, its just now starting its sysprep run as I'm typing this. Should I expect this error every time?
Answered 01/12/2012 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment
0
I get this exact error I have updated my mid level and post tasks to version .4 w7 x64 bit

Everything installs fine I just have this error stopping the install. Click OK and it goes past it :(
Answered 01/16/2012 by: shotton
Senior Yellow Belt

Please log in to comment
0
Just testing this with a Lattitude E5420.

It works perfectly for Windows XP SP3 but I get the "cannot install boot-critical drivers" with Windows 7.
Answered 01/18/2012 by: Arcolite
Senior Purple Belt

Please log in to comment
0
ORIGINAL: Tentacle Master

I'm probably doing something super dumb.
I get this error during the mid level x64 task

No Driver directory found
10

After I hit ok it appears to install the drivers ok, its just now starting its sysprep run as I'm typing this. Should I expect this error every time?


Hi Tentacle Master

Is this on your RSA? As I had the same error when running a scripted install on a RS but I have managed to get rid of the error using cserrins

http://downloads.kace.com/support/downloads/k2000/scripts/driverfeed_sync.zip
Answered 01/18/2012 by: shotton
Senior Yellow Belt

Please log in to comment
0
I get the same error E5420 W7 SP1
Line 2624 (File "Y:\applications\32\driver_feed_mid_task.exe"): Error: Subscript used with non-Array variable
Answered 01/18/2012 by: binuani
Third Degree Green Belt

Please log in to comment
0
I don't use RSAs in my environment, every computer in my network hits the K2000 directly, even from across town.

I think I'd like some RSAs but I'm not prepared to "fight" for one.
Answered 01/18/2012 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment
0
I have come across an issue on an Optiplex 780 with a windows XP scripted install (x86).
During the driver feed copy to the local machine the copy does 80% or more of the drivers it then asks if I wish to overwrite the files (when it gets to network and storage). I have checked for duplicate drivers but have not found any in that directory. If I press A for ALL it continues if I press Y there are 11 drivers that it wants to overwrite.
Has anyone experienced this?
The 780 works fine with win7 x86 and x64 and 790, 5520 works fine with win7x86,x64 and winxp.
Another issue that may be worth mentioning on the 790 is that with the x64 win 7 when the 32 bit internet explorer is loaded it causes IE8+ to crash.
The issue is the ATI video driver.
To get around this I created a post install task of the ati driver I then opened the 32 bit IE8 browser and it worked.
Answered 02/02/2012 by: JonathonV
Blue Belt

Please log in to comment
0
I found the issue for my problem. The network and removable storage drivers were in the drivers and drivers_postinstall folder under feed>780>xp so I deleted the drivers for network and Removable storage from the Drivers_postinstall folder. This allowed the drivers to install correctly and also didnt prompt to overwrite.
Answered 02/02/2012 by: JonathonV
Blue Belt

Please log in to comment
0
I have come across an issue on an Optiplex 780 with a windows XP scripted install (x86).
During the driver feed copy to the local machine the copy does 80% or more of the drivers it then asks if I wish to overwrite the files (when it gets to network and storage). I have checked for duplicate drivers but have not found any in that directory. If I press A for ALL it continues if I press Y there are 11 drivers that it wants to overwrite.
Has anyone experienced this?
The 780 works fine with win7 x86 and x64 and 790, 5520 works fine with win7x86,x64 and winxp.
Another issue that may be worth mentioning on the 790 is that with the x64 win 7 when the 32 bit internet explorer is loaded it causes IE8+ to crash.
The issue is the ATI video driver.
To get around this I created a post install task of the ati driver I then opened the 32 bit IE8 browser and it worked.

RESOLUTION:

I found the issue for my problem. The network and removable storage drivers were in the drivers and drivers_postinstall folder under feed>780>xp so I deleted the drivers for network and Removable storage from the Drivers_postinstall folder. This allowed the drivers to install correctly and also didnt prompt to overwrite.
Answered 02/05/2012 by: JonathonV
Blue Belt

Please log in to comment
0
ORIGINAL: shotton

I get this exact error I have updated my mid level and post tasks to version .4 w7 x64 bit

Everything installs fine I just have this error stopping the install. Click OK and it goes past it :(



cserrins and I did a webex and found that I didn't have the a patch installed for the driver feed
found here btw:
http://www.kace.com/support/kb/index.php?action=artikel&cat=59&id=1103&artlang=en
While this would have been a crippling issue if I was using scripted installs, images don't really need it.
The whole issue was the kbox was still dropping in all of drivers in the beginning, fine for images, but the mid-level task couldn't find the drivers_postinstall folder.

Additional note: I had to delete the drivers I had in the driver feed, install the patch (which made my kbox reboot), reload the drivers, then check the 780 (dell optiplex) driver folder for a misplaced folder, that should belong in drivers_postinstall, that's known to throw and error.

Issue resolved, give it a try.
Answered 02/06/2012 by: Tentacle Master
Fourth Degree Black Belt

Please log in to comment
0
Hi Folks.

Just wondering if anyone knows if the RSA Driver Feed fixes are implemented into the latest K2000 build (v3.4.54256).
I tried viewing the release notes from the KACE downloads page for v3.4.54256 and the link is actually broken.

I wanted to know if the latest RSA updates include a driver share setup or something that would not require the driver feed workaround/manual sync.

Much Appreciated.

Three | David Wedrat
Ausco Modular
Answered 02/19/2012 by: three
White Belt

Please log in to comment
0
Hey all, thanks for all of the great work with the driver_feed its such a great feature of the KACE box!

I recently ran into a problem however. Out of the blue I can no longer write to my drivers_postinstall folder. I get the error message "Access Denied". I can view the items in the folder still, and I can still write to the drivers folder. I am unsure what happened to cause this. I haven't updated the KACE box since I've been able to write to the drivers_postinstall folder. I could really use another brain to give me some ideas on where to look for my issue. Just for info's sake the K2000 box is running on 3.3.52857.

Thanks in advance for any help you guys can give me.
Answered 02/20/2012 by: readmckay
Yellow Belt

Please log in to comment
0
3.3.52857 is quite a recent version that is only able to be updated from within the K2000 "check for updates" section.
I would try and reapply the driver feed patch. Or you could update to 3.4 by downloading from the support site But read the release notes before you perform the upgrade.
Answered 02/20/2012 by: JonathonV
Blue Belt

Please log in to comment
0
Is there anything I need to do to prep the system for reapplying the driver feed patch? Or just do it again?
Answered 02/20/2012 by: readmckay
Yellow Belt

Please log in to comment
0
Nope you can just apply the driver_feed_update.41702.bin file.
But read the doc on the driver feed workaround to download and for what to expect when applying it http://itninja.com/question/silent-uninstall-oracle-8-cilent9275
Answered 02/20/2012 by: JonathonV
Blue Belt

Please log in to comment
0
Thanks I will, and in case anyone is reading this from Dell, the release notes for the 3.4 update say the page is missing.
Answered 02/20/2012 by: readmckay
Yellow Belt

Please log in to comment
0
But I stand corrected you can actually download the update that you are on manually from the support site under downloads.
Answered 02/20/2012 by: JonathonV
Blue Belt

Please log in to comment
0
I just wanted to hop back on and say thank you very much. Reapplying the patch fixed my issue.
Answered 02/20/2012 by: readmckay
Yellow Belt

Please log in to comment
0
Since you applied an update, you will have to reapply the driverfeed patch. This will give you back the write access.
Answered 02/21/2012 by: cserrins
Red Belt

Please log in to comment
0
EDIT: I think I found my answer here http://www.kace.com/support/kb/index.php?action=artikel&cat=59&id=1142&artlang=en I should check the last page of search results for 3.4 problems (because they have the least number of views)!

I guess I'm missing something here.

When I go to the driver feed on the KBOX I find the model number and click Install Feed, and it creates the following folder \\kbox-name\windows_7_x64\feed\dell\790\790\win7\x64\ and only has the network drivers in this directory.

In drivers_postinstall I have two possible locations where things are located. I know one was the old way of doing things in 3.3. I have

\\kbox-name\drivers_postinstall\dell\windows_7_x64\790 and then all the drivers associated with the machine
and
\\kbox-name\drivers_postinstall\windows_7_x64\feed\dell\790\ and then all drivers associated with this machine

(I know one of these last two I dragged files from one folder to another for some troubleshooting purposes).

If I get rid of the driver feed workaround tasks from 3.3 in my workflow, which of these directories is the location that the kbox checks for drivers? And can I delete the other directories? From this article:
http://www.kace.com/support/kb/index.php?action=artikel&cat=57&id=1128&artlang=en

It looks like I just need to keep the \\kbox-name\drivers_postinstall\dell?
Answered 02/22/2012 by: eavalos
Senior Yellow Belt

Please log in to comment
0
Correy,

Its my understanding that the workaround isn't needed with scripted installs, how about images?

Are there new tasks for 3.4 to handle the new directory structure?
Answered 02/23/2012 by: dchristian
Red Belt

Please log in to comment
0
Where exactly do I put the drivers? I have scripted installs working with the dell driver feed. However I want to use WIM imaging and use the driver feed. Do I need to copy the drivers from the Drivers folder to Drives_postinstall folder? If so what folder do I need to put them in? I am trying to deploy win7 x64 to 755's with a WIM image and drivers post install.
Answered 02/29/2012 by: dheinle
Yellow Belt

Please log in to comment
-1
Here's the drivers_postinstall path change article that the original post talks about but does not link: http://www.kace.com/support/kb/index.php?action=artikel&cat=59&id=1142&artlang=en
Answered 03/13/2012 by: aggybong
Senior Yellow Belt

Please log in to comment
0
I have a quick question about the driver feed method of imaging. I have a machine that I know was missing the nic prior to the driver feed adding drivers. What I am trying to do is have the sysprep process join our domain during sysprep. Would the nic driver have been added to the workstation yet, or does this run after sysprep is done? If it's done after the imaging would I just join the domain as I have in the past using post installs?

Either way this is pretty awesome.
Answered 03/15/2012 by: ddevore
Fourth Degree Green Belt

Please log in to comment
0
Looks like I got it. I had a bunch of invalid driver install paths in the registry pointing to locations from my original scripted install of windows...


Dennis
Answered 03/15/2012 by: ddevore
Fourth Degree Green Belt

Please log in to comment
0
Do I still need to apply the Driver_Patch on a K2000 3.4.54256? I can't see the dir c:\kace\drivers_postinstall and I have the required mid level task and post install task.
Answered 03/22/2012 by: jaskelly3578
Orange Belt

  • Also I am trying to use this with the Native Imaging Toolkit.
  • Imaging an Optiplex 990 with Win7x64
  • No, you do not need to apply the Driver_Patch on a K2000 on version 3.4. Are you downloading the Optiplex 990 drivers via the driver feed? if so, they should be exactly where they need to be.

    Also, is the mid-level task after all of your WIM tasks? If not, you will need to move it.
  • Yes we are downloading via the Driver Feed and the mid-level task is after all the WIM tasks. This beats me as everything looks fine. Could it be because it is a WIM captured using the Native Imaging Toolkit?
  • That shouldn't keep it from installing. You could try kicking off the image deployment, but don't reboot afterwards. Once it's done deploying, try running the task manually from KBE and see if it does anything.
Please log in to comment
0

Hi Corey,

Just wondering - I am running K2 on 3.4 and the feed tasks thing is working a treat!
I did however go to drop 2008 R2 onto an Optiplex 790 and I cannot get the drivers_postinstall to be picked up.

I have tried the following paths:

\\kbox\drivers_postinstall\dell\windows_2008_x64\OptiPlex_790
\\kbox\drivers_postinstall\dell\windows_2008_x64\790

Can you shed any light on this?

Kind Regards,

David Wedrat
Ausco Modular

Answered 04/11/2012 by: three
White Belt

  • Did you create those folders or were they already there?
Please log in to comment
0

I have something strange happening, that I think might be related to the driver feed.  I have an image, that up until recently, worked fine on XT2 Tablets.  Image has standard software installed (Windows 7 Pro), plus some post install tasks - including a rename of the computer account, and joining the domain.

The device will image fine, but when I get to the login screen, I am not able to select any user, other than administrator.  I know the local admin password that was set, but it will not take it (Error -> The specified domain either does not exist or could not be contacted).

I know the script we use to join the domain, can do weird things to the local admin account if it is unable to join properly.  I am thinking that my network drivers are not loading on the XT2 model (NOTE:  I can run this image on an Optiplex desktop, or a Latitude Laptop - and it works fine).

I have removed the XT2 drivers, and re-installed, but still no joy.  Any thoughts on what else I should look at?

Answered 12/11/2012 by: hutcha4113
Second Degree Blue Belt

Please log in to comment
Answer this question or Comment on this question for clarity

Share