7 Replies Latest reply on Oct 28, 2010 1:01 PM by tgsmith24

    DirectX - 1) Inventorying and 2) Deploying


      We're managing several thousand clients, most of which are still XP at this point.  An app being deployed to about 1600 of them requires DirectX 9.0c.  How to accurately identify from LANDesk inventories of the systems which clients are at what level of DirectX is presently eluding us.  (It would seem that LANDesk system inventories are hit-and-miss as to whether they catch the DirectX executables (dxdiag.exe, dxsetup.exe, etc) stored in c:\windows\system32.)


      So my questions are:

      1) How do we get LANDesk to accurately inventory the contents of each client's c:\windows\system32 directory for dxdiag.exe, dxsetup.exe, and other DirectX files, and

      2) How do we deploy a silent DirectX 9.0c installation to the clients?  When an attempt was made to push this out (using the installation command line dxsetup.exe /silent) to some test systems which found upon manual inspection to be at an earlier DirectX release, the following lines were logged in the system's c:\windows\setupapi.log file:


      [2010/09/11 21:53:10 4412.48]

      #-198 Command line processed: "C:\Program Files\LANDesk\LDClient\SDMCache\landesk\files\directx\DXSETUP.exe" /SILENT

      #E359 An unsigned or incorrectly signed file "c:\windows\system32\directx\dxc1.tmp\d3dx9_33_x86_xp.inf" blocked (server install). Error 1168: Element not found.

      #W187 Install failed, attempting to restore original files.

      #E064 Parsing install section [x86_Install] in "C:\WINDOWS\system32\DirectX\DXC1.tmp\d3dx9_33_x86_xp.inf" failed. Error 1168: Element not found.


      Any help is greatly appreciated!