Client Management Suite

 View Only

  • 1.  DeployAnywhere Intel NIC Drivers

    Posted Feb 17, 2012 08:21 AM

    Has anyone seen this issue and has a solution that will allow me to continue to use DeployAnywhere?

     

    I have a HP Pro 4000,and a Win7 X64 image.

     

    When deploying with DA, it fails due to missing critical drivers. The DA eval output is:

     

     

    Missing critical driver detected : 
    type =  NETWORK DEVICE
    PCI ID = PCI\VEN_8086&DEV_1525&SUBSYS_1493103C&REV_02
    Desc = @oem17.inf,%e1525nc.devicedesc%;Intel(R) 82567V-4 Gigabit Network Connection
    Inf Source = Windows InfDirectory
    Inf File = 
     
    However, I have the latest Win 7 x64 driver for this in the DriversDB, and also imported the direct download from Intel for the Pro/1000 drivers.
     
    Here is the Drivers Manifest for the driver that should be picking this up:
     
    {
        "Intel.e1kexpress.11.6.92.0_7" = {
            class = network,
            drivers = ({
                path = "Intel.e1kexpress.11.6.92.0_7\\E1K62x64.INF",
                devices = {
                    0x8086 = {
                        0x10de = (0x1408103c 0x143e103c 0x1489103c 0x3648103c 0x3647103c 0x3646103c 0x3048103c 0x3036103c 0x3035103c 0x3034103c 0x10de8086 -0x1),
                        0x10df = (0x10df8086 -0x1),
                        0x10ea = (-0x1),
                        0x10ef = (0x304b103c 0x304a103c 0x3049103c -0x1),
                        0x10f0 = (-0x1),
                        0x1525 = (0x1493103c)
                    }
                },
                os = ("X64_2008_R2" "X64_WINDOWS7"),
                architecture = (X86 AMD64),
                files = ("e1k62x64.inf" "e1k62x64.sys" "e1k62x64.din" "nicco36.dll" "nicinstk.dll" "e1kmsg.dll" "e1k62x64.cat"),
                warning = file_warning
            }),
            internal = 0
        }
    }
     
    As you can see from above, everything is matching 100%, however it is seeing that REV_02 on the eval scan, and thinking that the driver is missing because it is not listed in the drivers manifest file.
     
    Is there any way to duplidate the "0x1525 = (0x1493103c) line?  any way to add a wildcard there so if the 1525 matches, it ignores anything afterwards?
     
    I am working on a new image where i use pnputil to inject the driver, however, Id rather have a single image that can work on any hardware via using DeployAnywhere.
    (maybe I uncheck DA in the deploy image task, but then run a script in automation that does the same thing but ignores any missing drivers? - any idea on this?)
     
     
    Thanks!
     
     
    NOTES: Latest version of CMS 7.x, with the latest Service packs and fixes.


  • 2.  RE: DeployAnywhere Intel NIC Drivers

    Posted Feb 17, 2012 08:38 AM

    Currently attempting a re-image with the 0x1525 line changed to -0x1.

    My guess is that is the same as a wildcard, as other versions of this same driver (Intel  E1K) use that for the exact same 0x1525 line (32 bit Win 7, 32bit Vista, etc).

     

    I will report back if that ends up being the solution!



  • 3.  RE: DeployAnywhere Intel NIC Drivers

    Posted Feb 17, 2012 09:33 AM

    no dice on messing with the manifest files :/

    Time to see what DeployAnywhere does with a eval on a tower that is already setup properly.  Maybe I can then take that image as it will see the drivers already populated in C:\windows\

     



  • 4.  RE: DeployAnywhere Intel NIC Drivers

    Posted May 02, 2012 08:41 AM

    From time to time, I've also trouble with drivers in DeployAnywhere.
    The drivers ini-files from the Hardwarevendor (e.g. HP, Dell) are manipulated. Altiris can't use these files without changing the ini-files.

    What you can do, get the drivers from the NIC vendor (Intel, Broadcom).
    Add this drivers to deployanywhere and it will work.

    Hope it helps.



  • 5.  RE: DeployAnywhere Intel NIC Drivers



  • 6.  RE: DeployAnywhere Intel NIC Drivers

    Broadcom Employee
    Posted Jul 10, 2012 07:14 AM

    Looking at manifest files contents which you have copied , i could see there is a Warning specified ; this is a warning for a driver files ; check and make sure you have appropriate driver source files [Check :

    http://www.symantec.com/business/support//index?page=content&id=TECH187749&actp=RSS]

    Just to mention other reasons why it gives warning message :

    • There are some driver files are missing which are mentioned in the driver inf file
    • Files which are copied are corrupted
    • Driver files are not signed
    • Driver files has inappropriate extension

    I recommend to download the driver and import again.

    Also if it is possible can you provide that driver source files here , so that we can check and find out the exact reason for the failure.