locked
Application Detection doesn't pickup App-V 5.1 sequences when running Discovery/UDI... RRS feed

  • Question

  • Hello, I've just recently been introduced to UDI, specifically "Install Programs", which I've integrated into a fairly mature Windows 10 OSD. I've modified a list of Packages and Applications, have them installing fine and almost detecting fine, the issue seems to be the App-V 5.1 sequences aren't detected, despite what appears to be correct Mapping settings. I can show graphics if necessary but really it comes down to this, here is the WMI output for my test machine after imaging and installing via UDI:

    WBEMTest, root\appv, Enum Instances, AppClientPackage, returns 3 hits, below are the "Names" returned

    ProDiver 6.4.36 (v)
    MAC + PCW + Monitor Suite 24.04.0040 (v)
    Syngo Workflow Radiology Standard 32.0.4.9 (v)

    Here's a snippet from the AppDiscovery.log, run after as part of my UDI configuration:

    19:22:41.877 05-08-2016 2 AppDiscovery ----------------------------------------------------------
    19:22:41.893 05-08-2016 2 AppDiscovery Match Application
    19:22:41.893 05-08-2016 2 AppDiscovery ----------------------------------------------------------
    19:22:41.893 05-08-2016 2 AppDiscovery  --| Queried Attribute [Id] for Value [57]
    19:22:41.893 05-08-2016 2 AppDiscovery  --| Queried Attribute [DisplayName] for Value [Dimensional Insight, Inc ProDiver 6.4.36 (v)]
    19:22:41.909 05-08-2016 2 AppDiscovery  --| Initiating xpath query: [ApplicationMappings/Match[@Type="MSI" or @Type="SMS" or @Type="WMI"]]
    19:22:41.909 05-08-2016 2 AppDiscovery  --| XPath query success.
    19:22:41.909 05-08-2016 2 AppDiscovery  --| Found match node, attempting to read...
    19:22:41.909 05-08-2016 2 AppDiscovery  --| Queried Attribute [Type] for Value [WMI]
    19:22:41.924 05-08-2016 2 AppDiscovery  --| Queried Attribute [OperatorCondition] for Value [OR]
    19:22:41.924 05-08-2016 2 AppDiscovery Match type WMI
    19:22:41.924 05-08-2016 2 AppDiscovery  --| Initiating xpath query: [Setter[@Property="Name"]]
    19:22:41.924 05-08-2016 2 AppDiscovery  --| XPath query success.
    19:22:41.924 05-08-2016 2 AppDiscovery  --| Value to match against library: [prodiver 6.4.36 (v)]
    19:22:41.940 05-08-2016 2 AppDiscovery  --| Match found: [false]
    19:22:41.940 05-08-2016 2 AppDiscovery  --| Found match node, attempting to read...
    19:22:41.940 05-08-2016 2 AppDiscovery  --| Queried Attribute [Type] for Value [MSI]
    19:22:41.940 05-08-2016 2 AppDiscovery  --| Queried Attribute [OperatorCondition] for Value [OR]
    19:22:41.955 05-08-2016 2 AppDiscovery Match Type MSI
    19:22:41.955 05-08-2016 2 AppDiscovery  --| Initiating xpath query: [Setter[@Property="ProductId"]]
    19:22:41.955 05-08-2016 2 AppDiscovery  --| XPath query success.
    19:22:41.955 05-08-2016 2 AppDiscovery  --| Value to match against library: [{266e1831-16e5-4ac0-9f87-1c3c881f2cb3}]
    19:22:41.955 05-08-2016 2 AppDiscovery  --| Match found: [false]
    19:22:41.955 05-08-2016 2 AppDiscovery Application Function Result: [true]
    19:22:41.955 05-08-2016 2 AppDiscovery Application Matched: [false]
    19:22:41.955 05-08-2016 2 AppDiscovery  --| Initiating xpath query: [../..]
    19:22:41.955 05-08-2016 2 AppDiscovery  --| XPath query success.

    It seems clear that that "ProDiver 6.4.36 (v)" which was pulled directly from WMI does match "prodiver 6.4.36 (v)" pulled directly from the AppDiscovery.log but it evaluates as FALSE, I don't get it. I've been pulling my hair out with variation on the naming and clean files and small files with a single entry, nothing, I would appreciate some fresh ideas...

    Jack



    • Edited by JFetter Sunday, May 8, 2016 7:32 PM
    Sunday, May 8, 2016 7:30 PM

All replies

  • Can anyone point me to a good resource for this tool, a blog, anything? I just need to pick the brain of someone that designed it as I'm sure what I'm doing must be a mistake. I even wrote a vbscript to read the names of App-V Programs from WMI and write dummy GUID's to the Uninstall key to see if I could force it to detect (like with MSI's), I am so close to having this all working but can't seem to find who can support it...

    Jack

    Tuesday, May 10, 2016 10:09 PM
  • I don't know that anyone from the product team checkks the forums. 

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it.

    Wednesday, May 11, 2016 2:38 PM
  • I was told to post here <sigh>...

    Jack

    Wednesday, May 11, 2016 10:27 PM
  • I finally realized this may never be seen, a communication to one of the team members indicated they were hot and heavy into a production cycle and it would be best to post here, despite this maybe not being reviewed that often. I wonder if these tools are much more than second thoughts sometimes, like the old NT Resource Kit utilities that were mostly unsupported and either worked or didn't (take what you get).

    In any case, I got tired of waiting and created a vbscript to enumerate the App-V apps by "Name" and write out a Product GUID in the registry (where their application scans for MSI GUID's to map MSI's, which does work) for each entry. I then use thet dummy registry entry(s) to then map the App-V Application(s) by adding an MSI Mapping instead of a WMI Mapping. You simply add a TS to run the vbscript right before UDI...

    Jack



    • Edited by JFetter Thursday, May 12, 2016 1:08 AM
    Thursday, May 12, 2016 1:07 AM
  • You are one of the guys that when you ask it is generally a challenging question which is a good thing. Good in that it is always a good question and you have done your homework. :)

    Many questions such as where do I find logs and what logs are interesting are found in: MDT TechNet Forum - FAQ & Getting Started Guide Please take the time to read it.


    • Edited by Ty Glander Thursday, May 12, 2016 1:24 AM
    Thursday, May 12, 2016 1:22 AM