Storage of Licensing Settings for ArcGIS Pro

[RichardDaniels]

Anyone know where the licensing settings for ArcGIS Pro are stored? They do not appear to be in the Registry or in the  c:\users\all users\ESRI or c:\users\all users\Application data area. They are not under C:\Users\Default either.

We are looking into deploying the software to a larger number users and need to be able to define the license preferences in the install package or by script after the software is installed (i.e., license server name and license type (basic, standard, advanced)).

Ideas are welcome.

Rich

[DanPatterson_Retired]

at least one registry key is mentioned here

Set up ArcGIS Pro—ArcGIS Pro | ArcGIS for Desktop

and the setup section talks about the license setup

Set up ArcGIS Pro—ArcGIS Pro | ArcGIS for Desktop

then the administration section is here

ArcGIS Pro installation administration—ArcGIS Pro | ArcGIS for Desktop

or are you referring to something else?

[RichardDaniels]

Thank you for your response.

None of these help documents describe how to define the license information for your application as part of an installation (i.e., they all require user interaction to enter the licensing information). The problem is ESR has failed to realize (again) that they have customers with 100's if not 1000's of installations and that the licensing step has to be automated to enable enterprise deployments of their software.

What I'm looking for is the physical location/file that the licensing information for ArcGIS Pro is stored at. If we find it, then we could copy/deploy it with the application.

For example, In Desktop this information is found at HKLM\Software\WOS6432Node\ESRI\License10.3 or \License10.4 and several of the settings can actually be set within the desktop install package itself (i.e., the MSI).

[DanPatterson_Retired]

oh...I just thought something like the uninstall registry might get one close to the registry area at least

The product code for ArcGIS Pro is found in the registry at either HKEY_LOCAL_MACHINE\SOFTWARE\Esri\ArcGISPro (for a per-machine install), or HKEY_CURRENT_USER\SOFTWARE\Esri\ArcGISPro (for a per-user install), in the string value ProductCode.

[RichardDaniels]

Hello,

Though not the "machine wide" solution like I'm looking for, I did find a set of registry keys that will work for per-user installations.

By running this registry update after the software is installed the end user can avoid having to manually entering ArcGIS Pro's licensing information.Note - this example shows a "Standard" license level, other options are BASIC and ADVANCED.

I'm still open to better ideas

Rich

[MarkStorrings]

I'm not sure if you have found this (the thread is a couple of years old), but I was hunting for a resolution for the same problem and came across this thread.  In ArcGIS Pro 2.3, the following registry setting will set extensions active without requiring the user to access the "Licensing" option in the Project menu. 

HKEY_CURRENT_USER\Software\ESRI\ArcGISPro\Licensing\Extensions

[DanielUrbach]

Richard,
This might be what you are looking for:
Install options—ArcGIS Pro | ArcGIS Desktop 

-Danny

[JTessier]

@ThomasEdghill any love for this original question available?

[RichardDaniels]

We have built a C# application we have named ArcGIS Pro License Manager that allows the user to select their license level and extensions, these are saved just prior to ArcGIS Pro being launched. This allows 'non' administrators on their local machine to change their license levels and extensions on the fly. *This is something that ESRI should add to their application. 

[ToddAGrissom]

Assuming you are looking at an "each user may have different license settings" type install, the individual user settings will be available at

<MACHINE NAME>\HKEY_USERS\<USER SID>\SOFTWARE\ESRI\ArcGISPro\Licensing

I know someone previously posted "Current User", which is correct, if the user you are trying to modify is indeed the user making the changes, otherwise you are going to have to look up the user's SID in AD or Powershell - 

Import-Module ActiveDirectory
$User = Read-Host -Prompt 'Input the user name'
Get-ADUser -Identity $User

But for sheer elegance I like @RichardDaniels front end app and think that Esri should have incorporated the same type application in their deployment.  I also think that they should have returned FlexLM licensing errors more elegantly than just looping the licensing panel back up when there is an error - whether it's max exceeded, user not on include list, or another error - even the raw return provided in Desktop is far better than "Nope, try again".