locked
nic drivers inf RRS feed

  • Question

  • Hello,

    I'm using the Apply Driver Package step in the task sequence to apply my drivers.

    In our envirnment I need to set our nic speed on each computer manually to 100 Full.

    So in the past I manually set this after deployment. What I would like is to have this pre set for me so that I don't have to make this change. So what I have tried is to go into the inf file associated with the driver and change it to default at 100 Full. After I make the change on the source inf file, I update the distribution point.

    Unfortunitally this setting does not stay because after my osd completes the setting is back to Auto.

    Does anyone know why this would be happening?

    Thanks,

    Shawn

     

    Friday, June 10, 2011 4:13 PM

Answers

  • Really? Not to go off on that tangent, but that is obviously sub-optimal and against best practices as you shuld be configuring it on the switch side if necessary and leaving the client devices on Auto,

    However, you can use regmon to identify the stting in the registry that is updated when you make this chnage and then deploy this registry change during the deployment. It may have to be scripted though because the registry key, to the best of my recollection, is relative to the NICs registry keys.


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Friday, June 10, 2011 6:10 PM

All replies

  • Really? Not to go off on that tangent, but that is obviously sub-optimal and against best practices as you shuld be configuring it on the switch side if necessary and leaving the client devices on Auto,

    However, you can use regmon to identify the stting in the registry that is updated when you make this chnage and then deploy this registry change during the deployment. It may have to be scripted though because the registry key, to the best of my recollection, is relative to the NICs registry keys.


    Jason | http://myitforum.com/cs2/blogs/jsandys | Twitter @JasonSandys
    Friday, June 10, 2011 6:10 PM
  • Thanks for your reply.  The other techs and I have been asking why our network was setup like that in the first place but unfortunately we were overruled.

    I will give the regmon tool a try.

    Thanks again for your reply.

    Shawn

    Friday, June 10, 2011 6:53 PM
  • Setting a hard speed might be the only Soloution and there is a free software (penetcfg) on the net that can solve at least parts of it.

    However this will give another problem if you got roaming computers. With a hard set speed the Clients will work well with a switch that is hard set to the same speed and duplex values. However if you connect the client computer to another switch wich is set to Auto you will get a performance impact since most switches will take a failed Auto negotiation as a sign of a hub and therefore they will set the speed to 10 or 100 half-duplex.

    Therefore it is a lot better if this can be handled on the switch side. Since I got Cisco stuff in my network I know that they can do it with their auto (speeds) command.

    We ran into this situation  a few years ago when we uppgraded some of our switches. The old ones there 100Mbit but the new one where Gbit capable, Since the client computers also where capable of Gig speed the auto speed setting made them go for Gig speed. Unfortunally the cabeling was old IBM type1 cables. Type1 can not do gig speed so we got a lot of network problems, anything from not getting an IP to corrupt files and so on.

    We filed a Case to both MS and Cisco to work with them so that we could get a stable and supported soloution. MS Gave us a "By design" answer but Cisco came up with the option to set a max speed for auto in their switches. We have used that solution since then for "slow" cables.

    If you still need to do it client side there are a few options. One is penetcfg wich is a free utillity to set nic speeds. Another one is to write your own code for this. A simple version is to make a Config file (ini) that contains the right registry keys and values for each make and model of Computer you have. Then create a script that will detect the make and model of the computer, read the right values from the ini and apply these values. The downside is that the ini will need to be maintained.

     

    Monday, June 13, 2011 7:43 AM