UNSOLVED
CH
Cliff Hobbs
7 Posts
0
34877
June 22nd, 2011 09:00
Deploying E6410 XP Audio Driver via SCCM doesn't work
Hi all,
I want to deploy the latest version of the Dell E6410 Audio Driver for XP as part of my Task Sequence in SCCM but it's not working - this is what it says in the execmgr.log (abbreviated):
Executing program setup.exe /s /f1 setup.iss /f2"C:\Windows\Temp\audioLogDell.Log" in Admin context
Execution Request for package program MDT_E6410_Audio state change from NotExist to NotifyExecution
Successfully prepared command line "\\...\\setup.exe" /s /f1 setup.iss /f2"C:\Windows\Temp\audioLogDell.Log"
Command line = "\\...\\setup.exe" /s /f1 setup.iss /f2"C:\Windows\Temp\audioLogDell.Log", Working Directory = \\...\\
Program exit code -2147213312
Looking for MIF file to get program status
Script for Package:, Program: MDT_E6410_Audio failed with exit code 2147753984
Raised Program Error Event for Ad:SMS10000, Package:, Program: MDT_E6410_Audio
Execution is complete for program MDT_E6410_Audio. The exit code is -2147213312, the execution status is FailureNonRetry
The weird thing is when I login to the machine after it has been built and map a drive to the Package directory and run the exact same command line as the SCCM Program it works fine. The rest of the drivers install fine.
I've tried adding reboots after the drivers/ moving the audio driver to the end of the list of drivers to be installed in the MDT database all to no avail.
So I'm wondering if there is some sort of depedency the driver has that isn't being met at the time I'm trying to install it but which is met after the machine has been built.
If anyone has any experiences of this and would be willing share I'd be grateful as I'm not making any great progress on this.
Many thanks and kind regards,
Cliff
I want to deploy the latest version of the Dell E6410 Audio Driver for XP as part of my Task Sequence in SCCM but it's not working - this is what it says in the execmgr.log (abbreviated):
Executing program setup.exe /s /f1 setup.iss /f2"C:\Windows\Temp\audioLogDell.Log" in Admin context
Execution Request for package program MDT_E6410_Audio state change from NotExist to NotifyExecution
Successfully prepared command line "\\...\\setup.exe" /s /f1 setup.iss /f2"C:\Windows\Temp\audioLogDell.Log"
Command line = "\\...\\setup.exe" /s /f1 setup.iss /f2"C:\Windows\Temp\audioLogDell.Log", Working Directory = \\...\\
Program exit code -2147213312
Looking for MIF file to get program status
Script for Package:, Program: MDT_E6410_Audio failed with exit code 2147753984
Raised Program Error Event for Ad:SMS10000, Package:, Program: MDT_E6410_Audio
Execution is complete for program MDT_E6410_Audio. The exit code is -2147213312, the execution status is FailureNonRetry
The weird thing is when I login to the machine after it has been built and map a drive to the Package directory and run the exact same command line as the SCCM Program it works fine. The rest of the drivers install fine.
I've tried adding reboots after the drivers/ moving the audio driver to the end of the list of drivers to be installed in the MDT database all to no avail.
So I'm wondering if there is some sort of depedency the driver has that isn't being met at the time I'm trying to install it but which is met after the machine has been built.
If anyone has any experiences of this and would be willing share I'd be grateful as I'm not making any great progress on this.
Many thanks and kind regards,
Cliff
Dustin Hedges
1 Rookie
•
96 Posts
942
0
Posted June 28th, 2011 10:00
We used to install them as opposed to using the default driver injection with a driver package (using the CAB's) and we simply used "Setup.exe /S" to perform the install. We wrapped everything in a vbscript and did our own logging that way. Since the default Setup.iss is in the same directory as Setup.exe there is no need to force the use of the setup.iss file (it's done by default with the /s switch).
Try killing off your forced log directory and call to the setup.iss file and see if that works for you.Cliff Hobbs
7 Posts
942
0
Posted July 4th, 2011 09:00
Many thanks for the reply but I've already tried running "Setup.exe /S" with no difference :-(- I'd be very much interested to hear if there's a solution to this issue as I'm suffering the same fate at the moment.
It seems there is no way for you to install this driver via SCCM OSD...I've included the drivers as part of the Driver Package and also tried to use the Software Installation as part of my Task Sequence and it repeatedly fails.
Can anyone post if they have come up with a workable solution as I'm banging my head against a brick wall.
For info purposes:
OS - XP SP3
Device - Dell eSeries 6320
Many thanks for any replies!
DELL-Warren B
1 Rookie
•
1124 Posts
942
0
Posted June 22nd, 2011 23:00