jeaostro

It is a Dell Latitude E4200

So this should be right: I installed DCSU on a Dell computer, started the application, changed the settings on the client, and saved a settings.xml fil to the desktop on the client. Then I copied this file to the DCSU source package on server, and updated the distribution point. In the task sequence I install DCSU, then a new step to copy the settings.xml from the distribution point the the "%ProgramFiles(X86)%\Dell\ClientSystemUpdate\ The Dell step starts in the task, but it failed after a couple of minutes(error code =2 restart required) because an Audio driver requires a restart of the computer(it says so from the dell log in windows\temp). This was not an issue with HP or Lenovo because the computer restarts after all packages are installed.

Thanks a lot for this:) I will give this one a try, my way only works for the gui client, not command line. So if I understand you right, you do not need to run dcsu-cli.exe with the /catalog \\server\repository\catalog.xml because this is specified in the settings.xml? And you enter the server\catalog.xml information in the gui client before you export the settings? For 64bit computers I guess dcsu-cli.exe should start in: %ProgramFiles(X86)%\....

Okay Thank You.

Nice Do you have some sort of "how to" for the Dell Solution? I have used the Dell Repository Manager (Client), and exported all the updates for my models from the ftp.dell.com (with the gui) to a local repository, then saved my local repository. So I have some folders with drivers in the local repository with a catalog.xml When i try to run the client on a computer with dcsu-cli.exe /catalog \\server\dellrepository\catalog.xml it just gives me an error when the download starts If I run the DCSU in gui, and configure it to go towards the local repository it works. The problem is the command line client.. Thanks for the response

Hello Have you tried DCSU+Dell Repository manager? Install and Launch DCSU with commands during OS deployment, and point it to the Local Dell Repository Manager driver share. Just like Lenovo Thininstaller and Lenovo Update Retriever.

hehehe, nice to see you got it working :-) the status "test" is a fun one, done the same a couple of times In the settings change that the default is not test but active.

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.

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.

The problem here is the network. You can use Mtools (mdump and msend) to test if the network is working with Multicast. With us it doesn't work running test 3-4-5. It cant handle the speed. http://www.29west.com/docs/TestNet/initial-five.html

Good to hear

We can multicast yes, but only at the 10Mbit profile(remember when changing profile you will need to change it in both SCCM and in the registry for the WDS Multicast). We are going to use Mtools to test if this is a Network issue. If it is not a network issue we will set up a WDS server to se if the problem might be SCCM og WDS.

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?

So what you are saying is that it works when you us IP but not when you use the server name? DNS issue?

Just to be sure, you have entered the correct type number of the computer(for example 2055), selected the correct OS language and version? Could you try this on a computer that has almost none drivers or Lenovo Applications? From the client, when you type \\youserver\yoursharedtvsu you see all the packages?

Please try to copy the thininstaller application to a computer running windows. open cmd and go to the folder where you have thininstaller, and run the following: thininstaller.exe /CM -search A -action INSTALL -includerebootpackages 1,2,3,4 -repository \\youserver\yoursharedtvsu folder also make sure the packages are status "active" and not "test" on the Update Retriever, you can change this from the update view in update retriever. Do you get any errors then? Firewall rules?

I think those are the Microsoft updates, and not sure how they can be silent because you have to read and approve the license. Do a quick google search and maybe someone has solved this. I dont push these out with Update Retriever.

Hello Working now?

Also in the "start in section" it should say: c:\lenovo\thininstaller\

:Access to the path '\\10.55.65.5\tvsu' is denied Can the application access this path? Try sharing it and set everyone for read as a test.

Hello We are also working on Multicast between VLans and i will post a "how to" as soon as we are done. We can see that all the packages are going from the server to the client, the network card on the client is working hard(led blinking), but the client wont "read" the packages or do anything with them. Our scenario is almost as posted above.

You can have multiple repository shares, even use a local harddrive connected to a server.

Hello anyweb This is my new central site server, and the SQL is on the same server. There are no errors, only a warning. It looks like Volume Shadow Copy kills all the SCCM services, and they cant start again. And the event viewer is flooded with "SMS_EXECUTIVE service error", only a reboot helps. "Warning: Backup location and the sms sql data/log files are on the same volume. Sms Backup creates snapshot of the volume using VSS services and then copies the data to the backup location. It is advisable to have the backup location on a different volume (different than the one that has SMS data and SMS database files), so that the writes to the volume is minimal when the volume snapshot is active." Backup task completed successfully with zero errors but there could be some warnings, AFTERBACKUP.BAT will be started if available in its predefined location. Unable to initiate AFTERBACKUP.BAT. This file does not exist at its predefined location

and the attached file

Hello Got a problem with the backup. After it completes the SCCM Central site stops working?? And the event log is flooded with the following: "A timeout (30000 milliseconds) was reached while waiting for a transaction response from the SMS_EXECUTIVE service." Also on the attachment you can see that almost every service is stopped, and when trying to start it the service just "hangs". The only solution is a reboot of the server. The central site is a Windows Server 2008 64 bit, with MS SQL 2008 SP1 64 bit.