Following on from the ArcGIS Pro licensing registry setting post https://community.esri.com/t5/arcgis-pro-questions/regedit-values-to-start-up-arcgis-pro-as-named/m-...
For an AVD ArcGIS Pro user (multi-user pooled host pool with FSLogix) - I get that registry entries can be set to define default licensing settings (license type, level, server etc.) from registry settings at the HKLM level.
Is there a method to lock and prevent the user from ever changing these defaults?
I am thinking something like locking the HKLM with GPO/ACL etc, which I guess is FSLogix config?
I am cautious that doing so would cause a crashout if the user were to go into the licensing options in the Pro GUI - or would it just be greyed-out?
Any experience of implementing this, tips, tricks, ideas, all welcome.
thanks for reading.
Solved! Go to Solution.
Under HKEY_LOCAL_MACHINE\SOFTWARE\ESRI\ArcGISPro\Licensing you can create a key named LOCK_AUTH_SETTINGS = True. When set only local admins on the computer can update the license connection settings.
Users who do not have permissions to update registry settings will see 'grayed' out information in the GUI.
Under HKEY_LOCAL_MACHINE\SOFTWARE\ESRI\ArcGISPro\Licensing you can create a key named LOCK_AUTH_SETTINGS = True. When set only local admins on the computer can update the license connection settings.
Users who do not have permissions to update registry settings will see 'grayed' out information in the GUI.
Thanks Richard, I even read https://support.esri.com/en-us/knowledge-base/how-to-lock-licensing-options-in-arcgis-pro-000026114 and missed it..
Will have a test of this. You don't perhaps know if the ability to select extensions is then disabled do you? This would be least preferable..
Cheers pal.
LOCK_AUTH_SETTINGS = True applies to extensions as well. That being said, if you have local admin on the computer one can always change LOCK_AUTH_SETTINGS to false to regain access to turn on/off extensions.
One thing we do is take advantage of where I work is HKEY_LOCAL_USER, this contains copies of most of the HKLM keys that can be set per user. HKLU takes precedents over HKLM. For example, under HKEY_LOCAL_MACHINE\SOFTWARE\ESRI\ArcGISPro\Licensing\Extensions users can enable or disable extensions. In the .\Extensions keys the names are the feature names.
The extensions information described here is for concurrent use and single use licenses. Named User licensing should be picking up the Extensions settings from the individuals ArcGIS Online subscription.
Much appreciated Richard. Will see how it pans out.