Deployment Solution

 View Only
  • 1.  Deploy anywhere hangs at "Retargeting Device Drivers"

    Posted Sep 03, 2014 01:06 PM

    Once our image has been deployed via ghost, we run a task to detect certain model numbers that require additional driver support and then launch deploy anywhere via a command line when it is needed. This approach works as expected on some models and has been in production for a while. 

    We've recently introduced new models to our environment - Lenovo x240 and T440s - and deploy anywhere does not complete on these machines. Once Deployanywhere is launched, it hands at "Retargeting device drivers..." indefinitely. Windows task manager on the affected machine shows that the deploy anywhere .exe is idle. We have deployanywhere logging turned on but the log file never grows beyond 0KB. 

    The command line that we're using is below. 

    "X:\Program Files\Symantec\Deployment\ghost\DeployAnywhere64.exe" /target=D:\Windows/ddb="M:\DriversDB" /handleNonCriticalDrivers=adminLogon /logpath="D:\Scripts\DeployAnywhereNonCInstall" /skipMissingCriticalDrivers /byPassDrvVali=ALL 

    Additionally, if I manually run the above command line while the initial attempt is hung, deployanywhere finishes without issue. 



  • 2.  RE: Deploy anywhere hangs at "Retargeting Device Drivers"

    Posted Sep 03, 2014 01:43 PM

    Is that the exact command line? If so, then you might want to put a space in between /target=D:\Windows /ddb="M:\DriversDB".

    Do you launch DeployAnywhere in an administrative command prompt? I'm having an issue where I'm laying down my WIM file and trying to run DA using a script task and it doesn't indicate that it is running but just leaves the command prompt window open and nothing happens.



  • 3.  RE: Deploy anywhere hangs at "Retargeting Device Drivers"

    Posted Sep 18, 2014 01:20 PM

    If I were using DA only on certain models and only when I KNEW drivers were needed, I would NOT use DA.  That's scripting.  If I had to script it anyway, I'd use DISM instead.  Faster and more reliable.  Just be cautious - if you use DISM, it injects ALL drivers in the target folder, not just the ones needed as DA "attempts" to do.

     

    As for your issue, sounds like maybe the drive mapping is having issues or something of that nature?  Or rights?  When you run it "after it hangs" what EXACTLY do you do?  Map a drive and then run the line?  Use what is already mapped?