KACE Product Support

It sounds like you have firewall or IPS issues preventing proper communication to/from your K2100.

On a side note, you should probably avoid the driver feed anyway - all of the Dell models import a driver that causes an error during XP install. They are working on fixing this, but the driver feed is useless (for XP anyway) at this point.

the FW could be the problem, from which address could i expect the driver feed ? (?? service.kace.com:443 ??)
the Kbox is used for deploying windows 7 so i just want to give it a try. (doing an driver harvest from a pre-installed machine also does the trick offcourse).

The driver feed comes straight from Dell - at least that's what support told me. I don't know the exact URL, but you may want to submit a support ticket to find out.

The driver feed is a great idea (if it worked correctly).

I try to stay away from the driver feed and the harvesting.

I've found the safest way to handle the driver problem is to add all drivers as post-install tasks.

Driver harvesting works well, but it misses a few things from time to time. I've only had to resort to using post-install tasks for drivers for Intel chipset drivers - they are a pain and won't install themselves during Windows setup.

I agree the feed is an excellent idea - they just need to rip those RICOH media drivers out of there so Windows XP stops bombing out.

You would think that these sorts of things would be tested before they were released unto the wild. I am doing my first Win7 install with the driver feed tomorrow and hoping for better results than we had with XP.

ORIGINAL: airwolf

Driver harvesting works well, but it misses a few things from time to time. I've only had to resort to using post-install tasks for drivers for Intel chipset drivers - they are a pain and won't install themselves during Windows setup.

I agree the feed is an excellent idea - they just need to rip those RICOH media drivers out of there so Windows XP stops bombing out.

FYI- My biggest pain point has been mass storage drivers creating OS install conflicts. It's a great delivery mechinism for specific models, but personally I use the feed to download, then disable it and remove the drivers that cause conflicts. In reality the problem has always existed, we used to call it overharvesting- when folks uploaded every driver from every system and created the issue. Our recommendation is and always has been to upload to the driver repository only the specific drivers that you need; or use post install tasks to deliver your drivers as "driver packs". Driver packs are potentially much more efficient and less problematic because they're being delivered how the driver manufacturer intended (rather than how microsoft will allow it). Driver feeds were created due to demand- though we are working with the providers on cleaning out the known problem drivers. Please send your feedback to support as you encounter those issues though.

Drivers in a post-install task sound interesting, will take a look at that.
i noticed that not all of my machines are in the driver feed so for those it will be either post-install or driver harvest. (because some brands ship there pc's/laptops with a 32bit OS)

as i mentioned before i noticed not all of my machines are listed in the driver feed, are there any plans of adding more models to it?

i also checked some settings because of the error i have here:
ISP: not a problem
Proxy: not a problem (added the url's to the whitelist just to make sure)
FW: not a problem as port 80 and port 21 traffic will always pass thru.

does somebody have a great idea what the problem could be?

You would probably get a quicker solution by calling support on this.

ORIGINAL: petrybosch

as i mentioned before i noticed not all of my machines are listed in the driver feed, are there any plans of adding more models to it?

i also checked some settings because of the error i have here:
ISP: not a problem
Proxy: not a problem (added the url's to the whitelist just to make sure)
FW: not a problem as port 80 and port 21 traffic will always pass thru.

does somebody have a great idea what the problem could be?