Loading

License

Skip Feed
  1. How can I provide different views for managers to see Microsoft Entra ID licenses specific to their region?

    I am trying to integrate Entra ID in Flexera and have different views based off a location that is also stored in Entra. i.e., managers from the different locations should only see licenses credited to their location when they log into Flexera. Entra ID is already syncing with Flexera, however, I do not know how to proceed with the views for different managers.

    I have looked into enterprise groups as well, but having trouble interpreting / understanding how they can help.

    Anyone with a similar or different approach?

    Expand Post

    • JohnSorensenDK (Flexera Software)

      @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

      Expand Post

  2. 1 of 2
    • Hi Chanthasiri,

      As an addition, and just taking column 'License required' into account, I experience sometimes the column is checked, whilst it should perhaps not be.

      Double checking this with Snow's DIS team often confirms it is correct. What I mean to say is that the minute a piece of software seems to be licensable, it will be checked as such. For instance, in the situation where software bundle components demand a license.

       

      Best regards,

       

      Detlev Schigt

      Expand Post

  3. SQL Server Licensing Summary & Guidance

     

    Microsoft SQL Server is considered one of the most complex and expensive business applications to license. In today’s #DoMoreWithSnowServices article we look into why the product is challenging, and how Snow’s Professional Services team can help. Mike Rossouw, a Principal Licensing Consultant at Snow Software, shares the “need to know” information to get you started.

     

    Aside from the operational risks, insufficient planning of your business licensing needs will undoubtedly expose you to legal, financial, and reputational risks. At the time of writing, there are four main editions of SQL Server available and utilized.

     

    1.   Enterprise Edition – Commercially Available.

    2.   Standard and Web Edition – Commercially Available.

    3.   Express Edition – Freely Available.

    4.   Developer/Compact Editions – Freely Available.

     

    At a basic level, SQL Server is licensed on a per core basis for physical Servers (standalone), or the physical VMware ESX host (part of a cluster), then you need to license each physical processor in the server with a minimum of 4 SQL server core licenses per processor, or the total number of cores on the server, whichever is the higher of the two.

     

    If you are licensing the virtual server, the rules are slightly different. The minimum number of cores is based around the virtual server rather than the processors. You have to license a minimum of 4 cores per Virtual Machine (VM), or the total number of cores allocated to the VM, whichever is the higher of the two. If your VM's are part of a load balanced cluster, in other words they are free to move from one physical host to another within the same cluster, then you will have to make sure that the licenses you are assigning to the VM's have active Software Assurance (SA).

     

    SQL Server licensing starts to get even more complex when applying licenses at the cluster level with features such as DRS (VMware’s load balancing feature 'VMotion'), High availability (HA), and Disaster Recovery (DR) features such as passive failover.

     

    We often find that companies don’t have the required in-house knowledge or resources available to effectively plan out these SQL Server requirements. This is where Snow Software’s expert Professional Services team can assist and support you to optimize your Microsoft licenses.

     

    For more information, please contact the Snow team or visit our website from the link below.

     

    Snow Professional Services: https://lnkd.in/eJdvjaYF

    Expand Post

  4. What is the difference between assigning Application Rights and License assignment? I cant seem to work out the difference. Why would you use Application Rights if you have Licenses for the application assigned to the user?

    I cant seem to work out the difference. Why would you use Application Rights if you have Licenses for the application assigned to the user?

     

    Can anyone give me examples of when you would use one over the other? Would you use both at the same time for anything?

     

    Many thanks

    Jason

    Expand Post
    Question with a best answer.

    Best Answer

    Hi Jason,

     

    The difference between application rights and license assignment is the following.

     

    Application rights does not use affect your license compliance. it is a way for you to report on users who can /should not access applications. It is a function in Snow that is not used very often. where as license assignment is just that. it is used for compliance calculations. If it is license related always use license assignments if it is policy related use application rights.

     

    Kind regards,

     

    Jelle

    Expand Post
    Jelle Wijndelts by Jelle Wijndelts (Flexera Software)

    • Jelle Wijndelts (Flexera Software)

      Hi Jason,

       

      The difference between application rights and license assignment is the following.

       

      Application rights does not use affect your license compliance. it is a way for you to report on users who can /should not access applications. It is a function in Snow that is not used very often. where as license assignment is just that. it is used for compliance calculations. If it is license related always use license assignments if it is policy related use application rights.

       

      Kind regards,

       

      Jelle

      Expand Post
      Selected as Best

  5. Compliance Summary Multiple Metrics

    Hey Friends,

     

    I think this is a Snow design thing, but has anyone seen it where if an application has multiple metrics and is non-compliant, it shows up in the Compliance Summary report twice?

     

    We've got an application that is non-compliant and is showing up twice, but it looks like it's related to multiple metrics. I've cross checked this across a few different platforms we have on different versions and can see it across the board up to 9.12.1, so just curious if anyone else has seen this and if it's a by-design 'feature'?

    Expand Post
    Question with a best answer.

    Best Answer

    Hi Liam, I see the same behavior here on SLM 9.12

    I think you are right that this happens because of the multiple metric ... I think it makes sense to see both rows because that also gives hints regarding the best way to bring the application to compliance. The downside is that it shows double lines in some cases, I agree.


    1 of 3
    • Hi @Laim McKenzie​ ,

       

      As far as I know and also Samuel states this is intended, there is no other possibility to show the requirement for different metrics.

      Also the license tracking reports do show the result in several rows, one row per possible metric.

      But adding the column "Is multiple metrics" also to Compliance Summary would be a good idea.

      In Report Compliance per Organisation this column is available.

      Expand Post

  6. How we can assign oracle licenses at the vCenter level for Oracle?

    Hi All,

     

    I have query related with assigning licenses in SLM at vCenter level for Oracle Database.

     

    As I gone through with License assignment but there found that only Virtual Machine, Physical Server and Data Center level we can assign.

     

    In SLM only Datacenter and cluster level view available.

     

    Please suggest, How can I assign licenses at vCenter level.

     

    Thanks in advance!!

     

    Kind regards,

    Kishan Pant

     

    Expand Post

    1 of 2
    • Detlev Eufinger (Flexera Software)

      Hi Kishan,

       

      You need a new level in the DataCenter and Cluster.

      Like this one:

       

      vCenter

      |_DataCenter or Cluster

      |_Host

      |_Host

      |_virtual machine

       

      Unfortunately, this is currently not possible. Please create an idea if you don't already have it.

      Expand Post

    • If the app is showing that it's covered by a license added to snow you can go to list all licenses and search for the license, one of the fields is agreement... the agreement name will be there.

End of Feed
8 Chatter Feed Items
ALL CONVERSATIONS
UNSOLVED
ARTICLES
93 Posts
Loading
License | Flexera