Deployment Solution

 View Only
  • 1.  Driver Tagging Usage

    Posted Jan 06, 2016 04:56 PM

    I have found very little information or examples of anyone using Driver Tagging. Can someone help me understand the best way to deal with a scenario where I have two HP models, A and B. If I just add model A or model B to the DDB, DeployAnywhere works fine. If I add them both then some drivers from model B break DA for model A. Ideally now I use driver tagging right? So to use tagging do I need to make multiple deploy image tasks with different tags and add a bunch of logic to my job so I can still just run one generic Windows 7 image job?

    Reboot to WinPE

    If model A

         Deploy Image Win7 (Driver A tagging task)

    If model B

         Deploy Image Win7 (Driver B tagging task)

    else

    Reboot to OS

     

    I really don't like the idea of having to maintain multiple deploy image tasks just for the purpose of tagging since we know these all tend to break, act up, and even disappear after upgrades. Is there a better way to do driver tagging or has anyone posted a video/article about it that I have overlooked?

     

    Thank you in advance

     



  • 2.  RE: Driver Tagging Usage

    Posted Jan 07, 2016 04:56 AM

    You could use a WMI query to get the information about the product you want to deploy an image to.

    An example could be this...

     

    FOR /F "tokens=2 delims==" %%A in ('WMIC csproduct GET name /VALUE ^| Find /I "name="') DO SET machine=%%A
    
    <Continue to deploy the image using the variable %machine%>

    Hope this helps...



  • 3.  RE: Driver Tagging Usage

    Posted Jan 07, 2016 12:44 PM

    BBC, Do you mean I can use a variable or token in the tag field of deploy image task if I do that check with WMIC? I'm not sure I am following.



  • 4.  RE: Driver Tagging Usage

    Posted Jan 08, 2016 12:11 PM

    I can do something like this:

    FOR /F "tokens=2 delims==" %%A in ('WMIC csproduct GET name /VALUE ^| Find /I "6300"') DO Exit 61386
    FOR /F "tokens=2 delims==" %%A in ('WMIC csproduct GET name /VALUE ^| Find /I "600 G1"') DO Exit 69539

     

    That return code matches the HP drivepack to install which I can run with a condition. It's just rather messy to have so many conditions for many models. Being able to use a token in the Tag field of the deploy image task would really solve this. Is there a simple way like that which I am missing?