This post is more than 5 years old
2 Posts
0
11663
January 25th, 2012 04:00
after reading dell materials, how should i keep dell pcs updated with missing drivers
Hi,
I have read and even setup Repository manager, and DSCU,
it's not working the way it should,
the dscu-cli reboot whenever it wants too, there's no place to control reboots, even in policy xml file if i set False
it still reboots,
also it fails on 99% of the updates, and it also re-downloads the same ones (that "lucky" for me are the ones that need reboot)
Download succeed log:
- < LogEntry >
< level > Normal level>
< timestamp > 2012-01-25T07:32:56.350701-05:00 timestamp>
< source > Dell.ClientSystemUpdate.CLI.Program.DisplayMessage source>
< message > CLI: Download Success: R311171 (Driver) message>
< trace />
- < data >
< Type > Download Type>
< ReleaseID > R311171 ReleaseID>
< Name > INTEL UNIFIED AMT 7 MANAGEMENT INTERFACE DRIVER Name>
< Version > A02 (7.1.20.1119) Version>
< Criticality > Recommended Criticality>
< Date > 11/1/2011 9:08:39 AM Date>
< UpdateType > Driver UpdateType>
< Category > Chipset Category>
< Status > Success Status>
- < LogEntry >
< level > Normal level>
< timestamp > 2012-01-25T07:33:26.4319354-05:00 timestamp>
< source > Dell.ClientSystemUpdate.CLI.Program.DisplayMessage source>
< message > CLI: Installing update (2 of 6)... message>
< trace />
< data />
LogEntry>
- < LogEntry >
< level > Normal level>
< timestamp > 2012-01-25T07:33:27.1808458-05:00 timestamp>
< source > Dell.ClientSystemUpdate.CLI.Program.DisplayMessage source>
< message > CLI: Install Failed: R311171 (Driver) message>
< trace />
- < data >
< Type > Install Type>
< ReleaseID > R311171 ReleaseID>
< Name > INTEL UNIFIED AMT 7 MANAGEMENT INTERFACE DRIVER Name>
< Version > A02 (7.1.20.1119) Version>
< Criticality > Recommended Criticality>
< Date > 11/1/2011 9:08:39 AM Date>
< UpdateType > Driver UpdateType>
< Category > Chipset Category>
< Reboot > No Reboot>
< ExitCode > 10 ExitCode>
< Status > Failed Status>
data>
LogEntry>
it feels like a stupid cycle, because this is just an example it happens to all documents,
it's does not feel like a manageable solution.
i have a fully functional SCCM 2007 R3 environment,
is there any other way recommended for me to update dell drivers during operating system deployments?
No Events found!
DELL-Warren B
1.1K Posts
1
January 25th, 2012 07:00
Since you have a ConfigMgr infrastructure, the Dell recommended way would be to use the Dell Updates Catalogs with ConfigMgr via SCUP. The Dell updates are delivered with the same mechanism used by ConfigMgr to deliver Microsoft patches. Details at the link below.
en.community.dell.com/.../dell-updates-catalogs.aspx
DELL-Warren B
1.1K Posts
1
January 25th, 2012 07:00
As far as OSD goes, you shouldn't be trying to update drivers during deployment, you should be using validated drivers as a part of your OSD task sequence. Updates would only be required post deployment. More info on Dell Driver CABs can be found at the link below.
en.community.dell.com/.../2065.aspx
IT.NeverEnds
2 Posts
0
January 27th, 2012 06:00
These are good ideas, thanks for sorting this out,
so i'm guessing DCSU+DRM are not like ThinInstaller & Update Retriever combo we use for lenovo models,
after reading that excellent PDF (media.community.dell.com/.../dell-configmgr-osdeployment.pdf)
I'm thinking of making a Driver Package for those Dells' (i have 7 different ones)
I think the raw method will suit my environment since i keep only PE drivers in my sccm driver store,
since it has quite limited functionality.
Thanks again and i will update with what solution we decided to go with.
Good Day,
Avi
DELL-Warren B
1.1K Posts
0
January 27th, 2012 07:00
Excellent! let us know if you have any questions!