Jump to content


  • 0
jeaostro

How to install Lenovo Software and Drivers with Update Retriever and SCCM during OS deployment

Question

Here is my solution for Lenovo Computers:

 

1.Install and configure Lenovo Update Retriever on a server. Lenovo has good guides for this where you download the software.

2.Download Thininstaller

3.Create a software package that contains the thininstaller files(my software packages is the POC0002D below, this package contains all the thininstaller files) You can download Thininstaller from the same place that you download Update Retriever.

 

Then do the following in the OS deployment task:

1. Under "Install Software" in the OS Deployment task, create a command line task that has the following command line:

cmd.exe /c xcopy.exe \\SCCMSERVER1\SMSPKGE$\POC0002D\*.* c:\lenovo\thininstaller\ /E /D -> With timeout 5 minutes or so.

2.Create a new command line task that has the following command line:

cmd.exe /c thininstaller.exe /CM -search A -action INSTALL -noicon -includerebootpackages 1,2,3,4 -repository \\TVSU-Server\tvsu -> With timout 120 minutes if you like to.

 

The computers is deployed with all the Lenovo drivers and software you specified in the update retriever software.

 

If you get a new Lenovo Model, just add the model to Lenovo Update Retriever and download the drivers/software with this tool.

No need to add lenovo drivers or Lenovo software to sccm.

 

best regards.

jeaostro

Share this post


Link to post
Share on other sites

Recommended Posts

  • 0

Are you using my methode of copying the "Thininstaller package"(sourcefiles) down to the client? and running the thininstaller locally from the client? with the task?

 

The copy is done by a bat file:

 

prepare.bat

---------------begin--------------------

xcopy "%~dp0*.*" C:\ThinInst /E /Z /Y /I

----------------end---------------------

 

The whole folder and files is copied so it doesn't matter if it's your method or another.

 

The next step, executing the command is yours. Just that I choose the option Timeout = 120 minutes in the run command-line.

 

EDIT: Ok it's working now. Thanks!

Share this post


Link to post
Share on other sites

  • 0

The copy is done by a bat file:

 

prepare.bat

---------------begin--------------------

xcopy "%~dp0*.*" C:\ThinInst /E /Z /Y /I

----------------end---------------------

 

The whole folder and files is copied so it doesn't matter if it's your method or another.

 

The next step, executing the command is yours. Just that I choose the option Timeout = 120 minutes in the run command-line.

 

EDIT: Ok it's working now. Thanks!

 

Good to hear :)

Share this post


Link to post
Share on other sites

  • 0

Good to hear :)

 

Ok we are testing Win7 to deploy and I'm also into the Thininstaller thing. It works when I launch the command-line manually but not through task sequence.

I saw in the c:\programdata\lenovo\%computername%installation.txt that all needed packages were installed but this is when it's done manually.

Every access is good but it doesn't install with TS.

 

It's Win7 ENT x64

 

*The copy is working fine. (to C:\Windows\ThinIsnt)

*The command-line I use is:

"cmd.exe /c thininstaller.exe /CM -search A -action INSTALL -repository \\10.156.253.14\drivers -noicon -includerebootpackages 1,2,3,4 -noreboot"

Starting in; "C:\Windows\ThinInst"

Time-out; 45 minutes

Run as user; domain\sccm administrator

Share this post


Link to post
Share on other sites

  • 0

I got more info from the smsts.log. I can't have a separated log file for ThinInstaller or maybe I don't know where it is :huh:

 

Start executing an instruciton. Instruction name: Run Thininstaller. Instruction pointer: 32 TSManager 11/10/2010 10:01:18 1816 (0x0718)

Set a global environment variable _SMSTSCurrentActionName=Run Thininstaller TSManager 11/10/2010 10:01:18 1816 (0x0718)

Set a global environment variable _SMSTSNextInstructionPointer=32 TSManager 11/10/2010 10:01:18 1816 (0x0718)

Set a local default variable SMSTSDisableWow64Redirection TSManager 11/10/2010 10:01:18 1816 (0x0718)

Set a local default variable _SMSTSRunCommandLineAsUser TSManager 11/10/2010 10:01:18 1816 (0x0718)

Set a local default variable SMSTSRunCommandLineUserName TSManager 11/10/2010 10:01:18 1816 (0x0718)

Set a local default variable SMSTSRunCommandLineUserPassword TSManager 11/10/2010 10:01:18 1816 (0x0718)

Set a local default variable WorkingDirectory TSManager 11/10/2010 10:01:18 1816 (0x0718)

Set a global environment variable _SMSTSLogPath=C:\Windows\SysWOW64\CCM\Logs\SMSTSLog TSManager 11/10/2010 10:01:18 1816 (0x0718)

Expand a string: smsswd.exe /run: cmd.exe /c thininstaller.exe /CM -search A -action INSTALL -repository \\10.156.253.14\drivers -noicon -includerebootpackages 1,2,3,4 -noreboot -log "C:\Windows\TVSULog.txt" TSManager 11/10/2010 10:01:18 1816 (0x0718)

Expand a string: TSManager 11/10/2010 10:01:18 1816 (0x0718)

Command line for extension .exe is "%1" %* TSManager 11/10/2010 10:01:18 1816 (0x0718)

Set command line: smsswd.exe /run: cmd.exe /c thininstaller.exe /CM -search A -action INSTALL -repository \\10.156.253.14\drivers -noicon -includerebootpackages 1,2,3,4 -noreboot -log "C:\Windows\TVSULog.txt" TSManager 11/10/2010 10:01:18 1816 (0x0718)

Start executing the command line: smsswd.exe /run: cmd.exe /c thininstaller.exe /CM -search A -action INSTALL -repository \\10.156.253.14\drivers -noicon -includerebootpackages 1,2,3,4 -noreboot -log "C:\Windows\TVSULog.txt" TSManager 11/10/2010 10:01:18 1816 (0x0718)

!--------------------------------------------------------------------------------------------! TSManager 11/10/2010 10:01:18 1816 (0x0718)

Expand a string: WinPEandFullOS TSManager 11/10/2010 10:01:18 1816 (0x0718)

Executing command line: smsswd.exe /run: cmd.exe /c thininstaller.exe /CM -search A -action INSTALL -repository \\10.156.253.14\drivers -noicon -includerebootpackages 1,2,3,4 -noreboot -log "C:\Windows\TVSULog.txt" TSManager 11/10/2010 10:01:18 1816 (0x0718)

=======================[ smsswd.exe ] ======================= InstallSoftware 11/10/2010 10:01:18 2884 (0x0B44)

PackageID = '' InstallSoftware 11/10/2010 10:01:18 2884 (0x0B44)

BaseVar = '', ContinueOnError='' InstallSoftware 11/10/2010 10:01:18 2884 (0x0B44)

SwdAction = '0001' InstallSoftware 11/10/2010 10:01:18 2884 (0x0B44)

Getting linked token InstallSoftware 11/10/2010 10:01:18 2884 (0x0B44)

failed to get the token information InstallSoftware 11/10/2010 10:01:18 2884 (0x0B44)

Get RunAs private desktop SMSTS-88936\SMSTSDesktop InstallSoftware 11/10/2010 10:01:19 2884 (0x0B44)

Run command line under a user account InstallSoftware 11/10/2010 10:01:19 2884 (0x0B44)

Command line for extension .exe is "%1" %* InstallSoftware 11/10/2010 10:01:19 2884 (0x0B44)

Set command line: Run command line InstallSoftware 11/10/2010 10:01:19 2884 (0x0B44)

Working dir 'C:\Program Files (x86)\ThinInstaller' InstallSoftware 11/10/2010 10:01:19 2884 (0x0B44)

Executing command line: Run command line InstallSoftware 11/10/2010 10:01:19 2884 (0x0B44)

Create a process under given user token InstallSoftware 11/10/2010 10:01:19 2884 (0x0B44)

Process completed with exit code 1 InstallSoftware 11/10/2010 10:01:39 2884 (0x0B44)

Command line returned 1 InstallSoftware 11/10/2010 10:01:39 2884 (0x0B44)

Process completed with exit code 1 TSManager 11/10/2010 10:01:39 1816 (0x0718)

!--------------------------------------------------------------------------------------------! TSManager 11/10/2010 10:01:39 1816 (0x0718)

Failed to run the action: Run Thininstaller.

Incorrect function. (Error: 00000001; Source: Windows) TSManager 11/10/2010 10:01:39 1816 (0x0718)

Sending status message . . . TSManager 11/10/2010 10:01:39 1816 (0x0718)

Send a task execution status message SMS_TSExecution_ActionFailError TSManager 11/10/2010 10:01:39 1816 (0x0718)

 

I see the line "Failed to run the action: Run Thininstaller. Incorrect function. (Error: 00000001; Source: Windows)" but I can't see more why it is in error?

Share this post


Link to post
Share on other sites

  • 0

Ok we are testing Win7 to deploy and I'm also into the Thininstaller thing. It works when I launch the command-line manually but not through task sequence.

I saw in the c:\programdata\lenovo\%computername%installation.txt that all needed packages were installed but this is when it's done manually.

Every access is good but it doesn't install with TS.

 

It's Win7 ENT x64

 

*The copy is working fine. (to C:\Windows\ThinIsnt)

*The command-line I use is:

"cmd.exe /c thininstaller.exe /CM -search A -action INSTALL -repository \\10.156.253.14\drivers -noicon -includerebootpackages 1,2,3,4 -noreboot"

Starting in; "C:\Windows\ThinInst"

Time-out; 45 minutes

Run as user; domain\sccm administrator

 

 

If it works manually then you know the syntax is right. But you do not need to enter "run as user"?? It will run as the system user by default.

Share this post


Link to post
Share on other sites

  • 0

Working dir 'C:\Program Files (x86)\ThinInstaller ???

Do you copy the thininstaller files(already extracted?) or the thininstaller.exe installation file?

Have you tried to copy it to c:\Lenovo\

 

Create a task for the thininstaller step(copy and run), and then advertise this task to an up and running computer. then you dont waste so much time doing an OS deployment every time you try and fail.

Share this post


Link to post
Share on other sites

  • 0

Working dir 'C:\Program Files (x86)\ThinInstaller ???

Do you copy the thininstaller files(already extracted?) or the thininstaller.exe installation file?

Have you tried to copy it to c:\Lenovo\

 

Create a task for the thininstaller step(copy and run), and then advertise this task to an up and running computer. then you dont waste so much time doing an OS deployment every time you try and fail.

 

I tried by copying the whole extracted ThinInstaller folder to "Program Files (x86)" but now I'm copying it to '%systemdrive%\ThinInst'.

 

Did you ever ran this successfully in Win7 x64?

Share this post


Link to post
Share on other sites

  • 0

and what did you do to solve it ?

 

I tried a lot of thing on 3 days but finally I managed to see through the smoke :rolleyes:

 

What was failing was that the network share isn't accessible because the program (egather) is using the framework library. For that you must set a rule like %WINDIR%\Microsoft.NET\Framework\v2.0.50727\CasPol.exe -pp off -m -ag 1.2 -url file://\\server\share\ FullTrust

 

(Also I did it on ip address and not on netbios name)

Share this post


Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...



×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.