Applications Greyed Out/ Data Not Reflecting.

8 years ago

Hello Sakshi, Can you post a picture of the grayed out applications? I am not sure what view you are referring to. One reason applications might be grayed out is that you have activated whitelisting. In that case, any application that is not whitelisted will be greyed out, like this: (microsoft is whitelisted in this example, all other is gray.) Also, when you say that the majority of the applications are not reflected in Snow, can you give us some more details on that please? What is your main data source? Do you use the Snow Inventory Agent, or do you pull data from a third party tool like SCCM for example?

Expand Post

SLM
8 years ago
Thank You Martin, But We do not Whitelist, we are using an on-prem solution with agents on endpoints. Right now most adobe products suddenly appears as removed. We right now have also seen that MS Project Pro/Std and Visio is also not reflecting in SLM. We are running agent 6.0.0.2. And the problem seems to be quite big because the Inventory agent is picking up the data and all these installations are reflecting in SIM, But when we look into the License Manager it does not show anything and the status of all these applications is updated as removed. Please see the attached screenshot.
Expand Post
- Portal User
  8 years ago
  Hi Sakshi, Thank you for the screen shots, that gives me a much better picture of the situation. Your first screen shot shows the application mapping rules, and it is perfectly normal for a lot of them to be greyed out. That does not mean that they are removed, it simply means that they are hidden, and that is by design. They are hidden because they are a part of a combination of several rules, that together builds a recognition set for a product. For example, we often combine a registry (reg) rule with an executable (exe) rule to identify one singe application. We also combine several rules together to identify software bundles. We do not want these "atoms" to show as individual software rows in License Manager, therefore we hide them, and only show the single software that was identified by these atom rules. For Adobe Acobat DC professional you need to look at the Application Groups. Here you see that it requires two Application definition rules to activate, both the SWID and the executable: Going back to the Application Definitions we find these ones: one black and one gray. The gray one is not deleted or inactive, it is doing its job as a part of the group. The executable: And the SWID tag: If these two match rules the raw data you have in Inventory Server you should see the result in License Manager. Note that you need to match both rules, and all parameters of a rule, both name, version and executable location. It seems to me that you have 24 hits on the swidtags, but I cannot see from your screenshot how many hits you have on the executable.
  Expand Post

Portal User
8 years ago
Hello Sakshi, Can you post a picture of the grayed out applications? I am not sure what view you are referring to. One reason applications might be grayed out is that you have activated whitelisting. In that case, any application that is not whitelisted will be greyed out, like this: (microsoft is whitelisted in this example, all other is gray.) Also, when you say that the majority of the applications are not reflected in Snow, can you give us some more details on that please? What is your main data source? Do you use the Snow Inventory Agent, or do you pull data from a third party tool like SCCM for example?
Expand Post
- SLM
  8 years ago
  Thank You Martin, But We do not Whitelist, we are using an on-prem solution with agents on endpoints. Right now most adobe products suddenly appears as removed. We right now have also seen that MS Project Pro/Std and Visio is also not reflecting in SLM. We are running agent 6.0.0.2. And the problem seems to be quite big because the Inventory agent is picking up the data and all these installations are reflecting in SIM, But when we look into the License Manager it does not show anything and the status of all these applications is updated as removed. Please see the attached screenshot.
  Expand Post
  - Portal User
    8 years ago
    Hi Sakshi, Thank you for the screen shots, that gives me a much better picture of the situation. Your first screen shot shows the application mapping rules, and it is perfectly normal for a lot of them to be greyed out. That does not mean that they are removed, it simply means that they are hidden, and that is by design. They are hidden because they are a part of a combination of several rules, that together builds a recognition set for a product. For example, we often combine a registry (reg) rule with an executable (exe) rule to identify one singe application. We also combine several rules together to identify software bundles. We do not want these "atoms" to show as individual software rows in License Manager, therefore we hide them, and only show the single software that was identified by these atom rules. For Adobe Acobat DC professional you need to look at the Application Groups. Here you see that it requires two Application definition rules to activate, both the SWID and the executable: Going back to the Application Definitions we find these ones: one black and one gray. The gray one is not deleted or inactive, it is doing its job as a part of the group. The executable: And the SWID tag: If these two match rules the raw data you have in Inventory Server you should see the result in License Manager. Note that you need to match both rules, and all parameters of a rule, both name, version and executable location. It seems to me that you have 24 hits on the swidtags, but I cannot see from your screenshot how many hits you have on the executable.
    Expand Post

Related Product Forums