counter hit make
Configmgr 2007 OSD : Using Lenovo Update Retriever to install all your drivers without importing them in the ConfigMgr driver catalog - sccm

SCCM - System Center Configuration Manager

Blog about SCCM 2007 aka SMS v4

Recent Posts

Tags

News

Community

Email Notifications

    Blogs

    Archives

    Configmgr 2007 OSD : Using Lenovo Update Retriever to install all your drivers without importing them in the ConfigMgr driver catalog

    Did you also think that driver management  in OSD could be more simplified ? For example when you have Lenovo devices , you need to also install a lot of “bad” drivers en also in a very specific way or features such as “hotkeys”does not work .Let’s look at the process right now:

    1. Search drivers from the internet manually

    2. Unpack them in a correct folder structure

    3. Import drivers and categorize

    4. Handle duplicate drivers

    Problems often seen :

    1. Not all drivers work with the import ( there are drivers that simply do not work with the export method , they need to run thru setup.exe ) HP is a king in that area with the sound card & Quick launch buttons. This means that the admin need to create packages , programs and multiple steps in the TS to let it work.

    2. For getting some drivers you need to install the vendor msi on your test laptop , go to the install folder and find the extracted drivers there.After that you could import.

    3. HP & Lenovo needs certain additional software such as HP quick launch , HP power manager , Lenovo Hotkeys , Lenovo think vantage , etc . A lot of those packages needs to be installed in a very specific order or it just don’t work .

    4. You test your deployment and damn it seems you forgot 2 drivers . Find out by HWguid , download and import again …

     

    Lenovo Update Retriever – Thinstaller solution :

    If you don’t want to spent hours on searching, downloading and importing drivers for you LENOVO computer when going to build a Win7 image , read on . I have found a better way to accomplish this with thanks to Karel Serroels.

    It normally takes so much time for an admin , while with the HP / IBM solution it is a 5 minutes job per HW model :

     

    1. Install and run the Lenovo update retriever, select your model and software /drivers you want to install , download the drivers into a pre-defined file share . Nice , quick and easy .

    2. Create a package with the Lenovo Thinstaller source files , copy the Lenovo Thinstaller files to the local disk & run it thru your TS

     

    The advantage here is that I as an admin does not need to worry about the right install sequence , prerequisites , number of needed drivers or even OS type .The Thinstaller tool will do it for you .

    Prerequisites :

    Get the following software’s online from the Lenovo site as you will need it

    1. Link thininstaller: http://www-307.ibm.com/pc/support/site.wss/TVAN-ADMIN.html#ti
    2. Link update retriever: http://www-307.ibm.com/pc/support/site.wss/TVAN-ADMIN.html#ur

     

    Step 1 : Install Lenovo Update Retriever on your server and follow instructions to create a share for the repository , etc .

    image

    Step 2 : Launch the Lenovo Update Retriever and select your Model an Operating System. Download all files to the repository.

    image

    Step 3 : Modify your Task Sequence and add Run Thinstaller Trustzone. It needs to work with Dot.net 2.0 .

    If you run Lenovo Thinstaller via Configuration Manager task sequence , you cannot run the installation program, because it is a .NET executable and the default policy is to disallow running it from a network share or distribution point. You must therefore change the  following ipadress and sharename with the one from your environment!

    image

    Step 4 : Create the Lenovo thinstaller package in Configuration Manager.

    image

    Step 5 : Copy the Lenovo Thinstaller directory to C:\Windows\Thinstaller

    image

    Step 6 : Run Thinstalle with the following commend line . You must therefore change the  following ipadress and sharename with the one from your environment!

    image

    Step 7 : Remove the Thinstaller source files . Do a nice cleanup .

    image

     

    There you go .. The only disadvantage from using this , is the fact that your sourcefiles need to be always to one spot . You can solve this by using Sysvol , DFS or other technologies . However , Most companies have a team that will build the initial image on site and than replicate the images across the company .

    Hope it helps ,

    Kenny Buntinx.

    Comments

    Inflixi said:

    Hi, nice guide.

    Can you explain a little about what you have in your prepare.bat file?

    Also, is there a reason that you are using IP address instead of server name?

    # March 3, 2011 12:54 PM

    Svenn said:

    Hi, very nice guide (again)! I'v been using Update Retriever for many months now and are very happy with it. Goodbye driver headaches!

    What is step 3 doing? Cause I'm running it without this step and it works perfectly without it.

    I would have added this to the guide: Mark all BIOS and MICROSOFT kb updates as "test" packages so that they don't run/install during the task sequence. The MS packages can't be run silent because of licensing issues. I'v tried some BIOS updates during TS but all have failed. I'm not sure why though.

    We are using a 3rd party WAFS acc solution with DFS and it works well with our DFS shares and cache.

    \Svenn-Erik

    # March 4, 2011 8:03 PM

    rakkah said:

    Awsome post!

    You say that it's a five minute job with the HP solution aswell, can you please explain this also?

    # June 12, 2011 9:16 AM

    rtruss said:

    This is a GREAT post as we are a big lenovo shop!

    One problem is we cannot use sysvol and do nto have a DFS setup.  Is there a way to use a variable instead of an IP or server name as noted in step 6?  We plan to use ConfigMgr to replicate out the update retriever source that way.

    # January 10, 2012 6:47 PM

    rtruss said:

    The links at the top of the post do not work.

    Thinstaller:

    support.lenovo.com/.../detail.page#ti">support.lenovo.com/.../detail.page

    Update Retriever: support.lenovo.com/.../detail.page

    as you can see by the URLs they are attempting to sunset those applications (Again I might add.)

    # January 10, 2012 6:55 PM

    rtruss said:

    Lets try those URL's again:

    Thinstaller:

    "support.lenovo.com/.../detail.page

    Update Retriever:

    "support.lenovo.com/.../detail.page

    # January 10, 2012 7:24 PM

    Ben_Unic said:

    What could be the reason if thininstaller doesn't install all the drivers?

    # January 31, 2012 4:58 PM

    Sandman2672 said:

    I have had to go in and remove the prereqs or dependencies to get some software to install like the APS hard drive software for laptops. Sometimes I break the install into two thininstaller runs so I can reboot. It needs some enterprise capabilities but you can work with it.

    # April 27, 2012 2:21 PM