Video Screencast Help
Protect Your POS Environment Against Retail Data Breaches. Learn More.

Deployanywhere - USB3.0 devices

Created: 28 Dec 2012 • Updated: 08 May 2013 | 8 comments
This issue has been solved. See solution.

I had a ticket in this summer about deployanywhere not recognizing/deploying drivers to computers with USB 3.0.  An eTrack was created, but I am not sure what happened since then.  I just put another ticket in since I can't see the old ticket updates in the new system.

Does anyone have deployanywhere successfully deploying drivers to Dell USB 3.0 computers.  I do have the extracted driver files in my database.  I'm seeing this with Optiplex 7010s and Latitude 6230's.  I think I was hoping this would get fixed with 7.5 too but with that pushed back maybe just a newer DA file would help?

I did see this tech article which says "Some newer equipment (e.g. USB 3.0) may not be recognized at this time, but we will update DA as quickly as we can."

http://www.symantec.com/business/support/index?pag...

Comments 8 CommentsJump to latest comment

BBC's picture

Hi,

Not sure if this is of any help, but what I realized when it came to USB 3 devices and drivers is the following. Please note, I use DPInst for the driver installation, but the impact should be the same.

If you have USB 3 ports, the install of the drivers has to be done in two steps or repeated.

Reason I found:
On first run, the drivers are installed for the controller, but at this point the system cannot install the driver for the port itself. Install the driver again and all devices are installed.

-BBC

Sally5432's picture

Thanks for replying BBC, but I haven't seen that.  I have the extracted drivers, if I am in device manager and point the missing/complaining questionmark to the drivers they install wtih no problem so I think it's really a deploy anywhere issue.

---
Don't forget to mark posts as helpful if they are, and mark answers as solutions.

Indrek_K's picture

Hello Sally

As BBC noted the USB3 drivers and the ones I have seen and tested use two drivers. One for Controller and one for device. Can be confirmed if you look inside the driver inf files, and DA log file.

First driver that is needed is Controller, second is device. After controller is installed the device ID will appear for the device so that device driver can be installed.

On one case I worked we confirmed that DA was able to install the Controller. DA only runs once but for the USB3 we need to run it twice.

As a workaround for the customer I had we did a reboot to WinPE after Image was deploy'd and booted to production. Then when we where in WinPE again we ran DA with Script so it would install the device drivers also now when Controller drivers are installed and device ID is known.

Best Regards Indrek

Sally5432's picture

@Indrek_K seems like another step further away from true hardware independent imaging for Symantec if some machines with USB 3.0 require an extra WinPE/DA step.

I wonder how SCCM and other solutions handle it.

---
Don't forget to mark posts as helpful if they are, and mark answers as solutions.

BBC's picture

Hi Sally,

We use a WMI query from within the automation environment to detect the hardware and then use that to copy down the appropriate driver set to the client. Below is an example on how we do this.

Please note, for the driver installation part, I use DPInst with a set of parameters and simply execute the same command twice so that the controller and ports get installed. For your reference, I also pasted in the DPInst command line I use.

As I'm not a programmer, the code might be looking stupid or not the best, but works. And it is used by copying the VBS to the client and executing it locally.

Maybe this was of some help for you?

-BBC

DPInst:

START /W %~d0%~P0%DPInst.exe /c /el /lm /q /sa /se /sh /sw

Driver selection and copy script:

'vbScript
'This script is to identify the model name of the computer and
'copy across according drivers
Dim oFSO, oFS, MyModel, MySource, MyDest, MyCMD, MyWork

Set oFSO = CreateObject("Scripting.FileSystemObject")
Set WshShell = wScript.CreateObject("wScript.Shell")
strComputer = "."

MySource = "G:\DSLIB\Global\Drivers\WIN\Win7\"
MyDest = "C:\DisneyIT\Tools\Packages\*.* /s /e /y"

'Create Output File
'Set oTSOut = oFSO.CreateTextFile("C:\DisneyIT\Product.txt")

'Setup WMI query Computer Syetem Product Properties for Name and Version
Set objWMIService = GetObject("winmgmts:\\" & strComputer & "\root\CIMV2")
Set colItems = objWMIService.ExecQuery("SELECT * FROM Win32_ComputerSystemProduct",,48)

'Query the local system
For Each objItem in colItems
  If objItem.Vendor = "LENOVO" Then
    'oTSOut.WriteLine objItem.Version
    MyModel = rTrim(objItem.Version)
    MySource = MySource & "IBM\" & MyModel
    MySource = MySource & "\*.*"
    MySource = CHR(34) & MySource & CHR(34)
    MyCMD = "CMD /C XCOPY "
    MyWork = MySource & " " & MyDest
    WshShell.Run MyCMD & MyWork
  ElseIf objItem.Vendor = "Dell Inc." Then
    'oTSOut.WriteLine objItem.Version
    MyModel = rTrim(objItem.Name)
    MySource = MySource & "DELL\" & MyModel
    MySource = MySource & "\*.*"
    MySource = CHR(34) & MySource & CHR(34)
    MyCMD = "CMD /C XCOPY "
    MyWork = MySource & " " & MyDest
    WshShell.Run MyCMD & MyWork
  Else
    'oTSOut.WriteLine objItem.Name
    MyModel = rTrim(objItem.Name)
    MySource = MySource & "HP\" & MyModel
    MySource = MySource & "\*.*"
    MySource = CHR(34) & MySource & CHR(34)
    MyCMD = "CMD /C XCOPY "
    MyWork = MySource & " " & MyDest
    WshShell.Run MyCMD & MyWork
  End If
Next

Set oFS = Nothing

Sally5432's picture

BBC - thanks for this, appreciate it.  I was hoping symantec was going to get back to me with some supported way to handle usb 3.0 but so far no dice.  If we stay with symantec/altiris - I will definitely look into this.

 

---
Don't forget to mark posts as helpful if they are, and mark answers as solutions.

SaintFrag's picture

The easy work around is to copy the driver's folder to %systemroot%/inf

I usually create a folder in there called something like 'MyDriverStore' and copy the required driver's folders from %systemroot%/system32/DriverStore\FileRepository

I only do that on drivers that are stubborn like the USB 3.0 drivers, as they go in every image I build.  Thank goodness for Ghost Explorer, as that makes adding new 'stubborn' drivers a BREEZE post-capture.

Sally5432's picture

This is Symantec's solution for the problem.  Worked for the one machine I tested it on

http://www.symantec.com/business/support//index?page=content&pmv=print&impressions=&viewlocale=&id=TECH205253

They say running DPInst script post image on all machines shouldn't be an issue (whether or not they have USB3)

---
Don't forget to mark posts as helpful if they are, and mark answers as solutions.

SOLUTION