Either.

 

Your driver is bad, and MDT can't parse it. Or.

Your MDT control\drivers.xml is corrupted, and MDT can't write to it.

 

Try importing this driver to a *new* deployment share, to see if it's a
problem with the driver, then you may need to rebuilt the drivers by copying
back and forth between deployment shares.

 

From: [email protected] [mailto:[email protected]]
On Behalf Of Bain.John
Sent: Tuesday, July 29, 2014 8:47 AM
To: '[email protected]'
Subject: [MDT-OSD] Weird MDT error while importing drivers

 

Having trouble import drivers into an older MDT deployment. getting this
error message 

 

System.Management.Automation.CmdletInvocationException: Index was out of
range. Must be non-negative and less than the size of the collection.

Parameter name: index ---> System.ArgumentOutOfRangeException: Index was out
of range. Must be non-negative and less than the size of the collection.

Parameter name: index

   at System.ThrowHelper.ThrowArgumentOutOfRangeException()

   at System.Collections.Generic.List`1.get_Item(Int32 index)

   at Microsoft.BDD.PSSnapIn.Verifier.AddDriver(String theInfFile)

   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)

   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)

   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)

   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)

   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)

   at Microsoft.BDD.PSSnapIn.ImportDriver.ImportDrivers(String thePath)

   at Microsoft.BDD.PSSnapIn.ImportDriver.ProcessRecord()

   at System.Management.Automation.CommandProcessor.ProcessRecord()

   --- End of inner exception stack trace ---

   at
System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEn
umerate(Object input, Hashtable errorResults, Boolean enumerate)

   at System.Management.Automation.Runspaces.LocalPipeline.InvokeHelper()

   at
System.Management.Automation.Runspaces.LocalPipeline.InvokeThreadProc()

 

The whole message log can be seen here http://pastebin.ca/2826929

 

John

 


Reply via email to