Highlighted
Active participant

Conditioning Unauthorized Applications How?

Jump to solution

Is there a way or best practice to the creation of Unauthorized Applications?  Let's say we want to make MS SQL Server Unauthorized only in certain scenarios - say when installed on virtual machines instead of physicals so that we can get automated reporting monthly to flag our SAM team and the customer to possible license breaches or unforeseen licensing expenses?  The "unauthorized" status seems pretty binary in practice within FNMS - either on or off.  No way I can see to make it conditional.

0 Kudos
1 Solution

Accepted Solutions
Highlighted
Flexera
Flexera

Re: Conditioning Unauthorized Applications How?

Jump to solution

@dmathias - You are correct.  The setting for Authorized/Unauthorized is a global YES or NO.  Either this application is allowed to run in your environment, or it is not allowed/blacklisted.

For a scenario such as you describe, a Custom Report could be created for the specific condition that you want to look for - such as all installations of SQL Server on a Virtual Machine.

View solution in original post

2 Replies
Highlighted
Flexera
Flexera

Re: Conditioning Unauthorized Applications How?

Jump to solution

@dmathias - You are correct.  The setting for Authorized/Unauthorized is a global YES or NO.  Either this application is allowed to run in your environment, or it is not allowed/blacklisted.

For a scenario such as you describe, a Custom Report could be created for the specific condition that you want to look for - such as all installations of SQL Server on a Virtual Machine.

View solution in original post

Highlighted
Active participant

Re: Conditioning Unauthorized Applications How?

Jump to solution
Got it. Thanks. Would be nice to have a bit more granularity, but we can fall back to custom reports.
0 Kudos