Jump to content


IT-Hilger

Established Members
  • Posts

    21
  • Joined

  • Last visited

  • Days Won

    3

Posts posted by IT-Hilger

  1. Quote

    This is awesome. This may literally change my life =D Driver management in SCCM is a bear.

    The %OSDisk% variable is working for me but I had to add a trailing backslash right after the % because DISM is expecting C:\ and %OSDIsk% is stored as C:

    DISM.exe /Image:%OSDisk%\ /Add-Driver /Driver:.\ /Recurse

    Nice that you're happy with the solution.

    And thanks for your hint, think this might help somebody.

  2. Hello,

     

    I followed the instructions exactly but drivers do not install. The only error I can see in the smsts log is a network error due to the network driver not installing: (sending with winhttp failed; 80072ee7 TSManager 11/23/2016 9:45:42 AM 704 (0x02C0)). Is there something I should specifically look for in the smsts log? I assume either the Task Sequence Variable or DISM command line is the issue but nothing in the log points to that as far as I can tell.

     

    Thanks,

    Mike

     

    Hi Mike,

     

    can you create a TS from scratch and test it there?

     

    BR

  3. just wanted to chime in on this thread because it's something i'm testing in my lab. unfortunately, the task sequence variable doesn't seem to be working at all for me. however, dism.exe /image:c:\ DOES work. i've tried setting a variable in the partition and apply OS steps and using that same variable with dism but that made no difference. i also tried going the same route in OP's guide by adding a task sequence variable step separately and that didn't work either. i am on 1602. hopefully someone is in the same boat?

     

    don't know why task sequnce variables generally aren't working in your environment.

    But why must you use them? If a hardcoded "c:\" is working for you...

  4. I've been trying to do this method and during the task sequence I can see the drivers download, then they act like they are installing. When the task sequence eventually fails and the computer reboots none of the drivers are installed on the system.

     

    This is an HP Elitebook 840 G3 deploying Windows 7 - The environment is SCCM 2012 R2 ( I do not have SP1 installed yet).

     

    The problem is I can't even copy the logs, since no drivers are installed I can't even use a USB key to get to the log, network isn't loaded so I can't copy via network. I have to try and open the log in wordpad.. and you know how that is.

     

    Any thoughts, suggestions? Please help.

     

    Thanks

     

    Hi,

     

    did you completely follow the guide?

    Did you extract the drivers in the source folders, so that you have the .inf, .cat, etc. files?

     

    BR

  5.  

    Maybe you can help me get this working right. I am trying to push Windows 10 to an old Latitude E6420 (a random test system I have laying around). Everything almost works perfectly, but 4 drivers fail to install.

     

    The last driver pack from Dell for that laptop was for Windows 8, and those are the drivers I am attempting to use... I know they work just fine on Windows 10 and can easily update the driver using Device Managers an point to the drivers in my SCCM reposistory. I can post any logs or screenshots to help figure it out. It is driving me nuts.

     

    Hi,

    have you installed the latest CU Packs for ConfigMgr? (SCCM 2012 R2 SP1 CU2)

    and are you using the latest version of MDT? (2013 Update 1)

     

    I did the test with a Latitude E6320 - so almost the same device - and was also using the Windows 8 driver pack from Dell.

     

    BR

    • Like 1
  6. I hate to bump an old post but I found this extremely useful. I think I much prefer this to the native driver package model in terms of manageability - it's a lot cleaner to import and update driver packages. Thanks very much for the guide!

     

    One thing though - I had issues with dism working until I removed the backslash off the driver path:

    DISM.exe /Image:%osdisk% /Add-Driver /Driver:. /Recurse

     

    Hi Max,

     

    thanks for your comment!

    Great that this solution also works for you. Don't know why you have to remove the trailing backslash, it's working in our environment.

    And good idea with %osdisk% variable. Maybe I'll change it in our environment, too.

     

    BR

    Achim

  7. Hi,

     

    if you could help me to creation of package for .exe drivers that will be great, because while driver importing it doesnt take .exe drivers.

     

    regards;

    Sant

     

    Hi Sant,

     

    thats different from (exe) package to package.

    You must try to extract them and then use the .inf, .sys and .cat files.

     

    You can try to extract the .exe with 7zip for example.

     

    If this doesn't work, run the .exe and wait at the first dialog of the .exe program and don't click next.

    Then open the %temp% folder on the pc and have a look inside the last modified folder in %temp% folder.

    I think you should find the extracted driver files there.

     

    BR

    Achim

    • Like 1
  8. Yes, I cant get this to work. I have Lenovo machines, when I go and use the windows 7 dvd as an install source and it comes to this section I get no IP for my nic card and it fails.now it cant be a driver issue with winpe cause I made it to the apply drivers section.

     

    Hi Jeff,

     

    after which step you get stuck with no IP adress?

    In WinPE phase or after applying the Windows image?

  9. Hi! This is a very good idea! I love it! Thanks! I hate the driver repository integrated with ConfigMgr out-of-box. For this winroot thing: In "Patition Disk" step you can set OSDisk. For dism use

    dism.exe /Image:%OSDisk%\ /Add-Driver /Driver:.\ /Recurse

     

    What I cound'nt find: What means success code 2 50? Can you explain? Thanks!

     

    Hi Dietmar,

     

    nice to hear, thanks. Nice idea with OSDisk variable!

    DISM sometimes gives return code "2" or "50". By default, SCCM TS just takes "0" and "3010" as success codes.

    When you don't add the return codes 2 and 50 as success codes, the apply drivers works fine, but SCCM thinks that there was an error because it doesn't know that this return codes also mean success.

  10. I am having the same issue on my site. I also installed ConfigMgr to the D:\ drive and not C:\. I have tried editing the 2 files: InstallUtil.exe.config and regsvcs.exe.config located in: C:\Windows\Microsoft.NET\Framework64\v4.0.30319

     

    I used Visual Studio 2010, as well as an attempt with Notepad to edit these files to include the lines stated above. Here is the regsvcs.exe.config

     

     

     

     

     

    After doing this i tried both restarting the SMS_SITE_COMPONENT_MANAGER windows service as well as reinstalling the MP (I have a small environment with 1 site server, which serves all roles). The MP installs just fine, and MPsetup.log shows no errors. Once the MP is finished installing the BGBsetup kicks off, this is where i begin to see errors.

     

    Here is an error from BgbSetup.log:

     

     

     

    I have restarted the services, reinstalled the MP, rebooted the server....still no such luck. The SMS_NOTIFICATION_SERVER component still reports that the server failed to connect to the site database. Does anyone have any ideas for me? Any help is greatly appreciated! Thank you

     

    We also tried the above solutions but they didn't help.

    In our system the problem was a corruption in Windows performance counter library.

     

    Run this command in an Administrator CMD:

    cd C:\WINDOWS\system32
    
    lodctr /R
    

    You should see a success message after the above command.

     

    Then restart SMS_SITE_COMPONENT_MANAGER and see if it works.

     

    BR

    Achim

  11. Hi Everybody,

     

    this thread is for those who want the old SCCM 2007 driver management back.

    Normally you have to import every driver to the database first, put them into a driver package, and then deploy them during OSD.

    In SCCM 2007 you could easily create a Driver Package from your Driver Source Folder and apply this Driver Package during OSD.

    This way of Driver Management was much easier and more reliable than the new way in SCCM 2012.

     

    But luckily there is still a method to prevent importing drivers into database and directly distribute driver packages to your clients.

     

    Step 1

    Download drivers for your brands and models.

    Put them into seperate folders - one folder for one model - like you did in SCCM 2007

     

    post-24205-0-69833100-1403683770_thumb.png

     

    Step 2

    Create a Package for each model and operating system. Then distribute this packages to your DP.

     

    post-24205-0-99845800-1403684096_thumb.png

     

    post-24205-0-02203500-1403684101_thumb.png

     

    Step 3

    Create a Step "Set Task Sequence Variable" under your Auto Apply Drivers Group (after the Apply Operating System Step) in your Task Sequence.

     

    Task Sequence Variable: winrootdir

    Task Sequence Value: D:\

     

    Condition: If Folder "D:\Windows" exists

     

    I created a second step after this with Drive Letter E:\. Because on some Notebooks the Systemroot is E:\ during OSD.

     

    post-24205-0-30412000-1403684788_thumb.png

     

    post-24205-0-87966600-1403684788_thumb.png

     

    Step 4

    Create TS Steps for each model to apply the driver package.

     

    Type: Run Command Line

    Command line:

    DISM.exe /Image:%winrootdir% /Add-Driver /Driver:.\ /Recurse
    

    Package: Choose the corresponding package you created in step 2

     

    Success codes: Add 2 and 50

    Condition: WMI Query (here an example for Dell Latitude E7240)

    select * from win32_computersystem where Model like "Latitude E7240%"
    

    post-24205-0-32635100-1403685338_thumb.png

     

    post-24205-0-80516300-1403685338_thumb.png

     

     

    Repeat the steps above for each computer model you want to image.

    With this way of applying drivers we have 0 problems in our environment. Very easy and reliable.

     

    BR

    Achim

     

    If you have questions - feel free to contact me http://ithilger.de/kontakt

    • Like 2
×
×
  • Create New...