E6410 Broadcom USH Driver Control Point Win 7 32 bit.

Client and Mobile Solutions

Client and Mobile Solutions
Learn how to Deploy, Manage, Secure, and Virtualize Enterprise Client and Mobility solutions from experts and peers.

E6410 Broadcom USH Driver Control Point Win 7 32 bit.

  • I have a frustrating problem - don't we all right. Anyway, I am trying to set up an Image for del d6410 and there is one driver that doesn't seem to work correctly. It shows up sometimes as unknown device. Then when I go and update the driver it says the best driver is already installed. The Broadcom ush has a caution symbol under the control vault device. I installed the control vault manager, the control vault driver. It still didn't change the status. Then I uninstalled the USH and the "unknown device" using device manager. The driver finally looked good I said whew!. Then rebooted and now back to a caution symbol next to broad com ush. Any ideas?
  • "I have a frustrating problem - don't we all right. Anyway, I am trying to set up an Image for del d6410 and there is one driver that doesn't seem to work correctly. It shows up sometimes as unknown device. Then when I go and update the driver it says the best driver is already installed. The Broadcom ush has a caution symbol under the control vault device. I installed the control vault manager, the control vault driver. It still didn't change the status. Then I uninstalled the USH and the "unknown device" using device manager. The driver finally looked good I said whew!. Then rebooted and now back to a caution symbol next to broad com ush. Any ideas?"
    Are you sure it is the Broadcom USH device that is actually showing up? Did you already install the Free Fall sensor? That one always showed up for me as Unknown Device.
  • I made a little progress, it seems if I download the st microelectronics free fall sensor. I download and run the driver installer. But I think the problem is when SCCM tries to do the driver intalling its not installing it by the inf files. Before it says unknown device. So I tried to update it using the extracted driver files from the st microlectronics sensor file. When I try to do it. It says "the best driver is already installed" even when its unknown.
  • The drivers for the Broadcom USH are included in the Controlpoint Security Device Driver Pack.

    http://support.dell.com/support/downloads/download.aspx?c=us&cs=555&l=en&s=biz&releaseid=R269802&SystemID=LAT_E4310&servicetag=&os=W732&osl=en&deviceid=21539&devlib=0&typecnt=0&vercnt=1&catid=-1&impid=-1&formatcnt=0&libid=60&typeid=-1&dateid=-1&formatid=-1&source=-1&fileid=397318
  • The free fall sensor driver is the one needed. I have confirmed I have the right drivers. I can install from the driver inf files now instead of the executable. My problem now is that when I try to deploy the image through SCCM. The dell free fall driver doesn't apply. I can browse and update the driver, but it doesn't happen during the SCCM task sequence.

    As a side note: I downloaded the newest driver pack for the E6410. Is there a way to automatically update all the drivers? Or do I have to delete the drivers and then re import the new driver pack? I just don't want to get duplicates. Right now I have a00 driver pack. The newest is a93. Thanks for your help so far.
  • Try the new driver pack. I'm sure it has an updated free fall sensor driver and should address your issue. You can (and should) remove the old drivers from your driver store before importing the new ones, otherwise your driverstore will get bloated. Alternatively, you can skip your driver store altogether and place the extracted driver cab files directly into the driver package. This method makes for easier management in the future.
  • Thanks Can you tell me what the difference is with the driver store and the driver package? I thought you had to do both. First I created the package. Then imported the drivers. During the driver import it would ask which package that I wanted to put the drivers in. Is there another way to do it?
  • My whitepaper discusses the pros and cons between importing and not-importing.

    http://attachments.wetpaintserv.us/mDYE7bnRrlWoZizDORaazg857573

    I have a video that discribes the creation of a driver package from the Dell driver cabs without importing.

    http://delltechcenter.com/page/Client+Deployment

    Let me know if that doesn't clarify the two options for you.
  • Thanks thats the best explanation I've read and clears things up. I gues part of the confusion is there are so many ways to do it. I agree with the driver cabs without importing. I just didn't understand what was going on. Thanks for your help.
  • I am still working on this. Since we have several Latitude models. I am trying to download the combo driver pack. Its a zipped file. I tried to extract it and and error says its empty. Althought it shows over 500 mb size. Is the zipped file corrupted?

  • You are missing Dell ControlVault Driver (TPM drivers)


  • "
    You are missing Dell ControlVault Driver (TPM drivers)


    "
    Please verify the following:
    1.Cab file being used.
    2.Dell Model experiencing the issue.
    3.architecture being deployed (32 or 64-bit)

    Thanks,

    Warren
  • The splash screen for the security pack doesnt state win 7 enterprise as a supported OS. Anyone using Ent with this driver?
  • Yes, I've tested it with Win7 Enterprise.
  • I had the same problem, but the solution lies is the fact that Dell doesn't have "Broadcom" in the title or description for the driver you need.

    If you go to the device drivers page for the Latitude E6410 you'll find the "USH" in a description for a security driver.  In order to see the security drivers just select the "All related Drivers for your product."

    Here's what you need to download: