Microsoft

@bsenyonyi​ 

Depending on which views you want these managers to get access to you may be able to use enterprise groups to control which ITAM objects they would be able to see. You can configure the enterprise group data restrictions at the IT Asset Accounts Roles level, and then the license objects would have be restricted at their Ownership tab level. This will merely work for the views accessed through the ITAM menus and for created or imported objects in ITAM, i.e., this restriction will not apply to the Flexera One SaaS Management menus/views so you shouldn't give these managers access to these menus/views.

Thanks,

John Sorensen

Hi Bernardo,

Snow agents for Windows usually include an snowagent.exe file and some addittional powershell scripts (which are triggered by the agent).

For a laptop or desktop agent there is a powershell script "scan-msinfo" which is used to determine whether its Office2016 or Office365. This is one of the extra scripts that is normally included with an End User Compute agent package.

I think you will find that this powershell script is not running on your machines for some reason. Some examples could include

1. The scan-msinfo powershell script may not be present,
2. The Powershell scan imay not be running in the right security context
3. There could be a some other powershell issue
4. You have updated to the latest V7 snowagent and have not updated the powershell scripts

I recommend that you a check that scan-msinfo exists and then log a formal support ticket if necessary.

Regards

Tom

Hi Joanna

I would suggest to reach out to the DIS recognition team (via Support team) who could assist you with the recognition issue and advise / supply any related script however, you mention that you have spoken to Support and therefore may have spoken to the recognition team already?

If you have done the above then it could be a case that the current rules cannot identify the individual application or perhaps a global rule could not be applied for some reason, if this is the case then possibly the only way to recognize the application would be to write a local rule.

The link here explains what can and cannot be added to the Global database.

Use this link here to assist you in writing your own local rule

If you have issues writing your own rule and need further assistance, then you would need to raise a support request with the support team who may be able to advise you further. I'll add the link for here for the Snow Portal should you need this.

Kind

Regards

Mark Stenning

Digital Customer Value Manager

Hi Joanna

Apologies that you have not had any feedback with regards to your question.

There is some basic information that can be found within the Snow Documentation which I have put a link here, but I would suggest for more detailed answers, if you raise a case with our Support team, they will be able to assist you.

You can raise a support request via the Snow Portal.

Kind Regards

Mark

Stenning

Digital

Customer Value Manager

Still working through it. At this point, this is how I'm doing it:

• 1 master agreement with the MPSA/agreement number out to 2030
• 1 SCE sub agreement with 3 sub agreements underneath, 1 for each year
• 1 EAS sub agreement with 3 sub agreements underneath, 1 for each year
• Licenses for EAS are 1 year each, so each product/line item from the BOM is repeated 3 times, attached to each year's sub agreement
• SCE - not sure how I'm going to do that yet. One at a time I guess!

There doesn't seem to be a proper roll-up at the EAS or SCE sub agreement level which is a real shame, however doing things this way provides greater accuracy and detail when it comes to annual true-downs. It means I'm accurately recording the up-front 3 year commitment, but I have the ability to change subsequent years without having to fudge the numbers, in case I do a true-down or if next year's numbers are going to be higher.

I really wish there was a white paper on this however, explaining the benefits and disadvantages of each approach.

Hi Natascha,

A common cause of the "no eligible application installed" is not having Downgrade rights, or Cross Edition rights selected within the license. Please ensure these boxes are checked within the license.

Another point to note, is that if your host sits within a DCC, you need to ensure that all hosts within the DCC have licenses assigned, for this to work (you cannot partially license a datacenter/cluster). As per Jelle's comment above, the easiest way to do this is by licensing at the DCC level instead of the individual host level.

Thanks

Kelly

Hi,

​

Just adding my piece of my experience I had with this particular application :-)

In the past (2021) I raised this matter at DIS team too. Back then it was confirmed CLR types should not have a 'license required' flag. As such, it has been corrected as such. Ever since then, I observe indeed that matter is cleared. Meaning the software is shown as no license required.

​

Best regards,

​

Detlev Schigt