Deployment Solution

Currently in our image process I am scripting all the model detection and we have driver packs that I am copying over during PE and running DISM manually as part of the script.

I am attempting to test the deploy anywhere functionality since from my understanding this is what it is for, but can't get it to work.

The Ghost image we have is not an altiris capture, it is our own sysprepped image that we imported, not sure if this makes a difference or not.  We are on 7.5 SP1 Hotfix 5

I imported the drivers for one peticular model and the drivers db package grew substancially so I know it imported all the drivers.  When I do an image I do have the include deploy anywhere option checked.

Any help is appreciated.

Might be a red herring (as I don't know *how* DeployAnywhere injects these things), but assuming it's all sysprep in the end.... then it might be an issue with hardware detection being disabled.

You see sometimes people in environments with just one standard piece of hardware make their mini-setups faster by tweaking the sysprep xml. They override the default value of PersistAllDeviceInstalls in the XML used to sysprep the machine to stop sysprep cleaning out the PnP drivers.

You can judge if this is happening by looking closely at the machine in mini-setup and checking for the device detection phase.

Take a look at this,
https://technet.microsoft.com/en-us/library/cc722095(v=ws.10).aspx

So, in the orginal syspreping you either want this key to be missing entirely, or set explicitly to false in the Microsoft-Windows-PnpSysprep component.

    <PersistAllDeviceInstalls>false</PersistAllDeviceInstalls></component>

If it was set to true, then PnP devices weren't uninstalled at sysprep time, and won't be re-installed during the specialize pass.

Thanks we are not doing drivers in sysprep, we are using the DISM command within Windows PE, which is also the method that I have been told Deploy anywhere uses as well

If using DISM on the image within WinPE works, and it's definently the same image you are now trying to use use DeployAnywhere on, then PnP detection must be enabled. That means this key can't be the issue, and red herring it is.

Have you taken a look at this troubleshooting doc?

https://support.symantec.com/en_US/article.HOWTO95200.html

I know when I looked at the logs before it seemed like it wasn't even trying to run deployanywhere, or at least I couldn't find anything failing.  I'll run another test and grab the logs during PE.  

Am I correct in assuming I do not have to create a script task to run deploy anywhere and it is supposed to just run on its own if I have the check box checked in teh deploy image task?

Here are the lines I see related to deployanywhere in the logs

<DeployAnywhere><Commandline>/target=@WinInstallDir /ddb="@MappedDrive\Task Handler\DriversDB" /handleNonCriticalDrivers=miniSetup</Commandline><SkipNonCriticalDrivers>false</SkipNonCriticalDrivers><BypassDriverValidation/><LogLevel/></DeployAnywhere><DomainCredential guid="@DomainCredential">@DomainCredentialXML</DomainCredential><InstallSMPAgent>false</InstallSMPAgent><AutoReboot>0</AutoReboot></image>

and then a little later

[2015/07/09 14:56:45.330 1256:716 2] .util::ExecuteClass::GetActiveWindowsInstallationDrive:1656. Windows Active drive can not be found using GhConfig. Seraching for bcdosdevice.cgf file. Name of Tools is 0.n
[2015/07/09 14:56:45.330 1256:716 2] apps\DeploymentClient\ClientImageDeploy\Tcube_ClientImageDeploy.cpp@476 checking isVista
[2015/07/09 14:56:45.330 1256:716 2] apps\DeploymentClient\ClientImageDeploy\Tcube_ClientImageDeploy.cpp@480 isVista=Windows 7 Professional Service Pack 1
[2015/07/09 14:56:45.330 1256:716 2] apps\DeploymentClient\ClientImageDeploy\Tcube_ClientImageDeploy.cpp:509 - No system disk is involved in imaging operation. So not running DeployAnywhere