About greg_m

greg_m · ‎Oct 24, 2019

re. the license keys - you can enter these on the license record, but take due care as you won't want everyone with FNMS access to be able to see this information. You can possibly lock this down using role permissions. There is no bulk upload capacity OOTB, but you can probably do this via a business adaptor.

greg_m · ‎Oct 24, 2019

I would import PO records including SKUs if available and then from the "Unprocessed purchases" view, use the processing wizard to create license records. If you have a recognised SKU, the SKU library and PURL will do all the 'heavy lifting' for you and configure the license use rights accordingly. I do however recommend that you review the configuration after processing to ensure that these settings align with what you expect or update special terms have been negotiated bespoke to your organisation.

greg_m · ‎Oct 10, 2019

Hi, Where is a resolution to this bug currently at? I see this relates to release 2016 on-prem. I have noted this is still an issue in 2019R1 on -prem. Any feedback would be great.

greg_m · ‎Sep 01, 2019

Thanks for the response Robert

greg_m · ‎Aug 29, 2019

Hi, I was wondering what approaches others are adopting re. the configuration and consumption of Visual Studio / MSDN in FNMS? One approach is to allocate a user (with a Visual Studio / MSDN entitlement assigned) to a non-prod system as an assigned user and use this to drive consumption of the named user license. My concern with this approach is that it is static and doesn't accommodate for any adds/moves/changes and will need constant maintenance which is not always practical in larger organisations. I am wondering what other approaches others are adopting? TIA.

greg_m · ‎Jun 19, 2019

Hi Kathy, Licenses aren't restricted on the "Ownership" tab. This is done on the "Restrictions" tab. Is there any chance that there has been restrictions applied to the Enterprise groups?

greg_m · ‎May 22, 2019

Are you seeing any PO records created successfully? When using the MLS import, FNMS will import the values based on the "All Countries" numbers from the pivot data worksheet. It will not import granular amounts for the US or Canada. If this is what you are wanting to achieve, you might be best to use the standard PO template import. That way you can select the location and respective entitlement qty's.

greg_m · ‎Apr 28, 2019

In addition to this, as they are PVU licenses, you are most likely seeing a historical peak consumption. After you have made the changes, you will need to reset the PVU counts.

greg_m · ‎Apr 28, 2019

From what you have described, the Windows Server Std license is consuming based on cores not processors. If this is the case, the behaviour that you are seeing is correct as you will need to consume the 16 core min per host. The Datacenter license (I am assuming is also core based) should consume (x16) core licenses also. Have you configured the license type correctly? ie. Microsoft Server / Management Core license type and checked to the use rights and rules settings to ensure that the default value of (x16) core per host core limit has been applied?

Online Status	Offline
Date Last Visited	‎Jun 11, 2021 12:17 AM

Re: Creating License Records

Re: Creating License Records

Re: When Cloning a View/Report the Filters Are Lost

Re: Visual Studio / MSDN configuration

Visual Studio / MSDN configuration

Re: Unlicensed installations

Re: Microsoft License Statement (MLS) for specific country.

Re: IBM License Consumption

Re: Microsoft DataCenter Server license calculation vs. Standard in FNMS

Re: Creating License Records

Re: Creating License Records

Re: When Cloning a View/Report the Filters Are Lost

Re: Visual Studio / MSDN configuration

Visual Studio / MSDN configuration

Re: Unlicensed installations

Re: Microsoft License Statement (MLS) for specific country.

Re: IBM License Consumption

Re: Microsoft DataCenter Server license calculation vs. Standard in FNMS