Latest Contributions by DavidHoy

maybe Dan's solution could be achieved by first publishing your three "secret" layers as a map service in AGOL /Enterprise, then add this service to your Project before saving as PDF ... View more

Hi Mohammed, The questions the others are asking are likely relevant in certain circumstances, but can you first fully explain what you are trying to do? Are you attempting to register an Enterprise Geodatabase (e.g. SQL Server, Oracle, PostgreSQL) as a data store in your Portal? or are you trying to register/validate ArcGIS Relational Data Store associated with your ArcGIS Hosting Server? ... View more

@DougSims_GT  Did installing updated web adaptor solve your problem?  If yes could you please mark this as solved?   ... View more

Hi Joe I have personal experience where we have been able to route to https://portal.domain.com/portal/home without a web adaptor, but only within Azure using Azure Gateway, in AWS using ALB we cant do it because you need a URL rewrite functionality that AWS ALB does not provide. ... View more

@Jay_Gregory Did you get a resolution? Which way did your organisation choose to go? ... View more

The simplest solution may be to just use the "Measure" tool This will snap to existing features - and you can set the units as you desire. Another option you may be able to use is the Point Distance tool https://desktop.arcgis.com/en/arcmap/latest/tools/analysis-toolbox/point-distance.htm     Of course, these both only provide the 2D distance. ... View more

Hi William yes - the upgraded site needs its Web Adaptors to be upgraded as well. This actually means uninstall existing and install/configure new. You can get the WA installer from MyEsri You should also install the latest Patch for Web Adaptor before reconfiguring with the portal and server (this does not show up with the patchfinder tool or auto patching )  You can get it from https://support.esri.com/en/Products/Enterprise/arcgis-web-adaptor/arcgis-web-adaptor-iis/10-8-1#downloads?id=7855  ... View more

Sorry, I did miss that you were talking only about the internal Load Balancer. Well - you could - as you say (and as the Esri diagram shows) use :7443/:6443 as incoming for the internal LB, but, as your IT group are not keen on that - you could instead use the strategy I suggested - as you have F5 that is capable of url rewrite, direct requests coming in on gisadmin.organisation.com/portal to the portal servers on :7443 and  for gisadmin.organisation.com/server to the server site machines on :6443 you will need to set up the Health Checks for these as Noah's article suggests ... View more

Hi, are you locked in to the idea you want to direct traffic by using the ports? This would mean you need to allow incoming requests in F5 on :6443 and :7443, I am not surprised your Security team are unwilling - this would definitely not be a recommended practise in any site facing the public web. If it is a new site and you have not yet locked in to using those paths, then With F5, you could setup forwarding/rewrite rules that sent any requests for https://gis.company.com/portal  to portalmachine1:7443/arcgis & portalmachine2:7443/arcgis and requests for https://gis.company.com/server to agsmachine1:6443/arcgis & agsmachine2:6443/arcgis The WebContextURL for the Portal and the Server would need to be set to gis.company.com. You could choose to have just the one load balancer in the DMZ and use its public address for the federation privatePortalURL and ServerAdminURL and allow users and machines to communicate via this path. or use an internal load balancer for the federation admin URLs that has the same targets, but uses admingis.company.com as incoming URL  To have this work to allow administrative tasks (including re-publishing or updating an existing service) to be performed from client machines in your network, the admingis.company.com address would need to be resolvable from your client desktops as well as from the servers in your data centre. If you are however stuck with using the /arcgis paths It is possible to setup a list of addresses to look for to be routed to the  :7443 portal targets (e.g. /arcgis/home, /arcgis/portaladmin, /arcgis/sharing) and :6443 server targets (everything else) I hope this has not been too convoluted ... View more

Hi Jay, are you sure it is CIFS ? That's a pretty old protocol name (see https://www.varonis.com/blog/cifs-vs-smb/ and https://blog.fosketts.net/2012/02/16/cifs-smb/) Are you actually meaning SMB? or SAMBA  publishing a Linux share as SMB? SMB v1 (CIFS) is generally not recommended - but in a pinch, you can use it provided you disable OpLocks as this causes many issues with Service Publishing If using SMB2 or SMB3 - the conservative recommendation is to set Leasing Mode to "None" and Caching Here is a link to a Microsoft page providing a Powershell command to do this https://docs.microsoft.com/en-us/powershell/module/smbshare/set-smbshare?view=win10-ps ... View more

Hi William, Is your Portal security set to use Web Tier Authentication ? If yes, the upgrade process may have lost that when it reinstalled the Web Adaptor. When you go via port :7443, you are bypassing the Web Adaptor. As you can login by that route, it means the Portal Site Administrator account is still working OK. When you say you can login to the Server Manager - do you go via the Web Adaptor ? https://<yoursite.domain.com>/server/manager   - or direct to the ArcGIS Server?  https://<yoursite.domain.com>:6443/arcgis/manager  ... View more