Latest Contributions by JeffSmith

Matthew, Assuming you are using Server v10.1 or later, the command line column in the Windows Task Manager or Process Explorer are the easiest ways.  If you are using an earlier version, you will have to scour the logs and manually match them. ... View more

Jostein, Yes, this can be done but requires the use of the 'keytool' command or a 3rd-party utility like 'Keystore Explorer' to access and export both the public and private keys for the SSL certificate.  It is not a straight-forward process and you would need to get into the Server framework to find the correct files.  I would recommend contacting Esri Technical Support for assistance with this. ... View more

When Pro is launched, there are several things that occur for it to check out the licenses.  When Pro first opens, it communicates with Portal over the web adaptor url.  This displays the login page.  After you sign on, Portal validates that the user has licenses and sends back to Pro the hostname and port number for it to use to communicate directly with the License Manager.  I suspect this is where the failure is occurring for you.  To see what hostname is being returned, you can login to your Portal Admin directory and access https://portal.domain.com:7443/arcgis/portaladmin/system/licenses.  License Manager info will show both the hostname and port.  By default this is just a hostname.  This can be changed to a fqdn if needed.  You mentioned that your Portal server does not have a public DNS entry.  If that is the case, Pro will need to be behind your firewall when it is initially opened.  Pro needs to communicate directly with the server where the License Manager is installed to check out the licenses.  Once they are checked out, you have the option to borrow them (or work offline) for a period of time without needing to communicate with the License Manager. More information on that can be found here: Review ArcGIS Pro licensing information—ArcGIS Pro | ArcGIS for Professionals Sorry for the long reply.  Hope that helps. ... View more

Hi Mody, Yes, accessing the license manager is unique to portal.  AGOL does not use the same license manager. ... View more

Jay, Yes, when Pro opens, it first communicates with Portal to retrieve licensing information.  This is done over the web adaptor url.  It then needs to communicate directly with the License Manager to check-out the licenses.  This is done by default over port 27000.  In your case, since your License Manager is installed on your portal machine, you should just need to open port 27000 in your firewall to allow Pro to open and run successfully. ... View more

No, in 10.3 it will be the same as how you are seeing it in 10.2.2.  The protocol defined in the WebContextUrl is not used.  In other words, if your F5 load balancer is doing SSL offloading, the Login url you see on the Rest page will be HTTP, not HTTPS.  If you configure the F5 load balancer to redirect to the web adaptor over HTTPS, the Login url on the Rest page will be HTTPS. I want to make a correction from my last post.  The 'X-Forwarded-Host' header used from your F5 load balancer just needs to be the fqdn, not fqdn/webadaptor.  ... View more

Jason, the information you have heard from Support is accurate: the SSL offloading is not supported. Regarding the WebContextUrl, I'm not sure what version of ArcGIS Server and Web Adaptor you are using but in version 10.3, you shouldn't need it.  If the X-Forwarded-Host header is included from the F5 load balancer to the web adaptor, the fqdn for the Login url should match that header.  The format of the header should be fqdn/webadaptor (ex server.esri.com/arcgis).  The WebContextUrl is only necessary if you remove the web adaptor and redirect directly to the Server from the F5 load balancer. ... View more

The ability to integrate Portal for ArcGIS with enterprise groups (Active Directory or LDAP) is a new feature that is being introduced in 10.3.  This will allow you to link your Portal groups to Active Directory groups and maintain the group membership through Active Directory alone. In 10.2, 10.2.1, and 10.2.2, you can add users from Active Directory but there is not a way to link to the groups. ... View more

The issue you are seeing when linking a reverse proxy to a web adaptor to ArcGIS Server is a known limitation when the context name is different between the reverse proxy and the web adaptor.  As you have already mentioned, the webContextUrl parameter for ArcGIS Server is only applied when there is no web adaptor in the configuration.  The two solutions I can think of are ones you have already described. 1. Remove the web adaptor from the configuration and specify the external url in the webContextUrl parameters in the ArcGIS Server Admin API.  This matches this configuration: Clients - Reverse Proxy 1 - Reverse Proxy 2 - ArcGIS Server. 2. Install a second web adaptor called 'accesspoint' and configure your reverse proxy to redirect to the 'accesspoint' web adaptor url to access ArcGIS Server.  You can leave the 'arcgis' web adaptor in place if you'd like or uninstall it.  It won't impact ArcGIS Server having multiple web adaptors. Hopefully one of those will work for you. ... View more

Rick, Since you are defining the TNS_ADMIN variable to refer to the folder where you tnsnames.ora file resides, I assume you are using the full Oracle clients.  I would double-check to make sure the 'arcgis' user account has access to that file.  This may be difficult or impossible if the tnsnames.ora file is in a folder accessed via a UNC path and the 'arcgis' user is a local account.  If this is the case, you might have to store a copy of the tnsnames file locally or change the 'arcgis' user to be a domain account. A good way to test this is to open the command prompt as the 'arcgis' user and try to use sqlplus to connect to your Oracle database.  This should confirm if the arcgis user has access to the tnsnames.ora file. ... View more