Latest Contributions by AmnoyAm

Also worth noting, the license manager does not need to reside on the same network as Portal.  You can have Portal living in Azure and have the license manager on your local network.  They do not communicate with each other.  ArcGIS Pro calls out to the Portal machine through the URL address.  It than makes a separate call to the license manager through TCP/IP.  If the license manager resides on the same network as the Pro machine, there's no firewall to configure for.  Also you don't need to deal with Azure's internal/public name.  Just worth mentioning if this is an option for you.   ... View more

Just got back from vacation and saw your post.  I wasn't sure if you got this resolved.  Looks like you got everything installed and licensed correctly.  It's the communication that is the issue.  When configured, Pro will call to the portal's public FQDN.  If successful, it will display the portal's login prompt.  You then log in with a user with an assigned Pro Named User license.  Portal verifies the username and the license assigned.  It then tells Pro to go to the specified license manager for the Named User license.  This is where you're running into the issue.  Pro is not able to connect to the license license manager.  Either the named provided is not reachable publicly or the ports used by the license manager are blocked.  The following are things to consider in this configuration: 1.  The client machine where Pro was installed communicate with the license manager using TCP/IP protocol.  Whereas the call to the Portal uses https.   2.  Configure the license manager to work through a firewall.  This involves locking down the ports and opening those ports through the firewall.  Keep in mind, there are multiple firewalls to consider, the OS built-in firewall, Azure's firewall and your network firewall.  The following document provides more detail on the subject and a step-by-step process:  https://desktop.arcgis.com/en/license-manager/latest/configure-the-arcgis-license-manager-to-work-through-a-firewall.htm 3.  Verify the license manager host name is reachable from the Pro machine.  I assume you are using the public FQDN or IP Address.  Go to your portal admin/License/Update License Manager.  For the hostname, provide the public FQDN or IP Address.   Hope that helps.   ... View more

If you haven't done so already, the following documents provide the steps to download and authorize Concurrent Use Pro licenses.   https://pro.arcgis.com/en/pro-app/latest/get-started/authorize-arcgis-pro-with-concurrent-use-licenses.htm   ... View more

As Jerry pointed out, the user must be assigned an add-on Drone2Map license or a user type that includes a Drone2Map license.  In addition, Drone2Map will make a call to the license manager hosting a Drone2Map license.  The communication between the two system used TCP/IP protocal through two specific ports, 27000 and another open port.  If there is a firewall between the system, you must open these ports through the firewall.  Below is a doc on how to configure the license manager through a firewall.  The same rule applies to Concurrent Use and Named User with ArcGIS Enterprise.  The error you mentioned refers to a failed attempt to connect to the license manager hosting the Drone2Map Named User license.     https://desktop.arcgis.com/en/license-manager/latest/configure-the-arcgis-license-manager-to-work-through-a-firewall.htm ... View more

I suggest creating a new local user.  Use the Runs As option and start Pro as the new user.  The first time may take a while because its build the profile for that user.  After that it should start faster.   You can also log in the system with the new account and start Pro.  If you cannot reproduce the issue, it's likely something stored in your profile.  If that is the case, there are certain things in your profile or registry you can edit. See if you can reproduce the issue with a new user first.   ... View more

You're on the right track.  Here's what you basically need to do: 1.  Tie down the two ports used by the license manager.  2.  Open those two ports through the operating system's firewall or disable the firewall altogether.   3.  Open the two ports through the Azure security network. 4.  Open the two ports through the network where Pro is installed.   5.  Open the two ports through the firewall on the operating system hosting ArcGIS Pro.   As you can see, there are multiple firewalls involved in a typical configuration.  If possible, I disable the Windows Defender on the Windows machine hosting the license manager and the client application, ArcGIS Pro.  Also allow all machine access to the Azure network through those two ports.  It's just to simplify the process.  Once confirm Pro can access the license manager in Azure, you can always go back and tighten your security.  Of course you will need to contact your network administrator to open the ports through your network if Pro is on a machine in a specific local network.   It's not the step-by-step you're looking for but overview of the process.  Hope that helps. ... View more

It sounds like you have an older version of ArcGIS Pro and want to update it to the version it to the version that has the function or capability you need.  Furthermore, you are likely using a Concurrent Use licensing option if you are asking about the license manager.  If you start ArcGIS Pro, go to the "Settings" button and then to the Licensing tab.  It will display what licensing option you are using.  If you're still not sure, click on the "Configure your licensing options" button to get to the Configure Authorization dialogue.  The License Type determines what licensing option you are configured with.   Concerning your original question, the license manager version does not matter if the capability you need is not available in that particular version of ArcGIS Pro.  In your situation, determine the version of ArcGIS Pro you want to install.  From there, you can determine the minimum version of the license manager you will need.  If possible, always upgrade to the latest available version of the license manager because it is always backward compatible.  If you cannot do so and can only install a specific version, the table below should help.  It list the version of ArcGIS Pro and the corresponding License Manager version.   Pro Version License Manager 2.9 2021.1 2.8 2021 2.7 2020.1 2.6 2020 2.5 2019.2 2.4 2019   ... View more

As you have pointed out, the Single Use license captures characteristics of the system's hardware and software configuration.  We used the term, "anchors".  If one or more of the "anchors" change, the license becomes invalid.  This is necessary to prevent users from creating multiple vm's from an existing image with a single license.  It also prevents users from copying it to other systems.  This is one of many reasons.  With that said, the Single Use licensing option is not for you based on your issues of changing components in your environment.   The Named User licensing option is the best option for such an environment if you are using ArcGIS Pro.  For ArcGIS Desktop, you may want to consider using the Concurrent Use licensing option.  In such a case, the licenses are hosted on a license manager installed on a machine in the network.  ArcGIS Desktop will need to point to the license manager for the licenses.   Hope that helps.   ... View more

@rauwaeCINBELL @SailiTang1    Just came across your post.  I'm glad you were able to figure out your licensing situation.  I noticed you mentioned the license manager log file displaying error message,  'UNSUPPORTED: indexserver'.  This is a bug with the software.  It does not affect the license manager or ArcGIS Pro.  It's only inconvenience is that is create unnecessary entries in the file, causing it to grow over time.  We just provided a fix for this issue in the next release of ArcGIS Pro 2.9.     ... View more

There are advantages and disadvantages to each licensing type.  The main advantage of concurrent use (CU)-single point of managing licenses, 1 license can be use by multiple users (one at a time).  Users can select/deselect core and extension licenses.   Disadvantage-once a license is consumed, no one can start the application without additional licenses.  Must be on the same network as the license manager.   Main advantage of named user (NU)-user will always have a license assigned.  User can use Pro on up to 3 machines at the same time.  Only requires Internet access when using NU license through AGOL.   The main disadvantage of the named user licensing option is that the organization must have equal or more licenses than users assigned.   In your situation, I don't see much benefit to retaining a named user license.  You have to maintain the license manager for concurrent use and the licensing portal for named user.  It make sense to convert them all to concurrent use.  From a user's perspective, there is no difference in functionality.  The user can use the tool if licenses with wither concurrent or named user licenses.   ... View more

It's safe to say the issue is not with ArcGIS Enterprise.  It's specific to the license manager.  The service thinks the host ID doesn't match the one defined in the license file, but that is not the case, the host ID listed in the log is identical to the one in the license file.  That is odd and the first time I've heard about it.   You mentioned about upgrading the license manager.  What version of the license manager did you had installed and what version did you upgrade to?  While we're asking, what is the Portal for ArcGIS version? ... View more